Skip to main content
Talk to an expert
Exchequer logo

Exchequer integration for ecommerce

Live orders and stock synchronised with Exchequer reliably iWeb routes web orders into Exchequer with duplicate prevention and handles stock and pricing synchronisation, invoice reconciliation and exception flows that keep your ERP current and your storefront accurate. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: connector, plugin, extension, API integration, system integration.

ExchequeriWeb integration layeryour storefront
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
01 · What you get

What a Exchequer integration gives you.

Stock accuracy and availability

Shoppers see accurate available-to-promise stock on the storefront, and overbooking across channels is prevented by Exchequer holding the physical buffer and the integration enforcing hold queues.

Orders land correctly and once

Web orders flow into Exchequer as clean sales documents with no duplicates or data loss, and the timing of capture and acknowledgement is explicit and monitored.

Customer pricing is consistent and timely

Checkout applies the correct customer-specific pricing from Exchequer without delay, and you see when pricing lookups are stale or missing.

Finance reconciliation is predictable

Invoices, credit notes and dispatch confirmations flow back to Exchequer and finance systems with clear matching to the original web order, so month-end reconciliation is efficient and auditable.

Exceptions are visible and actionable

When stock, pricing, order capture or invoice sync encounters an error, it is logged and surfaced with enough context to retry or escalate without manual detective work.

02 · When it's worth it

Where a Exchequer integration earns its place.

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

Publishing available stock and base pricing from Exchequer to the storefront
Capturing web orders into Exchequer and preventing duplicate entry or loss
Applying customer-specific pricing retrieved from Exchequer during checkout
Sending invoice, credit note and dispatch confirmation events back to Exchequer for reconciliation
Buffering stock at the warehouse level so Exchequer remains the system of record
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 web order acknowledgement routing

Exchequer does not natively listen for or acknowledge web orders; the integration must handle order routing logic, duplicate detection, and timeout retry strategy. Without this, orders may be lost or entered twice.

Stock buffer logic not built-in

Exchequer publishes physical stock, but does not have a standard mechanism to enforce safety buffers or to hold stock for web orders pending payment. The integration must layer buffer rules and hold queues outside Exchequer.

No standard customer-specific pricing query interface

Exchequer holds customer pricing tiers and overrides, but does not expose these via a standard real-time API for checkout lookup. The integration must extract and cache pricing data or call it via custom endpoints.

Invoice and credit note export requires custom mapping

Exchequer generates invoices and credit notes in its own format; the integration must map these back to commerce line items and order references for matching and reconciliation.

No standard exception or dead-letter handling

When order capture, pricing lookup or stock sync fail, Exchequer has no built-in queue or alerting. The integration must implement its own exception capture, retry logic and escalation workflow.

04 · The real work

Stock drifts, orders land twice, and invoices sit unmatched in finance because order capture and reconciliation logic is either missing or owned by no one; the integration is where this ownership becomes explicit.

05 · Where it sits

Where this integration sits in your estate.

Exchequer 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 Exchequer to your storefront, ERP and everything between.

System of record
Source / owner
Exchequer
System of record for stock, pricing, customer accounts and financial transactions
  • Physical stock availability and buffers
  • Base and customer-specific pricing tiers
  • Customer account status and credit limits
  • Sales orders and invoice-to-cash cycle
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Storefront product display and checkout
  • Web order initiation and payment capture
  • Cart and inventory hold queues
  • Customer browse and purchase events
