Skip to main content

Shopify is very good at what it was built to do.

For brands selling direct to consumers, it has become the de facto ecommerce solution. Products go online, customers shop, orders come in, and payments get processed. It’s good for operating in a straight line.

Its B2B capabilities have grown, too. Brands can create B2B catalogs, set payment terms, capture purchase order numbers, assign sales staff to accounts, and give buyers faster ways to order variants. Depending on the Shopify plan, additional B2B capabilities are available as well.

For straightforward wholesale programs, maybe that’s enough. However, Shopify starts to stumble when wholesale gets more seasonal and specialized.

Think apparel, footwear, outdoor, accessories, or eyewear. Retailers are buying products that may not be available for months. A rep and buyer might go through 10 iterations of a buy together, trying to fit that retailer’s demographic and budget. An order could be divided across delivery windows, mixed with available inventory, and adjusted around the needs of a specific account.

At that point, it’s less about whether a retailer can place an order and more about whether the system can capture the buy correctly the first time, preserve the commitments being made, and then support everything that happens after the order is submitted.

In specialty retail, an order can be a production signal, an inventory commitment, a record of rep activity, and a future shipment plan. Eventually, it also becomes a transaction moving into the ERP.

That is a very different job from running a cart and checkout.

Seasonal prebook changes the shape of the order

Prebook is usually where the difference between Shopify and a dedicated wholesale B2B platform becomes obvious.

A retailer sitting down to buy the next season is making decisions against future inventory. They may want one group of products delivered early in the season and another several weeks later. They might also place an at-once order for current inventory while they are working through the future line.

The brand needs those bookings to help inform production and purchasing. In many cases, the finished inventory does not even exist yet. The brand opens a selling window, collects commitments from retailers, and uses those orders to help determine what it ultimately buys from the manufacturer.

To be clear, Shopify can support pre-orders and allows products to continue selling when inventory reaches zero. Shopify B2B also supports capabilities such as payment terms, with additional functionality available depending on the plan.

Those are useful capabilities, but a seasonal prebook workflow needs to go further.

The retailer is planning a season across intentional delivery windows. The brand needs visibility into what has been booked against those periods. Reps need to understand how the assortment will arrive and how the complete buy fits together. Operations needs those commitments to remain intact as future inventory is purchased, received, and eventually allocated.

That last part is where another major difference starts to appear.

Prebook inventory is not the same as inventory on hand

Shopify’s inventory model is built to answer a familiar commerce question: How many units do I have available to sell?

Seasonal wholesale often needs to answer a different one: How many units am I still willing to promise?

Those questions sound similar until a brand starts taking orders months before inventory arrives.

Imagine a apparel brand opening Spring prebook in September. Retailers place their buys throughout the fall. The brand uses those orders, along with its own forecast, to determine what it will purchase from the manufacturer. Months later, the product finally arrives at the warehouse.

By that point, some of that inventory is already spoken for.

The problem is that receiving 1,000 units does not necessarily mean the brand suddenly has 1,000 units available to anyone who wants them. Some may already be committed to wholesale prebooks. Some may need to remain available for at-once wholesale replenishment. Some may be appropriate to sell directly to consumers.

Shopify can allow a product to continue selling when inventory reaches zero, which is one way brands can accept pre-orders before inventory exists. But allowing something to be oversold is not the same as managing the commitments behind those future orders.

The problem becomes even more obvious when Shopify is being used for both B2B and DTC. In a blended Shopify store, inventory is shared between B2B and DTC orders, and Shopify states that inventory cannot be allocated based on customer type.

That can create a very familiar operational headache.

The production order arrives. Inventory becomes available. DTC orders are coming in. At-once wholesale orders are coming in. Meanwhile, hundreds of units may have effectively been promised to specialty retailers months earlier through prebook.

Now someone has to make sure the wrong demand does not consume inventory that was already committed elsewhere.

This is where brands start creating workarounds: inventory buffers, separate locations, spreadsheets, apps, custom rules, or manual intervention from operations to protect units for the right orders.

A dedicated Shopify B2B store can separate B2B inventory from DTC inventory, but that introduces a different consideration. The B2B store now has its own inventory environment, and the brand needs to make sure that environment stays synchronized with the ERP and the rest of the business.

For a seasonal wholesale brand, the underlying issue is bigger than displaying an inventory number.

Inventory is a series of commitments being made across time, channels, retailers, and delivery periods.

