Skip to main content
Talk to an expert
Counterly - trade counter systems logo

Trade counter systems integration for ecommerce and retail operations

Branch and online stock, pricing and customers stay in sync seamlessly iWeb connects trade counter till systems with ERP, OMS and ecommerce so branch operations and online channels see the same stock, pricing and customer records. Click-and-collect orders flow automatically to branches. In-store transactions reconcile to the central ledger. 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.

Trade counter systemsiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Magento Open Source · Adobe Commerce · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Trade counter systems integration gives you.

Branch and ecommerce stock converge

Online channels see real branch availability; customers do not discover unavailable items at checkout. Branch staff trust ecommerce stock decisions. Oversell across channels drops.

Pricing stays governed across all channels

Trade-account pricing, bulk discounts and local overrides flow from ERP to the till. Prices at the counter match prices online. Disputes and manual corrections shrink.

Click-and-collect becomes reliable

Online orders for branch collection arrive in the till or branch management workflow automatically. Pick slips print; customers collect on time. Customer frustration and failed collections fall.

Customer accounts unify across branch and online

A customer can build loyalty and account history across both channels. Staff recognise repeat customers. Promotions and rewards work wherever the customer shops. Loyalty grows.

Reconciliation and reporting automation

Branch sales, returns, discounts and stock adjustments flow to ERP without manual entry. Day-end reconciliation is faster. Finance and inventory teams trust the numbers.

02 · When it's worth it

Where a Trade counter systems integration earns its place.

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

Sync branch stock levels with ecommerce so online channels see real availability
Publish trade-account and local pricing to the till without manual intervention
Route click-and-collect orders from online into the branch picking and dispatch workflow
Link in-store customer transactions back to online account records and loyalty programmes
Reconcile branch sales, returns and discounts back to the central ledger and reporting
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-to-branch order routing

Most trade counter systems have no automatic way to receive click-and-collect orders from your storefront. Orders land in email or a manual queue; staff miss them or route them incorrectly.

Stock synchronisation gaps

Till systems often report stock end-of-day or batch. Real-time stock changes from online don't reach the till; branch staff over-commit or sell out stock that ecommerce thinks is available.

Pricing isolated from central rules

Local overrides and trade-account pricing are often hard-coded in the till. When ERP pricing changes, staff must manually update the till or use error-prone spreadsheets.

Customer records don't travel between channels

In-store customer lookups and loyalty transactions live in the till. Online customer accounts are separate. A customer who buys both in-store and online appears as two people; loyalty is fragmented.

Manual exception handling

Returns, discounts, refunds and order exceptions are reconciled by hand or spreadsheet after the fact. Gaps between what the till recorded and what ERP received become accounting and customer-service chaos.

04 · The real work

Branch operations and ecommerce often use separate customer records and stock systems; the till sees one number, online sees another, ERP sees a third. The integration has to define which system is ground truth for each data type and handle the reconciliation when reality drifts.

05 · Where it sits

Where this integration sits in your estate.

Trade counter 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.

Works across the whole stack. Connect Trade counter systems to your storefront, ERP and everything between.

System of record
Source / owner
Trade counter systems
Captures in-store transactions, stock movements, customer records and local operational data at branch locations
  • Till and point-of-sale transactions
  • Branch stock levels and movements
  • Local customer lookups and in-store loyalty
  • Pick and collection workflows for click-and-collect orders
  • Staff and checkout operations at the branch
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Customer ecommerce accounts and online identity
  • Storefront browsing and online cart
  • Online order placement and checkout
  • Click-and-collect order intake
  • Online customer communication and order tracking