Connected neighbours
Integration layer
WMS / 3PL shipping
Despatch and returns flow back to Exchequer; stock movements are reconciled via integration.
Integration layer
Payment gateway
Payment status and transaction IDs are captured and sent with orders into Exchequer for cash reconciliation.
Integration layer
Finance and accounting
Invoices and credit notes flow from Exchequer to finance; month-end reconciliation is driven by order and payment data.
Integration layer
Marketplace connectors
Multiple channels may feed orders through the integration into Exchequer; channel-specific pricing and stock may be managed separately.
Integration layer
Business intelligence
Order, stock and pricing data flow from Exchequer and commerce to BI for reporting and analytics.
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)
  • Exchequer (ERP)
  • WMS or 3PL shipping
  • Payment gateway
  • Marketplace connectors
  • Accounting or consolidation system
  • Business intelligence and reporting
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
From ERP
BOTH WAYS
Stock and pricing export: Stock availability, base price lists and customer-specific pricing rules flow from Exchequer to the commerce platform at defined intervals or on-demand
The flow includes handling of stock buffers, hold queues and pricing tier logic so the storefront reflects live Exchequer state without constant polling.
Web order capture: Completed orders from the commerce platform are sent into Exchequer as sales documents with line items, delivery address, customer account reference and payment status
The flow must prevent duplicate order creation and align order acknowledgement timing between commerce and ERP.
Invoice and credit notes: Once Exchequer generates an invoice or credit note against a web order, that document flows back to the commerce platform for customer account reconciliation, reporting and potential reverse-sync to accounting systems.
Customer account and credit changes: Customer account status, credit limit, hold flags and payment-on-account eligibility can be maintained in Exchequer and published to commerce
Returns and refunds initiated in commerce may flow back to Exchequer to trigger credit notes and account adjustments.
Dispatch and returns acknowledgement: Despatch confirmations and return merchandise authorisations from the WMS or shipping carrier flow into Exchequer to update sales order status and stock movements
This ensures Exchequer's transactional skeleton reflects fulfillment state.
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
    Order capture and duplicate prevention

    We design the order inbound flow to detect duplicate order IDs, validate essential fields against Exchequer's customer and tax rules, and implement retry-safe idempotency so that network failures do not create ghost orders.

  2. 02
    Stock and pricing synchronisation

    We build the export pipeline from Exchequer to commerce with configurable stock buffers, customer-tier pricing lookup, and refresh intervals that balance freshness against ERP polling load. We implement caching and fallback behaviour so checkout does not block on a slow pricing call.

  3. 03
    Invoice and credit note reconciliation

    We map Exchequer invoice and credit note data back to commerce orders and line items so finance teams can reconcile transactions and handle returns and refunds without manual cross-reference.

  4. 04
    Exception handling and monitoring

    We implement named exception queues for failed order captures, stale stock syncs, missing pricing data and invoice delivery failures. Alerts, dashboards and SLA tracking ensure issues are caught within your response time window.

  5. 05
    Testing and go-live support

    We validate stock parity, order flow end-to-end, pricing accuracy across customer tiers, and finance reconciliation against live Exchequer data. We establish fallback procedures so that ERP downtime does not halt the storefront.

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
DataStock availability and buffers
Source / ownerExchequer
Maintained byWarehouse and supply-chain team
NotesCommerce platform holds a cached or polled view; the integration enforces buffer rules and hold queues at the commerce layer to prevent overselling.
DataBase and customer-specific pricing
Source / ownerExchequer
Maintained byPricing and revenue management team
NotesLookup at checkout happens via integration; pricing is versioned in Exchequer and refreshed on a defined interval or on-demand.
DataWeb orders and order line items
Source / ownerExchequer
Maintained byOrder capture integration and operations
NotesCommerce platform originates the order; the integration routes it into Exchequer with duplicate detection and idempotency.
DataCustomer account and credit limits
Source / ownerExchequer
Maintained byCredit control and customer master team
NotesCommerce platform may enforce a hold or require approval at checkout; the integration publishes current credit status and flags.
DataInvoice, credit note and dispatch state
Source / ownerExchequer
Maintained byFinance and fulfillment team
NotesIntegration retrieves these documents and returns them to commerce for customer visibility and accounting reconciliation.
DataIntegration transport and exception handling
Source / ownerCommerce platform and iWeb integration layer
Maintained byIntegration operations team
NotesDead-letter queues, retry logic, monitoring and alerting are owned by the integration; escalation to Exchequer or commerce teams is defined per exception type.
10 · Experienced integrator

Built this before

iWeb has delivered multiple Exchequer integrations across retail, foodservice and manufacturing sectors. We understand how to design order capture, stock and pricing synchronisation, and invoice reconciliation so that Exchequer remains the system of record without blocking the storefront.

We know how Exchequer's stock, pricing and sales-order structures map to commerce checkout and how to enforce buffer rules and duplicate detection at the integration layer.
We have built order hold queues, idempotent capture logic and fallback behaviour so that orders are never lost and ERP downtime does not halt the storefront.
We understand how Exchequer integrates with WMS, shipping and finance systems, and ensure that despatch, returns and invoice data flows reconcile correctly.
We design exception handling, monitoring and alerting so that order, stock and pricing failures are caught and surfaced within your operations team's SLA.
11 · Before launch

What we test before launch.

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

Verify that duplicate order IDs are detected and not re-entered into Exchequer during retry scenarios.
Confirm that stock availability exported from Exchequer matches the storefront display, and that buffer logic holds the expected reserve.
Test customer-specific pricing lookup across multiple customer tiers and confirm checkout applies the correct price without delay.
Validate that invoices and credit notes returned from Exchequer match the original web order and can be reconciled by finance teams.
Confirm that order hold queues drain correctly when Exchequer becomes available again after a simulated downtime.
Verify that exceptions (failed order captures, stale pricing, missing stock updates) are logged with context and alerting works within your SLA.
Test the fallback path when Exchequer is down: orders should be queued or checkout should gracefully hold, not silently fail.
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.

Stale or missing stock on the storefront

If the stock export pipeline pauses or Exchequer is down, the commerce platform may serve out-of-date availability to shoppers. Overselling occurs when buffer logic is not enforced or when hold queues are not cleared after payment fails.

Duplicate or lost orders in Exchequer

