Your Rakuten Ichiba orders, inside MurrCloud, across every shop.
MurrCloud connects to Rakuten Ichiba through the RMS Web Service OrderAPI - pulling orders from one or more Rakuten shops, mapping SKUs to real products, and keeping Rakuten metadata attached to every sales order. Built natively for multi-account operations.
Reading time: 6 min | Best for: Rakuten Ichiba sellers, multi-shop operators, cross-border Japan sellers | Setup time: 30-60 minutes per account
Rakuten orders shouldn't require a separate dashboard.
Rakuten Ichiba is the largest marketplace in Japan, and sellers running multiple shops under RMS often end up checking each shop's order panel separately, exporting orders by hand, and matching Rakuten SKUs to internal product codes one line at a time.
That works at low volume. It breaks down once you're running several Rakuten shop accounts and trying to keep inventory, accounting, and fulfillment in sync with everything else in your business.
Each RMS account has its own order panel - there's no unified view without manual exports.
Rakuten SKU values don't automatically align with your internal product catalog.
Order status, fulfillment, and accounting live in different places without a connector tying them together.
One connector. Every Rakuten shop you run.
The Rakuten Connector is built around the RMS Web Service OrderAPI and designed from the ground up for multi-account operations - you can connect as many Rakuten RMS shop accounts as you operate, each with its own credentials and sync settings.
Orders pulled from RMS, with full Rakuten context preserved.
The connector calls the Rakuten RMS OrderAPI to create or update MurrCloud sales orders, and keeps Rakuten-specific metadata attached to each one so nothing gets lost in translation between systems.
| Field stored on sales order | Purpose |
|---|---|
| Rakuten account | Which RMS shop the order came from - essential once you're running multiple accounts. |
| Rakuten order number | The original Rakuten order identifier for cross-referencing in RMS. |
| Rakuten order datetime | The order's original timestamp from Rakuten, independent of import time. |
| Rakuten status | The order's current status as reported by Rakuten. |
| Last seen timestamp | When MurrCloud last confirmed this order's state with RMS. |
Sync runs two ways: manual, triggered from the account form whenever you want an immediate pull, or scheduled, via the Rakuten: sync orders cron job. The connector includes API throttling and retry handling, so rate limits and temporary RMS server errors don't interrupt the sync - they're retried automatically.
Rakuten SKUs mapped to real products - automatically where possible.
Every Rakuten order line carries a SKU value that needs to resolve to an actual MurrCloud product. The connector handles this with a dedicated Product Mappings workflow, accessible under Sales -> Configuration -> Rakuten -> Product Mappings.
When a Rakuten SKU matches a MurrCloud product's internal reference, the mapping is created automatically.
Unknown SKUs get a placeholder mapping so the order line is preserved, even when Rakuten sends no SKU at all.
Unmapped SKUs are flagged for review. Assign the correct product once, and it applies going forward.
Laying the groundwork for two-way Rakuten sync.
The connector adds Rakuten sync status fields to MurrCloud delivery orders, and when shipment tracking is enabled, a completed Rakuten customer delivery is marked pending until the tracking information is confirmed back to Rakuten.
This is the foundation for a future outbound shipment exporter - the data model and status tracking exist today, with the actual outbound API payload to Rakuten RMS planned as a near-term enhancement.
Pulling Rakuten orders into MurrCloud and resolving them to real products is fully implemented and production-ready.
Shipment sync status fields and inventory queue models exist; the outbound Rakuten shipment API payload and inventory export are not yet implemented.
A fully translated workflow for Chinese-speaking operations teams.
Many cross-border sellers running Rakuten Ichiba operate with teams based in China. The connector includes Simplified Chinese translations across menus, forms, buttons, statuses, validation messages, and workflow notifications - not just labels, but the operational messages your team actually reads day to day.
From account record to live order sync.
-
01Go to Sales -> Configuration -> Rakuten -> Accounts Create a new account record, or open an existing one if you're adding credentials.
-
02Enter your RMS credentials License Key, Service Secret, and Shop Code if your setup requires it.
-
03Click Test Connection Confirms RMS connectivity before you commit to syncing live orders.
-
04Enable Sync Orders Optionally enable Confirm Imported Orders if you want imported quotations confirmed automatically.
-
05Click Sync Orders, or wait for the scheduled cron job Either trigger the first sync manually or let the scheduled job pick it up.
-
06Review Product Mappings Assign the correct product to any Rakuten SKU flagged Needs Mapping.
Common issues and what to check.
| Issue | What to check |
|---|---|
| Test Connection fails | License Key and Service Secret are both set. Rakuten RMS has whitelisted the server IP. The server can resolve and connect to the Rakuten RMS API endpoint. RMS API permissions include OrderAPI access. |
| Orders don't sync | Sync Orders is enabled on the account. The account has valid RMS credentials. The last-sync timestamp is set far enough back to include the orders you expect. The scheduled sync cron job is active. Server logs for RMS network, authentication, or rate limit errors. |
| Product shows as unmapped | Go to Rakuten -> Product Mappings, open the SKU marked Needs Mapping, select the correct product, and click Apply Mapping. |
See your Rakuten orders inside MurrCloud.
Book a 30-minute walkthrough and we'll connect a live Rakuten RMS account during the call.
Book a Demo Explore Solutions