Real-time inventory sync across every channel and location

What does "one ledger" mean in practice?

Many product brands run inventory in several places at once: the Shopify admin, Amazon Seller Central, a 3PL portal, a wholesale spreadsheet and the accounting file. Each holds its own count, and someone reconciles them by hand.

SuppliFlex replaces that with a single append-only ledger per SKU and location. Every receipt, sale, transfer, adjustment and cycle count is a new entry; nothing is edited in place. Your own warehouses, 3PLs and Amazon FBA are locations in the same ledger, and lots, batches, serials, bundles and kits are tracked inside it. Channels read available stock from that ledger and write their orders back to it.

Because entries are appended rather than overwritten, the question "why is this number different from yesterday?" has an answer: the entries that changed it.

Why does nightly sync cause oversells?

A nightly batch sync publishes stock once a day. Between runs, each channel sells against the last number it was given. Take a SKU with ten units left. Shopify sells eight in the morning. Amazon still shows ten, because it will not hear about those eight until tonight, and it sells six more. You now owe fourteen orders against ten units.

The gap grows with the things brands want more of: more channels, more locations and more promotions. A sale, a marketplace spike or a wholesale order that ships from the same pool can drain stock in hours. A daily snapshot cannot keep up with that, and the cost shows up as cancellations, marketplace penalties and customer service time. The oversell calculator lets you put your own numbers on it.

How fast is near-real-time?

SuppliFlex syncs two ways in seconds, not nightly batches. The design target for sync freshness is under 60 seconds at the 95th percentile: the time from a change in one place to that change showing everywhere else, for 95 out of every 100 updates. It is a design target, not a measured result.

Two-way matters as much as speed. An order placed on Amazon reduces available stock in the ledger, and the new number is pushed to Shopify and WooCommerce. A receipt at your 3PL increases stock and is pushed out the same way. Connectors are contract-tested.

Which channels and locations stay in sync?

At the production beta on 13 November 2026, the live connectors are Shopify, Amazon (SP-API), WooCommerce, QuickBooks Online, Xero, FedEx, UPS, USPS and ShipBob. In the sandbox, which opens on 30 October, the same flows run against a SuppliFlex-hosted simulator that emits Shopify, Amazon, QuickBooks and carrier events every few minutes.

Plan tiers set what you can connect. Starter includes Shopify, Amazon, QuickBooks, Xero and CSV with one warehouse. Growth adds WooCommerce and a second warehouse. Scale covers three warehouses and includes 3PL connectors. See pricing for the full tier limits.

What happens when two channels disagree?

Sometimes two sources report different truths for the same SKU: a 3PL count that does not match the ledger, or a channel that rejected an update. SuppliFlex does not quietly pick a winner. During the beta the conflict policy is "always ask": the conflict goes to the exception inbox with the cause and a one-click fix, and a person decides. Failed syncs land in the same place.

That choice is deliberate. An automatic rule that resolves conflicts silently can turn one bad count into a wrong number on every channel. Asking keeps a human in the loop while the connectors run on real data.

How can I see it before connecting my store?

Open a sandbox from 30 October. It is the real product on seeded data: three seed packs with 18 months of history, including an apparel brand with two warehouses and a 3PL, and an electronics brand with marketplace spikes. The time machine jumps to the end of the day or month so you can watch stock move. From 13 November, the guided trial connects your own Shopify, Amazon or QuickBooks read-only.