Network retries or timeout loops can cause the same web order to be entered into Exchequer twice, or orders can be lost if the integration does not persist the order ID or acknowledge receipt. This breaks order tracking and duplicates revenue in invoicing.

Pricing mismatches or stale tiers

Customer-specific pricing lookups may time out or return cached data from before a price change in Exchequer. Checkout may apply the wrong price tier or fail silently, leading to margin loss or billing disputes.

Finance reconciliation gaps

If invoices or credit notes do not flow back from Exchequer to commerce with clear order matching, finance teams cannot reconcile transactions. Returns and refunds may not trigger credit notes, leaving accounts out of balance.

ERP downtime halts order capture

If Exchequer is unavailable and the integration has no fallback or hold queue, orders cannot be captured and customers cannot complete checkout. If orders are queued but Exchequer remains down for hours, the backlog becomes manual and error-prone to clear.

Unowned exception handling

When order, stock or pricing operations fail, if there is no named owner or escalation path, failures accumulate silently in logs. By the time someone investigates, orders are hours or days old and reconciliation is harder.

14 · Questions

Common questions about Exchequer integrations.

How does the integration prevent duplicate orders being entered into Exchequer?

The integration tracks order IDs and implements idempotent order-insert logic so that network retries do not create duplicate sales documents. Before capture, we check if the order ID already exists in Exchequer and skip re-entry if it does.

What happens to web orders if Exchequer becomes unavailable?

We implement a configurable hold queue that buffers orders while Exchequer is unreachable. Checkout can proceed or pause depending on your business rules. Once Exchequer recovers, the integration drains the queue in order. If downtime exceeds your SLA, we alert you so you can decide whether to reroute orders manually.

How is customer-specific pricing retrieved and applied at checkout?

The integration queries Exchequer for the customer's pricing tier at checkout based on customer account ID. We cache the result to avoid blocking checkout on a slow lookup, and we refresh the cache on a schedule or on-demand when pricing changes in Exchequer.

How does stock buffer logic work if Exchequer is the system of record?

Exchequer publishes the physical available stock. The integration applies buffer rules (safety stock held for warehousing, hold queues for pending orders) at the commerce layer, so Exchequer always reflects true inventory and commerce never oversells.

How are invoices and credit notes matched back to web orders?

The integration retrieves invoices and credit notes from Exchequer using the original web order ID or sales order reference. We map the line items and amounts back to the commerce order so finance can reconcile without manual cross-reference.

Can the integration handle returns and refunds flowing back to Exchequer?

Yes. When a return is initiated in the commerce platform or OMS, the integration sends it into Exchequer as a purchase return or credit note instruction. Exchequer generates the credit note and the integration retrieves it for accounting and customer refund processing.

How is order acknowledgement timing managed between commerce and Exchequer?

We define explicit acknowledgement points: order accepted by commerce, order successfully inserted in Exchequer, invoice generated in Exchequer. You choose which point triggers a customer confirmation email or holds further processing.

What happens when a pricing lookup fails during checkout?

We implement fallback behaviour: retry with backoff, serve cached pricing if available, or raise a flag to block checkout if pricing is critical. You define the fallback strategy so checkout does not silently apply wrong pricing.

How are exceptions tracked and escalated if they go unresolved?

The integration logs all failed operations (order capture, stock sync, pricing lookup, invoice retrieval) with context and timestamps. Alerts notify your operations team within your SLA, and dashboards show which exceptions require manual intervention or Exchequer investigation.

Can the integration support multiple sales channels or order sources feeding Exchequer?

Yes. The integration can route orders from multiple storefronts or marketplaces into Exchequer as separate sales orders or channels within a single sales order, depending on your Exchequer configuration. Deduplication and channel tagging ensure no order is lost or duplicated.

How does dispatch and returns data flow back from the WMS to Exchequer?

Despatch confirmations and return merchandise authorisations from your WMS or shipping system flow back into Exchequer via the integration to update sales order status and stock movements. This ensures Exchequer's transactional skeleton stays current with fulfillment state.

What observability and monitoring is available during go-live and after launch?

We set up dashboards showing order volume, stock sync freshness, pricing query latency, invoice retrieval status and exception queue depth. We establish SLAs for each flow and alert you when performance degrades or exception queues back up.

How does the integration handle Exchequer configuration changes, like new price tiers or stock locations?

We build the integration to refresh configuration metadata on a schedule and allow on-demand reloads without redeployment. Changes to price tiers or stock locations in Exchequer are picked up by the next refresh cycle, and we log what changed for audit.

Can payment status influence how orders are processed in Exchequer?

Yes. The integration can hold orders in a pre-invoice state until payment is confirmed, or can mark paid orders immediately for faster fulfilment. You define the logic based on your cash-flow and fulfillment needs.

14b · Same category

Other erp · finance integrations.

Adjacent integrations in the same category. Same shape of work, different vendor.

ERP · finance
Next step

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