Skip to main content
Talk to an expert
Epos Now logo

Epos Now integration for ecommerce and retail operations

Branch till and ecommerce working as one unified operation iWeb integrates Epos Now with ecommerce, ERP and operational systems so branch stock, customer accounts, click-and-collect orders and pricing stay synchronized without manual reconciliation. 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 NowiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Epos Now integration gives you.

Unified customer experience across till and online

Customers log in online and see their account, loyalty, trade pricing and purchase history. Staff at the till see the same account linkage, so returns, discounts and credit limits are consistent regardless of channel.

Real-time branch stock visibility online

Stock levels in the till are synchronized with ecommerce in real time or on a tight schedule. Shoppers can see if an item is available for next-day collection, and branches do not oversell or disappoint customers with phantom inventory.

Click-and-collect that actually works

Online orders for in-store collection appear instantly in the branch till with pick instructions and customer details. Collection confirmation flows back to ecommerce and the customer receives tracking and status updates.

Faster month-end financial reconciliation

Till transactions are mapped to ERP nominal codes automatically, and refunds, voids and adjustments are reconciled without manual rework. Finance closes on time and cash reconciliation matches between till and ledger.

Branch pricing and trade accounts managed centrally

Trade account pricing, local promotional pricing and credit limits are set once in a central system and published to both the till and ecommerce. Price changes take effect simultaneously, and no manual dual entry is needed.

02 · When it's worth it

Where a Epos Now integration earns its place.

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

Branch till transactions flowing into ERP and finance reconciliation
Online orders visible at the branch for click-and-collect handoff
Branch stock adjustments and transfers reflected online in real time
Customer account linking between in-store till and ecommerce login
Local branch pricing and trade account pricing published to online storefront
Returns and refunds processed at the till and reconciled against ecommerce 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.

No native ecommerce stock synchronization

Epos Now does not automatically push branch stock to ecommerce platforms. Manual feeds, scheduled batch jobs or third-party connectors are required, and synchronization lag during peak trading can cause oversell across channels.

Limited customer identity resolution

Epos Now can store customer records but does not natively resolve or link customers created online to till accounts. Manual reconciliation, duplicate accounts and lost loyalty history are common unless a separate identity or CRM layer is deployed.

No click-and-collect workflow by default

Click-and-collect orders from ecommerce do not automatically appear in the branch till. Custom feeds, integrations or manual import are required, and collection status does not flow back to ecommerce without additional work.

ERP integration requires custom mapping

Epos Now has limited ERP connectors. Till data such as transactions, refunds, nominal codes and payment methods must be mapped manually, and reconciliation with finance often requires post-close adjustment.

No native multi-channel pricing governance

Branch pricing and trade account pricing are stored in Epos Now but are not automatically published to ecommerce or kept in step when promotional pricing changes. Dual entry and price drift are common.

04 · The real work

The cost of not linking the branch till to ecommerce is duplicate customer accounts, stock that shows online but is not available in store, and reconciliation rework every month. When it is done well, customers experience consistent pricing and availability, and operations teams have real-time visibility.

05 · Where it sits

Where this integration sits in your estate.

Epos Now 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.

Commerce platform agnostic. Connect Epos Now across your entire technology stack.

System of record
Source / owner
Epos Now
Till and branch management system at the point of sale and stock control
  • Till transactions, refunds and cash handling
  • Branch stock adjustments and local inventory
  • In-store customer interactions and till staff workflows
  • Offline transaction queueing and recovery
  • Branch payment and card processing
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Online order capture and checkout
  • Ecommerce customer account and login
  • Product catalogue display and search
  • Online pricing and promotions display
  • Click-and-collect order status to customer