A wholesale B2B platform needs to understand those commitments and show the buyer the right quantity for the type of order they are building. When an ERP is involved, it should remain the operational source of truth while the B2B experience gives reps and buyers an accurate view of what can actually still be booked or purchased.

That is much different from simply asking what is currently sitting on the shelf.

Large wholesale orders get complicated fast

Shopify currently limits regular orders to 500 line items and draft orders to 200 line items.

For some businesses, that sounds enormous, but a footwear brand can chew through those numbers surprisingly fast.

One style might be sold in several colorways across a full size run, with multiple widths. Repeat that across the retailer’s assortment and divide the order into seasonal deliveries, and the number of individual SKUs grows long before the buy feels unusually large to the buyer.

Shopify has improved the experience with quick-order tools that let buyers enter quantities across product variants, which helps with bulk ordering. But specialty wholesale often needs a broader view of the line.

A footwear buyer is not simply trying to add variants faster. They are evaluating how styles work together, checking size runs, balancing color, deciding how deep to buy, and planning how inventory should arrive throughout the season.

For that buyer, a matrix view is an essential part of the buying process. The complexity is not created by the number of clicks required to add SKUs to a cart. It comes from trying to make a large assortment decision while keeping hundreds of variants organized.

Specialty retailers buy assortments, not individual products

A consumer usually arrives looking for a product. A specialty buyer is trying to build a department or sellable assortment.

That is one of the clearest differences between consumer ecommerce and wholesale ecommerce.

The specialty buyer wants to understand the seasonal story and compare styles without repeatedly moving between individual product pages. A good rep is also helping them make decisions based on the store’s history, its customer, what performed last season, and what is happening in the market.

That is why wholesale has historically relied on line sheets, workbooks, showroom appointments, and seasonal catalogs.

Digitizing wholesale should improve that process by centralizing the complexity in one experience and making the process easier for the buyer, not by simply moving the same work into a storefront.

The ordering experience needs to help a retailer understand the line while they build the buy. Ideally, the buyer can move from inspiration to assortment planning to order without losing the context of the season.

That is especially important when a rep is guiding the process and the final order needs to reflect decisions that were made visually, not one SKU at a time.

Customer-specific pricing is only part of account complexity

Shopify’s B2B catalog system can control product availability and pricing for different customers. Plan limits still matter, especially for brands with more complex catalog structures.

Shopify currently allows up to three active B2B catalogs across B2B markets on Basic, Grow, and Advanced, while Shopify Plus provides unlimited B2B market catalogs and allows catalogs to be assigned directly to specific companies and company locations.

For a growing wholesale brand, those distinctions can become important quickly.

Pricing, however, is only one part of account management. Segmentation often needs to run deeper than dollars.

One retailer may receive a particular assortment while another sees a broader collection. Key accounts might get different product access from independent specialty stores. Closeout inventory may be visible only to certain buyers. Rep groups can work within specific territories or account segments. Different regions can have their own products, availability, currencies, rules, and sales organizations.

Those differences are not exceptions to wholesale. They are how the channel operates.

The question is whether the system can manage them cleanly without forcing the brand to recreate its selling structure through an increasingly complicated collection of catalogs, customizations, and processes.

Sales reps need more than permission to enter an order

Shopify allows sales staff to be assigned to company locations and create orders for the accounts they manage.

For some sales organizations, that may be enough. But specialty reps tend to do quite a bit before order entry starts.

They are showing a new line at a trade show, visiting a retailer, helping a buyer decide how deep to go on a style, reviewing previous orders, educating store staff, recommending products, and changing an assortment while sitting across the table from the customer.

Order entry is the end result of that work, not the work itself.

A selling workspace built for reps should help them understand the account, present the line, build an assortment, collaborate with the buyer, and eventually turn those decisions into an accurate order.

Giving a rep permission to enter an order solves one step in that process.

It does not create the selling environment around it.

Small order details become operationally important

Wholesale orders carry information that a consumer checkout rarely needs.

Purchase order numbers are one example. Requested ship dates, delivery notes, shipment preferences, and account-specific instructions are others.

While many of these fields can be added through Shopify’s B2B or checkout customization tools, the challenge comes after the information is captured.

Where does the field live? Does the rep-created order use it the same way as the retailer-created order? Does the ERP expect the value in the same format? Will operations see it at the right point in the workflow? What happens when an order is split across multiple seasonal deliveries?

Wholesale teams eventually discover that capturing a field and operationalizing it are two different problems.

