eCommerce and POS Integration: One Customer, One Stock, Every Channel
Customers no longer think in channels. They browse online, collect in store, return a purchase at the counter and expect the loyalty points to follow them everywhere. For a retailer, F&B brand or hospitality group, that expectation puts one question on the table: are your online store and your point of sale (POS) really talking to each other?
When they are not, the symptoms are familiar: the website shows stock that the shelves do not have, customers are duplicated across systems, store staff cannot see online orders, and returns turn into manual refunds. Integrating eCommerce with the POS fixes these problems at the root.
This guide covers the core flows every omnichannel business needs, and the advanced flows that support click-and-collect, store returns and shared promotions.
Who owns which data
In this model, the POS is the system of record for what you sell and what you have in stock. The online store is the system of record for what the online customer orders and pays. Data flows in the direction of its owner, except for customers, who are shared.
Core integration: the essential flows
1. Customers: both directions
Customer data is the one area that flows both ways. A customer who registers on the website should be recognized at the store, and a customer created at the POS should be able to log in online. Keeping one customer record across both channels gives you a single purchase history, consistent loyalty data and no duplicates. Matching rules, usually on phone number or email, are the key design decision here.
2. Products, categories, prices and inventory: POS to eCommerce
The catalog is maintained in the POS and published to the store: products, categories, prices and stock levels. Price changes and new items reach the website automatically, and the inventory the customer sees online reflects the real stock. Depending on your model, you can publish the stock of one warehouse, add up several stores, or keep a safety buffer to avoid overselling.
3. Orders: eCommerce to POS
When a customer places an order online, it is created in the POS so the store or warehouse can process it. A webhook from the online store is the best trigger, because the order arrives within seconds.
4. Payments: eCommerce to POS
The payment made online is sent to the POS with the order, with the method, amount and transaction reference. The order arrives in the POS as already paid, so staff do not take payment again, and the finance team can reconcile online receipts with the POS records.
5. Shipments: POS to eCommerce
When the order is fulfilled, the POS sends the status back to the store: shipped, ready for pickup or completed, along with the tracking number where there is one. The customer is notified automatically.
Advanced integration: omnichannel scenarios
Send only pickup orders to the POS
Not every online order needs to go through the store. In many setups, only the in-stock, pickup orders are synchronized from the online store to the POS, because those are the ones store staff need to prepare and hand over. Ship-to-home orders go to the warehouse or fulfillment center instead. This keeps store systems and staff focused on what they can actually serve, and lets the warehouse handle parcel logistics.
Cancel order and refund request: POS to eCommerce
If an order is cancelled in the POS, for example because an item turns out to be damaged or unavailable, the cancellation is sent to the online store. If the customer has already paid, a refund request is sent too, so the money goes back through the original payment method and the order status stays correct on both sides.
Return request: eCommerce to POS
When a customer starts a return online, the request is created in the POS. Store staff then know what to expect and can process the return when the goods arrive, whether they are mailed back or brought to a store.
Return at store: POS to eCommerce
Customers also return online purchases in person. In this case the return is started at the POS, using the online order, and the result is updated back to the online store. The order shows the return, the refund is issued on the original payment, and the customer gets a consistent record in both channels.
Coupons and discount codes: POS to eCommerce
Promotions are usually managed in the POS. Publishing coupons and discount codes to the online store means the same offer can be used online and in store, with no duplicate setup and no mismatched rules. It also helps control usage, since a code redeemed in one channel can be reflected in the other.
All flows at a glance
| Flow | Direction | Level |
|---|---|---|
| Customers | Both directions | Core |
| Products, categories, prices, inventory | POS to eCommerce | Core |
| Orders | eCommerce to POS | Core |
| Payments | eCommerce to POS | Core |
| Shipments | POS to eCommerce | Core |
| In-stock pickup orders only (ship orders go to warehouse) | eCommerce to POS | Advanced |
| Cancel order and refund request | POS to eCommerce | Advanced |
| Return request | eCommerce to POS | Advanced |
| Return at store | POS to eCommerce | Advanced |
| Coupons and discount codes | POS to eCommerce | Advanced |
Best practices
- Decide the customer matching rule first. Duplicate customers are the hardest problem to clean up later.
- Treat inventory carefully. Use safety buffers and frequent updates to avoid overselling during busy periods.
- Use webhooks for events, such as orders, cancellations and returns, and scheduled syncs for bulk data like the catalog.
- Make every message safe to retry. Use unique references so a retry never creates a duplicate order or refund.
- Define the routing rule clearly. Decide exactly which orders go to the store and which go to the warehouse, and who is responsible for each.
- Handle partial returns and refunds, because customers often return only part of an order.
- Monitor and reconcile. Alert on failed messages and compare online and POS totals every day.
How AllSync helps
AllSync connects your online store and your POS through webhooks and APIs, and takes care of the mapping, routing, retries and monitoring. Many POS systems run on a server in the store or head office with no public API. For those, an offline connector installed on the local server reads the data and sends it to AllSync, so you can integrate systems that were never designed for the cloud. You can begin with the core flows and enable the advanced scenarios as your omnichannel strategy grows.
Conclusion
A connected eCommerce and POS gives your customers one identity, one price and one stock position across every channel. Start with customers, catalog, orders, payments and shipments, then add pickup routing, returns and shared promotions to deliver a true omnichannel experience.
Want to connect your online store with your POS? Talk to us about doing it with AllSync.