Skip to main content
Talk to an expert
Border CounterAct logo

Border CounterAct integration for ecommerce and retail operations

Branch and online stock, pricing and customers stay in sync. iWeb integrates Border CounterAct with your ecommerce storefront and ERP to give trade customers consistent pricing and credit limits, branch staff real-time visibility of online orders for pickup, and finance teams reliable nightly till-to-ERP 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.

Border CounterActiWeb 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 Border CounterAct integration gives you.

Unified stock visibility across till and online

Customers see accurate local availability when they browse the storefront. Branch staff can fulfill online orders confidently. Oversell across channels drops.

Trade-account pricing and credit enforced at checkout

Trade customers get the correct negotiated pricing and credit limits both online and at the counter. Manual pricing lookups and overrides disappear.

Click-and-collect orders arrive at the branch automatically

When an online customer orders for local pickup, the order routes directly to the branch till system. Staff receive alerts, prepare stock and track the customer.

Daily till-to-ERP reconciliation is automated and clear

Till totals, cash counts, refunds and trade-account sales post to ERP nightly. Finance teams see current ledger without manual spreadsheet work.

Unified customer account across online and in-store

Branch staff can see the customer's online order history and ecommerce account status. Cross-channel customer service becomes possible.

02 · When it's worth it

Where a Border CounterAct integration earns its place.

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

Trade-account customers placing orders on the ecommerce storefront and seeing their negotiated pricing and credit limits
Branch staff accessing online orders for click-and-collect pickup with real-time inventory visibility
Local stock levels and branch-specific pricing syncing from ERP to the till and storefront
In-store transactions posting to ERP ledger and feeding into order and financial reconciliation
Trade accounts linking branch till activity with online customer records for unified customer view
Returns and refunds initiated at the counter flowing back to ecommerce and ERP
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.

Trade-account pricing not automated to till

CounterAct may not automatically refresh negotiated customer pricing or credit limits from ERP during a shift, leaving branch staff to manually override or check spreadsheets.

Click-and-collect orders require manual handoff

CounterAct does not natively ingest ecommerce orders; staff must check email or a separate system, risking missed or delayed fulfillment and poor customer experience.

Stock visibility is branch-only by default

Till stock levels may not synchronize to the online storefront, causing oversell or confusion when ecommerce shows items as available but the branch is out of stock.

End-of-day reconciliation is manual and slow

Till data and ERP ledger reconciliation often require manual spreadsheet work, delaying financial close and hiding discrepancies until the next day.

Customer identity and online accounts not linked

Branch till records and online customer profiles may exist in silos, so staff cannot see a unified customer history or apply consistent account credit and pricing rules.

04 · The real work

Branch teams and ecommerce often operate as separate islands—till stock diverges from online availability, trade customers see different prices at the counter and storefront, and online orders for local pickup arrive as emails that staff may miss. The integration work is really about deciding which system is the source of truth for each piece of data and making sure the till and storefront are always working from the same current values.

05 · Where it sits

Where this integration sits in your estate.

Border CounterAct 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.

Built for your platform, not a specific one. Border CounterAct integrates with any ecommerce core through the same contract.

System of record
Source / owner
Border CounterAct
Branch point-of-sale and trade counter system for till transactions, local inventory and customer accounts.
  • Till transactions and daily cash reconciliation
  • In-store customer interactions and returns
  • Local branch stock visibility
  • Trade-account customer sessions and identity
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Online product catalogue and checkout
  • Customer account and login
  • Click-and-collect order capture
  • Storefront inventory display
