The scanner beeps. For the store, the sale is finished. For the rest of the company, nothing has happened yet.
Until that transaction is published as a business event, the website still thinks the size is available. The pickup order due in twenty minutes is still competing for the same unit. Loyalty has not moved. Returns eligibility has not changed. Finance will meet the sale tonight, or later, in a file. Customer service, if the shopper calls from the car, will not see it.
Retailers describe this as an online/offline sync problem. That understates it. A store sale is not a channel report. It is an operational fact that several other processes are entitled to know.
Integration architecture is how events travel in general. This article is the event itself: the register, the floor, the moment something leaves the building through a bag instead of a carton.
What the Beep Actually Changes
Follow one paid basket.
Inventory is no longer sellable — or should not be. If ATP on the site, in the call center, and in BOPIS still includes that unit, the next promise is a guess. Ship-from-store and pickup are the first places the guess becomes a customer standing at a counter.
Customer history should now include the purchase. If identity never left the POS, the next online session, the next return, and the next service case are strangers to the store sale. Loyalty that cannot see the basket will either under-credit or require a dispute. A return at another location will be argued because the original tender lives in a system the second store cannot query.
Promotions and tax were calculated in the POS. If commerce and ERP never receive those lines as they happened, replenishment, margin, and financial close are reconciling stories rather than recording one sale.
Returns are the delayed version of the same event. A unit that came back to the store is sellable again, or it is not. If POS cannot publish the return, the site keeps it dead and the next customer is sent to another location. Cross-channel returns — buy online, return to store, or the reverse — fail in the same way: tender, serial, and eligibility live in a system the second channel cannot see.
The question is not whether the POS and the website are "connected." It is how quickly the rest of the business can know the event occurred and act. Minutes matter for availability. Hours matter for pickup. Overnight files are a decision to let other channels sell the past.
Latency Is a Promise You Did Not Mean to Make
Batch POS integration is still common because it is operationally convenient for IT and operationally expensive for everyone else. The store can keep selling. The file can land after close. Finance can sort it in the morning.
The customer does not live on that clock. Neither does available-to-promise.
A BOPIS order allocated against last night's on-hand will fail in the aisle. An endless-aisle sale that cannot see this afternoon's walk-out will oversell. An associate who cannot see an online hold will sell the last unit off the rack. Replatforming the storefront does not shorten that delay. A new theme still reads yesterday's file.
Bidirectional flow is the other half people skip. Publishing the store sale outward is necessary. The POS also has to receive the commerce events that will walk into the store: pickup orders, customer records, price and promotion updates, return authorizations. A register that only sends and never listens is a silo with an API.
An associate who cannot pull up the online hold is not poorly trained. They are standing in front of a system that was never told the customer was coming. Price mismatches at the register have the same root: the POS is still on last week's promotion file while the site moved this morning.
Silent failure is worse than a slow file. If the event does not publish and nobody is told, inventory lies accumulate until cycle count or a furious pickup. Retry, visibility, and an owner for a stuck sale are part of the transaction, not an integration afterthought.
Replenishment should see the beep as consumption, not as a store-manager anecdote. A SKU that walked out fifty times today and still looks healthy online will be late to the next truck. That is not a forecasting model problem yet. It is a missing sales event.
Finance Already Knows This. The Floor Should Too.
End-of-day reconciliation exists because the sale was allowed to have two lives. Matching POS tenders to commerce and ERP is labor spent reconstructing a fact that should have been written once.
When the register event is the same object finance, inventory, and service consume, close becomes exception review. When it is not, omnichannel reporting is a spreadsheet of two truths: what the store says it sold, and what the site says it sold, and a third column for the difference.
Customer service inherits the delay as a script: "I don't see that purchase." The shopper is in the parking lot with a bag and a receipt the enterprise systems do not have yet. Loyalty points that post overnight train people not to use the identity the brand is collecting.
None of that requires pretending every retailer needs the same stack. It requires admitting that a completed store sale has consequences outside the four walls, and designing the beep as the start of those consequences — inventory, identity, loyalty, returns, fulfillment eligibility, replenishment signal — not as the end of a local ticket.
Store fulfillment programs fail here more often than they fail at last-mile logistics. The van can be ready. The inventory picture cannot. Treat POS latency as a fulfillment defect, not as a back-office convenience.
If the rest of the company cannot act on a store sale until tomorrow, "omnichannel" is a slogan printed on a bag. The leadership test is simpler than a platform RFP. When an item sells in a store, who else knows, how soon, and what are they now allowed to promise?
Time-box it. If inventory and identity cannot update within the window a customer still cares about — walking to another channel, starting pickup, calling service — the integration is a report, not an event. That window is shorter than a nightly batch.