Skip to main content
Talk to an expert
LS Retail logo

LS Retail integration for ecommerce and retail operations

Branch stock and pricing stay visible and synced across online and offline. LS Retail at the branch feeds stock, transactions and customer events back to your ecommerce platform, ERP and OMS so that click-and-collect works, branches do not oversell, and till reconciliation stays clean. 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.

LS RetailiWeb 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 LS Retail integration gives you.

Branches see online orders in real time

Click-and-collect orders, hold instructions and customer details arrive at the branch system with clear pick workflows and collection confirmations visible to staff and the customer.

Ecommerce avoids overselling branch stock

Live or batched stock feeds from LS Retail terminals ensure that ecommerce channels see accurate branch availability and can allocate or reserve stock correctly across locations.

Trade customers see consistent pricing both channels

Trade-account pricing and local terms are synced between LS Retail and ecommerce so customers encounter the same pricing at the till and online.

Till and inventory ledgers reconcile to ERP

Transaction data, item movements and local adjustments from LS Retail feed back to the ERP in a form that finance and inventory teams can reconcile without manual rework.

Returns and refunds flow correctly across channels

In-store returns, exchanges and refund requests are captured in LS Retail and flow to ecommerce and ERP, keeping customer and financial records unified.

02 · When it's worth it

Where a LS Retail integration earns its place.

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

Click-and-collect: online orders arriving at branches for in-store pickup
Branch stock visibility: ecommerce seeing live branch stock to prevent oversell
Trade account pricing: branch trade-counter customers seeing their account pricing in-store and online
In-store transactions to ERP: till receipts and local stock movements feeding back to central ledgers
Customer account linking: in-store customer records syncing with online customer accounts
Local pricing and promotions: branch-specific or region-specific price changes flowing both ways
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.

Click-and-collect workflows may require customisation

LS Retail's native hold and collection workflows may not map directly to your ecommerce or OMS order flow, requiring mapping of order states, notification triggers and branch-staff handoff logic.

Stock reconciliation across channels can drift

Real-time stock sync between LS Retail, ecommerce and ERP can lag or conflict if local adjustments, transfers or till corrections are not clearly owned and monitored.

Trade account and pricing mapping is manual-heavy

Matching LS Retail customer records, account codes and pricing rules to ERP or ecommerce identifiers often requires careful data mapping and ongoing governance.

Till reconciliation to ERP may need post-processing

Payment methods, discounts and tax treatment in LS Retail may not reconcile directly with ERP ledger rules, requiring transformation or exception handling.

Branch staff workflows are not visible to ecommerce teams

Click-and-collect pick status, collection confirmations and failed-collection handling are local to LS Retail and may not feed back to online customer notifications or support systems.

04 · The real work

The biggest tension in branch-connected ecommerce is not the technology; it is owning the boundary between what LS Retail terminals decide in real time and what central systems enforce.

05 · Where it sits

Where this integration sits in your estate.

LS Retail 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.

Connect across your stack. LS Retail plugs into the systems that run your trading operation, whichever ecommerce platform sits at the front.

System of record
Source / owner
LS Retail
Point-of-sale and branch operations layer, feeding stock, transactions and customer activity back to central systems
  • Till transactions and receipt detail
  • Branch stock levels and local adjustments
  • In-store customer interactions and sales data
  • Click-and-collect pick and collection status
  • Returns and exchanges at the till
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Online product catalogue and availability
  • Ecommerce customer accounts and carts
  • Click-and-collect order creation and status
  • Online pricing and promotions display
  • Shipping and delivery options for non-branch orders
