Skip to main content
Talk to an expert
EPOS systems logo

EPOS systems integration for ecommerce and retail operations

Connect branches, tills and ecommerce with governed order and stock flows. iWeb integrates EPOS systems with ecommerce, ERP and branch operations so online orders reach stores, stock is accurate, customer pricing is current and in-store refunds reconcile cleanly. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: EPOS, till system, retail POS, branch system, trade counter system.

EPOS systemsiWeb integration layeryour storefront
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
01 · What you get

What a EPOS systems integration gives you.

Orders reach branches with no rework

Online customers can place orders for in-store collection or branch fulfillment and branch staff receive them in the EPOS system ready to pick. No email forwarding, no re-entry, no confusion about where the order landed.

Stock accuracy across channels

Branch stock is published to ecommerce so customers see honest availability and click-and-collect orders can promise realistic fulfillment. Stock transfers and till adjustments keep branch records and ERP in sync.

Faster checkout for trade and known customers

Trade account customers see their negotiated pricing and credit terms at ecommerce checkout and at the till. Account lookups are instant and pricing changes are synchronized so no discrepancies break the sale.

Returns and refunds process cleanly

In-store returns reconcile automatically against the original order, trigger the correct refund amount and VAT treatment, and update customer accounts without manual intervention or day-2 rework.

Financial close with confidence

Till transactions flow to ERP with correct coding, discount and VAT treatment so the sales ledger and VAT return reconcile on schedule. Month-end close no longer depends on spreadsheet rework and manual matching.

02 · When it's worth it

Where a EPOS systems integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Online orders routed to branches for click-and-collect or local fulfillment
Branch stock visibility fed into ecommerce availability and allocation
Trade account pricing and customer records linked between till and online checkout
Till transactions and refunds synchronized to ERP for sales ledger and reconciliation
In-store returns processed at the till and reconciled against online orders
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Limited online-to-branch order visibility

Standard EPOS systems often lack direct integration with ecommerce order management, forcing staff to manually check order systems or rely on email notifications. This creates delays, order-picking errors and poor customer handoff experience.

Stock sync latency and reconciliation gaps

EPOS stock counts may not feed ecommerce in real time, leading to oversell, inaccurate availability displays and unmet customer expectations at pickup. Manual stock counts and till adjustments often drift from ERP records.

Trade account and local pricing drift

Customer records and negotiated pricing rules in the EPOS till can fall out of step with ERP account master and price books. Staff may apply outdated prices or miss credit limit changes, causing payment failures and reconciliation rework.

Returns and refund reconciliation complexity

In-store returns initiated at the till may not automatically reconcile with the original online order in ERP or trigger the right customer refund. Manual matching and reconciliation create exceptions and customer account disputes.

Financial and VAT reconciliation friction

Till transactions and adjustments in the EPOS system often require manual data entry into ERP for correct sales ledger posting and VAT recovery. Errors in transaction type coding, discount application or refund VAT treatment delay month-end close.

04 · The real work

Branch stock and till data are often the last pieces to flow into ecommerce and ERP, leaving availability stale and financial close delayed; integration friction here is where online-to-store strategies break down.

05 · Where it sits

Where this integration sits in your estate.

EPOS systems holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Platform-agnostic by design. EPOS systems sits at the centre of your estate, not at the edge of one platform.

System of record
Source / owner
EPOS systems
Branch operational system managing till, stock, customer accounts and fulfillment.
  • Till transactions, receipts and daily reconciliation
  • Branch stock levels, movements and physical counts
  • In-store customer interactions and refunds
  • Click-and-collect order fulfillment status
  • Local pricing and discount application
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Online order placement and checkout
  • Ecommerce product catalogue and availability display
  • Online customer account and saved payment methods
  • Click-and-collect order routing decision
  • Online refund initiation and customer notification
