How do B2B recurring/replenishment orders (distinct from consumer subscriptions) migrate their contract-level scheduling data to Shopify?
Shopify B2B has no destination object for a recurring replenishment schedule. Shopify states that "B2B doesn't support purchase options, such as subscriptions, pre-orders, and try before you buy", and a selling plan on a B2B order returns the error "Only one-time purchase is available for B2B orders" (per shopify.dev and Shopify Community, September 2026). B2B replenishment gets rebuilt, not migrated.
The mechanism, stated plainly
Consumer subscriptions on Shopify are purchase options: a selling plan attaches to a line, a subscription contract is created, and a billing attempt charges a stored payment method. B2B orders run on a different set of primitives entirely: a company, a company location, a catalog attached to that location, and payment terms (per shopify.dev, September 2026). The two systems do not intersect. There is no B2B subscription contract to import into.
What B2B does give you
| B2B capability | Detail | Plan |
|---|---|---|
| Payment terms | No terms, Net 7/15/30/45/60/90, due on fulfillment, fixed date | B2B-capable plans |
| Deposits | Partial upfront payment at checkout | Shopify Plus only |
| Catalogs | Attached to a company location, with negotiated price lists | B2B-capable plans |
| Draft orders | Created for a company contact | B2B-capable plans |
| Purchase options (subscriptions) | Not supported | — |
Per Shopify's Help Center and shopify.dev, verified September 2026.
So where does the schedule go?
Three honest destinations, and a trade in each:
- Scheduled draft orders. Keep the company, the location catalog and the payment terms intact, and generate a draft order on the cadence via Shopify Flow or a scheduled job against the Admin API. The buyer approves or it converts automatically. Terms, PO number and negotiated pricing all survive because the order is a real B2B order. This is the closest match to what a legacy B2B replenishment schedule actually was.
- A consumer subscription app, on a non-B2B customer record. Technically workable, and it discards the reason you were on B2B: no company hierarchy, no location catalog, no net terms, no approval flow. Card-on-file replaces invoicing. For a wholesale account that pays Net 30, this is a downgrade dressed as a migration.
- An ERP-driven schedule. If replenishment is already generated by an ERP or planning system, push the order into Shopify rather than re-implementing the cadence in the storefront. Most mid-market wholesale operations already have the schedule living upstream.
What to export from the legacy system regardless
Cadence, next scheduled date, quantity per line, the company and location the schedule belongs to, the PO reference, the payment terms, and the approver. Only the first three look like subscription data. The last four are the ones a consumer subscription app will silently drop, and they are the ones the buyer's finance team will ask about in week two.
The blunt version. If a vendor tells you they can migrate B2B replenishment schedules into Shopify subscriptions, they are describing option 2 without describing what it costs you. Shopify can run recurring B2B ordering well; it just does not do it through the subscriptions system.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Rebuild B2B replenishment as scheduled B2B orders, not as subscriptions. The company and location model is the whole reason to be on Shopify B2B, and a consumer subscription contract cannot reference it.
- What we’ve seen: The PO number and the approver are the fields that get dropped, and they are invisible until an invoice arrives that the buyer's AP system cannot match. Cadence is the easy part of a replenishment schedule; the approval context is the part that is load-bearing.
- Where we disagree: "Recurring order" gets treated as one category by migration tooling. In Shopify's data model consumer subscriptions and B2B reordering are separate systems with no shared object, and a plan that does not name which one it is building is not a plan.
- What this page adds: that this branch of the migration has no destination object at all (Shopify's own documentation rules purchase options out for B2B), so the correct output is a rebuild specification rather than a field mapping.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.