Connected neighbours
Integration layer
ERP or finance system
Receives branch transactions daily for nominal coding and reconciliation; sends stock levels and trade-account pricing to both Epos Now and ecommerce
Integration layer
Customer identity or CRM
Resolves customer accounts across till and ecommerce so loyalty, trade pricing and purchase history are visible at both channels
Integration layer
WMS or central warehouse
Supplies stock levels to Epos Now and ecommerce; receives stock adjustments from the branch till for reconciliation
Integration layer
OMS or order management
Receives online orders destined for click-and-collect at the branch; sends collection confirmations back to ecommerce
Integration layer
Payment processor
Handles payment authorization and settlement for both till and ecommerce; refund requests flow from both channels
Integration layer
Reporting and analytics
Receives till transaction and stock-movement data for reporting branch performance, inventory turns and sales trends across channels
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, NetSuite, Sage, Infor)
  • Inventory or stock management system
  • OMS or order orchestration layer
  • Customer identity or CRM system
  • WMS or fulfilment warehouse system
  • Finance or general ledger
  • PIM or product information system
  • Loyalty or customer-account platform
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 ERP & BRANCH
←From ERP & BRANCH
↔BOTH WAYS
Branch stock and pricing updates: Stock levels, price changes and trade-account pricing flow from the ERP or central inventory system to Epos Now so branch tills and staff see current availability and correct pricing
If branch can also adjust stock locally, those changes flow back to ERP.
Till transactions and reconciliation: Till transactions, daily takings, refunds and cash reconciliation flow from Epos Now into the ERP and finance ledger
Timing and format must match ERP nominal codes and financial close windows.
Online orders for click-and-collect: Orders placed online for in-store collection are sent to Epos Now and appear in the branch till system with pick instructions, customer details and collection status
Completion and collection confirmation flow back to ecommerce and customer.
Customer account and identity linkage: Customer records created online need to be recognized at the branch till so purchase history, loyalty, trade account status and pricing are visible
Account updates (address, credit limit, payment method) sync both ways between ecommerce and Epos Now.
Till staff transactions and adjustments: Manual transactions, no-sale events, staff discounts, void lines and local inventory adjustments captured by Epos Now are sent to central systems for compliance, training analysis and stock reconciliation.
Returns, refunds and credit notes: Customer returns initiated online or at the till must be reconciled with the ERP so refunds, credit notes and stock movements are recorded in the correct ledger
Refund status flows back to the customer and ecommerce.
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
    Data flow and ownership design

    iWeb designs the paths so branch stock, transactions, customers and pricing are synchronized between Epos Now, ecommerce, ERP and any OMS or WMS. Each flow has a named owner, a monitoring rule and an exception path.

  2. 02
    Till transaction mapping and financial reconciliation

    iWeb maps till line items, refunds, discounts, voids and cash to ERP nominal codes and cost centres so daily takings feed into finance without rework. Reconciliation rules match till batches to ERP journals.

  3. 03
    Customer account linking and identity governance

    iWeb connects customer records created online or at the till so loyalty, trade account status, credit limits and purchasing history are visible across channels. Deprovisioning and privacy rules are built in.

  4. 04
    Click-and-collect and branch fulfilment workflow

    iWeb sends online orders to Epos Now and the branch till with pick lists and collection instructions. Collection confirmation and any manual adjustments flow back to ecommerce and the customer in real time.

  5. 05
    Stock synchronization and oversell prevention

    iWeb synchronizes branch stock from Epos Now to ecommerce on a schedule or via event triggers, with rules for stock buffers, allocation and channel priority. Oversell is prevented by reservation or real-time stock checks.

  6. 06
    Monitoring, observability and exception handling

    iWeb builds dashboards, alerts and exception queues so branch staff, operations and finance teams see failed transactions, stuck orders, customer account mismatches and reconciliation gaps before they cascade.

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 transfers
Source / ownerERP or central inventory system
Maintained byWarehouse or inventory team
NotesBranch adjustments in Epos Now are sent to the ERP; published levels are read-only at the till and must not diverge.
DataLocal and trade account pricing
Source / ownerERP or pricing system
Maintained byPricing and trade-account team
NotesPublished to Epos Now and ecommerce simultaneously; manual dual entry is prevented by the integration.
DataCustomer account and identity linkage
Source / ownerEcommerce platform or identity system
Maintained byCustomer-account or CRM team
NotesBranch till resolves customers via identity system; account changes (address, credit limit, loyalty) sync both ways.
DataTill transactions and cash reconciliation
Source / ownerEpos Now
Maintained byTill and branch-finance team
NotesTransactions are sent to ERP daily; nominal-code mapping and financial-close reconciliation are owned by finance.
DataClick-and-collect orders and collection status
Source / ownerEcommerce platform
Maintained byEcommerce and branch-fulfilment teams
NotesOrders are sent to Epos Now; collection confirmation flows back to ecommerce; dispute resolution is joint.
DataReturns and refunds
Source / ownerERP or OMS
Maintained byCustomer-service and branch-return teams
NotesReturns initiated at till or online are tracked in the ERP; credit notes and stock movements reconcile across systems.
DataIntegration transport, monitoring and exception handling
Source / ownerIntegration layer
Maintained byIntegration and operations teams
NotesFailed transactions, stuck orders, account mismatches and reconciliation gaps are visible and actionable.
10 · Experienced integrator

