Free Shopify store auditSpeed, SEO and conversion leaks — no cost, no obligation.
Claim it
Thriftizer Solutions LLPShopify Select Partner
Book a Growth Audit
Shopify Aug 24, 2026 8 min read

Shopify B2B Wholesale: Running It Without a Second Store

Native B2B on Shopify Plus runs company accounts, price lists and net terms inside your existing store. Here's how we set it up, what breaks, and when an expansion store is genuinely the right call.

Shopify B2B Wholesale: Running It Without a Second Store

You don't need a second Shopify store to sell wholesale. On Shopify Plus, a native B2B setup runs company accounts, per-buyer price lists, net payment terms and a separate wholesale catalogue inside the same store, on the same theme, with the same inventory. Markets handles the currency and duty side when your distributor sits in Dubai or Dallas. The expansion store is the expensive answer to a problem Shopify solved natively about two years ago, and we still spend a fair bit of time talking founders out of it.

The honest caveat comes early: native B2B ships with Plus. If you're on Basic, Grow or Advanced, the second half of this post matters more to you than the first.

What a native Shopify B2B wholesale setup actually includes

The pieces are less abstract than the documentation makes them sound. In practice you're configuring five things:

  • Companies and company locations. A company is the buying entity. Each location under it gets its own catalogue, payment terms, tax settings, shipping addresses and set of authorised buyers. A distributor with a Mumbai warehouse and a Chennai warehouse can have different price lists and different credit terms under one company record.
  • Catalogues and price lists. A catalogue controls both which products a company sees and what they pay. Prices can be a blanket percentage off retail, or fixed rupee amounts per variant, or a mix. Volume tiers sit inside the price list, so 1–11 units at one price and 12+ at another.
  • Quantity rules. Minimum order quantity, maximum, and increments. If a carton is 24 units, the buyer physically cannot add 25.
  • Payment terms. Net 15, 30, 45, 60, due on fulfilment, or a fixed date. The order is placed, an invoice is issued, and the money arrives later. This is the feature that makes real wholesale possible, and it's the one that a discount-code workaround can never fake.
  • Buyer permissions. Who can pay by terms, who can only pay by card, who can see order history for the whole company.

Your sales team also gets draft orders on behalf of a company, which is how most Indian wholesale actually closes. The buyer calls, your rep builds the order, the buyer approves the payment link or takes it on terms.

The plan constraint that decides your B2B setup

B2B is a Plus feature. So the first question in any wholesale project isn't which catalogue structure to use, it's whether your wholesale volume pays for the plan.

Do the sum before you do anything else. Get a real quote for the Plus delta over your current plan, then divide it by your wholesale gross margin. Say the delta is ₹1.6 lakh a month and wholesale margin is 22%. You need ₹1.6L ÷ 0.22 = about ₹7.3 lakh of incremental wholesale revenue every month before the plan pays for itself, ignoring the build cost entirely. If your wholesale pipeline is three boutiques and a hopeful email from a distributor, you are not there yet, and no agency should tell you otherwise. Our view on when the upgrade earns its keep sits on the Shopify Plus page, and it isn't a sales pitch.

Until then, run wholesale on your existing plan with unglamorous tools:

  • Tag wholesale customers, gate a hidden collection behind a customer tag, and apply an automatic discount at the customer level.
  • Or skip the storefront entirely. Share a Google Sheet order form, take orders on WhatsApp, and raise draft orders manually. We've seen brands run ₹15–20 lakh a month of wholesale this way. It's ugly and it works.
  • A third-party wholesale app can add price tiers and minimum quantities on lower plans. What none of them do well is credit terms and invoicing, because that isn't a theme problem.

The failure mode is spending ₹3 lakh on a wholesale app stack and custom theme logic that you'll throw away the day you move to Plus. If Plus is six months out, wait.

Catalogues: how we structure them so they don't multiply

The temptation is one catalogue per customer. Resist it. Twelve catalogues become forty, and then nobody knows which one has the 2024 pricing.

What holds up: three or four tier catalogues built on percentage-off pricing — distributor, stockist, boutique, export — and fixed-price overrides only where a specific buyer has negotiated something you can't express as a percentage. Catalogues are assigned to company locations, so onboarding a new stockist takes two minutes instead of a build.

Two details that catch people out. First, catalogue priority: if a location somehow ends up in more than one catalogue, Shopify resolves it by the order you've set, and the result is rarely the one you assumed. Check it with a test company before launch. Second, product publishing is part of the catalogue, so if you sell some SKUs only to export buyers, that's controlled here, not with tags.

Wholesale buyers navigate differently from retail shoppers. They arrive knowing the SKU code and they reorder. If your wholesale catalogue runs to a few thousand variants, search that matches on SKU and filters that reflect the way a buyer thinks about your range does more for order value than any theme redesign. That's the use case we built FilterPro for, though any filter app that indexes SKUs will do the job.

