Skip to main content
Talk to an expert
Instore Boutique POS

Instore Boutique POS Integration Specialists

Branch stock and till transactions stay in sync with ecommerce iWeb integrates Instore Boutique with your ecommerce platform, ERP and customer systems so branches can fulfil click-and-collect orders, apply trade-account pricing and trade on account without manual intervention. Till transactions post to finance with clear GL codes and returns trace end-to-end. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Instore BoutiqueiWeb 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
00 · At a glance

Instore Boutique at a glance.

Category
POS · retail · branch systems
Role in the estate
The trade counter, till and branch system - owns walk-in transactions, click-and-collect touch points and often the local customer relationship.
Commonly connects with
Commerce platforms · ERP · finance · OMS · order management · Payments
Typical use cases
Branch stock visibility into ecommerce to prevent overselling across channels · Click-and-collect order routing from ecommerce into Instore Boutique for branch fulfilment · Trade-account pricing and customer lookup at the till · In-store returns and refunds fed back to ERP and ecommerce ledgers
Relevant services
BuildSupportRescue
01 · What you get

What an Instore Boutique integration gives you.

Branches fulfil click-and-collect orders

Online customers see click-and-collect as an option, pay online, and arrive at a branch to collect. Till staff see the order in Instore Boutique, pick and pack, and handoff to the customer without manual lookups or double-keying.

Stock stays honest across channels

Stock is reserved and decremented once, whether sold online or at the till. Overselling across locations is prevented by shared allocation logic that both ecommerce and Instore Boutique respect.

Trade customers use accounts at the till

Trade-account customers look up at the till, see their contract pricing and credit balance, and trade on account without manual verification or dispute.

Finance reconciliation closes faster

In-store and online transactions post to the same ledger with clear transaction types and GL codes. Reconciliation does not require manual lookup or adjustment rework.

Returns are tracked end-to-end

In-store refunds and online returns both update the customer's original order and the finance ledger, so refund tracking and chargeback defence are clear.

02 · When it's worth it

Where an Instore Boutique integration earns its place.

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

Branch stock visibility into ecommerce to prevent overselling across channels
Click-and-collect order routing from ecommerce into Instore Boutique for branch fulfilment
Trade-account pricing and customer lookup at the till
In-store returns and refunds fed back to ERP and ecommerce ledgers
Offline till transactions syncing to central finance 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 integration

Instore Boutique does not connect natively to Magento, Shopify, BigCommerce or other storefronts. Click-and-collect orders, stock updates and return events require custom build work to flow reliably.

Limited multi-location stock reservation

Stock visibility across branches may be read-only or delayed. Real-time stock allocation to prevent overselling across locations requires integration logic above the system.

No by default ERP sync

ERP connections are vendor-specific and often need mapping work for account hierarchies, price books, GL codes and transaction posting. Finance reconciliation gaps are common without careful handoff design.

Manual price and credit override risk

Till users can often override pricing and credit limits without audit trail. Without integration governance and alerts, branches may apply inconsistent rules or grant unauthorized discounts.

Offline queue visibility gap

When a branch goes offline, till transactions queue locally. Bringing the queue back into sync with ERP and ecommerce requires exception handling and retry logic that is not always clear to operators.

03b · Honest limits

When Instore Boutique may not be the simplest fit.

A short, honest list. Not a warning; just where a different shape of system usually costs less to run.

A pure online business with no physical branches
No appetite to change branch staff workflow
A till system with no serious integration surface
Expecting the EPOS to solve omnichannel on its own
04 · The real work

Branches and ecommerce often compete for the same stock if they cannot see each other's reservations in real time. The till operator sells an item online has already claimed, and the customer arriving for click-and-collect finds nothing to collect.

05 · How it connects

How this integration connects to your estate.

Instore Boutique 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.

Storefront independent. Instore Boutique feeds stock, pricing, orders and customer data into your chosen platform.