Connected neighbours
Integration layer
ERP
Holds customer accounts, negotiated pricing, credit limits, sales ledger and reconciliation. Stock and pricing sync with EPOS; till transactions feed ERP for month-end.
Integration layer
OMS
Routes online orders to the correct branch based on stock availability, location and fulfillment method. Receives fulfillment status and tracking from EPOS.
Integration layer
WMS or inventory system
Tracks warehouse stock and transfers. Branch stock and till movements are coordinated through integration so inventory records stay in step across locations.
Integration layer
CRM or customer data platform
Holds customer communication preferences, purchase history and segmentation. Click-and-collect orders and in-store transactions can feed segmentation and campaign triggers.
Integration layer
Payment processor
Handles online and in-store card payments. Refunds initiated at the till or online must reconcile with payment processor settlement.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, Sage, NetSuite, Infor)
  • OMS (order routing, allocation, fulfilment)
  • WMS (warehouse and stock movements)
  • Customer data platform or CRM
  • Reporting and business intelligence
  • Payment and refund processing
  • Stock and inventory management tools
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

Into BRANCH
From BRANCH
BOTH WAYS
Online orders for collection: Customer orders placed on the ecommerce storefront are routed to the designated branch or store
Branch staff receive the order in the EPOS system, pick and pack, and prepare for handoff to the customer.
Stock levels and availability: Stock counts, movements and reserved inventory from the EPOS till and branch management system flow to the ecommerce platform and ERP
Ecommerce stock rules consume this data to show accurate availability across online and in-store channels.
Till transactions and receipts: Daily till transactions, cash reconciliation and receipt detail from the EPOS system are captured and sent to ERP for sales ledger posting, VAT treatment and financial month-end.
Customer accounts and trade pricing: Customer records, trade account status and negotiated pricing from ERP sync to the EPOS till so staff can look up account rules, apply the right price and check credit limits
Updates to account status or pricing changes flow back to keep till and ERP in step.
In-store returns and adjustments: Returns processed at the till, manual stock adjustments and refunds initiated in the EPOS system flow back to ecommerce and ERP so the ledger, inventory records and customer refund status stay accurate.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Order routing and branch handoff

    iWeb defines how online orders are routed to the correct branch based on customer location, fulfillment method and stock availability. Orders land in the EPOS till as fulfillment instructions, staff confirm readiness, and the customer is notified when ready for pickup.

  2. 02
    Stock visibility and allocation

    iWeb sets up stock feeds from EPOS to ecommerce so availability reflects branch reserves and allocated inventory. Stock rules prevent oversell across channels and reserve inventory for click-and-collect orders at the branch.

  3. 03
    Customer account and pricing governance

    iWeb maps trade account status, credit limits and negotiated pricing from ERP to the EPOS till so staff apply the right price and check credit before checkout. Account changes flow back so both systems stay current.

  4. 04
    Returns and refund automation

    iWeb wires returns initiated at the till back to ecommerce and ERP so the original order status updates, refund amount and VAT are computed correctly, and the customer account is credited without rework.

  5. 05
    Financial and reconciliation integrity

    iWeb ensures till transactions flow to ERP with the correct sales code, discount and VAT treatment so the ledger is accurate and month-end reconciliation runs without manual intervention.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataBranch stock levels and movements
Source / ownerEPOS till system (primary)
Maintained byBranch staff (daily transactions), inventory team (stock takes)
NotesStock feeds to ecommerce for availability and to ERP for ledger updates. Discrepancies between till, branch physical count and ERP require exception handling.
DataTill transactions, receipts and daily reconciliation
Source / ownerEPOS till system (primary)
Maintained byBranch staff (during trading), till operator (EOD reconciliation)
NotesTransactions flow to ERP for sales ledger and VAT. Discounts, refunds and adjustments must map to correct nominal codes.
DataCustomer accounts and trade pricing at branch
Source / ownerERP (primary), synchronized to EPOS
Maintained byCredit control / pricing team (ERP side); branch staff confirm during transaction
NotesPricing and credit limits must flow to EPOS daily. Branch staff apply the rules but cannot override; changes flow back for audit.
DataIn-store returns, refunds and adjustments
Source / ownerEPOS till (primary event source)
Maintained byBranch staff (process return), customer service / warehouse (authorization if needed)
NotesReturn must link to the original ecommerce order to calculate correct refund amount and VAT. Adjustment coding drives ERP ledger posting.
DataClick-and-collect and online-to-branch order routing
Source / ownerOMS or ecommerce order system (primary)
Maintained byFulfillment routing logic; branch staff acknowledge and pick
NotesOrders route to EPOS as fulfillment instructions. Branch status (ready for pickup, collected, not available) must feed back to ecommerce and customer.
DataIntegration transport, monitoring and exception handling
Source / ownerIntegration layer (logs, reconciliation ledger)
Maintained byOperations team
NotesOrder handoff failures, stock sync gaps, pricing mismatches and refund errors must be surfaced and escalated to the right owner.
10 · Experienced integrator