Connected neighbours
Integration layer
ERP
Source of truth for stock levels, base and trade-account pricing, customer credit limits and financial ledger.
Integration layer
OMS
Routes and tracks click-and-collect orders from ecommerce to the branch, manages order status and fulfillment confirmation.
Integration layer
eCommerce storefront
Displays branch stock and trade-account pricing to online customers; captures click-and-collect orders.
Integration layer
Stock management
ERP-based inventory feeds stock levels and rules to the till; till transactions post adjustments back to ERP.
Integration layer
Pricing engine
ERP pricing rules, including trade-account tiers and local variations, flow to the till and storefront.
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 (Sage, NetSuite, Infor)
  • OMS for click-and-collect order routing
  • eCommerce storefront
  • Trade-account customer master
  • Stock and pricing feed engine
  • POS reconciliation and reporting
  • Payments processor
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 & COMMERCE
←From ERP
↔BOTH WAYS
Stock and pricing to the branch: Branch stock levels, local pricing and trade-account pricing rules flow from ERP to CounterAct at scheduled intervals or on-demand
The till displays current availability and customer-specific costs.
Till transactions and reconciliation: Daily till totals, cash reconciliation, trade-account sales and refunds post to ERP via a reconciliation feed
This keeps the general ledger and customer accounts current.
Trade-account linking and credit: Trade-account customer records sync bidirectionally between ERP and the till, including credit limits, payment terms and account balance
ERP updates propagate to the till; till sales update account ledger.
Online orders for click-and-collect: Orders placed on the ecommerce storefront for local pickup route to the branch via OMS or manual handoff
Branch staff retrieve the order, confirm stock and prepare for collection.
Branch stock availability to storefront: Local branch stock levels feed to the ecommerce storefront so online customers can see if items are available for click-and-collect or same-day local delivery.
Customer account and returns: In-store customer identity can link to online customer records for unified account visibility
Returns initiated at the counter post back to ERP and update online order records.
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
    Design trade-account pricing and stock rules

    We map which customer attributes (account type, credit limit, local pricing tier) flow from ERP to the till and how they refresh. We define fallback rules if ERP is unavailable.

  2. 02
    Build the click-and-collect handoff

    We connect ecommerce orders to OMS or CounterAct directly, with confirmation and customer notification. We ensure the branch has real-time visibility of pickup status.

  3. 03
    Implement stock sync from ERP to till and storefront

    We set up scheduled or event-driven stock feeds so that branch inventory, ERP ledger and ecommerce display stay aligned. We define the reconciliation window and tolerance.

  4. 04
    Automate till-to-ERP reconciliation

    We build the nightly posting of till totals, refunds, trade-account sales and cash reconciliation to ERP. We create alerts for discrepancies and stuck items.

  5. 05
    Link customer identity across systems

    We define how branch till customers map to ecommerce customer records, so that account credit, pricing, order history and support cases stay unified.

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 local inventory
Source / ownerERP
Maintained byBranch counts and ERP posting
NotesTill displays current ERP stock; discrepancies are flagged for branch count and ERP adjustment.
DataLocal and trade-account pricing
Source / ownerERP
Maintained byERP pricing rules, branch configuration
NotesTill retrieves pricing from ERP at shift start and applies customer-specific rules; manual override is logged.
DataTrade-account customer records and credit limits
Source / ownerERP
Maintained byERP and till transaction posting
NotesCustomer record, credit limit and payment terms live in ERP; till posts daily sales and refunds; ecommerce reads ERP for pricing and credit on checkout.
DataTill transactions, cash reconciliation and daily sales
Source / ownerCounterAct
Maintained byBranch till operators and reconciliation process
NotesTill records the authoritative transaction detail; a nightly reconciliation feed posts totals and refunds to ERP ledger.
DataClick-and-collect orders and pickup status
Source / ownerOMS or ecommerce
Maintained byOrder capture and branch confirmation
NotesOrder originates in ecommerce and routes via OMS to the till; branch staff confirm stock and fulfillment status back to OMS and customer.
DataIn-store returns and refunds
Source / ownerCounterAct and ERP
Maintained byBranch staff and till posting
NotesReturn is recorded at the till; refund posts to ERP ledger and updates trade-account balance. If an online order, return event propagates back to ecommerce.
DataIntegration transport, monitoring and exception handling
Source / ownerIntegration layer
Maintained byiWeb and branch operations team
NotesAll flows are monitored; failures trigger alerts. Exception queue holds stuck orders and reconciliation gaps until resolved.
10 · Experienced integrator

Built this before

iWeb has integrated Border CounterAct with major retail and trade-merchant estates. We understand how the till sits between ERP, local stock, trade-account pricing and ecommerce, and we know the data ownership and reconciliation patterns that keep both channels accurate.

We design the stock and pricing flows from ERP to the till and storefront, and handle the reconciliation when they drift.
We build click-and-collect handoffs so that online orders route to the branch till in real-time with clear fulfillment status.
We map trade-account rules (pricing tiers, credit limits) from ERP to the till and ecommerce so customers see consistent terms.
We automate till-to-ERP reconciliation so that daily sales, refunds and cash reconciliation post reliably without manual spreadsheet work.
We define monitoring and fallback behaviour so that offline periods, ERP downtime and data drift are surfaced and handled before they disrupt the branch or customer experience.
11 · Before launch

What we test before launch.

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

Verify that trade-account pricing rules from ERP refresh correctly at till start and on-demand, and that storefront applies the same pricing.
Confirm that stock levels sync from ERP to both the till and ecommerce, and that a till sale immediately decrements stock visible on the storefront.
Test a click-and-collect order from the storefront: confirm it arrives in the till, staff can confirm stock, and the customer receives a pickup notification.
Run a full day of till transactions (sales, refunds, discounts, payments) and verify the nightly reconciliation feed posts correctly to ERP ledger without gaps or duplicates.
Test offline mode: disable the till's connection to ERP, perform sales, restore connection, and confirm all transactions sync without loss or corruption.
Verify that a customer return at the branch posts to ERP, updates the trade-account balance, and if the item was ordered online, the online order record reflects the return.
Check monitoring and alerting: simulate a failed stock sync, hung reconciliation, and pricing rule mismatch; confirm iWeb alerts are triggered and the exception queue captures the issue for triage.
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 levels drift between till, ERP and ecommerce

