Skip to content

Fous楽天市場 RMS

Get your 楽天市場 RMS orders and figures through an API

Read your R-Backoffice orders by status and your R-Karte sales, access and conversion figures with one API call each. A workflow can check 注文確認待ち each morning and email you the weekly 店舗カルテ numbers every Monday.

Works with your own 楽天市場 RMS account. Fous is an independent product.

What you can build on RMS

  • Get orders by status

    Build this

    Reads 新規受注一覧 (new orders list) under 受注・決済管理 (order and payment management) for one status, such as 注文確認待ち (awaiting confirmation) or 発送待ち (awaiting shipment).

    Takes
    Status, ordered since (optional)
    Returns
    Order number, order date, status, items, quantity, total
  • Read the 店舗カルテ figures

    Build this

    Reads 店舗カルテ (shop report) in R-Karte for a date range: 売上 (sales), アクセス人数 (visitors), 転換率 (conversion rate) and 客単価 (average order value).

    Takes
    Start date, end date
    Returns
    Date, sales, visitors, conversion rate, average order value
  • Get search keywords for an item

    Build this

    Reads 商品別検索キーワード (search keywords by item) in R-Karte for one item: the keywords shoppers used to reach it.

    Takes
    Item number, start date, end date
    Returns
    Keyword, and the access and sales figures R-Karte shows for it
  • Enter the shipping date and tracking number

    Build this

    Opens one order in 発送待ち in R-Backoffice and enters its 発送日 (shipping date) and お荷物伝票番号 (tracking number).

    Takes
    Order number, shipping date, carrier, tracking number
    Returns
    Order number, status, shipping date, tracking number

Automate RMS with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Orders waiting in 注文確認待ち, every morning

    Build this
    Starts
    Every day at 8:00, Asia/Tokyo
    Step 1
    Get the orders in status 注文確認待ち.
    Step 2
    Keep the orders that were not there on the last run.
    Step 3
    Email you the list with order number, order date, items, quantity and total.
  • Weekly 店舗カルテ report

    Build this
    Starts
    Every Monday at 9:00, Asia/Tokyo
    Step 1
    Read 店舗カルテ for the past 14 days.
    Step 2
    Summarize the last seven days' 売上, アクセス人数, 転換率 and 客単価 against the seven days before.
    Step 3
    Email you the summary with the daily figures underneath.
  • Orders in 発送待ち, posted to your warehouse system

    Build this
    Starts
    Every weekday at 14:00, Asia/Tokyo
    Step 1
    Get the orders in status 発送待ち.
    Step 2
    Stop when there are none.
    Step 3
    Post order number, order date, items, quantity and total to your warehouse system's webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get orders by status” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "glogin.rms.rakuten.co.jp/get_orders_by_status",
    "input": {
      "status": "発送待ち",
      "ordered_since": "2026-11-10"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "status": "発送待ち",
    "orders": [
      {
        "order_number": "100001-20261111-0000012345",
        "order_date": "2026-11-11T09:42:00+09:00",
        "status": "発送待ち",
        "items": "Acme 保温タンブラー 500ml",
        "quantity": 2,
        "total": 6380,
        "currency": "JPY"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

RMS’s own options

Rakuten offers RMS WEB SERVICE, an API for shops, documented inside RMS for signed-in shops; each connected system gets its own access setting in RMS. RMS also lists a CSV data download for order and shipping data, and BOSS, an order automation plan from 3,000 yen a month. Analytics such as 店舗カルテ are read in R-Karte.

OptionWhat it coversWhat it takes
RMS WEB SERVICEAPI access to shop data such as orders, for your own code or a connected system. Its documentation is inside RMS.A shop account. Each connected system gets access under WEBAPIサービスアクセス許可設定 in RMS, with a licence key.
CSVデータダウンロードサービス (CSV data download)Order and shipping data from R-Backoffice, for delivery slips, address labels and your own sales system.A service listed among RMS's functions on Rakuten's own page.
BOSS (RMS自動化プラン)Automatic order processing that R-Backoffice does not offer: sorting orders, sending emails and editing orders by condition.From 3,000 yen a month, with a 30-day trial.
RMS by hand新規受注一覧 and the order screens in R-Backoffice, and 店舗カルテ and the other reports in R-Karte.An R-Login or 楽天ビジネスログイン sign-in for each person on the shop.

Read on November 12, 2026: 店舗運営システム「RMS」とは, 受注・決済管理 (R-Backoffice), RMS WEB SERVICE.

Signing in to RMS

RMS has two sign-ins. R-Login takes the shop's R-Login ID and password, then each person's own Rakuten member ID and password; 楽天ビジネスログイン takes a Rakuten ID, password and a code sent to Viber. With Fous you sign in once through RMS's own sign-in with your own account, the login is sealed with AES-256, and with R-Login an expired session is signed back in.

Worth knowing

New orders start in 注文確認待ち
You confirm each order and send the サンクスメール (thank-you mail). Once the customer's payment is complete, the order moves to 発送待ち, where you enter the 発送日 and お荷物伝票番号.
Two keys: the shop's and the person's
R-Login needs the shop's key and a personal key. Every user registers their own Rakuten member account, and a ダブルアカウント (outside contractor) is for editing pages in R-Storefront.
Viber codes last two minutes
On 楽天ビジネスログイン a code is valid for 2 minutes, up to 5 codes per attempt. Trusting a PC skips the code for 14 days, in that browser only.
One licence key per connected system
In RMS each connected system has its own row and key. Integrators' guides say a shop can hold two valid licence keys, so an old one is suspended before a new one is issued.

More in E-commerce: marketplaces and app stores

Other industries: Edexcel Online, Eversource online account, Sligro, BancaNet Empresarial, WEX Online, Virtual Pag-IBIG for Employers.

Frequently asked questions

Yes. RMS WEB SERVICE is Rakuten's API for shops, documented inside RMS, and each connected system gets access and a licence key in RMS. RMS also lists a CSV data download for order and shipping data, and BOSS, an order automation plan from 3,000 yen a month.

In RMS's main menu under 受注・決済管理 > 1 受注・受付管理 > 新規受注一覧. New orders appear in 注文確認待ち, and after payment they move to 発送待ち, where you enter the 発送日 and お荷物伝票番号.

You can build a method that reads 店舗カルテ, with 売上, アクセス人数, 転換率 and 客単価, and run it from a workflow every Monday. The workflow can email you a summary or post the figures to your own system's webhook.

Yes, as a ダブルアカウント in R-Login, which is for editing pages in R-Storefront. Each person needs their own Rakuten member account.

No. Fous is an independent product. You use it with your own RMS account, and a method reads and does only what that account can.

Put 楽天市場 RMS behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextPayPal BusinessTikTok Shop Seller Center千牛卖家中心Edexcel OnlineHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of 楽天市場 RMS (Rakuten Group). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.