How do B2B recurring/replenishment orders (distinct from consumer subscriptions) migrate their contract-level scheduling data to Shopify?

Why is there nothing in Shopify to import a B2B replenishment schedule into?

There is nothing in Shopify to import a business-to-business (B2B) replenishment schedule into, because Shopify keeps recurring billing and B2B on separate rails. A consumer subscription is a purchase option: a subscription contract is "the agreement between a customer and a merchant" for recurring purchases (Shopify's subscriptions guide, October 2026). Shopify says "B2B doesn't support purchase options, such as subscriptions, pre-orders, and try before you buy" (shopify.dev, October 2026). B2B orders run on companies, company locations, catalogs and payment terms instead. So this branch of migrating an active subscription program produces a rebuild specification, not a field mapping. Developers have hit the wall: a selling plan on a B2B order returned "Only one-time purchase is available for B2B orders" (community-reported, Shopify Community, January 2025). Whether any app supports company-level recurring orders is answered separately.

Which Shopify B2B features does a rebuilt replenishment schedule rely on?

A rebuilt replenishment schedule relies on Shopify business-to-business (B2B) payment terms, draft orders and reorders, which run on every B2B plan, and only staged payments need Plus.

So rebuilt orders keep the account's terms, catalog and PO reference, because each is a real B2B order. Test the Flow charge on one account before relying on it.

Where does the replenishment schedule go instead?

The replenishment schedule goes to one of three places, and each trades something.

1. Scheduled draft orders, the closest match. A draft order is created for the company location on each due date, through the draft order application programming interface (API) Shopify documents for business-to-business (B2B) orders (shopify.dev, October 2026). Flow's Scheduled time trigger repeats by days, weeks or months (Shopify Help Center, October 2026), but Flow has no action that creates a draft order (Flow's actions list, October 2026). So use Flow's Send Admin API request action, which "can use most mutations" (Shopify Help Center), or a standing-order app. Orumio Standing Orders ($29 a month) and OrderCadence (free for one schedule) draft a company location's order on a schedule; neither had reviews in October 2026 (Orumio, OrderCadence).
2. A consumer subscription app on a non-B2B customer record. It discards the company, the location catalog, net terms and approvals: a downgrade dressed as a migration.
3. An enterprise resource planning (ERP) schedule. If the ERP already generates replenishment, push its orders into Shopify instead.

Deploi's draft-order flows record scores a custom flow BUILD once negotiated pricing or approvals are how you sell (October 2026).

What should you export from the legacy system before cutover?

Export seven fields per schedule from the legacy system before cutover:

1. Cadence
2. Next scheduled date
3. Quantity per line
4. The company and location the schedule belongs to
5. The purchase order reference
6. The payment terms
7. The approver

Only the first three look like subscription data. The last four are what a consumer subscription app drops, so they are what the buyer's finance team asks about first. Shopify also needs every company, location, contact and product in place before a business-to-business (B2B) order imports (shopify.dev, October 2026). How draft-order and quote data migrates covers that sequence. Net terms come across as native terms only where Shopify has a match: net 7, 15, 30, 45, 60 or 90 (Shopify Help Center, October 2026).

When is a consumer subscription app the wrong home for wholesale replenishment?

A consumer subscription app is the wrong home for wholesale replenishment whenever the account buys on terms, because Shopify can't attach a subscription to a business-to-business (B2B) order.