What Shopify Collective actually does for wholesale, what it requires, where it falls short today, and the part of your order flow it does not solve.
Most Shopify merchants running wholesale have never opened Collective.
That is not a criticism. It sits quietly in the admin, it is described in Shopify's own documentation mostly in terms of dropshipping, and the wholesale use case is not the one it leads with. So merchants who sell B2B skip past it and keep running their partner relationships the way they always have: a spreadsheet, an email, a PDF, a purchase order, an invoice, and a reconciliation at month end.
Which is a shame, because underneath the dropshipping framing is something more interesting. Collective is Shopify's first real attempt at treating the relationship between two businesses as a native object on the platform rather than a stack of documents passed back and forth.
This article explains what it actually does, what it requires, where it currently falls short, and how to think about it if you sell wholesale.
Shopify Collective is a native feature that connects two merchants who both run on Shopify: one supplying products, one selling them.
Once connected, three things happen automatically that normally take manual work.
Products sync. The supplier publishes a catalog. The retailer selects products. Those products appear in the retailer's store, live and sellable, without anyone creating a product record, uploading images, or copying descriptions from a spreadsheet.
Orders route. When a buyer places an order on the retailer's store, the corresponding order is created on the supplier's side automatically and enters their fulfillment queue. The supplier ships. Tracking information flows back to the retailer and to the end buyer without either party sending an email.
Money moves. Payment between the retailer and the supplier is handled by the platform at the transaction level. No invoice is issued. No purchase order is created. No accounts payable cycle runs.
That last point is the one worth pausing on. In a Collective transaction, the PO and the invoice do not exist as documents at all. The commercial terms are configured once, in the connection, and every transaction settles against them.
Here is the full sequence for a single order.
Count the manual touchpoints in that list. There are none after the initial connection is configured.
Compare the same relationship run the conventional way. Eight steps versus zero. Same commercial relationship, same products, same money changing hands.
This is what people mean when they say unified commerce, stripped of the marketing language. It is not one dashboard for everything. It is the catalog, the order, the fulfillment, and the settlement living in the same system, so the handoffs between them stop being work.
The constraint is straightforward and it is also the main limitation.
Both parties must be on Shopify. This is not a connector that reaches out to a partner's NetSuite or their QuickBooks or their custom ERP. It works because both sides are native, which is exactly what makes the automation possible and exactly what limits its reach.
Beyond that, availability depends on region and on merchant eligibility, and Shopify has been expanding both. Because eligibility criteria change, check the current requirements in your admin rather than relying on a third-party article, including this one.
The practical requirement most merchants overlook is operational rather than technical. Collective settles transactions automatically against terms agreed in the connection. If your wholesale pricing lives in six different spreadsheets with customer-specific exceptions nobody has written down, you will not be able to configure the connection cleanly. The tool assumes your commercial terms are already coherent.
The two sides of a connection have different concerns.
If you are the supplier, the appeal is distribution and control. You publish once and your products federate to every retailer you are connected to. When you change an image or update product data, it updates everywhere. You also get visibility you do not normally have: traditional wholesale ends your line of sight at the loading dock.
If you are the retailer, the appeal is inventory risk and speed. You can list and sell products without holding stock, which means you can test whether there is demand before committing capital to it. Onboarding a new supplier stops being a multi-week project and becomes a connection.
Being useful about a tool means being clear about its edges.
It was built dropshipping-first. The mechanics were designed around the retailer never holding inventory. Wholesale, where the retailer buys and stocks the product, is supported less completely. If your model is buy-and-hold rather than pass-through, expect gaps.
API coverage is incomplete. A number of actions still require a person to go into the admin and click, rather than being scriptable. If you are a larger operation with your own systems, this matters.
It only covers partners who are already on Shopify. For most manufacturers and distributors, that is a minority of the partner book. Your largest customers are frequently the least likely to be on Shopify, because they are running an ERP that predates it.
Here is the honest shape of the problem for a mid-market manufacturer or distributor.
Some percentage of your wholesale orders come from partners on Shopify. For those, Collective is a genuinely good answer. The rest arrive the way they always have: a PDF attached to an email, a spreadsheet with a customer-specific layout, an EDI feed, a portal you have to log into, or a phone call.
Those orders do not have a platform-native path. They arrive in formats nobody designed, containing customer part numbers that do not match your SKUs, quantities expressed in cases when your catalog is in units, and line items described in the buyer's language rather than yours. Somebody reads them and types them in.
No roadmap fixes this by itself, because it is not a roadmap problem. Platforms standardize the path first. The parts of your order process that resist standardization are exactly the parts that encode how your business actually operates. That knowledge lives in the head of whoever has been doing order entry for eleven years.
Which is why the sequencing matters. Team, process, tools, in that order. AI and automation do not repair weak foundations. They amplify whatever is already there, at speed.
If you sell wholesale on Shopify, three practical steps.
One: audit your partner mix. How many of your wholesale customers are already on Shopify? If the answer is more than a handful, Collective is worth an hour of evaluation this quarter.
Two: write down your commercial terms. Whatever you decide about Collective, the exercise of documenting pricing tiers, minimums, and customer-specific exceptions is the prerequisite for automating anything.
Three: separate the platform-native flow from everything else. Collective handles one lane. Map the rest honestly: which partners send PDFs, which send spreadsheets, which use EDI, and how many hours a week your team spends turning those into orders.
Shopify has been explicit that connected commerce between merchants is where it is heading: quote becomes purchase order becomes order becomes fulfillment becomes invoice and payment, with no rekeying at any step. Collective is the first working piece of that.
If you are running B2B and wholesale orders entirely outside the platform today, the gap between platform-native commerce and document-based commerce widens every quarter. Getting your wholesale operation onto Shopify now is what makes it possible to plug into what comes next without rebuilding.
The vision will take time to arrive. Your orders arrive Monday.
Maxime Lavoie
Founder, LevelOps
Industrial engineer by training. Former Deloitte supply-chain consultant. Former VP Operations at Goodfood Market. Now writes the ERP, MRP and B2B order playbooks he wishes had existed in 2018.
Voice of customer
The phrases that kept recurring in customer calls: very manual process, their format to our format, lives in one head, and why EDI still leaves work behind.
Operations
LevelOps' Operational Excellence framework for AI success: Team, Process, and Tools. Before bringing in AI, get the fundamentals right.
Operations
The second pillar of LevelOps' Operational Excellence framework: building clear, aligned, and measurable processes before automating anything.
The documents. Products sync from the supplier's catalog into the retailer's store, orders are created on the supplier's side automatically when an end buyer purchases, tracking flows back without anyone emailing it, and the wholesale amount settles through the platform. There is no purchase order and no invoice, because the commercial terms are configured once in the connection and every transaction settles against them.
Coherent commercial terms, which is an operational prerequisite rather than a technical one. Collective settles transactions automatically against the terms agreed in the connection, so if your wholesale pricing lives across six spreadsheets with customer specific exceptions nobody has written down, you cannot configure it cleanly. Documenting your pricing tiers, minimums and exceptions is worth doing whatever you decide about Collective.
Only partly today. API coverage is incomplete and a number of actions still require a person to go into the Shopify admin and click. If you are a larger operation running your own systems and expecting to script the workflow, check the specific actions you need before planning around it.
Partially, and with gaps. The mechanics were designed dropshipping first, around a retailer who never takes possession of the product. Buy and hold wholesale is supported less completely, so test it against your own model rather than assuming feature parity.
They have no platform native path, and for most manufacturers and distributors that is the majority of the partner book. Those orders keep arriving as PDFs, spreadsheets in a customer specific layout, EDI feeds, portals you log into, or phone calls, often with customer part numbers that do not match your SKUs and quantities in cases when your catalog is in units. That lane needs its own answer: order intake that reads whatever layout arrives, matches it to your catalog and produces a draft order for someone to approve.
Audit your partner mix first. Count how many of your wholesale customers already run on Shopify, and if it is more than a handful, Collective is worth about an hour of evaluation. Then map the rest of the book honestly, by which partners send PDFs, which send spreadsheets, which use EDI, and how many hours a week your team spends turning those into orders.
It depends entirely on your partner mix. If a meaningful share of your wholesale customers already run on Shopify, the automation it removes from your week is real. If almost none do, it will not touch the bulk of your order volume.
There is no separate subscription fee for Collective itself. Standard Shopify transaction and payment processing costs apply to the transactions that move through it. Check current terms in your admin.
Any Shopify merchant who publishes a catalog for other merchants to source from. There is no separate supplier network to join outside the platform.
Both are supported, but the feature was designed dropshipping first and wholesale functionality is less mature. Evaluate against your specific model.
Yes. This is the main constraint on how much of your partner book Collective can cover.
Book a short demo with a real purchase order and we run it live on your own data.
