Skip to main content
Talk to an expert
Intact iQ logo

Intact iQ integration for ecommerce

Orders flow to finance while stock stays governed in sync iWeb integrates Intact iQ with your commerce platform so web orders land in Intact iQ for invoicing without manual re-entry, stock levels stay current across storefronts, and customer credit limits enforce at checkout. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

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

Intact iQiWeb 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 Intact iQ integration gives you.

Orders flow to finance without re-entry

Web orders land in Intact iQ as invoiceable documents with correct customer, amounts and delivery details, eliminating manual order re-entry and the associated keying errors and reconciliation delays.

Stock stays accurate across channels

Intact iQ stock feeds to all commerce instances so physical inventory is never oversold. When stock adjustments occur at the warehouse, commerce reflects them within minutes.

Credit risk is managed at checkout

Customer credit limits and account status check against Intact iQ at the point of order. Overspent accounts trigger a checkout warning or block, preventing bad-debt orders from being created.

Pricing is current and rule-governed

Customer-specific pricing syncs from Intact iQ so each buyer sees their negotiated prices. List price changes propagate to commerce automatically, eliminating manual feed updates and price drift.

Finance reconciliation is straightforward

Because orders flow into Intact iQ in a governed format with audit trails, month-end reconciliation against commerce is faster and produces fewer unexpected variances.

Returns and refunds close the loop

Returns flow back to Intact iQ to reverse invoices and adjust stock. Credit notes are created automatically and can be sent to customers digitally, closing the financial loop without manual journal entries.

02 · When it's worth it

Where a Intact iQ integration earns its place.

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

Web orders flow into Intact iQ for invoicing and dispatch without manual order re-entry
Stock levels from Intact iQ update commerce inventory to prevent oversell
Customer credit limits and account status block or warn at checkout
List and customer-specific pricing syncs from Intact iQ to commerce
Invoice and credit note PDFs return to commerce for customer download
Returns and refunds flow back to Intact iQ for stock adjustment and finance reconciliation
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 commerce connector

Intact iQ has no built-in API or middleware for commerce platforms. A bespoke integration layer must be built to handle order format translation, field mapping, error queuing and retry logic between Intact iQ and your chosen commerce platform.

Order acknowledgement latency

Intact iQ processes orders synchronously during normal business hours. Orders placed outside office hours or during peak traffic may queue for next-business-day processing, delaying customer confirmation and dispatch.

No real-time stock visibility

Intact iQ exports stock snapshots at intervals. Commerce cannot see true live availability during a surge in orders; oversell risk exists if the export interval is longer than peak order velocity.

Customer-specific pricing requires mapping

Intact iQ holds customer price bands or tiered pricing, but does not publish them directly to commerce. A custom pricing feed must translate Intact iQ pricing rules into commerce price attributes or promotion logic.

No built-in returns workflow

Intact iQ has no dedicated returns or RMA module. Returns must be manually logged as negative sales documents or debit notes, requiring careful order and stock reversal logic in the integration layer.

04 · The real work

Most teams underestimate the latency and exception-queue discipline required between commerce and Intact iQ; orders that fail submission must be monitored and replayed within hours, or dispatch schedules slip and customer satisfaction declines.

05 · Where it sits

Where this integration sits in your estate.

Intact iQ 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.

Platform-agnostic by design. Intact iQ sits at the centre of your estate, not at the edge of one platform.

System of record
Source / owner
Intact iQ
System of record for stock, pricing, customer accounts and finance
  • Stock on-hand balances and availability
  • Base and customer-specific pricing
  • Customer account status and credit limits
  • Sales order invoicing and dispatch
  • Credit notes, refunds and reversals
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Product content and storefronts
  • Shopping cart and checkout experience
  • Customer self-service account portal
  • Order history and document download
  • Promotional rules and discounting