Connected neighbours
Integration layer
ERP
Master customer accounts, trade pricing, GL codes, reconciliation ledger
Integration layer
OMS
Order routing, click-and-collect holds, fulfilment status, returns orchestration
Integration layer
Inventory or stock system
Central stock records, allocation rules, reconciliation tracking
Integration layer
Payment platform
Payment processing, refund settlement, transaction reconciliation
Integration layer
Reporting and BI
Branch sales analytics, stock movement dashboards, transaction drill-down
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 200, NetSuite, Microsoft Dynamics, Infor)
  • OMS (order routing, click-and-collect, exceptions)
  • Inventory management system
  • Trading portal or B2B platform
  • Payments platform
  • Reporting and BI (for branch analytics)
  • Customer data platform or CRM
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: Click-and-collect orders and hold instructions flow from ecommerce or OMS into LS Retail, triggering branch staff workflows and pick notifications.
Branch stock and availability: Real-time or batch stock levels, local adjustments and transfers flow from LS Retail to ecommerce and inventory systems so online channels see accurate branch stock.
Till transactions and receipts: In-store transactions, payment summaries and item-level sales feed from LS Retail to ERP for financial reconciliation and stock movement ledgers.
Trade account and pricing: Customer account records, trade-account identifiers and local pricing rules synchronise between LS Retail and ERP or commerce so branch counters see the right customer terms.
Pricing and promotional changes: Price updates, promotions and product-level changes push from central systems into LS Retail terminals to keep in-store displays and till behaviour in line.
Customer returns and refunds: In-store returns, exchanges and refund requests flow back to ecommerce, OMS and ERP to maintain unified customer and financial 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
    Define stock ownership and allocation rules

    We agree whether branch stock is reserved for click-and-collect, allocated to online channels, or held locally, and we build the sync logic and monitoring to enforce it.

  2. 02
    Map customer and trade-account identity

    We design how LS Retail customer records, account codes and pricing rules link to ERP master data and ecommerce customer profiles so that no one gets duplicated or lost.

  3. 03
    Build click-and-collect order handoff

    We connect ecommerce or OMS order flow to LS Retail hold, pick and collection workflows with clear status feedback, exception handling and customer notifications.

  4. 04
    Reconcile till, pricing and promotional data

    We define how till transactions, discounts, tax treatment and local prices in LS Retail map to ERP ledger codes and how pricing changes flow from central systems to terminals.

  5. 05
    Monitor and govern the integration live

    We set up dashboards and alerts for stock drift, pricing mismatches, stuck orders and failed transactions so issues surface before they impact customers or reconciliation.

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 adjustments
Source / ownerLS Retail (local authority)
Maintained byBranch staff via till transactions and manual stock moves
NotesSynced to ecommerce and inventory systems at regular intervals; overstock or shortage alerts should trigger reconciliation review.
DataLocal pricing and trade-account terms
Source / ownerERP (central authority)
Maintained byERP or merchandising team; LS Retail receives and displays pushed updates
NotesLocal overrides at the till must be logged and reported; persistent discrepancies indicate control failure.
DataTill transactions, receipts and payment summaries
Source / ownerLS Retail (operational record)
Maintained byLS Retail till and payment terminal; ERP receives daily or batch summaries
NotesERP reconciliation team matches payments, discounts and tax treatment; mismatches trigger exception review.
DataCustomer accounts and trade identifiers
Source / ownerERP or identity system (master)
Maintained byERP or trading-portal admin; LS Retail caches or references for till lookup
NotesNew customer or account-flag changes must be synced promptly; stale customer data can cause pricing or credit errors at the till.
DataClick-and-collect holds and pick status
Source / ownerOMS or ecommerce order system (command authority)
Maintained byOMS creates hold instruction; LS Retail updates pick and collection status
NotesCollection completion must be reported back to ecommerce to mark order fulfilled; missing updates leave the customer order pending indefinitely.
DataReturns, exchanges and refund requests
Source / ownerOMS or returns system (authority)
Maintained byLS Retail records in-store refund or exchange; returns system ingests and reconciles
NotesRefund processing and credit application happen in ERP; LS Retail return event must be complete and timely for reconciliation to succeed.
DataIntegration transport, monitoring and exception handling
Source / ownerIntegration layer (governance)
Maintained byiWeb integration team and operations
NotesFailed syncs, stale data and reconciliation drift must be monitored and escalated; SLAs define how quickly issues are resolved.
10 · Experienced integrator

Built branch integrations before

iWeb has connected LS Retail to ecommerce, ERP and OMS platforms in multiple branch and trade-counter estates. We understand the operational tension between local till autonomy and central system governance, and we know how to design the data flows, monitoring and fallback paths so that both survive.

We map click-and-collect workflows from ecommerce or OMS into LS Retail pick and collection terminals with clear status feedback and customer notifications.
We design stock allocation rules so that branch inventory is reserved for click-and-collect, allocated to online channels or held locally according to your business policy, with monitoring to catch drift.
We handle trade-account pricing and customer-identity sync so that customers see consistent terms and credit limits across the till and ecommerce.
We build till reconciliation so that transaction details, discounts, tax and payment methods from LS Retail map to ERP ledger codes without silent mismatches.
We support offline operation and recovery so that branch till work continues if connectivity drops, with clear reconciliation and data-loss testing before go-live.
11 · Before launch

What we test before launch.

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

Verify click-and-collect orders from ecommerce arrive at the branch with complete pick instructions and appear in LS Retail within SLA window.
Confirm branch stock levels sync to ecommerce every X minutes (or hours per your policy) and ecommerce prevents oversell when stock is reserved for online or click-and-collect.
Validate till transactions reconcile to ERP: payment methods, discounts, tax treatment and item GL codes match expected ledger output.
Test trade-account customer lookup at the till matches ecommerce display and both apply correct pricing, credit terms and discounts.
Confirm in-store returns and refunds are captured in LS Retail, flow to OMS/returns system and refund payment is processed without orphaning the record.
Verify offline resilience: branch can complete transactions when connection drops and queued data syncs without loss or duplication when reconnected.
Check monitoring and exception dashboards show stock parity, pricing variance, failed syncs and reconciliation status in real time with escalation alerts.
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.

Click-and-collect orders stuck at branch

Orders may arrive in LS Retail but not trigger clear pick workflows, or collections may complete at the till but not notify ecommerce or the customer, leaving the order state broken.

Branch stock drift between till and ecommerce

Local stock adjustments, transfers or till corrections in LS Retail may not sync back to ecommerce or inventory in real time, causing oversell or false-shortage claims.

Trade-account pricing mismatches across channels