Every workaround creates another place where an otherwise valid order can become incomplete before it reaches the systems responsible for fulfilling it.

The app stack can slowly become the wholesale system

Shopify’s app ecosystem is one of its biggest advantages.

It is also easy to see how the demands of wholesale can push a brand toward more apps and custom changes.

Pre-order logic, quick ordering, customer-specific pricing, minimum quantities, bulk ordering, inventory rules, delivery dates, and other B2B workflows are all areas where brands may extend Shopify through apps or custom development.

There is nothing inherently wrong with that. Shopify was designed to be extensible, and the right app can solve a legitimate problem.

The concern is architectural: How many separate tools have to participate before a normal wholesale order can be captured the way the business actually needs it?

The problem appears when the collection of extensions starts carrying the logic of the wholesale channel.

Now one app determines how a future product can be ordered. Another helps with minimum quantities. A custom workflow protects inventory. Someone maintains a spreadsheet to keep track of what has already been committed. Another integration makes sure the resulting order reaches the ERP correctly.

Eventually, Shopify is no longer the wholesale system.

The collection of workarounds around Shopify is the wholesale system.

That means the team has to understand how each piece communicates, how changes affect other workflows, and what needs to be fixed when something behaves differently during the next selling season.

The original cheap and easy wholesale project can gradually become an integration and operations project.

Software cost is only part of that calculation. There is also manual cleanup, internal support, maintenance, troubleshooting, and orders that need to be corrected after they have already entered the business.

The real goal is a clean wholesale order

Here’s the simplest way to evaluate any wholesale ecommerce system: Look at what has to happen before and after an order reaches the ERP.

How much manual work is required to make that order usable?

If a retailer selected the right products but the delivery window is wrong, the order is not really correct.

If a rep negotiated the buy but the account terms do not carry through, someone has to repair it.

If a prebook was accepted months ago but operations still has to manually protect that inventory when the production PO arrives, the system has not really completed the job.

If quantities were built without the right inventory context, sales operations or customer service may have to untangle the problem later.

The best wholesale workflow moves that work upstream.

The retailer and rep should have enough information to build the right buy while they are building it. Account rules should already be applied. Products should be organized around the way the line is sold. Seasonal delivery information should travel with the order. Inventory commitments should be understood before new demand is accepted.

Then the ERP receives a transaction it can actually use, and the information coming back from the ERP can continue informing the rep and retailer after the order has been placed.

That is the difference between capturing an order and actually managing wholesale.

What purpose-built wholesale can look like

This is where a platform such as Envoy B2B approaches the problem differently.

Envoy can sit alongside Shopify while acting as the dedicated wholesale destination for reps and retailers. Product, customer, pricing, inventory, order, shipment, and invoice data can remain connected to the brand’s backend systems while the front-end experience is built around the realities of wholesale buying.

The difference shows up in the workflow around the order.

A footwear buyer can work through size-run matrices built for footwear while placing prebook and at-once orders, with replenishment handled in the same wholesale environment.

Future availability can be treated differently from inventory sitting in the warehouse today. A brand can collect seasonal commitments without pretending that every unit being sold is already on hand, while still giving buyers useful availability information when at-once inventory becomes available.

Reps can build recommended assortments and visually merchandise a buy with the retailer instead of treating merchandising as something that happens in a separate presentation.

The seasonal story can stay connected to commerce, too. Digital catalogs and flipbook-style line sheets can be built from backend product data and connected directly to assortments and ordering.

Those capabilities are not useful because they add more features to a portal. They are useful because they reflect how specialty retail buying actually happens.

A rep introduces the line. The buyer evaluates it and shapes an assortment. The retailer makes a commitment against a future season. The brand uses those commitments to plan production. Inventory eventually arrives and needs to be allocated correctly. In-season orders follow. Shipment and order information continues flowing back to the retailer and rep.

It is one continuous wholesale process, even though it may unfold over six months.

That is the standard worth using when evaluating wholesale technology.

Sure, Shopify can absolutely accept wholesale orders.

But running and managing the complexity of a wholesale channel asks a bigger question: Can your system represent the way your brand actually sells a season, preserve the commitments made along the way, and capture the order correctly the first time?

If every prebook season requires another spreadsheet, inventory workaround, app, or round of manual correction, the challenge has moved beyond ecommerce checkout.

At that point, the brand is not trying to make Shopify better at taking an order.

It is asking Shopify to run wholesale operations.