Data flows iWeb integrates
How this mid-market ERP fits the operational estate.
Questions we get asked.
Which Sage editions does iWeb integrate?
The team integrates with the Sage edition the client already runs (commonly Sage 200, X3 or Intacct) through that edition's published integration surface or middleware. The pattern is the same; the connector differs.
Where does pricing and discounting live with Sage?
In Sage where the operation runs accounts and contracts in Sage. The storefront reads pricing through a governed boundary and caches it at read time so the ERP is not called on every page view.
Can Sage handle B2B account ordering online?
Yes. Account customers see contracted pricing, credit position, statements and account-only catalogues, with credit limits honoured at checkout.
Does iWeb integrate Sage with commerce platforms other than Adobe Commerce or Magento?
Most Sage integrations iWeb has shipped sit alongside Adobe Commerce or Magento. The integration pattern is platform-agnostic and can be applied to other commerce platforms where the architecture and Sage edition's integration surface support it.
Is iWeb a Sage development partner?
No. iWeb is an ecommerce agency working alongside the client's Sage partner or in-house team on the integration boundary.
What Sage data usually moves between Sage and ecommerce?
Pricing and discounts, stock, account ordering and credit, orders, dispatch confirmations, invoices and credit notes. Exact scope depends on the Sage edition and how the business runs it.
Real-time or scheduled sync with Sage?
Mixed. Pricing and stock are read on demand and cached at storefront read time. Orders post asynchronously through monitored queues. Reference data refreshes on a defined schedule.
Can Sage connect to a PIM?
Yes. Sage typically owns pricing, stock and accounts; a PIM such as Akeneo owns enriched product attributes and channel rules. Both feed the commerce platform through their own connectors.
When is middleware needed between Sage and ecommerce?
When more than one system sits either side of the boundary, when transformation, retries or routing need to be observable, or when the storefront should not own ERP semantics. Simpler estates can run on a direct connector.
Can iWeb take over an existing Sage integration?
Yes. The team reads the existing integration, message contracts and incident history first, then writes down what to fix first and what is safe to defer. The first month on support is deliberately conservative on change.
How is hosting and release governed for Sage-integrated commerce?
Release process tied to live trading, with monitoring across storefront, middleware and Sage, and a named senior owner on both sides of the boundary.
Can iWeb support multi-company Sage estates across editions?
Yes. Multi-company and multi-edition estates (Sage 200, Sage Intacct, Sage 50, Sage X3) are wired against the actual Sage ledger, with the integration contract written down per company and per edition.