If stock feeds from ERP to till or storefront are delayed or fail silently, the branch may sell stock that ecommerce has already committed, causing fulfillment failures and customer complaints.

Trade-account pricing fails to update at the till

If negotiated customer pricing or credit limits do not refresh on the till at the start of the day, staff either charge the wrong price or approve credit they should not, causing revenue leakage and bad debt.

Click-and-collect orders are missed or delayed at the branch

If ecommerce orders do not route reliably to CounterAct or staff do not see pickup alerts, customers arrive to collect non-existent stock or wait hours without notification.

Till-to-ERP reconciliation hangs or falls silent

If the nightly posting of till data to ERP stalls or fails, finance teams reconcile to an out-of-date ledger, causing month-end delays and hidden discrepancies.

Customer accounts become duplicates or unlinked

If branch till customers are not cleanly mapped to ecommerce records, staff see a fragmented view, trade-account rules do not apply consistently and customer service cannot access full history.

Offline periods break stock and pricing sync

If the branch loses connectivity to ERP or the internet, the till continues to operate but stock and pricing become stale. When the connection returns, reconciliation may be complex and manual.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Border CounterAct integrations.

How does the branch see real-time online orders for click-and-collect?

Orders placed on the ecommerce storefront for local pickup route to the branch via OMS or direct integration to CounterAct. The till displays a pickup queue with customer name, order contents and expected collection time. Staff confirm stock availability and update the customer when the order is ready.

Can trade-account customers see their negotiated pricing on the storefront?

Yes. When a trade-account customer logs into ecommerce, the storefront retrieves their account tier and pricing rules from ERP via the integration. Cart and checkout show the correct negotiated prices. The same pricing applies at the till when the customer visits the branch.

How does the till know current stock levels if inventory is managed in ERP?

Branch stock levels sync from ERP to CounterAct at scheduled intervals (e.g. hourly) or via near-real-time events. The till displays current availability and prevents oversell. If ERP is unreachable, the till operates on cached stock with a warning to staff.

How do till sales and refunds post to the ERP ledger?

At the end of each shift or daily, the till exports transaction totals, refunds, discounts and cash reconciliation. The integration posts these to ERP as sales ledger entries and updates trade-account customer balances. The process is automated and flagged for exceptions.

What happens if a customer's trade-account credit limit changes in ERP while they are shopping at the branch?

The till refreshes trade-account rules at shift start and typically once per day. If a credit limit changes urgently during the day, staff can request a manual refresh via the till interface or fallback to a manual credit check with management approval.

Can an online customer see branch stock availability when browsing the storefront?

Yes, if the integration syncs branch stock to ERP and ecommerce displays it. The storefront can show local availability and offer click-and-collect pickup. Stock feeds update regularly so the customer sees current status.

How do in-store returns get recorded across ERP and ecommerce?

When a customer returns an item at the branch, staff enter a return in the till. The till posts the refund to ERP, updating the customer's account balance. If the item was ordered online, a return event propagates back to the ecommerce system so the order record is accurate.

What happens to the till if the connection to ERP drops?

The till continues to operate in offline mode using cached stock and pricing. Once the connection returns, pending transactions are synced to ERP and reconciliation is reconciled. The integration alerts operations to any drift.

How is customer identity managed across the till and ecommerce?

Trade-account customer records live in ERP with a unique customer ID. The till and ecommerce both reference this ID. When a customer visits the branch or the storefront, their account, credit, pricing and order history are visible. Returns and account changes sync bidirectionally.

Who owns the reconciliation process between the till and ERP?

The branch team reconciles the till cash and receipts each day. The integration automatically posts till totals to ERP. iWeb monitors the feed for failures. A designated operations or finance team owns the exception queue and investigates discrepancies.

Can branch staff override prices at the till, and how does that affect ecommerce pricing?

Branch staff can apply manual discounts or overrides at the till for approved reasons (e.g. damage, loyalty). These are logged in the till and do not affect the ecommerce storefront pricing. Overrides are flagged in the reconciliation feed so finance teams can review them.

How does the integration handle the case where ecommerce and the till have different stock counts for the same item?

The integration syncs stock from ERP as the source of truth to both the till and ecommerce. If discrepancies occur (e.g. till miscounts or unposted sales), they are flagged in the reconciliation process. The branch and finance teams investigate and correct the ERP record; both channels then refresh from ERP.

What payment methods are supported at the till via the integration?

The till supports card, cash and trade-account payment. Trade-account payments update the customer's ERP balance. Card and cash are reconciled daily. If ecommerce accepts additional payment methods (e.g. buy-now-pay-later), those are separate from the till integration and reconcile via their own payment gateway.

How are multi-branch businesses handled? Can a customer order from Branch A for pickup at Branch B?

If multiple branches are integrated, the OMS or ecommerce routing logic can assign orders to the customer's preferred branch or nearest location. Branch B's till receives the order in its pickup queue. Stock reservations and fulfillment status are tracked per branch.

Next step

Have a Border CounterAct 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 →