Let me say something that makes platform vendors uncomfortable: when they say "real-time inventory sync", they're not telling you the whole truth.
What they actually mean is a very short interval. They're polling your ERP or POS system every 2–10 minutes, bundling whatever changed into a batch job, and pushing it to Shopify. And when things are quiet — low order volume, low warehouse activity — that works fine. You'd never notice the difference.
The problem surfaces exactly when you can least afford it.
What They Actually Mean By "Real-Time"
Here's how most inventory sync systems actually work under the hood:
- A scheduler fires every N minutes (typically 2–10)
- It queries your ERP, POS, or WMS for any stock changes since the last run
- Those changes get bundled into a single API call — a batch — sent to Shopify
- Shopify updates product quantities
- The cycle repeats
During a typical Wednesday afternoon this is indistinguishable from real-time. Orders come in slowly. Warehouse picks are spread out. Sync jobs complete in well under their interval. Everything looks fine.
The scheduler fires on time, the sync finishes before the next one starts, and inventory on Shopify is only a minute or two stale. For low-volume periods, this is a reasonable trade-off.
But there's a structural assumption baked into this model: that each sync job will always finish before the next one begins. And that assumption breaks the moment your order volume spikes.
The Snowball Nobody Talks About
Imagine it's your flash sale. 11am launch. Orders start flooding in. Pickers are running across the warehouse floor. A thousand line items are being picked, confirmed, and updated every few minutes. Now watch what happens to your sync system:
"Your biggest sales day becomes your worst operational nightmare."
— Mohammed Atif Sami, CEO at Unity RetailThe cruel irony is that this failure mode is perfectly correlated with your business success. The more orders you drive, the worse your inventory accuracy gets. The better your marketing performs, the more oversells you create. The system works exactly until you need it most.
Two Real Brands. Two Real Breakdowns.
This isn't theoretical. Here's what we saw when we diagnosed inventory sync problems for two brands — Cambridge Garments and Highfy — before they switched to Unity Retail.
Cambridge Garments
Cambridge operates across multiple retail stores, each pushing inventory changes simultaneously. The sync system wasn't just processing one warehouse — it was aggregating changes from every store location into the same batch queue.
During peak periods, fresh sync waves were queuing before previous ones had even started. A full inventory synchronisation cycle was taking 2 to 3 hours. By the time Shopify reflected reality, the team had already processed hundreds of orders against stale stock.
during peak periods
Highfy
Highfy runs from a single warehouse with a massive SKU catalogue. On paper the system looked clean — one location, straightforward setup. But the sheer volume of SKU-level changes meant the batch size was enormous on any busy day.
The backlog was perpetual. Even on a "normal" day with moderate volume, the queue never fully cleared. This wasn't an implementation problem — the design itself was the problem.
couldn't clear on any day
What's important to note about both cases: these weren't broken systems. The polling architecture was working exactly as designed. The problem is the design.
What Event-Driven Actually Looks Like
At Unity Retail, we don't poll. We eliminated scheduled batch jobs from inventory sync entirely.
Instead, every discrete warehouse event — a picker scanning an item, a pack being confirmed, a return being received — immediately triggers an isolated push to Shopify. There's no aggregation. No queue. No scheduled timer. The moment something changes in the warehouse, Shopify knows about it.
Because each event is independent and tiny — one item, one update — there's nothing to queue. Order volume going up doesn't slow down inventory sync. A flash sale hitting 10x normal traffic doesn't change the latency. Every stock movement reflects in Shopify in under a second, regardless of what's happening elsewhere in the warehouse.
Fixed-interval scheduler
Checks for changes every 2–10 minutes. Bundles all changes into one API call. Queue grows during peak volume. Lag compounds. Oversells are a mathematical certainty on your biggest days.
Instant per-event push
Each warehouse action triggers an immediate, isolated update. No scheduler. No queue. No lag accumulation. Inventory accuracy is constant regardless of order volume or time of day.
Why This Matters More Than You Think
Every minute of inventory lag is a minute during which a customer can purchase something that no longer exists in your warehouse. That means:
- Oversells — you take money for stock you can't fulfil
- Manual cancellations — someone has to call or email the customer
- Refunds — revenue reversal, payment processing fees, accounting overhead
- Support tickets — customer service cost that compounds with scale
- Brand damage — a cancelled order after payment is a trust-destroying experience
For a brand doing a few hundred orders a month, a polling system probably gets away with it. The volume is low enough that even a 2–3 minute lag rarely causes a real oversell. But the moment you're running thousands of monthly orders — or your sales are seasonal and spiky — the math changes completely.
The difference between polling and event-driven isn't a technical nicety. It's the difference between operational control and controlled chaos.
"Real-time means the system reacts to what happened, the moment it happened — not on a schedule, not in batches."
— Mohammed Atif Sami, CEO at Unity RetailA real real-time system doesn't ask "what changed in the last 2 minutes?" It reacts to changes the instant they're recorded. There are no batches. There are no windows. There is no lag to manage.
If your platform syncs on a schedule — even a 30-second schedule — it is not real-time. That's polling with a very short interval, and under pressure it will fail you in exactly the same way.
Ask your vendor what their sync architecture looks like. If they can't explain the difference between polling and event-driven, or if they tell you their 2-minute interval is "effectively real-time" — you now know what that actually means for your flash sale.
See Event-Driven Inventory Sync in Action
Book a 30-minute walkthrough and we'll show you exactly how Unity Retail handles inventory across your warehouses, stores, and Shopify — in real-time, not batch time.