Shopify B2B vs Retail EDI: What Company Accounts Actually Cover

Shopify B2B and retail EDI solve different problems, and brands buy the wrong one regularly. B2B is a wholesale storefront: a buyer logs in, sees their negotiated catalog and payment terms, and places an order. Retail EDI is a compliance protocol: the retailer’s system sends an 850 to yours, and no human on the buying side ever visits your site. If a vendor packet says EDI, no amount of B2B configuration satisfies it. If your wholesale accounts are boutiques emailing spreadsheets, EDI is the wrong tool entirely.

Two different problems

Shopify B2B is a sales channel. Buyers authenticate, browse a catalog priced for them, and check out under terms you set. The order arrives in Shopify as an order.

Retail EDI is a machine-to-machine contract. A retailer’s ERP emits a purchase order in a standardized format on their schedule, and expects an acknowledgment, an advance ship notice, and an invoice back in the same format, inside windows their vendor agreement defines. Miss the format and you get a chargeback rather than an error message.

One is about giving buyers a good ordering experience. The other is about satisfying a specification you did not write. Most brands over about $10M in revenue end up needing both, because the boutique accounts and the big-box program are different businesses that happen to share your inventory.

What Shopify B2B gives you

Most of what brands believe about this is a year out of date. B2B is no longer Plus-only, and the plan limits change what belongs on your shortlist.

• Companies and company locations. Unlimited companies, and a company can carry up to 10,000 locations. Pricing, payment terms, and checkout behavior attach to the location, not the company — so one retail group can buy differently per region.
• Catalogs and price lists. Catalogs control which products a buyer sees and what they pay, with percentage-based or per-product pricing. A company location can have up to 25 catalogs assigned.
• Payment terms and deposits. Net terms and deposit requirements configured per company location, with orders tracked and sorted as they come due.
• Draft orders as a sales-rep tool. A rep can build a draft order that inherits the account’s pricing, terms, and checkout, then email a checkout link for approval. Orders can also be set to arrive as drafts for review before they are accepted.
• Quantity rules. Minimums, maximums, and increments, which is how case-pack behavior gets enforced.

The plan line that matters: on Basic, Grow, and Advanced you can assign up to three active catalogs across your B2B markets. Shopify Plus lifts that to unlimited catalogs and allows direct assignment to companies and locations. So the question is not whether you can run B2B below Plus — you can — it is whether three catalogs covers your pricing tiers.

What retail EDI demands that B2B does not touch

Requirement	Shopify B2B	Retail EDI program	Endless Commerce
How orders arrive	Buyer logs in and checks out	850 from the retailer’s system, unattended	Either, into one order record
Order acknowledgment	Order confirmation email	855 within a contractual window	Native, windowed
Advance ship notice	None	856, carton and pallet level, before delivery	Native, from the shipment record
Invoicing	Shopify order and payment terms	810 in X12 format, priced off the PO	Native, generated from PO and ASN
Carton labels	Code-128 via the barcode app	GS1-128 with serialized container codes	Native
Routing guide compliance	Not modeled	Per-retailer, penalties attached	Tracked per partner
Chargeback exposure	None	Expense offsets per violation	Monitored and attributed
Inventory commitment	Draft order reservation with an expiry	Committed at PO acceptance	Committed against one record

B2B models the commercial relationship. EDI models the operational obligation. Nothing in the B2B feature set produces an 856 or a GS1-128 carton label, because that was never what it was for.

Shopify has no native EDI. Documents flow through a connected platform, and — in Shopify’s own description — an 850, 855, 860, 997, 856, or 810 “simply become single-line updates on the Shopify order record.” That is a clean architecture when the connected system is your source of truth. It is a reconciliation problem when it is a second system syncing against Shopify.

Which one you need

B2B is enough when: your wholesale accounts are independents and boutiques, they are happy to order through a portal, nobody has sent you a vendor compliance packet, and your pricing fits inside your plan’s catalog allowance.

You need EDI when: a retailer mandates it. That is the whole test. Big-box, grocery, and most distributors will not accept portal orders from a vendor at scale, and the packet will name the transaction sets. Our per-retailer requirements cover what the major programs ask for.

You need both when: you sell wholesale to small accounts and run at least one retail program. This is the common end state, and the architecture question is whether both live on the same inventory and order model or in two systems that reconcile nightly. The API vs EDI guide covers the protocol side of that decision.

The mistake that costs the most

Running B2B and EDI as separate stacks over the same physical stock.

A wholesale order placed through B2B commits inventory in Shopify. A retail PO sitting in a bolted-on EDI system commits nothing there, so the same units stay available to your storefront and your B2B catalog simultaneously. Nothing errors. You discover it when a pick runs short, and by then you are choosing which customer to disappoint — and one of them charges you for the privilege.

No process fixes this. It takes one inventory record that both channels commit against. On Endless, EndlessEDI is native across all tiers, so a retail PO, a wholesale order, and a DTC sale all draw down the same number — and the forecast sees all three. Retail demand shows up in planning instead of ambushing you in week six. A Shopify-only view of demand will never see it at all.

Before you shortlist a vendor, the Shopify retail EDI readiness checklist is the ungated list of questions worth asking. If a retailer has already said yes and you are working out the sequence, start with your first retail PO on Shopify.

Sources

Shopify B2B capability and plan limits come from Shopify’s B2B documentation and developer resources — companies and locations, catalogs and price lists, payment terms, draft orders, quantity rules, and the per-plan catalog allowances. The characterisation of EDI documents as updates on the Shopify order record is Shopify’s own, from its enterprise writing on operationalising EDI with a cloud OMS. Transaction set names follow the ANSI ASC X12 standard.

Shopify ships changes to B2B regularly and plan level affects what you get. Verify the current allowances in your own admin before you build a pricing structure on them.