---
title: "Hold Back Stock for Retail Accounts | SKU.io"
url: "https://www.sku.io/hold-stock-for-retail-accounts/"
description: "A percentage cap on your online stores doesn't keep stock for a retailer. A buffer sized to the retailer's next order does. How to set it, and what it costs."
published: 2026-11-21
---

[Inventory Management](https://www.sku.io/category/inventory-management/)

# Holding Back Stock for Your Retail Accounts When Every Channel Sells From One Pool

By [Kalvin Mizzi](https://www.sku.io/our-story/) · November 21, 2026

![Holding Back Stock for Your Retail Accounts When Every Channel Sells From One Pool](https://www.sku.io/_astro/cap-vs-buffer.z4ClzyzK_1LRpOG.webp)

If your Shopify store, Amazon and a retail account all ship from the same stock, the online channels will sell the retailer’s units before the retailer’s purchase order arrives. To stop that, hold back a fixed number of units from each online channel, sized to the retailer’s next order. A percentage cap on the stores won’t do it.

In May 2024 we were rewriting how SKU.io works out the number it sends each channel, and one of our engineers asked about the inventory rules on each connection: the caps, the floors, the buffer. I said that for a first version we could arguably drop them, “because again, no one’s really using them right now.” In the same breath I said that in my own business I’d want a buffer only on “a particular listing that’s high volume.” The rules stayed in.

I had the wrong customer in mind. The people who need those rules most are brands with a retail account or two, where the online channels sell all day and the retailer orders by EDI every week or two. An operations lead at one multichannel brand described the default exactly: “each channel sells as much as it can.” Whoever sells first gets the stock, and online always sells first.

## A percentage cap is not a reserve

What most people try first is a split: show Shopify 60% of what you have and keep the rest for retail. In SKU.io that’s a Max rule of **% of Available**.

But it’s 60% of what’s available now, not 60% of a delivery. Say 600 jars land at your 3PL on a Monday and online sells about 55 a day. Shopify is shown 360. A week later 215 are left, and Shopify is shown 129, so it keeps selling. A cap on Amazon doesn’t change that: both channels are shown 60% of the same jars. The listings look a bit scarcer on the way down, and the retailer’s order still comes up short.

A fixed split, where each channel gets its own slice of the stock, fails the other way. When someone asked me for one on a call, my first worry was the slice nobody uses: “what if Channel A doesn’t always use 40%, you know, then it’s kind of like allocating it unnecessarily.” Those units sit on the shelf while another channel runs out.

## Hold back a fixed number instead

**Subtract Buffer Stock** is a fixed number of units a channel is never shown. Put 240 on Shopify and 240 on Amazon and each is shown what’s available minus 240. They share the pool, so between them they stop selling at 240 left, not 480. That’s what the retailer’s next order lands on.

Run the same week with the buffer and online stops after 360. When the retailer’s purchase order for 240 comes in the next Monday, the 240 are still there. With the cap, online would have sold 385 by then and the order would be 25 short.

Once you approve the retailer’s order, its units are allocated to it and leave what’s available for every channel. That part is automatic. Holding them until the order shows up is the part you set.

![Two charts of the same 600 jars over one week. With a 60% cap the online channels keep selling until the shelf is nearly empty. With a 240-unit buffer they stop at 240, and the retailer's order is filled on Monday.](https://www.sku.io/_astro/cap-vs-buffer.z4ClzyzK_ZbGdHQ.webp)

## How big to make it

I’d size the buffer to the retailer’s next order. Retail buyers reorder on a pattern, and the last three purchase orders tell you most of it.

It can still be too big. If the retailer orders 180 instead of 240, 60 units stay hidden from every online channel until someone lowers it. And it doesn’t reset. After the retailer’s order takes its units, the buffer is still 240, so online is held back again, now for the order after next. If that order is two weeks out, lower the buffer when each retail order lands and raise it a few days before the next one is due. SKU.io won’t do that for you.

Most of your catalog doesn’t need one. Any listing can drop its channel’s rules and take its own, so put the buffer on the items the retailer actually buys.

## When you want a wall

If you’d rather the retail stock were physically out of reach, keep it in its own warehouse in SKU.io and leave that warehouse out of each online channel’s stock warehouses. Nothing in it is ever shown online.

That only works if the stock really is counted apart: another building, or a 3PL that keeps it separate for you. If your 3PL holds all of it as one count, a second warehouse in SKU.io is a number the 3PL doesn’t know about, and you’ll reconcile it by hand. Use the buffer. A wall also keeps whatever the retailer didn’t order until someone transfers it back.

## What the retailer sees

Retail buyers order from your inventory advice, the EDI 846 that tells them what you can ship. With SPS Commerce connected, SKU.io sends each retailer one every day at 05:00 UTC, counted from the warehouses you choose, less a buffer of its own. That one keeps the retailer from ordering your last few units. It’s a separate setting from the online buffer, which keeps your stores from selling the retailer’s. If you walled the retail stock off, count the 846 from that warehouse.

## Channels that sell through Shopify

A buffer is set per connection, and per location on Shopify. Faire or TikTok Shop set up as Shopify sales channels read the same Shopify quantity, so they get the same rules, and you can’t hold stock back from one and not the others. To treat them differently, connect them directly.

## Related

None of this matters if you sell on Shopify alone with no retail accounts; inFlow or Zoho Inventory will do more for you than SKU.io. If the retailer has already ordered and you want part of an incoming shipment kept for them, that’s [reserving incoming stock for a wholesale order](https://www.sku.io/reserve-incoming-stock-for-wholesale/). The settings are in the docs under [set the stock each channel sees](https://www.sku.io/docs/guides/integrations/basics/map-products-stock-and-payouts/set-the-stock-each-channel-sees/), and the full calculation is in [how the stock each channel sees is calculated](https://www.sku.io/docs/guides/integrations/basics/map-products-stock-and-payouts/how-channel-stock-is-calculated/).

To see it on your own catalog and channels, [book a call](https://www.sku.io/book/).

![Kalvin Mizzi, founder of SKU.io](https://www.sku.io/_astro/the-story-of-sku.BNjQHdxV_Z4P6NF.webp)

Written by

[Kalvin Mizzi](https://www.sku.io/our-story/) Founder, SKU.io

Kalvin has run his own multi-channel e-commerce business since 2008 and built the system behind it, which became SKU.io. He still gives every demo personally.

-   [LinkedIn](https://www.linkedin.com/in/kalvinmizzi/)
-   [X](https://x.com/kalvinmizzi)

## Keep reading

-   [A B2B Ordering Portal Your Retailers Will Actually Use](https://www.sku.io/b2b-ordering-portal/)Nov 20, 2026
-   [Backorders Across Online and Wholesale: Who Gets the Next Delivery](https://www.sku.io/backorders-online-and-wholesale/)Nov 20, 2026
-   [Field Sales CRM for Wholesale Distributors: A Rep's Day, Not a Pipeline](https://www.sku.io/field-sales-crm-for-distributors/)Nov 20, 2026