Connected neighbours
Integration layer
ERP
Holds customer master, pricing rules, trade-account tiers, product master, stock ledger and financial records. Till transactions flow to ERP; pricing rules flow from ERP to till.
Integration layer
OMS
Routes click-and-collect orders from ecommerce to the branch and manages order status and fulfillment visibility across all channels.
Integration layer
Ecommerce platform
Manages online storefronts, customer accounts and checkout. Consumes stock from ERP; sends click-and-collect orders to OMS; receives pricing from ERP.
Integration layer
Inventory management
Holds consolidated stock view across all locations. Till feeds stock movements; ecommerce consumes allocated stock; OMS reserves stock for orders.
Integration layer
Loyalty platform
May hold unified loyalty balance and transaction history across till and online. Till and ecommerce both update and read loyalty state.
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)
  • Magento Open Source
  • Adobe Commerce
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (Sage, NetSuite, Microsoft Dynamics, SAP)
  • OMS (order routing and fulfilment orchestration)
  • Till system (EPOS, NCR, Tiller, Lightspeed)
  • Inventory management (stock visibility and allocation)
  • Customer data platform or ERP customer master
  • Loyalty platform
  • Branch management or warehouse management system
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 & ERP
↔BOTH WAYS
Stock changes at till: Stock movements, sales and adjustments recorded at the till flow to ERP and OMS so ecommerce sees real branch availability
Branch stock feeds online stock algorithms and availability messaging.
Pricing and promotions to till: Base pricing, trade-account pricing, promotions and local overrides flow from ERP to the till system
Staff see correct prices; customers pay the right amount; discounts are tracked.
Click-and-collect orders: Online orders flagged for branch collection arrive at the till or branch management system
Staff pick, pack and stage goods; customer collects in-store with receipt or online ID.
In-store transactions: Till receipts, payment details, returned items and staff-authored sales flow to ERP and reporting
Finance sees branch turnover; reporting teams see channel mix and product performance.
Customer account linkage: Customer records created or updated online sync to branch so staff recognise repeat customers
Branch transactions and loyalty activity feed back to the online customer profile.
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
    Stock synchronisation engine

    We build the inbound flow from the till to ERP and OMS that captures stock movements in real time or near-real time. eCommerce stock APIs pull live availability. Oversell risk and stock drift drop.

  2. 02
    Pricing and discount distribution

    We design the outbound flow from ERP that publishes base prices, trade-account pricing and promotions to the till system. Staff and customers see the correct price without manual intervention.

  3. 03
    Order ingestion and branch routing

    We build the inbound flow from your storefront that captures click-and-collect orders and routes them to the branch till, management system or picking solution. Orders arrive automatically and on time.

  4. 04
    Customer record linkage and synchronisation

    We design the bidirectional flow that links ecommerce customer records with till customer lookups. Online updates propagate to the branch; branch transactions and loyalty activities feed back to the online profile.

  5. 05
    Exception handling and reconciliation

    We map the failures: offline till periods, stock adjustments that arrive out of order, returns and refunds that need to be matched back to the original transaction. We build the monitoring and reconciliation layer that surfaces these exceptions so you can fix them intentionally, not discover them during audit.

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 / ownerTill system (local reality); ERP (central record)
Maintained byTill at branch; synchronised to ERP; ecommerce consumes ERP stock via OMS / inventory API
NotesTill stock is ground truth for the branch; ERP holds the consolidated view; ecommerce must see ERP stock to avoid oversell across channels.
DataTrade-account pricing and local overrides
Source / ownerERP (base and trade-account pricing rules)
Maintained byERP publishes to till; till applies at checkout; exceptions flagged to finance for review
NotesERP owns pricing rules and customer account tiers; till applies them; mismatches are a reconciliation risk.
DataClick-and-collect order intake and status
Source / ownerOMS or branch order management system
Maintained byEcommerce captures the order; OMS routes to branch; till or branch system manages pick and collection
NotesOrder originates online; branch must see it promptly; collection status must flow back to ecommerce for customer visibility.
DataIn-store customer records and transactions
Source / ownerTill system (in-store transactions); ERP (customer master)
Maintained byTill records sales and returns; ERP holds customer accounts; ecommerce customer profile linked to ERP customer
NotesTill transactions must flow to ERP for financial reporting; customer identity must link across till, ERP and ecommerce to enable unified loyalty and personalisation.
DataBranch sales, returns and reconciliation data
Source / ownerERP (financial record)
Maintained byTill captures transactions; flows to ERP; finance reconciles daily or periodically
NotesTill is the capture point; ERP is the financial ledger; exceptions between till and ERP reconciliation must be surfaced and resolved before month-end.
10 · Experienced integrator