Built this before

iWeb has built EPOS integrations across retail, trade, grocery and hospitality estates. We understand how till systems sit between branch operations, ecommerce checkout, ERP financial records and stock control, and what can break when they fall out of sync.

Routinely design order routing from ecommerce to EPOS so branch staff see online orders in the till without manual intervention.
Set up stock feeds from EPOS to ecommerce so availability is honest and click-and-collect inventory is reserved without oversell.
Map customer accounts and negotiated pricing so the till and ecommerce apply consistent rules and changes sync without day-2 rework.
Wire returns from the till back to ecommerce and ERP so refunds calculate correctly and customer accounts reconcile on the same day.
Know where EPOS sits next to OMS, WMS, ERP and payment systems, and which integration seams are most prone to failure and exception.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Click-and-collect order appears in the branch EPOS till within 30 seconds of customer checkout, with no manual re-entry or email rework.
Stock reserved for a click-and-collect order is held at the branch and does not appear available for online purchase at other locations.
A customer refund processed at the till reconciles to the original ecommerce order and triggers a refund in payment processor and ERP.
Trade account pricing synced from ERP is applied correctly at the till and matches the price displayed on ecommerce storefront.
Till transactions flow to ERP within one hour with correct nominal codes and VAT treatment so day-end reconciliation runs without exception.
Stock discrepancy between EPOS and ERP is detected within the next sync cycle and logged in an exception queue for the inventory team.
If EPOS goes offline, transactions are queued locally and processed in order when connectivity returns; no transactions are lost or duplicated.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Orders stuck in email or manual handoff

When online orders do not flow directly into EPOS, branch staff may miss orders, pick wrong items, or fail to notify customers. Customers arrive to find their order not ready, damaging trust and creating complaints.

Stock oversell across channels

If EPOS stock counts do not feed ecommerce in real time, the online system may oversell while inventory sits reserved at the branch. Customers are promised stock that is not available, forcing cancellations and refunds.

Trade account pricing and credit limit drift

When account pricing or credit limits are not synchronized, staff may apply outdated pricing at the till or miss a credit limit breach. Customers receive the wrong price or payment fails at checkout, causing disputes and rework.

Returns not reconciling to the original order

In-store returns that do not link back to the ecommerce order may be recorded as general till adjustments instead of refunds. The customer account is not credited, refund amounts are incorrect, and ERP inventory records drift from till counts.

Till transactions failing VAT and ledger reconciliation

When till transactions do not flow to ERP with correct coding and VAT treatment, month-end reconciliation stalls. Finance teams spend days matching till totals to journal entries and recalculating VAT on refunds and adjustments.

Stock movement visibility gaps during offline periods

If the EPOS till goes offline, stock adjustments may not sync when connectivity returns. Ecommerce and ERP see stale stock, leading to inventory holes or phantom orders after the till comes back online.

14 · Questions

Common questions about EPOS systems integrations.

How do online orders reach a branch for click-and-collect?

iWeb configures order routing so that when a customer selects a store for collection, the order is transmitted directly to the EPOS till at that branch. The branch receives the order as a fulfillment instruction, staff pick and pack the items, and a notification is sent to the customer when the order is ready. The status updates back to the ecommerce system so the customer can track progress.

How does branch stock feed into ecommerce availability?

