A furniture brand selling into Japan, run from China on MurrCloud
A furniture and home-goods company operates from China and sells to customers in Japan through Rakuten. MurrCloud connects the marketplace, Japanese carriers, warehouses, invoicing and after-sales in one bilingual Chinese–Japanese system, so the team can serve Japan without a local IT department.
Customers in Japan, team in China, rules from both.
Rakuten orders and payments must sync exactly. Each Japanese carrier has its own file format and rules. Most products ship as multi-box sets, invoicing follows Japanese accounting, and after-sales cases cross several teams.
A marketplace that can't drift
Orders, payments, cancellations and shipping status must match Rakuten exactly: no duplicates, no missed updates.
Carriers with their own rules
Sagawa and Yamato each need their own export format, delivery time slots, package counts and remote-area surcharges.
Sets, not single SKUs
A sofa or bed ships as several boxes. Components, counts and names have to be right on every shipment.
From Rakuten order to settled invoice, without re-keying.
Orders flow in from Rakuten, ship from Japanese warehouses through local carriers, and close with an invoice matched to the payment.
Order and payment sync
Orders, payments and cancellations imported automatically, with retries and duplicate protection.
Prepared, packed, shipped
Batch picking exports, set components expanded, carrier files for Sagawa or Yamato.
Invoiced on shipment
Invoice dated by shipment; the prepayment is matched automatically.
Every order moves through the same states: imported → confirmed → prepared → shipped → invoiced → matched. Payment and shipping are checked independently, and exceptions land on a list instead of in someone's inbox.
No duplicates
A retry never creates a second order, shipment or invoice.
Stock moves on shipment
Inventory isn't deducted, and Rakuten isn't notified, until shipment is confirmed.
People approve refunds
Refunds, postings and outbound messages keep a human approval.
Bilingual by design
Staff work in Chinese; customers and carriers see Japanese.
Japan-ready modules on one operating platform.
Standard MurrCloud apps cover sales, inventory, accounting, helpdesk and the knowledge base. Custom modules add Rakuten, Japanese carriers, sets and after-sales.
Orders, payments, status
Two-way sync with retries, duplicate protection, exception lists and Japanese messaging.
Sagawa and Yamato
Carrier export templates, delivery time slots, multi-package shipments and remote-area surcharge rules.
One record per set
Japanese categories, SKU-to-component mapping and Rakuten listing maps, with missing-data checks.
Batch picking and hand-off
Filter by date, carrier and status; multi-batch exports that can't be handed off twice.
Invoice on shipment
Japanese accounting localisation; prepayments matched to receivables automatically.
Seven case types
From replacement parts to refunds and exchanges, each with its own steps and evidence.
Tickets and guides
Service tickets with response targets; Chinese operating guides kept in the knowledge base.
Briefings now, drafts next
Scheduled business briefings are live; reply drafts, exception explanations and bill review follow.
Daily backups, tested restores
Two-factor sign-in, daily database and file backups, quarterly isolated restore drills.
Seven ways a delivery can go wrong, each with its own path.
After-sales is a workflow, not a mailbox. Every case type has its own steps, evidence and approvals, and links back to the original order.
After-sales case types
- Replace a part or the whole itemWarranty registration carried over; returned goods tracked
- Missing partsReshipment linked to the original order and set
- Return & refund, partial refundReturn evidence and approval before any money moves
- Wrong item, customer exchangeReturn and resend handled as one case, closed with the customer
Running in production, order by order.
Cumulative records from the live system. Second-route shipping and full accounting are still in acceptance.
Cumulative records from a production snapshot on 29 October 2026; may include historical imports.
Live core, acceptance underway, intelligence next.
The everyday order-to-cash path is running. The remaining work closes the loop on logistics, after-sales and the books.
Core order-to-cash
- Rakuten order and payment sync
- First shipping route and product sets
- Automatic invoicing and matching
Close the loops
- Second carrier route with return files
- Warehouse hand-off in daily use
- Seven after-sales flows end to end
Books and intelligence
- Full accounting and a controlled month-end
- Dashboard of up to 10 key metrics
- Three AI assistants, each tested on 50+ anonymised samples
What this project proves MurrCloud can run.
The same building blocks fit any brand selling into a market with its own platforms, carriers and rules.
Marketplace integration
Reliable two-way sync with retries, duplicate protection and exception handling.
Local carrier logistics
Carrier-specific files, time slots, multi-package shipments and surcharges.
Sets & bundles
Multi-box products expanded into components on every order and shipment.
Localised finance
Country accounting, invoicing on shipment and automatic payment matching.
Structured after-sales
Case types with their own steps, evidence and approvals.
Bilingual operations
One system, the team's language inside and the customer's language outside.
Selling into a market your systems weren't built for?
Cross-border brands, marketplace sellers and overseas teams: MurrCloud builds the operating platform and the finance behind it.