Field Notes

Drops Are Not Stock

Retail wall display of sneakers on pegboard pegs, rows of different colorways
A drop is a dated release, not a unit count sitting on a shelf. Photo by Mick Haupt on Unsplash

A drop is an upcoming release a seller publishes before owning the product. It is a promise, not a unit. Drops belong in the inventory register as their own state: visible to customers, never counted as sellable stock. Some drops become inventory once the seller acquires the pair. Many never do.

Sneaker, streetwear, and collectibles sellers live on the release calendar.

Customers want to know what is coming. You want the listing, photos, and your take ready before release day, so the page is live when interest peaks.

That means publishing products you do not own yet. Some you never will.

Most inventory tools were not built for that. They know two states: in stock and out of stock. A drop is neither. Force it into one and something breaks, usually an order for a pair that does not exist.

Drops are not stock. Here is how to run a drops calendar that drives demand without touching what you can actually ship.

What is a drop, operationally?

A record with a date, a product, and an intention.

It usually carries:

  • Release name, brand, and style code.
  • Release date and time, and where it drops.
  • Images, a description, and your take.
  • A price expectation, if you plan to resell.
  • Whether you intend to buy, and roughly how many.

What it does not carry is a unit. Nobody has checked its condition or put it on a shelf. It might arrive next week, arrive in different sizes than planned, or never arrive.

A drop says “this is coming and we are watching it.” Stock says “this is here and you can buy it now.” Mix them, and a marketing promise turns into a fulfillment promise.

Why do most sync tools treat drops as stock?

Because both look like a listing.

Rows of open, empty cardboard boxes seen from above
Inventory only exists once the drop has landed and the boxes are counted. Photo by Luke Heibert on Unsplash

Storefronts and marketplaces have one object for “a thing on the site”: the product listing. Sync tools copy listings and quantities between channels. Create a listing for an upcoming release and the tool does its job. It publishes everywhere and treats the quantity field as sellable.

Sellers work around this in three familiar ways:

  • Quantity zero, “coming soon” in the title. Works until someone edits the quantity, or a channel ignores the title.
  • A drops collection on the storefront only. Works until a marketplace sync picks it up.
  • A spreadsheet calendar and no listings. Safe, but customers cannot find or follow the release.

Each one depends on someone remembering the rule. That holds for a few releases. It breaks when the calendar gets busy, which is when drops matter most.

What does a separate drop state look like?

One register, with drops as a state no channel can sell.

In The Single Register Pattern, every unit you own has one record that every channel reads. Drops live in the same register, in their own state.

StateOn your siteSellable on any channelCounts as stock
DropYes, as upcomingNoNo
AvailableYesYesYes
Sold or heldNoNoNo

That gives you three things at once:

  1. Customers see drops. The brand site reads drop records and shows the calendar, images, and your take.
  2. No channel can sell a drop. Marketplaces and checkout only read available units.
  3. Drop and stock stay linked. When a pair arrives, the new unit points back to its drop, so the release history stays with the pair.

The system enforces the rule. Nobody has to remember to set a quantity to zero.

When does a drop become inventory?

When a pair is acquired, checked, and entered. Not before.

  1. Publish the drop. The record exists with its date, images, and take.
  2. The release happens. You buy, win, or trade for some pairs, or none.
  3. Enter each pair. Size, condition, cost, and location go into a new unit record, linked to the drop.
  4. The unit goes live. Channels can list and sell it, with your pricing rules and margin floors applied.
  5. The drop stays as history. It can show as a past release, with links to any pairs in stock.

Some drops become inventory. Many do not. You might track a release, decide the price is wrong, and never buy. The drop ages into the archive. Nothing gets cancelled or refunded, because nothing was ever for sale.

What about size runs and partial wins?

Treat each pair as its own unit, and the drop as the parent.

A release rarely lands the way you planned. You wanted four pairs across sizes and got two, both in 10.5. Or a raffle came through for one size you did not expect.

  • One drop, many units. Each acquired pair gets its own record with its size and condition, linked to the same drop.
  • Sizes you did not get stay on the drop. Customers following a size see that it did not arrive, instead of seeing a stale listing.
  • Late arrivals still link. A pair bought weeks after release can attach to the same drop, so its history stays in one place.