Built branch and till integration before

iWeb has designed and built Epos Now integrations across retail, hospitality and trade sectors. We understand how the till sits between ecommerce, inventory, customer accounts and finance, and we know where oversell, reconciliation gaps and customer friction typically hide.

We map till transactions to ERP nominal codes and build reconciliation rules so branch accounting closes on time without rework.
We design stock synchronization so branch adjustments feed back to the ERP and ecommerce stays in step, preventing oversell and collection disappointments.
We link customer accounts across till and ecommerce so loyalty, trade pricing and purchase history are visible at both channels and staff discounts are applied consistently.
We build click-and-collect workflows so online orders appear in the branch till with pick instructions and collection status flows back to ecommerce in real time.
We handle offline recovery, network resilience and exception queues so branch operations are not blocked by temporary failures and no transactions are lost.
11 · Before launch

What we test before launch.

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

Branch stock adjustments in Epos Now are visible in ecommerce within the target synchronization window and do not cause oversell.
A customer who signs up online can collect an order at the branch without staff creating a duplicate account.
Click-and-collect orders from ecommerce appear in the branch till within 5 minutes of order placement with correct customer and product details.
Till transactions including refunds, voids and discounts are mapped to the correct ERP nominal codes and appear in the daily reconciliation file.
Epos Now offline mode queues transactions and syncs them when the network returns; no transactions are silently lost.
Trade-account pricing changes made in the ERP are published to both Epos Now and ecommerce simultaneously within the synchronization window.
Customer account changes (credit limit, address, loyalty status) made in ecommerce are visible at the branch till within the agreed latency.
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.

Branch stock drift between till and ecommerce

When stock is adjusted at the branch till, ecommerce is not updated in real time. Customers order items that are no longer available, or shoppers cannot reserve items that the branch has in stock. Reconciliation lags during peak trading compound the problem.

Click-and-collect orders lost or stuck at branch

Online orders for collection do not appear in the branch till, or they appear hours after the customer expects them. Collection staff do not pick or hold the order, and the customer arrives to find nothing ready or is turned away.

Duplicate or unlinked customer accounts

Customers sign up online and at the till as separate accounts. Their account details, loyalty points, trade pricing and credit limits are not visible across channels. Returns or refunds go against the wrong account, and reconciliation is manual and error-prone.

Till transactions failing to reconcile with finance

Till refunds, discounts or adjustments are not mapped to the correct ERP nominal codes or are recorded in the wrong period. Month-end close is delayed, and cash reconciliation between till and ledger requires manual investigation and adjustment.

Branch pricing and trade accounts out of step

