
Ecommerce
Shopify
Connect Shopify and Shopify Plus to your ERP, 3PL, marketplaces and CRM with Patchworks, Shopify’s only certified technology partner for integrations.
Patchworks connects Microsoft Dynamics 365 Business Central to Rithum, so retailer drop-ship orders from Rithum’s Dsco and OrderStream platforms arrive in Business Central as sales orders, and acknowledgements, shipments, invoices and inventory go back automatically.
Part of our Business Central integration range, on the integration platform (iPaaS) trusted by 1,700+ brands.
Supporting complex retail operations across fast-growing brands
















































| Item |
|
|---|---|
| What it is |
An integration between Business Central and Rithum’s supplier drop-ship platforms, built and run on Patchworks
|
| Who it’s for |
Brands and suppliers running Business Central that fulfil retailer drop-ship orders through Rithum
|
| Business Central connection |
Prebuilt Business Central connector (API v2.0, OAuth 2.0 through a Microsoft Entra ID app registration), for Business Central online
|
| How Rithum connects |
Rithum’s supplier API, or file exchange over SFTP (including EDI documents), whichever your retailer programme uses
|
| Flows |
Orders in; acknowledgements, shipments, invoices and inventory out; catalogue updates and returns configurable
|
| Triggers |
Scheduled collection of new Rithum orders, plus event-driven flows from Business Central
|
| Testing |
Staging in Patchworks, plus Rithum’s own validation before your retailer approves go-live
|
| Extend and manage with AI |
AI Studio builds flows from a prompt, AI Agents explain failed runs, and the MCP Server connects AI tools to your integration
|
| Security / pricing |
SOC 2 and ISO 27001 / connected systems plus monthly operations, with unlimited users
|
New retailer orders are collected from Rithum on a schedule you set and land in Business Central as sales orders. Acknowledgements and tracking go back without re-keying, helping you meet the deadlines retailers measure suppliers against.
Business Central publishes available inventory to Rithum, so retailers only sell what you can ship, and your own channels draw on the same stock.
Posted sales invoices are sent to Rithum against the original retailer order, so finance stops copying invoices into the supplier portal.
| Flow |
Direction
|
What happens in the system |
|---|---|---|
| Orders → sales orders |
Rithum → Business Central
|
Each retailer drop-ship order becomes a sales order, with the retailer’s PO number, the consumer’s ship-to address and mapped items
|
| Acknowledgements and cancellations |
Business Central → Rithum
|
Accepted orders are acknowledged, and lines you can’t fulfil are cancelled with a reason
|
| Shipments and tracking |
Business Central → Rithum
|
Posted shipments send the carrier, service and tracking number to the retailer’s order, including partial shipments
|
| Invoices |
Business Central → Rithum
|
Posted sales invoices are sent against the original retailer order
|
| Inventory |
Business Central → Rithum
|
Available quantities are published on a schedule, from one or more locations
|
| Catalogue and cost (configurable) |
Business Central → Rithum
|
Item details and cost updates for retailer catalogues
|
| Returns (configurable) |
Rithum → Business Central
|
Retailer returns create return orders or credit memos
|
Connect Business Central online with the prebuilt Patchworks connector, authorised through a Microsoft Entra ID app registration.
Add your Rithum supplier API credentials or SFTP account, whichever your retailer programme uses. AI Studio’s Implementation Agent can build the Rithum connector and flows from Rithum’s API specification.
Map retailer SKUs to Business Central items, ship methods and locations using cross-reference lookups, then test the full order cycle in staging. Rithum also provides a staging environment for its API.
Rithum checks that messages flow correctly in both directions before your retailer approves production. From then on, run logs, alerts and AI Agents keep watch.
|
Supplier portal
|
Standalone EDI service | Patchworks | |
|---|---|---|---|
| How orders reach Business Central |
Keyed in by hand
|
Translated EDI documents
|
API or files, mapped into sales orders
|
| Other channels |
Managed separately
|
Usually separate tools
|
Shopify, 3PLs and marketplaces on the same platform
|
| Changing a mapping |
Not applicable
|
Often through the provider
|
On the visual canvas, or with a prompt in AI Studio
|
| Best for |
A few orders a week from one retailer
|
Many EDI-only trading partners
|
Growing drop-ship volume alongside other channels
|
Your Rithum account is set up as a supplier, and the integration works on that side of the relationship: collecting each retailer’s orders, then acknowledging, shipping and invoicing them from Business Central.
Rithum lets suppliers mix connection methods, such as files for some flows and the API for others, and move across one flow at a time. Patchworks supports both, so you can start with whatever your retailer programme uses today.
Rithum’s supplier API doesn’t push new orders out, so Patchworks checks for them on a schedule you set. If Rithum’s API is busy, Patchworks backs off and retries, as Rithum recommends.
Retailer SKUs are held as item references, each retailer is set up as a Business Central customer, and the consumer’s address goes on the order as the ship-to. Drop-ship sales sit alongside the rest of your trade, with no separate ledger to reconcile.
If your team already works in Claude, ChatGPT or Gemini, the Patchworks MCP Server connects them to this integration. Your assistant can answer questions that span both systems, such as which retailer orders haven’t been acknowledged yet, and retry a failed sync when you ask, all within the permissions you set. Taking on a new retailer programme? Describe its requirements in AI Studio and the Implementation Agent builds the flow.
Drop-ship programmes are tested in the fourth quarter, when retailer orders spike and acknowledgement deadlines stay the same.
Virtualstock
Retailer drop-ship programmes run on Virtualstock, connected to Business Central.
Microsoft Dynamics Business Central
Storefronts, 3PLs, CRMs and more.
It connects Microsoft Dynamics 365 Business Central to Rithum so suppliers can run retailer drop-ship programmes from their ERP. Retailer orders arrive in Business Central as sales orders, and acknowledgements, shipments with tracking, invoices and inventory go back to Rithum automatically. It runs on Patchworks alongside your other Business Central integrations.
Yes. Rithum was formed in December 2023, when CommerceHub, ChannelAdvisor and Dsco came together under one brand. Dsco and OrderStream are the Rithum platforms retailers use to run drop-ship programmes with their suppliers, so a Business Central Dsco integration is a Business Central Rithum integration.
Both are Rithum platforms that retailers use to send drop-ship orders to suppliers. OrderStream is the network that came from CommerceHub, and Dsco joined Rithum through acquisition. The retailer decides which one you use, and some suppliers work with both. Patchworks connects Business Central to either.
Yes. CommerceHub is now Rithum, and many retailer onboarding guides and supplier logins still use the CommerceHub name. If a retailer has asked you to connect to CommerceHub for drop-ship orders, this is the integration you need.
Business Central connects through a prebuilt Patchworks connector. The Rithum side is built on Patchworks for your retailer programme, using Rithum’s supplier API or file exchange, so it fits how your retailers work rather than a fixed template. AI Studio’s Implementation Agent and Connector Builder build the connector and flows, so you start from a working model.
Use whatever your retailer programme supports. Rithum offers its supplier API, file exchange over SFTP and EDI documents, and lets you mix them flow by flow. Patchworks works with the API and with files over SFTP, including EDI documents, so your Business Central EDI and API flows run on one platform. See EDI integrations.
Each retailer order becomes a Business Central sales order. The retailer is set up as the customer, the consumer’s address is the ship-to, the retailer’s PO number stays on the order, and retailer SKUs are matched to your items through item references. New orders are collected on a schedule you set.
When you post a shipment in Business Central, Patchworks sends the carrier, service and tracking number to Rithum against the retailer’s order, line by line. Partial shipments are sent as they’re posted, so the retailer can keep its customer updated.
Yes. When a sales invoice is posted in Business Central, Patchworks sends it to Rithum against the original retailer order, with the quantities, prices and charges your retailer programme requires. Finance no longer needs to re-enter invoices in the supplier portal.
Business Central stays the source of truth. Patchworks publishes available quantities to Rithum on a schedule, from one or more locations, and can hold back a buffer for each retailer. The same stock feeds your own channels, such as a Shopify integration, which reduces the risk of overselling.
Yes. Rithum is one set of flows on the same Patchworks platform as your storefront, 3PL and marketplace integrations, all connected to Business Central. Retailer orders can be fulfilled from your own warehouse or routed to a 3PL like any other channel. See marketplace integrations.
Yes. ChannelAdvisor is now part of Rithum, and Patchworks has a prebuilt Rithum connector for its marketplace and channel management platform, built on the ChannelAdvisor API. If you sell on marketplaces through Rithum as well as running retailer drop-ship programmes, both can connect to Business Central through Patchworks.
It depends mostly on your retailer programme. The Business Central side is quick with the prebuilt connector, and AI Studio speeds up building the Rithum flows. Before you go live, Rithum validates the connection and your retailer approves production, so plan around their onboarding timeline as well as your own.
Yes. The MCP Server connects Claude, ChatGPT, Gemini and other MCP-compatible assistants to your integration, so they can answer questions such as which retailer orders haven’t been acknowledged, and retry a failed sync when you ask. AI can only use the tools and permissions you define, and AI Studio’s agents build flows from a prompt and explain failed runs.
Patchworks pricing is based on the number of connected systems and monthly operations, not seats. An operation is counted each time Patchworks sends or receives a data payload, and every plan includes unlimited users. See pricing.