Fixed scope
Fixed price
against a written scope
- Written scope and acceptance criteria up front
- Fixed price against that scope
- Staged delivery with review points
- Change requests priced separately, never absorbed silently
Shopify B2B and wholesale
Native B2B on Shopify Plus — company accounts with multiple locations, customer-specific catalogues and price lists, payment terms, quantity rules and reordering built for someone placing the same order every fortnight rather than browsing.
B2B buyers are not shopping
A wholesale buyer knows exactly what they want, orders it repeatedly, and is measured on how fast they can get it done. Everything that makes a DTC product page persuasive is friction to them.
Reordering is the product
The single highest-value B2B feature is usually not a catalogue at all. It is the ability to reorder last month’s order in four clicks, or paste a list of SKUs and quantities and check out.
Quick order, order history, saved lists and CSV upload consistently do more for wholesale revenue than any amount of merchandising.
What we build
Native B2B, or a workaround
Shopify’s native B2B — company accounts, price lists, payment terms — is a Plus feature. Below Plus, wholesale is served by apps, tagged customers and discount logic, all of which work but carry real limits.
We will be straight about which you are looking at, because a wholesale build on the wrong plan tends to be discovered late and expensively.
Plus vs the alternatives
The Shopify B2B stack
Native Plus features first. Apps only where Shopify genuinely does not cover it.
Company accounts
Companies with multiple locations, multiple buyers per company, and permissions per buyer — the actual shape of a wholesale customer.
Catalogues & price lists
Customer-specific catalogues and per-company pricing, including fixed prices and percentage adjustments off retail.
Payment terms & net invoicing
Net 30, 60 or 90 as a native payment method, with the order placed against terms rather than a card. This is the feature that most often decides whether a wholesale channel can move onto Shopify at all.
Quantity rules & volume pricing
Minimums, increments and case quantities enforced at the product level, and volume breaks applied automatically — so a buyer cannot order 7 of something that ships in cases of 12.
Customer Account API
B2B account experiences — order history, saved lists, approvals — built on Shopify’s own authentication.
Shopify Functions
Discount, shipping and payment logic expressed as Functions rather than as legacy scripts.
What a B2B build covers
The catalogue is the easy part. These are the pieces that decide whether buyers actually use it.
Company & buyer model
Companies, locations, buyers and permissions structured to match how your customers actually order.
Pricing & terms
Price lists, volume breaks, quantity rules and payment terms — configured natively rather than approximated with discount codes.
Quick order and reorder, built for repeat buyers
Order history you can reorder from, saved lists, a paste-a-list-of-SKUs box and CSV upload. A wholesale buyer placing the same order fortnightly should never have to browse a catalogue to do it.
- Reorder in a few clicks
- SKU paste
- CSV upload
ERP integration that reconciles
Stock, pricing, customers and orders synchronised with your ERP through supported APIs and webhooks, with retry, idempotency and a reconciliation report — so a failed sync is visible rather than discovered when a buyer is invoiced twice.
- Two-way sync
- Retry & idempotency
- Reconciliation report
Approvals & workflows
Multi-buyer approval flows and purchase-order references where the buying process requires them.
Mixed DTC and B2B
Running both from one Shopify organisation without either experience compromising the other.
Native B2B on Plus vs the alternatives
All three ship wholesale. They differ in what happens at scale and who has to maintain it.
| Apps / tags / second store | Native B2B on Plus | |
|---|---|---|
| Company accounts | Approximated with tags | Native, with locations and buyers |
| Customer-specific pricing | Discount logic or an app | Native price lists |
| Payment terms / net invoicing | Manual or third party | Native payment method |
| Quantity rules | App-dependent | Native, enforced at product level |
| Catalogue visibility | Tag-based, easy to leak | Native, per company |
| Two storefronts to maintain | Often | No |
| Cost | Lower plan, more apps | Plus pricing, fewer apps |
| Best when | Wholesale is a side channel | Wholesale is a real revenue line |
How we work
How a B2B build runs
7 stages. Open any one of them.
How your buyers actually order
Ask the buyers, not the catalogue.
Order patterns, approval chains, terms, case quantities and what your sales team currently does by hand. The manual workarounds are the requirements list.
Companies and pricing
The structure everything inherits.
Company and location model, buyer permissions, price list structure and quantity rules, agreed before build.
Buyer experience
Designed for speed, not persuasion.
Quick order, reorder, saved lists and account screens designed around a buyer who already knows what they want.
Development
On a Plus development store.
Native B2B configuration, storefront build and account experiences, with the ERP integration developed in parallel.
ERP and operations
Where B2B projects actually fail.
Two-way sync with retry, idempotency and reconciliation, tested against real data volumes and real failure modes.
A few real customers
Before everyone.
A small group of real buyers placing real orders, with your sales team watching. Fix what they hit, then widen.
Migrate the channel
With the sales team, not around them.
Onboarding, training and communication for buyers and internal staff, then decommissioning the manual process.
Ways to engage
Three shapes, depending on how well defined the work is. Every one starts with a scoped written proposal — no work begins on a verbal estimate.
Retainer
Monthly
block of hours
- A block of hours each month
- Prioritized by you, replanned as often as you like
- The same developers month to month
- Reporting on what the hours went to
Time & materials
Tracked time
billed as used
- Billed against tracked time
- Suits discovery, R&D and migrations
- Estimate per ticket before it starts
- Stop or change direction at any point
Rates are quoted against a written scope rather than published as a tier, because the same service costs very different amounts on a five-template store and a five-hundred-template one.
Context
The categories we build for
Wholesale mechanics vary enormously by category — case quantities in food, size runs in apparel, compatibility in components.
Fashion & Apparel
Beauty & Cosmetics
Food & Beverage
Jewelry & Luxury
Home & Outdoor
Electronics
Health & Supplements
Subscription
B2B & Wholesale
Sports & Fitness
Multi-region
Marketplace & Multi-store
Questions about Shopify B2B
Shopify B2B is the native wholesale layer on Shopify Plus: company accounts with multiple locations and buyers, customer-specific catalogues and price lists, net payment terms, quantity rules and volume pricing. TLX Apps builds the buyer experience around repeat ordering — quick order, reorder from order history, saved lists, SKU paste and CSV upload — plus ERP integration with retry, idempotency and reconciliation.
For native Shopify B2B — company accounts, customer-specific price lists and payment terms — yes. Below Plus you can run wholesale with apps, customer tags and discount logic, and plenty of businesses do. We will tell you which one your requirements actually need before you commit to a plan.
Yes, and on Shopify Plus that is the intended design: one organisation with separate catalogues, pricing and experiences. A second store is occasionally right, but it doubles the maintenance and is chosen more often than it is justified.
Yes — through supported APIs and webhooks, with retry, idempotency and a reconciliation report, so a failed sync of stock, pricing, customers or orders is visible rather than silent. Where a well-maintained connector already exists we will tell you to use it rather than bill you to rebuild it.
Yes. Net 30, 60 and 90 are native on Shopify Plus B2B: terms are a payment method, so the order is placed against terms rather than a card. This is frequently the single feature that decides whether a wholesale channel can move to Shopify at all.
Yes. Shopify B2B price lists are per company and support both fixed prices and percentage adjustments off retail, with volume breaks applied automatically.
Multiple buyers per company with permissions is native to Shopify B2B. More elaborate multi-step approval chains usually need custom work or an app — we scope which of your requirements falls where.
It depends far more on integration scope and pricing complexity than on catalogue size. We scope first and quote against a written scope.
No — done properly they gain visibility. Orders placed by buyers are visible to your team, and the sales team stops rekeying orders from email, which is usually the change they care about most.
Wholesale still running on email and spreadsheets?
Tell us how your buyers order today and what your sales team does by hand. That list is usually the whole requirements document.