System of record
Source / owner
Instore Boutique
Till and branch-management layer for in-store trade and click-and-collect
  • Till transactions and in-store sales
  • Branch stock movements and adjustments
  • In-store refunds and voids
  • Click-and-collect order receipt and fulfilment
  • Customer lookup and trade-account verification at the point of sale
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Online product catalogue and checkout
  • Online order creation and customer account
  • Click-and-collect order placement and status
  • Online returns and refund requests
  • eCommerce customer and cart management
Connected neighbours
Integration layer
ERP
Source of truth for stock, base pricing, trade-account terms, GL codes and customer credit. Receives till transactions, stock adjustments and refunds for financial posting.
Integration layer
eCommerce platform
Storefront where customers browse, buy and choose click-and-collect. Respects branch stock availability and trade pricing. Receives collection status and returns from Instore Boutique.
Integration layer
OMS or stock allocation system
May govern stock reservation and allocation rules across locations. Both eCommerce and Instore Boutique check availability against the same allocation pool to prevent overselling.
Integration layer
Finance and reporting
Consumes till transactions, refunds and stock adjustments from the integration for reconciliation, dashboards and regulatory reporting.
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 (SAP, Oracle NetSuite, Sage, Infor)
  • Stock and OMS (e.g. order management, allocation rules)
  • eCommerce platforms (Magento, Shopify, etc.)
  • Finance systems and GL posting
  • Customer account and credit management
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.

Ask us about your stack
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 & INSTORE BOUTIQUE
←From ERP & INSTORE BOUTIQUE
↔BOTH WAYS
Stock and pricing changes: Branch stock levels and trade-account pricing flow from ERP into Instore Boutique so till users see current availability and correct customer pricing
Updates may be scheduled or event-driven depending on freshness requirements.
Till transactions and adjustments: In-store sales, voids, refunds and stock adjustments post from Instore Boutique to the ERP for financial reconciliation and stock ledger accuracy
The flow must capture transaction type, amount, customer account and timestamp.
Click-and-collect orders: Online orders flagged for in-store collection arrive in Instore Boutique with customer name, item list and collection deadline
Till staff see the order, pick and pack items, and mark collection complete.
Collection and in-store returns: Click-and-collect completion, in-store refunds and returns flow back to ecommerce so the customer and finance ledgers stay in step
Returns must capture the original order or transaction, reason, and refund amount.
Customer account and trade-credit state: Customer names, trade account status and credit limits sync between ERP and Instore Boutique
Changes to credit or account status must propagate so till staff apply the correct rules and ecommerce reflects open account eligibility.
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
    Maps branch operations to central ERP

    iWeb designs the data dictionary so branch stock, till transactions, customer accounts and pricing rules flow consistently between Instore Boutique and your ERP. Ownership and update frequency are named upfront.

  2. 02
    Builds click-and-collect workflows

    iWeb connects ecommerce platforms with Instore Boutique so online orders arrive at the right branch, till staff see them, and collection status updates the customer and finance ledger.

  3. 03
    Handles offline and retry scenarios

    When a branch goes offline or a sync fails, iWeb builds queuing, retry and alerting so transactions do not disappear and operations know what needs manual attention.

  4. 04
    Defines stock allocation rules

    iWeb works with you to decide how stock is reserved across branches, online warehouses and channels. Allocation logic is coded once and shared by ecommerce, OMS and till systems.

  5. 05
    Governs pricing and account rules

    iWeb maps trade-account pricing, credit limits and customer rules so they apply consistently at the till and online. Changes to pricing or credit are staged, monitored and rolled back if needed.

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 stock adjustments
Source / ownerERP (source), Instore Boutique (transaction point)
Maintained byERP for master stock; Instore Boutique for in-store movements and adjustments
NoteseCommerce reads from a shared allocation pool updated by both ERP and Instore Boutique. Overselling is prevented by real-time deduction rules.
DataTrade-account pricing and contract terms
Source / ownerERP
Maintained byERP publishes price books and rules; Instore Boutique applies them at the till
NotesPrice changes must flow from ERP to Instore Boutique before the till applies them. eCommerce respects the same price books so customer sees consistent pricing across channels.
DataTill transactions and in-store sales
Source / ownerInstore Boutique
Maintained byInstore Boutique records the transaction; integration posts to ERP for finance and stock ledger
NotesTransaction must include customer account (if trade), items, amounts, and discounts applied. Finance reconciliation depends on clear transaction type and GL code.
DataClick-and-collect order handoff and status
Source / ownerInstore Boutique (in-store collection); ecommerce (order origin)
Maintained byeCommerce creates the order; Instore Boutique marks receipt, pick, pack and collection complete
NotesStatus changes must flow back to ecommerce so the customer and finance ledger see the order lifecycle end-to-end.
DataIn-store and online returns and refunds
Source / ownerERP (finance ledger)
Maintained byInstore Boutique records in-store refunds; ecommerce records online returns; both flow to ERP
NotesRefund must link to the original order or transaction and must post to ERP with clear reason and amount. Chargeback reconciliation depends on clean tracing.
DataCustomer accounts and credit state
Source / ownerERP
Maintained byERP holds credit limit, account status and account hierarchy; Instore Boutique and ecommerce apply the rules
NotesCredit changes in ERP must propagate to Instore Boutique so till staff see current limits. Branches and ecommerce must apply the same hold rules.
DataIntegration transport, monitoring and exception handling
Source / ownerIntegration layer
Maintained byiWeb integration team
NotesRetry logic, dead-letter queues, failed-sync alerts and offline-queue visibility are owned by the integration and must be monitored by operations.
10 · Experienced integrator

Built branch integrations before

iWeb has built Instore Boutique integrations for retail and trade retailers who operate both online and in-store. We understand how branches, till systems, ecommerce and ERP need to talk to each other without overselling or losing refunds.

Designed stock allocation and click-and-collect routing so branches and ecommerce share the same inventory pool
Built offline handling and retry logic so till transactions do not disappear when a branch loses connection
Mapped trade-account pricing, credit rules and GL codes consistently between till, ERP and ecommerce
Set up monitoring and exception handling so operations see stock variance, failed syncs and offline queues in real time
Defined clear ownership of returns, refunds and reconciliation so finance and customer service have a single source of truth

Enterprise digital commerce specialists since 1995

UK-based, employee-owned team

Adobe Gold Commerce Partner

ERP, PIM and operational integration experience

Build, replatform, rescue and long-term support

Platform-led where appropriate, integration-led across the wider estate

11 · Before launch

What we test before launch.

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

Stock allocation prevents overselling: sell the last unit online and verify the till cannot sell it at the same moment
Click-and-collect order arrives in Instore Boutique within 30 seconds of placement and till staff can see it in their queue
Till transaction posting to ERP includes correct customer, items, GL codes and amounts, and finance reconciliation shows no variance
Offline till queue replays without duplicating transactions after the branch reconnects to the network
In-store refund links to the original order and posts to ERP with clear reason and GL code; online customer sees the refund on their account
Trade-account credit lookup shows current ERP balance and prevents sales above the limit unless explicitly overridden with audit trail
Stock variance between ecommerce and Instore Boutique triggers an alert within 5 minutes and operations have a clear reconciliation path
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 overselling across locations

If ecommerce and branches do not share a live stock pool, an item can be sold out online while a branch still has stock (or vice versa). Click-and-collect orders arrive at branches with no stock in hand. Integration must enforce a single stock view.

Click-and-collect orders lost between systems

Online orders routed to Instore Boutique may not arrive, or may arrive without clear handoff status. Till staff do not know which orders are waiting, so customers arrive to find nothing prepared.

Pricing mismatches between till and ecommerce

If trade-account pricing is updated in ERP but not pushed to Instore Boutique, a customer may be quoted one price online and charged another at the till. Trust breaks and disputes follow.

Offline till transactions stuck in queues

When a branch loses network connection, till sales queue locally. If the queue is not monitored or purged correctly, transactions may be replayed after coming back online, creating duplicate posts to ERP and duplicate refunds.

Returns not matching original orders

In-store refunds may be processed against the wrong original order, or without linking to ecommerce orders. Finance sees refund cash out but not the matching order or reason. Reconciliation and chargeback defence fall apart.

Credit limit overrides without governance

Till staff can often bypass credit checks for trade accounts. Without audit trail or alert, a branch may grant credit to a customer whose account is already over limit or on hold.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Instore Boutique integrations.

How do we prevent overselling when a customer buys online but stock is at the branch?

iWeb designs a shared stock pool so ecommerce and Instore Boutique deduct from the same source. When an online order is placed, the ecommerce platform reserves stock at the fulfilling location (branch or warehouse). Instore Boutique sees the same reserved count at the till, so a till operator cannot sell stock that is already online.

How does click-and-collect routing work?

When a customer chooses click-and-collect at checkout, ecommerce routes the order to the selected branch. The order arrives in Instore Boutique with customer name, items and collection deadline. Till staff see the order queue, pick and pack the items, and mark the order ready for collection. Status updates flow back to the customer and ecommerce.

What happens when a branch goes offline?

Till transactions queue locally in Instore Boutique. When connection is restored, the integration replays the queue into ERP and ecommerce with retry logic to handle any temporary failures. iWeb builds alerting so operations know when a queue is pending and can check that transactions posted correctly.

How do trade-account customers see their pricing at the till?

Customer name is looked up or scanned at the till, and Instore Boutique applies the contract pricing from the ERP price book. eCommerce applies the same pricing at checkout so the customer sees consistent prices across channels. If pricing changes in ERP, both systems must be updated before the till applies the new price.

How do in-store refunds get back to ERP and the customer?

When a customer asks for a refund at the till, the refund is recorded in Instore Boutique linked to the original transaction or order number. The refund posts to ERP with the correct GL code, and if the original order was online, ecommerce is notified so the refund appears on the customer's account.

Can a till operator override credit limits or apply unauthorized discounts?

Instore Boutique may allow overrides, but iWeb integration can log overrides with audit trail and alert finance or operations when a limit is breached or a large discount is applied. Governance rules are defined upfront so branches know what is allowed and what requires approval.

How do we know stock at the branch is accurate?

iWeb builds a reconciliation flow where till movements are posted to ERP and the integration reports any discrepancies. Periodic physical counts at the branch are recorded in Instore Boutique and reconciled back to ERP. If discrepancies are found, they are logged and flagged for investigation.

What if a till transaction fails to post to ERP?

iWeb builds retry logic and dead-letter handling so failed transactions are queued and retried. Operations are alerted if a transaction cannot be posted after a set number of retries, so manual intervention is possible. The transaction is not lost and the till operator can see the status.

How do we handle returns initiated online but collected in-store?

When a customer initiates a return online, ecommerce notifies Instore Boutique that the customer will be bringing the item to the branch. Till staff scan the return label, inspect the item and approve the refund. The refund posts to ERP and the online order is marked as returned.

Can we see real-time till sales in reporting and finance dashboards?

Yes. iWeb designs the integration so till transactions post to ERP with clear GL codes and can be reported in real-time or near-real-time dashboards. Finance and operations can see daily till totals, customer sales and trends by branch.

How do we manage multiple branches with different opening hours or stock policies?

Each branch has its own Instore Boutique instance or location record. Stock allocation rules can be branch-specific, and ecommerce can show click-and-collect availability only at branches that are open and have stock. Pricing and customer rules can also vary by location if needed.

What happens if ecommerce and Instore Boutique have different stock counts?

iWeb builds a monitoring dashboard so operations can see stock variance between systems. If a discrepancy is found, the integration logs the difference and alerts operations. A reconciliation process is defined: either ecommerce or Instore Boutique is chosen as the source of truth for that period, and the other is corrected.

How do we roll back a pricing change if it was applied incorrectly?

Price changes in ERP flow to Instore Boutique with a timestamp. If an incorrect price is published, it can be corrected and re-published. Till staff may need to void and re-ring a sale if the customer was already charged. iWeb integration logs pricing changes so audits are clear.

Next step

Have an Instore Boutique 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 →