Built this before

iWeb has integrated till systems with ERP, OMS and ecommerce platforms for retail and trade operations. We understand the branch operational rhythm, the need for real-time stock sync, the complexity of unified customer records across channels, and the reconciliation discipline that keeps branch operations and online channels in step.

We map the till-to-ERP stock and transaction flow, handle offline queuing and reconciliation, and ensure ecommerce sees real branch availability without oversell risk.
We design the pricing flow from ERP to the till, handle trade-account and local overrides, and prevent pricing drift between till and ecommerce.
We build the click-and-collect routing so online orders arrive in the branch till automatically, pick slips print on time, and collection status flows back to the customer.
We design customer record linkage so branch staff recognise repeat customers, loyalty works across channels, and in-store transactions feed back to the online account.
We build the exception and reconciliation layer so operations can trust that branch stock, pricing and customer data are consistent with ERP and ecommerce without manual daily fixes.
11 · Before launch

What we test before launch.

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

Verify stock movements from till (sales, returns, adjustments) reach ERP and ecommerce within the expected time window; check parity between till reported stock and ERP consolidated stock at day-end.
Test click-and-collect orders: place an online order flagged for branch collection, confirm it appears in the branch till or management system, pick and stage the goods, confirm collection status flows back to ecommerce and the customer sees it.
Confirm ERP pricing changes (bulk updates, trade-account tier changes, promotions) flow to the till and apply at the next transaction; verify staff and customers see the new price.
Link a customer record that exists both online and in-store; confirm till staff can look up the customer by email or phone, see online order history and loyalty balance, and that in-store transactions flow back to the online customer profile.
Simulate till offline: perform transactions while disconnected, restore connectivity, confirm queued transactions replay to ERP and ecommerce in the correct order with no gaps or duplicates.
Reconciliation: run the day-end reconciliation report; check stock parity between till and ERP, pricing agreement between till and ERP, and customer record consistency across all systems; confirm any exceptions are surfaced and actionable.
Test exception handling: process a return that originated online, confirm the refund is matched to the original order and the customer's online account is credited; repeat for an in-store return linked to an online order.
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.

Stock drift between till and ecommerce

If the till reports stock end-of-day but ecommerce stock updates in real time, a customer orders online while the till is finishing a large transaction. The branch sells the last unit. Ecommerce promises the next unit is in stock. One customer goes unsatisfied.

Click-and-collect orders lost at the branch

If orders do not reach the till or branch management system automatically, they sit in email or a shared folder. Staff miss them. Customers wait. Refunds and complaints follow.

Trade-account pricing mismatches

If the till pricing is hard-coded and ERP pricing changes, the till still charges the old price or staff manually override. Invoices and customer statements do not match what was actually charged. Finance reconciliation fails.

In-store customer records do not link to online

If the till customer lookup is separate from the ecommerce customer account, a returning customer is treated as new both times. Loyalty is fragmented. Personalisation and cross-channel offers do not work.

Returns and refunds booked against the wrong channel

If an in-store return is not clearly linked to the original online order (or vice versa), accounting records the reversal in the wrong ledger. Refund reconciliation drifts. Customer account balances become hard to trust.

Offline till periods breaking synchronisation

When the till loses connectivity, stock movements, sales and customer changes are queued locally. When connectivity resumes, if the queue is not processed in the right order, stock counts in ERP can become inconsistent with what the till recorded.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Trade counter systems integrations.

How do we keep ecommerce stock in sync with branch stock?

The integration captures stock movements from the till (sales, returns, adjustments) and flows them to ERP in real time or batch. OMS or your inventory API pulls the consolidated branch stock from ERP so ecommerce knows real availability. If the till is offline, stock changes are queued and replayed when connectivity resumes, in the correct order.

