WooCommerce + FBA + NetSuite at a Glance
- Overselling happens when three systems each think they own the authoritative stock count.
- NetSuite should hold total inventory; WooCommerce and FBA hold reserved/committed allocations against it.
- Amazon’s inventory feed has its own delay profile — build a buffer, don’t trust real-time assumptions.
- Reconcile all three systems against one number daily, not just store-vs-NetSuite.
Selling through WooCommerce and Fulfilled-by-Amazon at the same time, with NetSuite as the ERP underneath both, means three systems now have an opinion about how many units you have. WooCommerce thinks it knows. Amazon’s Seller Central inventory feed thinks it knows, on its own delayed schedule. NetSuite is supposed to be the truth, but only if every channel actually reports back to it fast enough to matter. Overselling — the single worst failure mode in multi-channel commerce — happens in the gap between these three clocks.
NetSuite Holds the Number, Channels Hold Reservations
The correct architecture: NetSuite maintains total available inventory per SKU. WooCommerce and Amazon each receive a channel-specific allocation — not the full total — and that allocation shrinks as orders come in on that channel and grows back only when NetSuite explicitly reallocates.
Allocation, not shared total, prevents the race condition.
If both WooCommerce and Amazon are told “50 units available” as a shared total, and both sell 30 in the same hour, you’ve sold 60 units of a 50-unit stock before either sync catches up. Split it into fixed allocations per channel — say 30 to WooCommerce, 20 to Amazon — and the worst case is one channel selling out early, not both channels overselling simultaneously.
Respect Amazon’s Feed Delay — Don’t Assume Real-Time
Amazon’s inventory feed API does not update in real time. Depending on feed type and Amazon’s processing queue, changes can take anywhere from a few minutes to well over 30 minutes to reflect on the live listing. Teams that build their sync logic assuming near-instant propagation end up overselling during exactly the busy periods — flash sales, holiday spikes — when Amazon’s own processing queues are also under the most load and slowest.
| Channel | Typical sync delay | Buffer recommendation |
|---|---|---|
| WooCommerce (webhook-driven) | Seconds to low minutes | Minimal buffer needed if webhooks are reliable |
| Amazon Seller Central feed | 15-30+ minutes, longer at peak | Hold back 5-10% of allocation as a safety buffer |
| NetSuite reconciliation job | Depends on your sync interval | Should run more frequently during known peak windows |
Flash sales expose Amazon’s delay first.
A WooCommerce flash sale that drains stock in minutes will oversell on Amazon almost every time if your Amazon allocation buffer wasn’t sized for the feed delay. Reduce Amazon’s allocation temporarily during any planned high-velocity sale rather than relying on the standard sync cadence to keep up.
Reconcile All Three, Not Just Two
Most teams build a solid WooCommerce-to-NetSuite reconciliation report and stop there, treating Amazon as “handled” by the Amazon integration app. That’s the gap. Build one report that pulls current stock from NetSuite, current allocation from WooCommerce, and current allocation from Amazon Seller Central, and flags any SKU where the three numbers don’t add up to the expected total. Run it at least every 30 minutes during peak periods, daily otherwise.
What to Do When You Oversell Anyway
Even with buffers, oversells happen. The response that protects the customer relationship: detect it within minutes (not when the customer emails asking where their order is), auto-flag the affected order in NetSuite, and have a pre-written communication template ready — offering a substitute, a discount, or an immediate refund — rather than making customer service improvise under pressure.
Sources
- Amazon Selling Partner API: Inventory ReferenceAmazon Developer Docs — FBA inventory feed and processing behavior.
- Oracle NetSuite DocumentationNetSuite multi-location and inventory allocation reference.
- WooCommerce Inventory Management DocumentationWooCommerce.com — stock management and reservation settings.
Leave a Reply