iWeb sets up a stock feed from the EPOS system to ecommerce so that branch inventory levels are published in real time or at agreed intervals. Ecommerce uses this data to show accurate stock status (in stock, low stock, out of stock) to customers. Stock reserved for click-and-collect orders is held separately so oversell is prevented.

What happens when a branch is out of stock for a click-and-collect order?

iWeb designs exception handling so that if stock is not available at the requested branch, the order either cancels automatically with a customer notification, or is rerouted to another branch with stock. The customer is informed of the new pickup location or offered an option to shop at the original branch later. ERP and branch stock are updated so the order does not sit in limbo.

How do trade account pricing and credit limits work at the till?

iWeb syncs customer account records, negotiated pricing and credit limits from ERP to the EPOS till daily. When a known trade customer approaches the till or logs into ecommerce, the system applies their custom pricing and checks their credit before allowing checkout. If pricing or credit status changes on the ERP side, the till receives the update so staff always apply the current rules.

How are in-store returns reconciled to the original ecommerce order?

When a customer returns an item at the till, staff use the order number or receipt to look up the original transaction in the EPOS system. iWeb wires this return back to ecommerce and ERP so the order status updates, the refund amount and VAT are calculated correctly, and the customer account is credited. If the return is linked to an online order, the refund reconciles automatically without manual rework.

What VAT treatment applies to till refunds and adjustments?

iWeb ensures that when a till refund or adjustment is recorded in the EPOS system, it carries the correct VAT code so that when it flows to ERP, the VAT amount is recovered correctly. This prevents VAT reconciliation errors at month-end and ensures the finance team is not chasing manual adjustments on the VAT return.

How do till transactions flow to ERP for the sales ledger?

iWeb configures an automated feed of till transactions from EPOS to ERP. Each transaction is coded with the correct nominal account so sales, discounts and refunds post to the right ledger. Daily reconciliation is performed so till totals match the ERP journal entry and any discrepancies are highlighted for investigation.

What happens if the EPOS till goes offline?

iWeb designs offline resilience so that if the till loses connectivity, it continues to operate locally and records transactions in a local queue. When connectivity returns, the queue is processed and transactions are sent to ecommerce and ERP in the correct sequence. iWeb monitors for queued transactions and alerts operations if sync is delayed so manual intervention is not needed.

How are stock discrepancies between the till and ERP resolved?

iWeb sets up a reconciliation process where daily stock feeds from EPOS are compared to ERP records. Discrepancies are logged and raised to the warehouse or inventory team for investigation. The integration does not overwrite one system with the other without approval; instead, exceptions are surfaced so the right owner can investigate and correct the source.

Can a customer return an item bought online at a different branch?

Yes. iWeb designs multi-location returns so that a customer can return an online purchase at any participating branch. The return is linked to the original order, the refund is computed correctly, and stock is posted back to the fulfillment location (not necessarily the return location) so inventory balances stay accurate.

How does the integration handle promotional pricing at the till?

iWeb syncs promotional pricing rules from ecommerce or ERP to the EPOS till so that in-store customers receive the same promotions as online shoppers. If a promotion ends or changes, the till receives the update and applies the new pricing on the next transaction. This prevents mismatches where an in-store customer is charged a different price than online.

What reporting is available on click-and-collect and in-store sales?

iWeb ensures that all till transactions and click-and-collect orders are recorded in ERP with clear attribution to the branch and sales channel. This allows reporting on in-store revenue, click-and-collect fulfillment rates, branch profitability and customer behaviour across channels. Data flows to reporting systems so analytics teams can analyse trends without manual extract-transform-load work.

How is customer identity managed across ecommerce and the till?

iWeb links the customer account in ecommerce to the customer record in the EPOS till using a consistent identifier. When a known customer shops online, their account opens on the till for credit check and pricing. When they shop in store, their online activity is visible. This enables a unified customer view across channels.

What training and support do branch staff need for the integration?

iWeb provides training materials and support so branch staff understand how click-and-collect orders appear in the EPOS till, how to process returns, and what to do if an order is missing or stock is not available. The integration is designed to require minimal training; orders arrive with clear fulfillment instructions and the till automation handles pricing and refund calculation.

Next step

Have a EPOS systems integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →