Skip to main content
Talk to an expert
Lightspeed logo

Lightspeed integration for ecommerce and retail operations

Branch stock and ecommerce in sync, click-and-collect working Lightspeed till operations and branch stock feed ecommerce visibility, click-and-collect orders route to locations cleanly, and till transactions post to your ERP. 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.

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

What a Lightspeed integration gives you.

Branch stock trusted by ecommerce

Checkout logic reflects current branch capacity so customers see accurate availability and collection windows. Oversell incidents and collection delays drop.

Click-and-collect order confidence

Ecommerce orders route cleanly to branches with full customer and item detail. Branch staff confirm readiness without hunting for the order or customer record.

Till data feeds finance on schedule

Daily till closures, refunds and payment movements post to the ERP automatically. Month-end reconciliation shifts from manual hunt-and-peck to variance review.

Trade accounts work across channels

Customers see consistent pricing and account balance whether shopping in-store or online. Account holds, credit limits and discount rules apply uniformly.

Customer history visible everywhere

Till staff and ecommerce service teams see the same customer record and purchase timeline, whether sales happened in-store or online.

02 · When it's worth it

Where a Lightspeed integration earns its place.

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

Branch stock visibility in ecommerce and vice versa
Click-and-collect order handoff from ecommerce to branches
Trade account and local pricing synchronisation
Till transactions feeding back to ERP and finance
In-store customer record linkage with online accounts
Branch-to-ecommerce returns and refund workflows
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.

Stock visibility is batch, not real-time

Lightspeed's default stock export runs on a schedule. Ecommerce may not see branch availability updates for 15-60 minutes, creating windows where online checkout and branch capacity drift.

Click-and-collect workflows are partial

Lightspeed does not natively publish ready-for-collection status back to ecommerce or customer notification systems. Manual confirmation or third-party apps are often needed to close the loop.

Till and ERP reconciliation is manual

Payment tenders, refunds and till-close discrepancies typically require manual review or custom reconciliation logic. Automatic posting to the ERP general ledger is not standard.

Trade-account pricing lacks ecommerce sync

Lightspeed stores trade customer discounts and account rules locally. Syncing those rules to ecommerce pricing engines or checkout logic requires custom fields and mapping.

Multi-location customer identity is ambiguous

Lightspeed manages customers per location by default. Linking in-store customer records to a single ecommerce identity and loyalty account requires extra identity resolution and API work.

04 · The real work

Till operations and ecommerce must stay separate until stock and customer identity are clearly owned; without that clarity, click-and-collect gets stuck in manual workarounds and oversell multiplies.

05 · Where it sits

Where this integration sits in your estate.

Lightspeed 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. Lightspeed integrates with any ecommerce core through the same contract.

System of record
Source / owner
Lightspeed
Point-of-sale, retail management and branch stock system
  • Till transactions and end-of-day settlement
  • Branch stock levels and reserves
  • In-store customer lookups and loyalty
  • Local pricing and trade-account rules cache
  • Pick and readiness for click-and-collect orders
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceShopify PlusMagento Open SourceBigCommerceOther storefronts
  • Ecommerce customer master and orders
  • Online checkout and cart
  • Inventory visibility and availability messaging
  • Click-and-collect order initiation
  • Omnichannel customer identity and loyalty
Connected neighbours
Integration layer
ERP
Source of trade-account pricing, credit limits, GL codes and finance reconciliation.
Integration layer
OMS
Order routing decisions, fulfilment allocation and customer-service visibility.
Integration layer
CRM
Customer master, loyalty and behavioural events; till transactions feed back loyalty activity.
Integration layer
Payment systems
Refunds from till transactions and click-and-collect returns route back to payment processor.
Integration layer
Reporting and BI
Till sales, stock movements and click-and-collect conversion metrics exported for analysis.
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
  • Shopify Plus
  • Magento Open Source
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (NetSuite, Sage, SAP)
  • OMS (order routing and fulfilment)
  • PIM (trade-account pricing and rules)
  • CRM (customer identity and loyalty)
  • Payment systems (refund and settlement)
  • Finance / general ledger
  • Reporting and BI 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 RETAIL