Does this work with my channels?

It works with the channels that matter to most resellers, because the register sits above them.

  • eBay and StockX read available units from the register and report sales back to it.
  • Your storefront, whether Shopify, WooCommerce, or a custom site, reads both drops and available units, and shows each differently.
  • In-person sales at shows or a counter write to the same register, so a pair sold at a table comes off every channel.

Platforms named here are representative. What matters is that no channel keeps its own copy of what you own.

HEAT4YAFEAT, a collector in Indianapolis selling through eBay and StockX, runs this way. A drops pipeline publishes upcoming releases with listings, images, and a take in his voice into the register as drops, not stock. A pair becomes inventory only when he acquires it. The published results: 650+ pairs placed, 99.1% positive on eBay, selling since 2016. Demand was never the problem. Agreement was.

How do you publish a calendar customers trust?

Never let the calendar promise what the shelf cannot deliver.

  • Label every drop by state. “Upcoming,” “released,” and “in stock” should look different. Customers learn the difference.
  • Publish early, promise nothing. Drop pages can go live weeks ahead. They show the release and invite customers to follow. They do not take payment.
  • Link released drops to real stock. When pairs arrive, the drop page points to them, with real sizes and condition.
  • Retire quietly. Drops you never bought move to the archive.

What breaks if drops and stock share a table?

Four things, in roughly this order:

  1. A pair you do not own sells. A sync reads the drop as available, a buyer checks out, and you cancel. Marketplaces count that against your seller metrics.
  2. Counts stop meaning anything. “How many pairs do we have?” needs a spreadsheet and a person.
  3. Reports get muddy. Sell-through and margin mix releases you tracked with pairs you held. Buying decisions get worse.
  4. Someone becomes the fix. One person checks drops every morning. The business now depends on their attention.

None of this shows on launch day. It shows on the busiest release weekend of the quarter.

Why not just buy a sync tool?

Buy one if your catalog fits it.

A $200/month sync tool handles standard SKUs, standard channels, and one price per product. If you own everything you list and it is on the shelf, that may be all you need.

Drops are not the standard case. Neither are one-of-one pairs, pair-level pricing, or consignment. We build for the part the platform will not do, and we’ll tell you plainly when the platform is enough. The retail systems page shows how the pieces fit, and Your Channels Don’t Talk covers the wider cost of channel disagreement.

How much are drop mistakes costing you?

Use your own numbers, not a benchmark.

Count the orders you cancelled last quarter because the pair was a drop, not stock. Multiply by the cost of each: fees, refund, and any marketplace penalty. Then estimate the hours per week someone spends checking drop listings by hand, times the loaded cost of that time.

Add the two. The overselling diagnostic walks through the other symptoms.

Take the next step

If your release calendar and your inventory share a table, the next busy weekend will find the gap.

Request an Operational Fit Review | Explore retail systems

Questions About Release Calendars and Sellable Stock

When Should a Planned Sneaker Release Become Inventory?

Only when the business has acquired and verified a sellable unit. A release date, expected allocation, or sourcing target belongs in the planning calendar until then. Listing availability should follow the owned-unit record rather than the publication schedule.

Can Release Content Be Published Before We Own Any Pairs?

Yes, provided it describes the release rather than implying stock is available to buy. Keep editorial dates and sourcing information separate from live quantity and reservations. When stock is verified, the selling layer can reference the owned units.

How Should Size and Condition Be Recorded for Recommerce Stock?

Record the attributes that distinguish the actual unit, including size and verified condition, with a unique identifier. Those attributes connect listings and orders to the same physical item. A product-level release record cannot substitute for pair-level stock.

Take the Worksheet With You

Get the sample pack

Multi-Channel Inventory Register and Margin Floor Matrix. Three pages for multi-channel sellers: a sample map, a blank worksheet, and what to bring to a review. A model, not a client; every figure field is blank for your own numbers.

Leave the box unticked to get the pack only. Either way you get the download link.

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