Shopify B2B architecture should not start with “Do we need Plus?” Start with companies, locations, contacts, catalogues, prices, terms, approvals, inventory, ERP, and market rules. Define who can see, order, approve, and collect before assigning boundaries to platform, apps, and custom development.
Establish company and location master data
Give companies, locations, contacts, tax IDs, currencies, price lists, addresses, credit limits, and terms stable IDs. A multi-location customer should not inherit one default address or price for every order. Define the system of record, field mapping, conflicts, failure queue, and human review across ERP, CRM, and Shopify.
Build catalogue, price, and permission matrices
Set visibility by company or location, market, currency, validity, and catalogue. Test login, quote, order, partial fulfilment, refund, credit breach, expired price, disabled location, and rejected approval. Accept platform, app, custom code, and operating process separately.
FAQ
Does B2B always require Shopify Plus?
No. Assess company/location, price, permissions, approvals, ERP, and market complexity against standard and custom boundaries.
How can multi-location price mismatches be avoided?
Use company/location IDs, price lists, currency, and validity; do not let a default override every order.
What should a B2B portal test before launch?
Permissions, catalogues, quotes, orders, addresses, terms, partial fulfilment, refunds, and approval failures.
What happens when ERP sync fails?
Retain event and resource IDs, queue and alert the failure, and require review rather than overwriting unknown data.