Case study collection
B2B & Supplier Operations
The operational layer around a wholesale store: suppliers, purchase orders, quality control and the work that happens long before an order is ready to ship.
05
Case studies
None of this is storefront work. It is the internal tooling a wholesale business actually runs on, built where the merchant already works rather than in a separate system nobody opens.
The supplier portal replaced a sourcing workflow that lived across messages and spreadsheets. Suppliers and staff hold different permissions over purchase orders, product submissions and approvals, and draft product records have a lifecycle of their own rather than behaving like Shopify products before anyone has agreed they are ready.
The QC workflow defines what ready means: sampling, design approval, countersampling, quality control and data completeness, calculated rather than eyeballed, across three levels of EAN. The artwork generator then turns that standardised data into four packaging sticker designs and a combined order PDF in a single click — tested on an order of more than 60 products.
Two more sit alongside them. Product synchronisation lets a B2B and a B2C Shopify store share technical truth while merchandising stays independent, with explicit control over which fields are written on create and which on update. Transactional email generates customer updates from the same data the dashboard uses to decide what can ship, so the two cannot drift apart.
The engineering behind this work is Shopify B2B and wholesale engineering.
Written up
What this work taught us, in detail.
Architecture
Shopify B2B trade account onboarding: automated VAT validation, credit gating, and GraphQL company creation
Engineering
Shopify Fulfillment Orders API in ERP integrations: holds, line splits, and multi-warehouse routing
Architecture
Shopify supplier portals: managing purchase orders, ASNs, and container milestones
Integration
Wholesale quote requests belong in draft orders, not contact forms or app iframes
Engineering
Completeness is calculated, not inspected
Engineering
One product, three barcodes
Architecture
Operational email is sent by a person, not fired by an event
Architecture
Two stores, one product: a sync is a contract, not a mirror
Architecture
Supplier portals: the operations layer Shopify doesn't have
Your store next
Most engagements start with the same question.
What is actually slowing this store down, and is it worth fixing? Send us the URL and we will answer it honestly.