A marketplace inventory system is the machinery that lets several marketplaces sell from one honest stock pool: every sale anywhere decrements it, every channel advertises from it, and the whole arrangement is auditable when a number looks wrong. Sellers assemble one deliberately or accrete one accidentally, and the difference shows the first busy week.
The five components
1. The pool. One authoritative count per SKU, owned unambiguously: by your store if you have one, by the hub if you are marketplace-only. Everything else in the system serves this number.
2. Identity (SKU matching). The mapping that says your store’s product, the Amazon offer, and the eBay listing are one shelf item, joined on canonical SKUs, with uncertain cases surfaced to a human instead of guessed.
3. Sync (the nervous system). Event-driven propagation in seconds, both directions: sales in, availability out, the real-time versus batch decision that defines the system’s character.
4. Rules (policy at the boundary). Per-channel prices from one base (markup rules), safety buffers on what channels advertise, low-stock thresholds that alert. Rules are your judgment, codified once.
5. Observability. Per-channel sync health, event logs, failure alerts, the confession layer that turns mysteries into lookups. A system without it is trusted on faith exactly until the first drift.
Around the core, the derived layer: days-of-cover forecasting, oversell-risk flags, and the KPI read, computed from the pool’s live history rather than exported snapshots.
Accretion versus design
The accidental system grows one connector at a time: a store-to-eBay plugin, then an Amazon app, then a spreadsheet reconciling the two, then a virtual assistant who owns the spreadsheet. Each piece was cheap; the assembly has five failure surfaces, no shared identity, and nobody who can answer “what changed at 14:02”.
The designed system is a hub: channels as spokes over one pool, matching and rules in one place, one log. Same monthly cost as two or three plugins, the pricing-shape math, and one seam instead of five.
Setting one up, the afternoon version
- Clean identity first: canonical SKUs everywhere, variants as child SKUs, an hour of spreadsheet honesty, the migration guide if that is where you live today.
- Connect the source of truth, your store (Shopify, WooCommerce, OpenCart) or the hub itself.
- Connect marketplaces (Amazon, eBay, Etsy) through their standard authorizations.
- Match and resolve: SKU pairing runs automatically; the exception queue takes minutes when step 1 was honest.
- Set the rules: markups, buffers, thresholds.
- Run the five-scenario test, stopwatch, both directions, forced failure, then trust it with real stock.
Common questions
Is this different from a WMS?
Yes, different axis: a WMS runs a warehouse’s floor (bins, waves, picking); a marketplace inventory system runs channel truth. Small multichannel sellers need the second long before the first.
Can my ecommerce platform BE the system?
It can own the pool; its native marketplace connectors are usually the weak spokes (interval sync, one-way flows). The platform-as-pool, hub-as-nervous-system split is the common mature shape.
What does it cost?
For small and mid-size sellers, real systems live in the $29-99/month band, judged on sync architecture, caps, and observability rather than sticker, the buying guide. Unifystock is $49/month flat with unlimited orders.
How long until it pays for itself?
One prevented oversell typically covers months; the quieter payback, hours not spent reconciling channels, arrives weekly from day one.
Assemble it on purpose
One pool, matched identity, second-level sync, rules, and a log that confesses, connected in an afternoon. From $49/month with unlimited orders. See pricing.