Promotional pricing changes are made in the ERP but not pushed to Epos Now, or they are manually entered in both systems and drift over time. Customers see different prices online and at the till, and trade account terms are not enforced consistently.

Offline or network failure breaks till and ordering

When the Epos Now cloud or network is unreachable, the till falls back to offline mode and cannot sync stock, customer accounts or pricing. Online orders for collection are not queued, and reconciliation is delayed.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Epos Now integrations.

How do branch stock levels stay in sync with ecommerce?

iWeb synchronizes stock from the ERP to Epos Now at the branch and to ecommerce on the same schedule or via event triggers. Stock adjustments made at the till are sent back to the ERP for re-publication. Buffers and channel priority rules prevent oversell.

What happens when a customer buys online and wants to collect in store?

iWeb sends the online order to Epos Now and the branch till with customer details and pick instructions. Branch staff pick and hold the item. When the customer collects, staff mark it complete in the till, and the confirmation flows back to ecommerce and email.

How are customer accounts linked between the till and ecommerce?

iWeb connects Epos Now to an identity or CRM system so that customers created online or at the till are recognized across channels. Account details, loyalty points, trade pricing and credit limits are visible at both the till and online checkout.

Do branch pricing and ecommerce pricing have to be manually entered twice?

No. iWeb publishes trade-account pricing and local promotional pricing from a central system (ERP or pricing engine) to both Epos Now and ecommerce on the same schedule. Changes take effect simultaneously, and manual dual entry is eliminated.

How do till transactions and refunds get into the ERP for finance?

iWeb maps till transactions, voids, refunds and adjustments to ERP nominal codes and cost centres, then sends them daily to the ERP. Reconciliation rules match till batches to ERP journals so month-end close does not require rework.

What if the till is offline and cannot sync with ecommerce or the ERP?

Epos Now falls back to offline mode so the till can still operate. iWeb queues transactions for sync when the network returns, and monitoring alerts the operations team so any missed orders or stock adjustments are caught.

How are returns or refunds initiated at the till reconciled with online orders?

iWeb tracks returns initiated at the till or online so that refunds, credit notes and stock movements are recorded in the ERP and reconciled to the correct order. Status flows back to the customer via ecommerce.

Who owns the integration between Epos Now, ecommerce and the ERP?

iWeb defines ownership before build: which team owns stock governance, which owns customer accounts, which owns till-transaction mapping, and who escalates exceptions. Clear ownership prevents finger-pointing when something breaks.

How does iWeb handle branch staff discounts, voids or no-sale events?

iWeb captures these transactions in Epos Now and sends them to the ERP with the correct nominal code and reason code so finance and management can track them. Compliance and audit trails are built in.

What happens if ecommerce and the till prices diverge?

iWeb monitors price differences and raises alerts before they create customer friction or reconciliation rework. Pricing governance rules ensure changes in the ERP are published to both channels simultaneously.

Can branches reserve online inventory for collection?

Yes. iWeb integrates reservation or hold rules so that when an online order is placed for a specific branch, that stock is reserved at the till and is not sold to a walk-in customer. Real-time or near-real-time stock checks prevent mismatch.

How does iWeb ensure click-and-collect does not break during peak trading?

iWeb builds queues and retry logic so that orders are delivered to the branch even if the till is briefly busy. Monitoring ensures no orders are silently dropped, and branch staff are alerted to collection deadlines.

What observability does iWeb provide for branch operations?

iWeb builds dashboards and alerts for stock drift, stuck orders, customer account mismatches, failed till transactions, click-and-collect delays and reconciliation gaps. Operations teams see issues in real time and can respond before close of business.

How often is data synchronized between Epos Now and ecommerce?

iWeb configures synchronization based on trading hours and peak demand. Stock and pricing may sync hourly or in real time; till transactions and click-and-collect orders usually sync continuously with retry logic for network hiccups.

Next step

Have a Epos Now 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 →