Skip to main content

Inventory sync

One stock count. Every channel. Updated in under 60 seconds.

Stop reconciling four spreadsheets. Webhooks-first sync keeps your inventory consistent across every storefront you sell on — and reserves stock the moment a sale fires, before another channel can oversell it.

Start free trial Book a demo
Inventory grid

The problem in 30 seconds

Multi-channel inventory is a tax on every sale you make.

  • A unit sells on Amazon. By the time the spreadsheet update lands, eBay already accepted the same SKU. Now you're refunding a customer.
  • Your operator updates stock in five seller centrals every morning. That's 20 minutes you'd rather spend negotiating with suppliers.
  • A variant goes out of stock at one warehouse. Other warehouses have plenty. But the channel listing already paused.

How it works

The plumbing that makes oversells impossible.

Real-time

Webhooks-first, polling as backup.

The moment a sale fires on any connected channel, the webhook hits our queue and the SKU is reserved across every other channel — typically in under 60 seconds. Channels without webhooks (or with patchy ones) fall back to fast polling.

  • Reserves stock the instant a sale fires
  • Fallback polling for channels with patchy webhooks
  • Per-channel sync latency surfaced in the dashboard
Sync activity log — placeholder

Multi-warehouse

Route stock by location — without overselling the wrong shelf.

Split inventory across warehouses, mark stock as channel-reserved, and let routing rules pick the right location per order. A Brooklyn warehouse can sell on the East-coast Amazon listing without exposing its count to West-coast eBay.

  • Channel-specific stock reservation per location
  • Order routing by closest, fastest, or cheapest
  • Transfer orders move stock between locations with audit trail
Multi-warehouse routing diagram — placeholder

Variants

Variant-level accuracy. No parent-SKU oversells.

Sync the size-medium-blue variant, not the parent t-shirt. Bundle SKUs decrement their components automatically; gift-bundle stock equals min(components) ÷ kit-size, calculated on every sync.

  • Per-variant tracking across every channel
  • Bundle / kit SKUs decrement components on sale
  • Restock-on-cancel returns the unit to availability automatically
Variant + bundle inventory — placeholder

Under the hood

What inventory sync actually does.

Real-time channel webhooks for Shopify, eBay, WooCommerce, BigCommerce
Configurable channel reservation per warehouse
Low-stock alerts with channel-specific thresholds
Bundle / kit SKU auto-decrement
Restock-on-cancel returns the unit to availability
Transfer-aware: stock in transit shows as committed, not available
Exclude-from-channel rules (e.g. don't sell this SKU on Amazon)
Decremental adjustment audit log — every change, by whom, when

Who it's for

Built for the team that runs operations.

For founders

Stop being the inventory-syncing bottleneck. Sleep through a sale without checking your phone.

For operations leads

Real-time visibility into channel reservation. Build the rules; let them run.

For warehouse managers

Stock count matches the shelf. Transfers create an audit trail, not a Slack thread.

Pairs with

Inventory sync is one piece. Here's what it talks to.

Order management

One queue for every channel's orders, with fulfillment routing and status sync.

Learn more

Warehouse ops

Pick lists, cycle counts, transfers, returns — the workflows your warehouse actually runs.

Learn more

Automation

Rule-based triggers off inventory events. Auto-pause listings, auto-reorder, auto-notify.

Learn more
We were doing manual sync across four channels every morning. Now we don't think about it. The first time a TikTok Shop sale auto-paused our Shopify listing 30 seconds later, we knew this was different.
Beta customer

Operations, Early access program

Inventory sync — common questions

Webhook-driven channels (Shopify, BigCommerce, WooCommerce) typically sync in under 30 seconds. Polling-driven channels (eBay's notification API, etc.) are typically under 60 seconds. We surface real per-channel latency in the dashboard so you can see it, not just trust us.
Our queue worker falls back to scheduled polling at higher frequency for that channel until webhooks recover. You see the latency change in the dashboard; we email you if the channel stays degraded.
Yes. Per-channel reservation is configured at the warehouse-location level. A Brooklyn warehouse can expose 50 units to Amazon US and 30 to eBay US while keeping 100 in reserve for direct Shopify.
A bundle's available stock is calculated as min(component stock) ÷ kit-size on every sync. When the bundle sells, each component's count decrements by the kit-size automatically. Mixed-channel bundle sales are deduplicated correctly.
There's an exclude-from-channel rule (don't sell this SKU here), a max-per-channel cap, and a minimum-reserve threshold. Anything beyond that hooks into automation — see the automation feature page.

Ready to never oversell again?

14-day free trial. No credit card. Connect one channel and watch sync run.

Start free trial Book a demo