Retail Ecommerce Integration: How to Connect POS, ERP, OMS and Online
How to integrate retail systems with ecommerce: POS, ERP, inventory, OMS, CRM, loyalty and payments, with APIs, webhooks, data ownership, reliability and monitoring.
Quick answer
Retail ecommerce integration keeps stores, back office and online selling consistent. Start by naming the system of record for products, prices, inventory, orders, customers and loyalty. Then connect POS, ERP, OMS, CRM, loyalty and payments to the commerce platform using APIs for immediate requests and webhooks or events with queues for changes. Make every consumer idempotent, handle offline stores, reconcile daily, and give each integration an owner and monitoring.
Where This Fits
Systems and Ownership
| Data | Usual system of record | Consumers |
|---|---|---|
| Item master and costs | ERP or PIM | Commerce platform, POS, marketplaces |
| Prices and promotions | ERP, pricing engine or commerce platform | Commerce, POS |
| Available stock by location | Inventory service, OMS or unified platform | Commerce, POS, marketplaces |
| Orders across channels | OMS or commerce platform | ERP, WMS, POS, CRM |
| Customer profile and consent | CRM or CDP | Commerce, POS, marketing |
| Loyalty balances | Loyalty system | Commerce, POS, app |
| Payments and refunds | Payment provider via commerce or POS | Finance, OMS |
POS Integration
- Sales and returns update stock by location in near real time
- Online orders (pickup, ship from store, returns) visible in store
- Products and prices from the same source as online
- Customer lookup by email, phone or loyalty ID
- Offline mode with queued sync and reconciliation
- Refunds for online orders back to original payment
ERP Integration
The ERP usually owns the item master, purchasing, costs and finance. It receives orders, returns and payments from commerce and POS, and sends products, prices and sometimes stock. Agree mapping for items, taxes, currencies, payment methods and store locations early. See ERP integration.
OMS and Inventory
Order management and inventory are the heart of omnichannel integration. The OMS captures orders from every channel, routes them and tracks status; the inventory service calculates availability by location. Both depend on fast, reliable stock events from POS and warehouses. See retail inventory visibility and OMS guide.
Systems out of sync across stores and online?
ZSpace can audit your retail integrations, define systems of record and build reliable event-driven connections with monitoring.
CRM and Loyalty
Customers expect loyalty to work everywhere. Integrate POS and commerce with the loyalty system so earning and redemption happen in real time, and with the CRM or CDP so purchases in every channel join one profile. Keep consent in one place. See loyalty programmes and clienteling.
Payments
Online and store payments often use different providers or accounts. Cross-channel returns need a refund path to the original method, and finance needs consolidated reconciliation. Gift cards and store credit must work in every channel. See BORIS.
APIs, Webhooks and Events
| Need | Pattern |
|---|---|
| Availability on a product page | API call to inventory service, with caching |
| Order placed | Webhook or event to OMS, ERP, CRM |
| Stock adjusted at POS | Event to inventory service |
| Price change | Event or scheduled publish to commerce and POS |
| Nightly reconciliation | Batch comparison between systems |
Reliability
- Durable queues between systems
- Idempotent processing keyed by event or order ID
- Retries with backoff and dead-letter queues
- Rate limit handling for platform APIs
- Timezone, currency and tax mapping tested
- Daily reconciliation of stock, orders and refunds
Monitoring and Ownership
Every integration needs an owner, dashboards for message volume, lag and failures, alerts for customer-impacting problems and a runbook. See ecommerce observability and webhooks.
Worked Example
An illustrative scenario, not a client case: a retailer's ERP integration posts online orders as a batch every hour. During a sale, the batch fails and nobody notices until the warehouse runs out of work. The team switches to event-driven posting through a queue with retries, adds a dead-letter queue and alerts, and a dashboard showing order-to-ERP lag. During the next sale, a slow ERP causes lag to grow, but nothing is lost and the queue drains when the ERP recovers.
Implementation Steps
- List systems and the data each owns
- Map flows: what moves, when and in which direction
- Choose patterns per flow: API, event, batch
- Build with queues, idempotency and retries
- Add reconciliation
- Add monitoring, alerts and owners
Common Mistakes
- Connecting systems before agreeing ownership
- Batch stock updates for fast-moving items
- No offline plan for POS
- Duplicate orders from retried webhooks
- Separate gift card systems per channel
- Integrations nobody monitors
Ready to connect your retail systems properly?
Talk to ZSpace about retail integration engineering, workflow automation and Shopify POS and ERP integration.
Conclusion
Retail integration succeeds when ownership is clear, changes move by events, consumers are idempotent, stores can work offline and everything is reconciled and monitored. Related: omnichannel architecture and API integration.
Common questions
Connecting a retailer's ecommerce platform with store and back-office systems, such as POS, ERP, inventory, OMS, CRM, loyalty and payments, so products, prices, stock, orders and customers stay consistent.