←From RETAIL
↔BOTH WAYS
Branch stock levels to ecommerce: Stock balances, reserves and availability from Lightspeed locations feed back to the ecommerce platform and connected OMS or ERP, so online checkout reflects current branch capacity
Real-time or near-real-time updates prevent oversell across channels.
Click-and-collect orders to branches: Ecommerce orders tagged for collection route into Lightspeed locations with pick instructions, customer identity and collection window
Branch staff confirm availability and readiness through the till system.
Till transactions to ERP and finance: In-store sales, refunds and payment tender data from Lightspeed tills export to the ERP and finance systems for reconciliation, tax treatment and ledger posting
Daily settlement files or event streams capture transaction detail.
Branch pricing and trade-account rules: Trade account pricing, local promotions and discount eligibility sync from ERP or PIM to Lightspeed terminals, and branch staff actions (account lookups, manual overrides) feed back for audit and compliance.
Customer account linkage: Online customer records and loyalty identifiers route into Lightspeed so till staff can recall purchase history, account balance and preference data
Conversely, in-store loyalty transactions flow back to the ecommerce CRM.
Returns and refund events: In-store returns trigger credit-note or refund events that travel to ERP, payment systems and the ecommerce order record
Online returns authorised via ecommerce or OMS route instructions to branches for local processing.
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 sync and allocation design

    iWeb designs the polling frequency, reserve logic and fallback behaviour for branch stock feeds to ecommerce. We define which locations feed which checkout regions and how system downtime is handled.

  2. 02
    Click-and-collect order routing

    iWeb builds the order-to-branch routing logic, handles order handoff into Lightspeed, monitors pick and readiness status, and triggers customer collection notifications.

  3. 03
    Till reconciliation and finance posting

    iWeb maps till tenders, refunds, discounts and adjustments to ERP accounts. We build daily settlement feeds and exception queues so unposted or unmatched transactions surface for review.

  4. 04
    Trade-account pricing synchronisation

    iWeb extracts trade-account discounts and local pricing from the ERP or PIM, formats them for Lightspeed upload, and keeps ecommerce checkout pricing in sync with branch pricing rules.

  5. 05
    Multi-location customer identity

    iWeb designs the customer ID resolution so Lightspeed per-location records link to the ecommerce customer account. We handle loyalty lookups, account-balance checks and returns routing from either channel.

  6. 06
    Monitoring and exception handling

    iWeb sets up observability for stock feeds, click-and-collect order status, till posting, and customer-record sync. Exception queues flag stock mismatches, unposted tills or orphaned orders for immediate review.

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 availability
Source / ownerLightspeed (per location)
Maintained byWarehouse and branch staff via till and inventory adjustments
NotesEcommerce reads branch availability; OMS or ERP may hold central reserves. Sync frequency defines how long branches hold stock before ecommerce sees it.
DataClick-and-collect orders and fulfilment status
Source / ownerEcommerce platform and OMS (order created) + Lightspeed (pick and readiness)
Maintained byEcommerce order entry + branch pick and confirmation workflows
NotesOrder routes to branch; branch staff confirm readiness; status travels back to ecommerce for customer notification.
DataTill transactions, refunds and payment tenders
Source / ownerLightspeed (transaction record) + ERP (posted account)
Maintained byTill operators during the day; reconciliation and posting at close and month-end
NotesLightspeed is the transaction ledger; ERP is the financial ledger. Daily settlement files or API events carry the posting.
DataTrade-account pricing, discounts and local pricing
Source / ownerERP or PIM (master) + Lightspeed (cache at each location)
Maintained byFinance or merchandising team; pushed to Lightspeed on schedule
NotesPricing rules originate in ERP/PIM; Lightspeed terminals cache them. Ecommerce checkout also caches or looks up the same rules.
DataCustomer account, loyalty and purchase history
Source / ownerEcommerce platform and CRM (master); Lightspeed (local cache per location)
Maintained byCustomer registration and CRM; synced to Lightspeed for till lookups
NotesEcommerce customer record is the single source; Lightspeed caches identity and balance for till staff. In-store loyalty transactions feed back to CRM.
DataReturns, refunds and credit notes
Source / ownerLightspeed (in-store return) or Ecommerce/OMS (online return); ERP (final credit note)
Maintained byBranch staff or customer-service team; reconciled by finance
NotesEither channel can initiate. Refund and credit note flow back to payment system and ERP. Ecommerce order record updated to reflect the return.
DataIntegration transport, monitoring and exception handling
Source / owneriWeb integration layer
Maintained byiWeb support and operational teams
NotesStock feeds, order routing, till posting and customer sync all monitored. Exception queues flag stock drift, unposted tills, orphaned orders and mismatched pricing.
10 · Experienced integrator

Built branch sync before

iWeb has designed and built Lightspeed integrations into ecommerce estates where branches, trade counters and click-and-collect matter. We understand how till operations, stock reserves, customer identity and pricing rules need to move between locations and the online storefront without manual handoff.

We design stock-sync patterns that balance real-time accuracy with cost and system load, and handle branch downtime gracefully.
We build click-and-collect workflows including order routing, location confirmation and customer collection notification end-to-end.
We map till transactions and refunds to ERP GL codes so finance posting is automatic and month-end reconciliation is variance-driven.
We handle trade-account pricing and customer identity resolution so Lightspeed tills and ecommerce checkout enforce the same rules.
We set up observability and exception queues so stock drift, unshipped click-and-collect orders and unposted tills surface immediately.
11 · Before launch

What we test before launch.

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

Stock parity: verify branch stock visible in ecommerce checkout within the defined sync window and reflects reserve thresholds.
Click-and-collect routing: send test orders to each location, confirm they appear in Lightspeed, and verify readiness status returns to ecommerce for customer notification.
Till posting: run a full trade-day simulation with refunds and discounts, confirm all tenders and adjustments post to ERP GL codes and month-end reconciliation finds no gaps.
Trade-account pricing: update an account discount in ERP, confirm Lightspeed tills and ecommerce checkout apply the new price within the sync window.
Customer lookup: create an online customer, sync to Lightspeed, verify till staff can recall ecommerce purchase history and account balance.
Fallback behaviour: simulate Lightspeed outage during high ecommerce traffic; confirm orders queue and stock sync resumes cleanly when service returns.
Exception handling: trigger unposted till errors, stuck click-and-collect orders and pricing mismatches; verify alerts surface and exception queues are actionable.
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 across channels during peak

