POS Integration in Practice: Syncing Inventory and Members Across Online and Offline

"Our stores have a POS and our website has a cart — can the inventory and members connect?" This is the most common request from physical brands moving into e-commerce, and the line item most often underestimated on a quote. The difficulty of POS integration isn't the technology itself — it's that two systems understand "the same thing" differently. This article shares our experience from actually doing online-offline integration, across the three core battlegrounds.

Cold water first: not every POS can be integrated

The first task before starting is confirming whether your POS has an API. The POS spectrum in Taiwan is wide: newer cloud POS systems mostly have well-documented APIs; legacy standalone POS terminals may only export report files, or export nothing at all. In the latter case, "integration" actually becomes "scheduled jobs that fetch and parse files" — real-time behavior and reliability both take a hit, and this should be made explicit during evaluation, not discovered after signing. Replacing the POS is sometimes cheaper than force-integrating the old one. That sentence is brutal, but it's often true.

Battleground 1: inventory sync

Inventory is the most urgent, because out-of-sync means overselling: the store sells the last unit at the same moment an online order lands, and now you owe someone an apology and a refund. Real-time sync is the ideal, but reality requires accepting two things:

• Sync always has lag. Even with POS webhooks, there's a seconds-to-minutes window between checkout completing and the e-commerce stock being deducted. The answer isn't chasing zero latency — it's designing buffers: set safety stock on hot items (sellable quantity shown online = actual stock − reserve), so the lag consumes your buffer, not a customer's order.
• Designate one authoritative source. In an architecture where both sides can modify inventory, you won't know which to trust when the numbers disagree. Our approach: the inventory-management system is the single authority, POS and e-commerce are endpoints that report movements, and a daily reconciliation job catches the drift. Read this alongside how to prevent overselling for the details.

Battleground 2: members and points

The first hurdle in member integration is "how do we recognize the same person?" The store POS uses phone numbers; the website registers by email; one customer becomes two records. In Taiwanese retail practice, the phone number is the most reliable primary key — build phone verification into website registration so the two sides can match. Existing legacy data needs a merge: a one-time dirty job, but skip it and your points will forever run as two separate ledgers.

Points rules must also converge into one set: put the earn-and-burn logic in a member service that both POS and e-commerce call, rather than each computing its own. We've seen the outcome of each side calculating independently: the same purchase earned 10 points in-store and 12 online, and when the customer showed up with screenshots asking which was right, nobody had an answer.

Integration isn't really about connecting two machines — it's about converging two definitions of the facts into one.

Battleground 3: invoicing and reconciliation

The store POS typically issues its own invoices, while e-commerce goes through a government e-invoicing service provider — two number tracks, two workflows. What integration must think through is month-end reconciliation: revenue reports need to distinguish channels, invoices must trace back to orders, and returns and allowances must be processed back through the original channel. Define a "channel" field on the order data from day one — every report you build afterward will thank you for it.

A pragmatic rollout order

Don't try to do it all at once. Our recommended order: connect members first (biggest experience impact, lowest risk), then inventory (highest value, needs careful design), and finally consolidate reporting and invoicing (dirty but stable). Leave a verification period at each step — run two weeks, reconcile the books, then move on. Online-offline integration is a marathon, not a sprint. If you'd like a partner to plan it with, take a look at our custom systems and SaaS services.