Key takeaways
Choose a Shopify wholesale approach around the actual ordering workflow: public discovery and enquiries, assisted orders, or authenticated B2B purchasing. Verify current plan capabilities, model companies and pricing carefully, and pilot the complete fulfilment process before expanding access.
- Choose the approach from the ordering workflow: public enquiries, assisted orders, or authenticated B2B purchasing.
- Verify what your current Shopify plan supports before designing around it.
- Model companies and write pricing rules in plain language before importing contacts.
- Make quantities and units impossible to misread, and design approval and payment as one workflow.
- Pilot the full fulfilment process with accounts that expose different problems before widening access.
Decide what the first wholesale experience must accomplish
A business that receives a few carefully qualified stockist enquiries may not need immediate online ordering. It may need a clear explanation of its wholesale offer, a useful catalogue, an application form and a reliable response process. That can be a sensible first stage when assortment, pricing and approval rules are still evolving.
At the other end, established accounts placing repeat orders may be slowed down by emails and spreadsheet attachments. Those customers could benefit from accurate stock, agreed pricing and a convenient reorder flow. Build around that repeatable work first, rather than reproducing every exception a sales representative has handled over the years.
Separate acquisition from account service in the brief. The public site should help a suitable retailer understand the range and next step. The authenticated experience should help an approved buyer act efficiently. They serve connected goals, but a strong landing page does not prove that the ordering system is ready.
Check current Shopify B2B capabilities by plan
As checked in September 2026, Shopify documents B2B availability on Basic, Grow, Advanced and Plus. It is no longer accurate to assume every native B2B project requires Plus. Feature differences still matter: Shopify lists up to three active catalogues across B2B markets on Basic, Grow and Advanced, while Plus supports unlimited catalogues and direct company-location assignment.
Turn your requirements into a capability checklist and compare it with the current official plan documentation before quoting. Do not choose a subscription from the word “wholesale” alone. A shared price tier and a large matrix of negotiated account prices describe different operating needs.
Keep subscription cost separate from implementation, apps, integrations and ongoing administration. Native capability does not remove the work of preparing company records, testing pricing or training the team. Conversely, an existing app may remain appropriate if it meets your requirements reliably. Evaluate the actual workflow and migration effort before replacing a functioning system.
Choose between a blended and dedicated store
Shopify describes a blended store as one store and admin serving retail and B2B customers. A dedicated store separates the B2B operation into its own store and admin. This is an operational decision with implications for inventory, content, integrations and staff responsibilities, so make it before detailed interface design.
A blended approach may suit a business where both channels share products, stock and staff. A dedicated approach may suit a distinctly different wholesale operation. Neither arrangement automatically gives you the right pricing or fulfilment rules; those still need configuration and verification.
Consider who will maintain each environment during a seasonal launch. If two teams change product data independently, how will they avoid contradictory specifications? If one stock pool serves both audiences, how will the business handle a large trade order during a retail promotion? The software choice should reflect a deliberate answer to those questions.
| Decision | Question for your team |
|---|---|
| Catalogue ownership | Who approves products, descriptions and the assortment available to each buyer group? |
| Inventory | Are trade and retail orders supplied from the same available stock? |
| Brand experience | Do wholesale customers need a different information hierarchy or an entirely separate identity? |
| Administration | Can the team maintain more than one store and reconcile changes across systems? |
Model companies before importing contacts
A wholesale customer is often a company with locations and multiple people, not simply a retail account with a discount tag. Sketch the real relationship: legal business, purchasing locations, delivery addresses, buyers and the people responsible for payment. Use a small sample of representative accounts before importing the full database.
Shopify B2B uses companies and company locations, and requires customer accounts rather than legacy customer accounts for B2B. Confirm the intended account flow early. An apparently minor sign-in change can affect invitations, buyer expectations and support material.
For a hypothetical retailer with three shops, decide whether each location buys independently or a central buyer orders for all three. Record how shipping addresses and purchasing permissions should behave. Then test the permissions with representative users. The important test is whether each buyer can do the right work without seeing or changing information outside their role.
Write the pricing rules in plain language
Prepare a pricing worksheet before touching the catalogue configuration. Identify each buyer group, eligible assortment, price basis, currency and exceptions. If the current rules live in a salesperson’s memory, implementation will expose that ambiguity rather than solve it.
Use hypothetical examples to make disagreements visible. “Independent retailers receive the standard trade list; distributors use a separately approved list; promotional discounts do not combine unless explicitly permitted” is a testable business rule. “Everyone gets their usual deal” is not.
Include how prices change over time. Decide who approves a new price list, when it takes effect, how customers are informed and what happens to an order already under discussion. Keep a controlled record of published pricing. A portal that displays accurate prices today but has no update process will become unreliable as soon as the assortment changes.
Make quantities and units impossible to misunderstand
Wholesale pricing is easily misread when the selling unit is unclear. State whether a displayed price applies to one item, one case or a pack. Show the contents of the pack and any applicable purchasing increments. Ensure the order confirmation and fulfilment records express the same unit.
A hypothetical stationery supplier selling twelve notebooks per case should test what happens when a buyer enters one, twelve or thirteen into the quantity field. Does the field represent cases or individual notebooks? What reaches the warehouse? The interface, inventory model and packing documents must tell the same story.
Shopify offers quantity rules and volume pricing within its B2B feature set. Map your rules to the current supported behaviour, then verify actual variants and carts. Do not assume that a theme label or a frontend restriction enforces the underlying purchase rule.
Design approval and payment as one workflow
Document what happens from account application to the first completed order. Name the person who reviews an application, checks commercial information, assigns the approved terms and sends access instructions. A beautiful form does little if requests disappear into an unmonitored inbox.
Then define when an order becomes a commitment. Some businesses can accept it immediately; others need a freight quote, production confirmation or sales review. Explain that distinction to the buyer before submission. “Order received for review” and “Order confirmed” should never be interchangeable messages.
Treat payment terms as a business policy that the platform implements. Establish who approves terms, how exceptions are recorded and who follows up when payment is due. Have the appropriate finance or accounting owner validate those requirements. The design team should not infer credit arrangements from how the old checkout happened to behave.
Test fulfilment and integrations before polishing edge cases
Trace one order through the systems that matter: storefront, Shopify admin, accounting or ERP, warehouse and customer communications. Record which system owns each piece of information and when updates should happen. Integration scope is clearer when it describes a sequence of events rather than a list of software logos.
Test failures deliberately. What happens if stock changes while an order is being reviewed? If an external system is unavailable, who sees the error? Can a retry create a duplicate order? How does a cancelled line reach the warehouse? Define the operational response as well as the technical handling.
Keep a reconciliation process for the pilot. A staff member should be able to compare the order, amount, quantities and fulfilment state across the relevant systems. Automation should make a correct process easier to operate; it should not make incorrect data harder to notice.
Keep public discovery useful without exposing private terms
An entirely gated experience can be appropriate for serving existing accounts, but a prospective stockist still needs enough public information to decide whether to apply. Explain product categories, the type of retail partner you serve, the application process and how to contact the team. Publish only terms you intend to make public.
The public wholesale page can answer questions about assortment, ordering routes and application requirements. Keep negotiated pricing and account records behind the proper access controls. Do not publish private commercial information simply to make the site appear more complete for search engines.
Binevi’s Little Magpie case study documents an English and French wholesale discovery experience, an enquiry form and catalogue/Faire options on an existing Dawn theme. That is useful evidence for public wholesale discovery. It should not be read as a claim that the project included native company accounts, payment terms or an ERP integration.
Plan language and content ownership
For Canadian businesses serving English and French buyers, translate the entire important journey: enquiry questions, product specifications, validation messages and operational instructions. A translated landing page followed by unexplained account emails leaves the experience unfinished.
Decide who approves terminology for pack sizes, materials and ordering terms. Keep a short shared vocabulary so catalogue pages, downloadable documents and account communications remain consistent. Technical integration names can stay in internal documentation; buyers need language that helps them order correctly.
Also decide how language updates are maintained. A new product or changed minimum order should trigger a review in every supported language. Record the owner and status rather than relying on someone to remember which page was translated last season.
Pilot with accounts that reveal different problems
Invite a small, purposeful set of approved accounts to test the workflow. Include a new buyer, an experienced repeat buyer, an account with multiple delivery locations and a buyer who mainly orders by phone. Their behaviour will expose different friction than an internal demonstration.
Give them real tasks with controlled test data: find an item, understand the selling unit, build an order, submit it, check its status and request help. Watch where they hesitate. Do not explain every control in advance; the gaps you have to explain are useful design evidence.
Review the staff experience at the same time. Track approval time, manual corrections, pricing questions and fulfilment exceptions. Fix the highest-impact problems before adding more accounts. A successful pilot produces a repeatable operating process, not simply a screenshot showing that a test order exists.
Measure whether wholesale became easier to operate
Choose metrics that reflect the reason for the project. These may include time to approve an account, repeat-order completion, manual interventions per order and pricing-related support requests. Keep revenue and margin in the conversation, but do not assume every shift was caused by the new portal.
Compare similar account groups and account for product launches, seasonality and sales activity. A sales representative bringing in several large customers can change results independently of the website. Document those events so the team can make sensible decisions about the next stage.
The next investment might be faster reordering, better product data or an integration that removes a recurring correction. Let the pilot show what matters. Expanding into every available feature before observing real orders creates more moving parts than the business may need.
Frequently asked questions
Does Shopify B2B require Shopify Plus?
Not in all cases. Shopify’s current documentation lists B2B on Basic, Grow, Advanced and Plus, with feature and catalogue limits that differ by plan. Match the current plan capabilities to your pricing, account and purchasing requirements before deciding.
Can we start wholesale with an enquiry form?
Yes, when the immediate need is to qualify stockists and arrange orders with the sales team. Make the offer and response process clear. Move toward self-service when the ordering rules are stable and repeated manual work justifies the implementation.
Sources and further reading
Keep exploring