Markets plus B2B: export wholesale without an expansion store

This is where the second store usually gets proposed. You've signed a distributor in Sharjah, they want AED pricing, they want to see delivered cost, and someone suggests a separate .ae store.

You don't need one. A catalogue's prices are set in a currency, so your export catalogue can be denominated in USD or AED while the retail storefront stays in INR. Assign the UAE distributor's company location to that catalogue and their entire session prices in their currency. Markets handles the rest: domain or subfolder if you want one, translated content, and estimated duties at checkout.

Duty quoting matters more in wholesale than retail. A retail customer grumbles at a surprise customs bill. A distributor refuses the shipment and you eat the freight both ways. Get HS codes and country of origin onto your variants before the first export order, not after.

Where an expansion store genuinely earns its place: when the legal entity is different and you need separate books, separate GST or VAT registration, and separate payment gateway settlements. Also when the brand positioning genuinely differs by market. Currency alone is not a reason.

The parts of a single-store setup that hurt

I'd rather you hear these from us than discover them in week three.

Customer accounts. B2B buyers log in through the newer customer accounts system, not the legacy one. If your store still uses classic accounts with a heavily customised login page, that page is going away for wholesale. Budget for it.

Apps that don't know what a company is. Loyalty apps, subscription apps, bundle apps, upsell apps — a good share of them read the customer object and have no concept of a company location or a catalogue price. We get bitten by this on roughly a third of first-pass B2B builds and the fix is usually to disable the app for B2B sessions rather than to make it work. Test your review widget, your shipping rate rules and anything that writes to cart attributes.

Theme gating. Modern themes expose whether the logged-in visitor is a B2B buyer in Liquid, so you can hide the retail promo banner, swap the delivery messaging, and show an order form layout on product pages without duplicating the theme. It's a day or two of work, not a rebuild. Skip it and your distributors will see "Free shipping over ₹999" while ordering forty cartons.

Promotions. Retail discount mechanics and gift card behaviour don't map cleanly onto a B2B checkout. Test every promotion path you rely on with a real test company before you announce the portal.

The India layer: GST, credit and getting paid

Shopify will not produce a GST-compliant tax invoice with the buyer's GSTIN and HSN codes on its own. For B2C nobody notices. For B2B, your buyer cannot claim input credit without it, so this is a hard blocker, not a nice-to-have.

What works: capture GSTIN as a metafield on the company location, mark the location tax-exempt or tax-inclusive as appropriate, and push orders into Zoho Books, Tally or your ERP for invoicing. Handle the interstate IGST versus intra-state CGST/SGST split there, not in Shopify's tax engine. If a consignment crosses ₹50,000 in value you also need an e-way bill, which again lives in your accounting stack.

Payments: forget COD. Wholesale in India runs on NEFT, RTGS and credit. Enable a manual payment method for bank transfer, put the account details and a reference format into the confirmation email, and use Shopify's payment terms to track what's outstanding. Razorpay works fine for card and UPI on smaller wholesale orders, but a ₹4 lakh order is going by bank transfer and your ops team will reconcile it by UTR.

Decide your credit policy before launch, not per customer over WhatsApp. Net 30 for anyone with three clean paid orders, prepaid for everyone else, is a rule your team can enforce without escalating to you.

Costing a single store against an expansion store

The plan licence usually isn't the difference. The duplication is.

Run through the apps you'd need on both stores. Reviews at $29, email and automation at $60, filters at $29, shipping rate rules at $19, and an inventory sync app to keep the two stores honest at $79. That's $216 a month, roughly ₹18,500 at ₹86 to the dollar, or about ₹2.2 lakh a year. Add a theme build for the second store at ₹1.5–3 lakh and you're at ₹4–5 lakh in year one. Then add the thing nobody budgets: every future change gets built and QA'd twice, and the two themes drift apart within about four months no matter how disciplined the team is.

Against that, a native B2B configuration on your existing store is a two-to-three week engagement — catalogues, company onboarding, theme gating, invoicing integration, and a proper test company. Comparable rates and scope are on our Shopify development cost page.

A sane rollout order

Configure one company, with one location and one catalogue, and put your own team in it as buyers. Place a real order on net 30. Watch what happens in the invoice, the accounting integration and the packing slip. Fix what breaks.

Then onboard three friendly stockists and let them order for two weeks while you're still watching. Only after that do you email the full list. Wholesale buyers are not forgiving of a portal that quotes the wrong price, and they will go back to WhatsApp permanently after one bad experience.

If you're weighing a second store against a native setup and want a second opinion on which way the numbers fall for your catalogue, send us the store and we'll look at it — the audit is free and we'll tell you if the answer is to wait.

Previous postNext post

Ready to scale your D2C brand profitably?

Let's build a growth engine that drives more traffic, more conversions and more profit.

Book a Growth Audit
📅 Free Audit💬 WhatsApp