High-velocity sales on ecommerce or in-store can outpace stock sync. A branch may show stock available online while it sells the last unit at the till, or ecommerce oversells a branch location.

Click-and-collect orders stuck in limbo

Ecommerce order routes to a branch but branch staff don't see it in Lightspeed, or pick and readiness status never routes back to ecommerce. Customer waits without knowing their order status.

Till transactions don't post to ERP

End-of-day settlement files don't match till totals, or custom refund adjustments lack proper GL codes. Finance teams spend hours matching and manually posting.

Trade-account pricing mismatches

A customer account's discount updates in ERP but Lightspeed terminals show the old price, or ecommerce checkout applies a different discount than the till. Customers complain or chargebacks arise.

Returns lost between branch and ecommerce

An in-store return processes in Lightspeed but never becomes a credit note or refund in the ecommerce order record. Customer order history shows sale but no return.

Branch downtime breaks ecommerce checkout

Ecommerce stock lookups depend on Lightspeed availability. If a location goes offline, checkout may stall or show stale stock. No graceful fallback is defined.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Lightspeed integrations.

How often does branch stock sync to ecommerce?

Stock sync frequency is a design decision iWeb makes with you. Real-time polling is costly and not always necessary. Many retailers run 15-minute, 30-minute or hourly updates depending on velocity and channel separation. iWeb sets up fallback behaviour so ecommerce can reserve stock from a location even if the Lightspeed feed is temporarily slow.

What happens if a branch location is offline during a click-and-collect order?

iWeb designs a fallback: the order either routes to an alternate branch, queues for manual review, or the customer is notified that that location is unavailable at checkout. We define SLA and retry logic so orders are not silently lost.

How do till refunds and adjustments post to ERP and finance?

iWeb extracts the Lightspeed transaction file, maps payment tenders and refunds to the correct ERP GL codes, and posts daily or on demand. Discrepancies and manual adjustments queue for manual review. Till reconciliation becomes a variance check, not a data-entry marathon.

Can trade-account pricing from ERP automatically update Lightspeed tills?

Yes. iWeb designs a nightly or on-demand feed from ERP or PIM that uploads trade-account discounts and pricing to Lightspeed locations. Ecommerce checkout reads the same pricing source so both channels apply consistent discounts.

How do we link an in-store customer to the same ecommerce account?

iWeb designs customer ID resolution so Lightspeed per-location customer records match to the ecommerce customer ID. Lookups work via email, phone or loyalty number. Till staff can recall ecommerce purchase history and account balance.

What happens when a customer returns an item in-store that they bought online?

Lightspeed initiates the return. iWeb routes the return event to the ecommerce order record, OMS, payment system (to refund) and ERP (to post credit note). The customer's ecommerce order history reflects the return.

How do we handle oversell if ecommerce and a branch sell the same item at the same time?

iWeb designs stock-reservation logic. Either ecommerce or the branch can reserve units as they sell. Stock feeds to ecommerce show already-reserved units as unavailable. Sync frequency and reserve thresholds determine how tight the fit is.

Who owns the mapping between Lightspeed fields and ERP GL codes?

iWeb owns this mapping. We document which till tender types, refund categories and adjustments post to which GL accounts. Finance and IT review and approve before launch. Changes go through iWeb so the mapping stays consistent.

Can Lightspeed locations create orders directly in ecommerce checkout?

Lightspeed is primarily a retail till and stock system. Branch staff do not create ecommerce orders. Ecommerce customers place orders online; those orders route to branch for collection. Till staff can look up ecommerce orders in the Lightspeed customer screen.

How do we monitor if click-and-collect orders are stuck at a branch?

iWeb sets up alerting for orders that route to a branch but don't move to 'ready for collection' within a defined SLA. Exception reports flag unconfirmed orders so managers can follow up and resolve them.

What happens to till data if the ecommerce or ERP system is down?

Lightspeed is resilient. Till operations continue. iWeb queues till transactions and replays them into ERP and finance as soon as services are back. No sale is lost, but posting may be delayed a few hours.

Can branch managers see real-time ecommerce sales or customer activity?

Lightspeed is a till and stock tool, not an analytics platform. iWeb can export daily or hourly sales summaries to Lightspeed or a BI tool so branch managers see ecommerce trends. Real-time dashboards require a separate BI or reporting platform.

How do we handle local branch promotions that shouldn't appear online?

Lightspeed can hold local price overrides. iWeb isolates those overrides at the location level. Ecommerce reads central pricing from ERP or PIM, not local Lightspeed prices, so branch-only promotions stay in-store.

What if a trade customer's credit limit changes in ERP?

iWeb syncs credit limit and account status changes from ERP to Lightspeed daily or on demand. Till staff see updated account flags so they can flag unavailable credit. Ecommerce also reads the same account status for checkout rules.

Next step

Have a Lightspeed 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 →