Field Notes

The Single Register Pattern: Multi-Channel Inventory Without Overselling

The Single Register pattern keeps one record for every unit you own, and every sales channel reads from and writes to that record. Channels stop keeping their own copies of the inventory, so they stop disagreeing. A sale on one channel removes the unit everywhere, and upcoming drops stay separate from stock you can actually ship.

Selling on several channels is normal now. A storefront, one or two marketplaces, maybe a resale platform, maybe a counter in a physical shop.

Each channel brings reach. Each one also brings its own opinion about what you have in stock. When those opinions disagree, you sell the same unit twice, cancel an order, refund a customer, and take a hit on your marketplace rating.

The pain isn’t one broken platform. It’s the space between platforms. This article explains the pattern we use to close that space, and how to tell whether you need it.

Why do multi-channel sellers oversell?

Because every channel keeps its own copy of the truth.

The usual setup looks like this. The storefront has a product catalog with quantities. The marketplace has its own listings with their own quantities. A sync plugin copies numbers between them on a schedule, often every few minutes to every hour.

Most of the time that works. It breaks at the worst moments:

  • During busy periods. Two buyers on two channels purchase the last unit inside the same sync window. Both orders go through.
  • With one-of-one items. Collectibles, used goods, and unique SKUs have no buffer. One sync delay is one oversell.
  • When a sync fails quietly. An API error or an expired token stops updates. Nobody notices until orders start failing.
  • When someone edits by hand. A quantity changed directly on one channel overwrites the plugin’s value, or gets overwritten by it.

Faster syncing helps at the margins. It does not change the design. As long as each channel holds its own count, there is always a window where they can disagree.

What is the Single Register pattern?

One record per unit. Every channel reads from it. Every sale writes to it.

Instead of copying quantities between channels, the business keeps a single inventory register it owns. The register holds each unit or SKU, its condition, its cost, its location, and its state. Channels become views of that register rather than separate catalogs.

When a unit sells anywhere, the sale is written to the register first. The register then removes the unit from every other channel. There is one place to look, one place to change, and one answer to “do we have it?”

What are the parts of the register?

Four pieces do most of the work.

1. Event-driven updates

Channels report sales the moment they happen, through webhooks or order notifications, rather than waiting for a scheduled check. The register processes each sale as an event and pushes the new state to the other channels right away.

Where a channel cannot send events, the register checks it frequently and treats it as the slowest link. Knowing which channel is slowest tells you where an oversell is most likely.

2. Holds at checkout

For scarce or one-of-one items, the register can place a short hold on a unit when a buyer starts checkout on any channel. Other channels see it as unavailable until the purchase completes or the hold expires.

Holds close the window that syncing alone cannot close: two buyers reaching the last unit at nearly the same moment.

3. Channel details as a layer, not a copy

Each channel has its own title rules, fees, shipping options, and pricing. Those differences live as a layer on top of the register record, not as a separate inventory row per channel.

That way the channel-specific details can vary while the unit itself stays single. Changing a price on one marketplace never changes how many units you own.

4. States that mean something

A unit in the register has a clear state: available, held, sold, returned, in repair, or reserved for a drop. Returns come back with their real condition instead of as a fresh copy. Units in repair do not appear on any channel.

Clear states are what let the register answer operational questions without a spreadsheet.

Why are drops not stock?

Because a drop is a promise, not a unit.

Sneaker, streetwear, and collectibles sellers often publish upcoming releases before they own the product. Customers want to see the calendar. The seller wants listings, images, and a take ready to go.

If the calendar and the inventory share a table, a pair you do not own can sell. Most sync tools cannot tell “coming soon” from “in stock,” because both look like a listing.

In the Single Register pattern, drops live in their own state. They can publish to the storefront as upcoming releases without adding a single unit of sellable inventory. A drop becomes stock only when the unit is acquired and entered into the register.

Drops are not stock.

How does this work for a real seller?

HEAT4YAFEAT is a collector in Indianapolis selling through eBay and StockX seller portals.

Demand was real. Infrastructure was not. There was no owned catalog, no owned checkout, and no record of a pair that a second channel could read.

