Does the POS Share the Ledger, or Merely Integrate With It?

The defining characteristic of a retail platform built directly on top of an ERP is that the point of sale, the ledger, and the inventory master are not integrated systems — they are the same system. Sales post to finance without a bridge. Stock decrements without a sync job. That single architectural fact is why a unified retail platform behaves differently from a best-of-breed POS bolted onto an ERP, and why the integration failures common in the second model simply do not exist in the first.

Offline Resilience Is a Performance Characteristic

A terminal that degrades gracefully through a connectivity loss and reconciles cleanly on reconnect is, from the store’s point of view, faster than one that is technically faster but stops when the link drops. An offline-resilient POS is not a feature — it is the difference between a connectivity blip and a closed store. Availability under adverse conditions is part of perceived performance, not separate from it.

Real-Time Has a Latency Budget, and It Is Small

"Real-time sync" is a commitment that scan-to-central propagation stays within tens of milliseconds, sustained across the day’s peak transaction rate, not just at quiet hours. Designing for the peak — and proving the budget holds under it — is the difference between a system that feels instant and one that feels real-time only in the morning.

Sector Compliance Is Part of the Sale, Not a Wrapper Around It

In airport, duty-free, and regulated retail, the transaction carries obligations the generic POS does not model: a boarding-pass reference on every sale, same-day exchange-rate conversion for foreign currency, an end-of-shift cash count that must reconcile to posted transactions. These belong in the operating model from day one. Retrofitted, they become the audit findings nobody wants.