LS Retail terminals may show different account pricing than ecommerce if the data mapping breaks, local pricing is overridden at the till, or pricing feeds are stale.

Till transactions failing to reconcile to ERP

Payment methods, discounts, tax or rounding handled differently in LS Retail and ERP can cause ledger mismatches that require manual investigation or write-off.

Returns lost between branch and central systems

In-store refunds or exchanges recorded in LS Retail may not flow to ecommerce or ERP, leaving customer records incomplete and reconciliation broken.

Offline periods breaking stock and order sync

If LS Retail or the connection to ecommerce goes down, local transactions continue but do not queue for sync, causing a burst of exceptions and stale data on recovery.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about LS Retail integrations.

How do click-and-collect orders get from ecommerce to the branch?

Orders are transmitted from ecommerce or OMS to LS Retail with customer name, items, hold location and collection deadline. LS Retail staff see the pick instruction at the till, fulfill it, and scan or confirm collection when the customer arrives. Collection status flows back to ecommerce to mark the order fulfilled.

How does ecommerce know what stock is available at each branch?

LS Retail transmits stock levels from each terminal, either in real time via API or in batch feeds at intervals (hourly or daily). Ecommerce consumes these feeds and updates availability by location. Stock is reserved as committed to click-and-collect orders or held for online-channel allocation according to your stock rules.

What happens if branch stock goes out of sync with ecommerce?

The integration includes monitoring dashboards showing stock parity by location and item. Significant variance triggers an alert so the inventory or branch team can investigate. Root causes include unsynced local adjustments, transfers between branches, or till-correction delays. Regular reconciliation cycles and clear ownership prevent drift.

How are trade-account customers and pricing handled across channels?

Trade customer accounts are mastered in the ERP. Customer code, credit limit, pricing tier and applicable discounts are pushed to LS Retail terminals so staff can look up the customer at the till and apply correct pricing. The same data is available in ecommerce so online orders use the same terms. Changes to account status or pricing are synced promptly both ways.

How do till transactions and receipts reconcile with the ERP?

LS Retail produces daily or batch transaction summaries (payment methods, discounts, tax, items sold) which the integration transmits to ERP. The reconciliation team matches payments, verifies tax treatment and ensures discounts map to approved GL codes. Exceptions are flagged for investigation; the ERP then posts the transactions to the ledger.

What if a branch is offline when the integration goes down?

LS Retail is built to operate offline at the till. Transactions continue to be recorded locally. When the connection restores, queued transactions, stock moves and customer changes are synced in order. The integration includes monitoring to detect reconnection delays and reconciliation rules to catch any data loss.

How are in-store returns and refunds captured and reported?

When a customer requests a refund or exchange at the till, LS Retail records the return with item details, reason, refund amount and original order reference (if ecommerce). The return event flows to OMS or the returns system for processing. Refund approval and payment happen in ERP or the payment system; LS Retail confirms when the customer receives their money.

How do pricing changes and promotions flow to the branch?

Merchandising or pricing teams publish updates (new price, promotion, discount code) to ERP or a pricing service. The integration pushes these to LS Retail terminals on a schedule or in real time. Till staff see the active prices and promotions when they ring items. Changes are validated so that only approved pricing is live at checkout.

Can customers link their in-store and online accounts?

Yes. The customer identity system (ERP, ecommerce or identity platform) holds the master account. Customers can log in at the till using loyalty ID, email or phone, and the same account is used online. Promotions, credit, loyalty points and purchase history are visible across both channels.

What happens if the ERP is down; can branches still operate?

LS Retail continues to operate at the till and can serve customers offline. Orders for click-and-collect may be delayed if OMS is also down, but local till transactions queue. When ERP and ecommerce recover, the integration resynchronises stock, customer and pricing data and reprocesses any pending orders. Clear recovery procedures are tested before launch.

How is data quality and reconciliation monitored?

The integration includes daily or real-time dashboards showing stock parity, pricing variance, transaction counts, failed syncs and reconciliation status. Alerts trigger when variances exceed thresholds. A reconciliation team reviews exceptions and confirms that stock, pricing and customer data stay aligned. Monthly sign-offs confirm data integrity.

Who owns the decision of what stock is branch-only versus online-available?

Stock allocation rules are defined by the business (retail operations, ecommerce, inventory planning). iWeb encodes these rules in the integration so that LS Retail stock is reserved, withheld or allocated correctly. Changes to rules are managed through a change-control process and tested before they go live.

What data is kept in LS Retail and what is synced back to central systems?

LS Retail holds the till transactions, local stock adjustments, branch-level activity and customer interactions as they happen in-store. Stock levels, till summaries, transaction details, returns and customer events are synced to inventory, ERP, OMS and reporting systems according to defined frequency and data rules.

How long does it take to integrate LS Retail with ecommerce and ERP?

Integration scope depends on the complexity of click-and-collect workflows, stock allocation rules, trade-account pricing and the number of branches. Typical builds span 8-12 weeks from requirements through testing and go-live. Phased rollout (pilot branches first) is common to manage risk and refine processes.

Next step

Have a LS Retail 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 →