Conjai built the operating layer first. One inventory register for every pair he owns. eBay and StockX connected to that record. A drops pipeline that publishes upcoming releases with listings, images, and a take in his voice, without treating those rows as stock. A pair becomes inventory only when he acquires it. The brand site is the public layer of the register, not a separate catalog.

The published results: 650+ pairs placed, 99.1% positive on eBay, selling since 2016. Demand was never the problem. Agreement was. The full story is in Your Channels Don’t Talk.

When do you need a register instead of a sync plugin?

Not always.

Buy the sync tool if most of these are true:

  • You sell standard SKUs with interchangeable units.
  • One price per product per channel is fine.
  • You own everything you list, and it is on the shelf.
  • Oversells are rare enough that fixing them by hand costs less than engineering.

Build a register when the opposite is true: unique or low-quantity items, unit-level pricing, pre-release listings, several marketplaces with different rules, or oversells that are costing you ratings. We’ll tell you plainly when the platform is enough.

What should the register be able to answer?

A working register answers everyday questions without anyone opening a spreadsheet:

  • What do we own right now, by condition and location?
  • What sold this week, on which channel, and at what margin after fees?
  • Which units have been listed longest without selling?
  • What is on hold, in repair, or waiting to come back from a return?
  • Which upcoming drops are published, and which have been acquired?

If answering any of those requires exporting from several channels and merging by hand, the register is not yet the single source. Those questions make a good acceptance test for the build.

How do you move to a single register?

In stages, without stopping sales.

  1. Count once. Build the register from a physical count, not from any channel’s numbers. Every channel’s count is suspect until checked.
  2. Connect one channel. Start with the channel that sells the most. Make it read from and write to the register.
  3. Add channels one at a time. Each new connection is tested against real orders before the next one starts.
  4. Move exceptions into states. Returns, repairs, holds, and drops each get a defined state instead of a note in a spreadsheet.
  5. Retire the old sync. Once every channel reads from the register, the plugin that copied numbers between them can go.

How much are oversells costing you?

Use your own numbers, not a benchmark.

Count oversold orders per month and multiply by the cost of each: refund fees, shipping, and any marketplace penalty. Then count the hours per week spent fixing listings and counts by hand, and multiply by the loaded cost of those hours. Add the two. That monthly figure is the reconciliation tax. The retail systems page has a calculator that runs the arithmetic.

Take the next step

If your channels are reading from separate catalogs, they will keep disagreeing.

Request an Operational Fit Review | Explore retail systems

FAQ

What is a single inventory register?

It is one record of every unit you own that all sales channels read from and write to. Channels stop keeping separate inventory counts.

Why do sync plugins still allow oversells?

They copy counts between channels on a schedule. Between syncs, two channels can sell the same unit, especially during busy periods or with one-of-one items.

What does “drops are not stock” mean?

Upcoming releases can be listed and promoted without counting as sellable inventory. A drop becomes stock only when the unit is acquired.

Do we need a register if we only sell on two channels?

Not always. If you sell interchangeable SKUs and rarely oversell, a sync tool may be enough. Unique items or pre-release listings change the answer.

Where should we start?

Start with an Operational Fit Review. It maps your lifecycle, stack, handoffs, and manual work, then tells you what to fix first.

Joshua Pyne, MBA — Founder and Principal of Conjai Growth Systems Engineering

Who Builds It: Joshua Pyne, MBA, Founder & Principal

Joshua Pyne has sat on both sides of the table. As an executive, he sold and scaled digital, data, and media programs for Fortune 500 brands. Now he builds the same kind of systems for growing companies, and he writes them himself: commerce platforms, multi-agent tools, and the rules that let automation run unattended.

Career figures from before Conjai, not client results:

$25M Multi-year client retention across complex delivery programs (enterprise career record; Accenture, Deloitte, Tata, Cognizant and PwC)
$5.5M/mo Media strategy under management, tying spend to measurable outcomes
$400K → $4M Startup go-to-market scaled to 10x annual revenue and acquisition

The through-line is adoption. An MBA in Organizational Leadership and twenty years of change work taught him one rule: a system only matters if people use it.

More about Joshua and Conjai