What happens to trade-account pricing when ERP pricing changes?

ERP publishes trade-account pricing rules and customer-account tiers to the till system. When ERP pricing changes, the till receives the update and applies the new price at the next transaction. Overrides or delays are flagged so finance can spot them. Pricing is not hard-coded in the till; it is always ERP-driven.

How do click-and-collect orders reach the branch?

Ecommerce captures the order and flags it for branch collection. The order flows to OMS and is routed to the branch till or branch management system. A pick slip prints or a notification appears on the till screen. Branch staff pick, pack and stage the goods. When the customer arrives, the till looks up the order and completes collection.

Can a customer who buys online also be recognised in-store?

Yes. The integration links ecommerce customer records to ERP customer master records. When a customer walks into the branch, staff can look them up by email, phone or loyalty number. The till sees their account history, loyalty balance and any online orders they have placed. Loyalty and personalisation work across both channels.

How do in-store returns and refunds get recorded in ERP?

Till staff record the return or refund at the branch point of sale. The transaction flows to ERP with a reference to the original order (online or in-store). Finance sees the reversal in the correct ledger. If the original order was online, the refund is matched back to that transaction so the customer's account is accurate.

What if the till goes offline?

The till continues to operate and queues transactions (sales, returns, stock adjustments, customer changes) locally. When connectivity resumes, the queue is replayed to ERP and ecommerce in the order transactions happened. Stock counts are reconciled; customer records are updated. The integration ensures no transactions are lost or duplicated.

How do we know branch stock, pricing and customer data are in sync?

The integration builds a reconciliation layer that checks branch stock against ERP at day-end (or on-demand), flags pricing mismatches between till and ERP, and audits customer record consistency across till, ERP and ecommerce. Exceptions are surfaced in a dashboard so operations and finance can investigate and resolve them before they become bigger problems.

Can we bulk-update branch pricing without touching the till manually?

Yes. ERP publishes pricing updates to the till system automatically. Bulk changes (promotional pricing, seasonal adjustments, trade-account tier updates) all flow from ERP without manual till configuration. Staff do not need to re-key prices or apply spreadsheet updates.

How do we prevent oversell when both branch and ecommerce are selling the same stock?

OMS or inventory management holds a reserved pool of stock for each branch and channel. When a customer buys online, stock is reserved for that channel. When the till sells, the till reports the movement immediately (or batch). ERP sees the consolidated position and ecommerce is fed the true available quantity. Oversell across channels is prevented by allocation rules, not manual tracking.

What data flows back to reporting and finance?

Till sales, returns, discounts and stock adjustments flow to ERP daily (or per-shift). Finance sees branch turnover by product and customer. Reporting teams see channel mix (branch vs. online), product performance across channels, and customer behaviour by location. All data is sourced from the integration, not manually entered spreadsheets.

How does the integration handle multiple branches?

Each branch till is configured as a separate location in ERP and OMS. Stock, pricing and customer records are branch-aware. Orders can be routed to the nearest branch for click-and-collect. Pricing can vary by branch (local promotions). Stock visibility is by location. Reconciliation and reporting roll up across all branches into the central ledger.

Can we still run local branch stock takes and adjustments?

Yes. Branch staff can perform a stock take at the till, record adjustments and submit them. Adjustments flow to ERP, are marked for review by central inventory, and are reconciled against the ERP count. The integration does not prevent local management; it ensures adjustments are transparent and governed.

What happens if ecommerce and the till disagree on a customer's loyalty balance?

The integration defines a source of truth for loyalty (usually ERP or a dedicated loyalty platform). Both till and ecommerce pull the current balance from that system at checkout. When a customer makes a purchase (online or in-store), the loyalty transaction is recorded immediately and is visible to both channels. Discrepancies are flagged by the reconciliation layer for investigation.

Next step

Have a Trade counter 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 →