Connected neighbours
Integration layer
WMS or 3PL
Receives dispatch instructions from Intact iQ and returns tracking and stock-movement confirmations
Integration layer
PIM
Manages product attributes, images and descriptions that are published to commerce; separate from Intact iQ stock and pricing
Integration layer
Payment provider
Authorises and captures payment at checkout independently; order financial status lives in Intact iQ, not the payment provider
Integration layer
BI or accounting system
Receives invoice and sales data from Intact iQ for reporting and reconciliation; must match orders flowing from commerce
Integration layer
Marketing or CRM
Receives order and customer data from commerce for segmentation and campaign triggers; customer master lives in Intact iQ
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)
  • Intact iQ (ERP and financial management)
  • WMS or 3PL (dispatch and tracking)
  • Ecommerce platform (storefront and checkout)
  • PIM (product content and enrichment)
  • Marketing or CRM platform (customer segments and messaging)
  • Payment provider (card auth and capture)
  • BI or data warehouse (sales and financial 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 feed: Stock levels and base or customer-specific pricing export from Intact iQ and update the commerce platform inventory and price tables
This flow usually runs every few minutes or on-demand to keep shopper visibility current.
Web order capture: Orders placed on the commerce platform extract to Intact iQ as sales documents with customer, delivery address, line items and value
Order status remains in Intact iQ as the system of record for invoicing and dispatch.
Invoice and credit note delivery: Once Intact iQ invoices or credits an order, the PDF and transaction details return to commerce so customers can access them via their account or order history.
Customer account and credit changes: Customer name, delivery address and credit limit updates flow both ways
Changes made in Intact iQ refresh commerce, and changes made in commerce admin sync back to Intact iQ to keep account data consistent.
Returns, refunds and cancellations: When a shopper returns an item or a refund is issued, the transaction flows into Intact iQ to adjust stock, reverse the original invoice and record the credit note or debit.
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 format translation and validation

    We build a translation layer that converts commerce order payloads into Intact iQ sales documents, validating customer existence, stock availability and credit limit before submission. Failed validation routes to an exception queue for triage.

  2. 02
    Stock and pricing synchronisation

    We design a two-way feed that exports stock and pricing from Intact iQ to commerce at a frequency that matches your peak order rate, and handles partial updates so a pricing or stock change does not require a full refresh.

  3. 03
    Exception handling and retry logic

    We implement queues for orders that fail initial submission, duplicate-detection logic and retry schedules so transient Intact iQ outages do not lose orders. Failed orders escalate to your operations team with a clear remediation path.

  4. 04
    Customer and credit limit governance

    We build a customer sync that keeps names, delivery addresses and credit limits aligned between Intact iQ and commerce, and enforce credit checks at checkout so orders do not proceed if credit is exhausted.

  5. 05
    Invoice and returns flow

    We connect Intact iQ invoice and credit note PDFs back to commerce so customers see their transaction history. Returns are modelled as debit notes or negative sales documents in Intact iQ with stock reversal.

  6. 06
    Observability and alerting

    We add logging, metrics and alerts so you can see order throughput, stock sync freshness, credit-block events and failed submissions in real time. Dashboards track integration health and surface exceptions before they affect customers.

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 on-hand balances
Source / ownerIntact iQ
Maintained byWarehouse and inventory team in Intact iQ
NotesCommerce receives stock snapshots and must cache them; oversell risk if snapshot interval is too long or if stock is adjusted outside Intact iQ.
DataBase and customer-specific pricing
Source / ownerIntact iQ
Maintained byPricing and sales team in Intact iQ
NotesCommerce publishes pricing to storefronts; list prices and customer price bands must be translated into commerce price attributes or promotion rules.
DataCustomer accounts and credit limits
Source / ownerIntact iQ
Maintained bySales and credit control in Intact iQ
NotesCommerce reads credit limits to enforce checkout rules; changes in either system must sync bidirectionally to keep data consistent.
DataWeb order capture and acknowledgement
Source / ownerIntact iQ
Maintained byOrder intake and operations in Intact iQ
NotesCommerce creates the order; Intact iQ invoices and dispatches it. Order status lives in Intact iQ; commerce must poll or receive webhooks for status updates.
DataInvoice and credit note documents
Source / ownerIntact iQ
Maintained byFinance team in Intact iQ
NotesIntact iQ generates PDFs; commerce stores and serves them to customers. Invoices must be reconciled to orders in commerce for month-end reporting.
DataReturns, refunds and cancellations
Source / ownerIntact iQ
Maintained byOperations and finance in Intact iQ
NotesCommerce initiates a return request; Intact iQ creates a debit note or credit note and adjusts stock. Both systems must agree on the return value and stock reversal.
DataIntegration transport and exception handling
Source / ownerIntegration layer
Maintained byCommerce operations team
NotesFailed orders, pricing gaps, credit-check failures and duplicate submissions queue for manual triage. Ownership of queue review and remediation must be assigned and monitored.
10 · Experienced integrator

Built this before

iWeb has designed and supported multiple Intact iQ integrations serving retail, manufacturing and wholesale operations. We understand how Intact iQ sits as system of record for transactional data and how commerce platforms must adapt to its stock, pricing and order workflows.

We have mapped commerce order formats to Intact iQ sales documents across multiple storefronts, including multi-channel and B2B scenarios with customer-specific pricing.
We design exception queues and retry logic so orders survive Intact iQ outages and latency without losing data or creating duplicates.
We implement stock and pricing feeds that refresh at a rate matching peak order velocity, and we help you set realistic buffer stock to avoid oversell.
We govern credit-limit checks at checkout and customer sync flows so credit risk is enforced consistently across all channels.
We build observability into every data flow so you can see order throughput, pricing freshness, exceptions and reconciliation gaps in real time.
11 · Before launch

What we test before launch.

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

Verify that order IDs in commerce map consistently to Intact iQ sales documents and that duplicate submissions are detected and rejected.
Confirm that stock exports from Intact iQ refresh commerce inventory at the agreed frequency and that oversell risk is within tolerance.
Test credit limit enforcement by attempting checkout with an account at or over its limit, and verify the expected block or warning appears.
Run exception-queue scenarios: submit an order while Intact iQ is temporarily unavailable, then restore and verify the order replays without duplicating.
Validate pricing sync by changing a customer price band or list price in Intact iQ, then confirm the new price appears in commerce within the SLA.
Create a test return in commerce and confirm the debit or credit note is generated in Intact iQ with correct stock adjustment and PDF delivery.
Confirm invoice and credit note PDFs are successfully retrieved from Intact iQ and served in the commerce customer portal with correct dates and amounts.
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.

Oversell during stock sync delays

If the stock export interval is longer than order velocity during peak trading, commerce may allocate inventory that has already been sold in Intact iQ. Buffer stock can mitigate this, but must be governed and reviewed regularly.

Duplicate orders from retry logic

If an order submission fails and is retried, Intact iQ may receive two copies if idempotency checks are missing. This creates duplicate invoices and stock adjustments that are costly to reverse.

Orders lost in exception queues

Orders that fail initial submission queue for manual review. If the queue is not monitored and orders are not resubmitted within hours, dispatch schedules slip and customers do not receive shipment confirmation.

Credit limit checks fail silently

If the customer credit sync lags or the credit-check API call fails, checkout may not enforce limits. Orders from over-extended accounts proceed to Intact iQ, creating credit risk and reconciliation problems.

Pricing not updated when rates change

If the pricing feed breaks or is scheduled too infrequently, customers see old or incorrect prices. If prices are changed in commerce but not synced back to Intact iQ, invoices are raised at wrong amounts.

Returns and refunds orphaned in transit

If a return is processed in commerce but the debit or credit note is not created in Intact iQ, the original invoice remains open and stock is never adjusted. This leaves physical inventory out of sync with Intact iQ records.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Intact iQ integrations.

How do we prevent orders placed on the web from being entered twice - once in commerce and once in Intact iQ?

Orders flow from commerce into Intact iQ as the single point of invoice and dispatch. The integration assigns a unique commerce order ID to each Intact iQ sales document so duplicates can be detected. If an order fails submission, it queues for retry rather than being re-entered manually.

What happens if Intact iQ is down when a customer places an order?

The integration can operate in fallback mode, accepting orders into a local queue and replaying them to Intact iQ once it recovers. Alternatively, you can pause checkout and inform customers of the temporary outage. The fallback path and recovery SLA must be agreed in advance and tested.

How often does stock update from Intact iQ to the commerce platform?

Stock export frequency is configurable and should match your peak order rate. For high-velocity businesses, exports may run every 5-15 minutes. For lower volumes, hourly or on-demand exports are typical. Stock buffers can mitigate oversell risk during intervals between exports.

Can we handle customer-specific pricing on the web, and how does it stay in sync?

Yes. Customer-specific price bands or tiered pricing from Intact iQ can be exported and loaded into commerce price catalogs or promotion rules. The integration must refresh these feeds whenever pricing changes in Intact iQ. Frequency depends on how often pricing changes - typically daily or on-demand.

How do credit limits work, and what happens if a customer exceeds theirs?

Customer credit limits from Intact iQ are checked at checkout before an order is submitted. If a customer has insufficient credit, the checkout can warn them or block the order. The credit check runs in real-time and depends on the integration's ability to query Intact iQ or a cached credit-limit feed.

What if an order fails to reach Intact iQ - does the customer see a confirmation?

The integration should validate orders before confirming them to the customer. If validation fails (e.g., customer not found, stock unavailable, credit exhausted), the customer is informed at checkout. Orders that fail after confirmation queue for manual review and replay.

How do returns and refunds flow back to Intact iQ, and how long does it take?

A return request in commerce triggers a debit or credit note in Intact iQ, reversing the original invoice line and adjusting stock. The flow usually completes within hours. Once the credit note is created in Intact iQ, it can be sent to the customer as a PDF.

Who owns the responsibility for monitoring failed orders and fixing them?

The commerce operations team owns monitoring the exception queue and triaging failed orders. Remediation may involve investigating data quality issues, resubmitting orders or escalating to finance or customer service. SLAs for queue review (e.g., within 4 business hours) must be defined and measured.

How do we reconcile web sales back to Intact iQ for accounting?

Because orders flow into Intact iQ with full traceability, month-end reconciliation compares the total invoice value in Intact iQ to total order value in commerce. Differences usually point to orders still in exception queues, cancelled orders or returns not yet credited. Audit logs on both sides support the reconciliation.

What happens to orders and pricing if we replatform our commerce system?

The integration layer must be rebuilt to map the new commerce platform's order format to Intact iQ. Historical orders remain in Intact iQ unchanged. Pricing and stock feeds can usually be adapted with new field mappings. A parallel-run period allows validation before cutover.

Can the integration handle multi-currency or multi-location orders?

Intact iQ supports multi-currency and multi-location operations. The integration must map commerce locations and currencies to Intact iQ entities, ensure pricing is converted correctly, and route orders to the correct Intact iQ location. This adds complexity and must be planned in the design phase.

How do we handle edge cases like gift cards, discounts or shipping charges in the order?

These must be explicitly mapped into Intact iQ sales document line items or charges. Gift cards may create a separate receivable line; discounts may reduce line values; shipping is usually a separate charge line. The integration must preserve the detail so Intact iQ invoices are accurate and auditable.

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 Intact iQ 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 →