What a Centra integration gives you.
Centra runs as the storefront and commerce layer while ERP and PIM stay authoritative for pricing, stock, accounts and product content, so trading, finance and product teams work from consistent data.
DTC storefront orders and wholesale account orders both flow through Centra with the right pricing, terms and product visibility per audience, and post cleanly into ERP, OMS or WMS for fulfilment.
Stock levels, base pricing and wholesale price lists from ERP publish to Centra on a governed cadence, so storefront, wholesale and customer service teams see the same numbers as finance and operations.
Payment authorisation, capture and refunds flow between Centra, the payments provider and finance, and orders hand off to OMS, WMS or 3PL with dispatch and tracking coming back to the storefront.
Where the business trades across markets, currencies and languages, Centra runs the commerce layer while ERP, PIM and CRM stay authoritative per country, region or brand without duplicating masters.
Marketplace and channel feeds sit around Centra as connected workflows for reach, while the commerce layer, ERP, PIM and OMS stay the operational core of trading.
Where a Centra integration earns its place.
If two or more of these are true, the integration usually pays for itself quickly.
Where off-the-shelf connectors fall short.
Vendor connectors are fine for simple cases. Here's where the real ones need more.
Centra provides APIs but not out-of-the-box ERP integration; base pricing, wholesale price lists, on-hand stock and customer accounts require designed mapping and cadence per ERP.
Per-account catalogues, price lists, credit terms and approval workflows have to be modelled explicitly against the ERP or CRM record; Centra does not infer wholesale rules from raw data.
Order posting from Centra into ERP for finance and into OMS, WMS or 3PL for fulfilment requires transformation, idempotent retries and exception handling rather than a native connector.
Payment authorisation, capture, refund and settlement between Centra, the payments provider and ERP finance need explicit reconciliation; drift is not surfaced without monitoring.
Centra can push selective catalogue, pricing and stock to marketplaces and channels, but the data ownership model between Centra, PIM and each channel needs an explicit contract to avoid drift.
When trading teams talk about growth, the real question is whether the commerce platform, ERP, PIM and fulfilment systems agree on stock, pricing, orders and customers. That is where integration work lives.
Where this integration sits in your estate.
Centra is the commerce platform - the customer-facing experience, catalogue, checkout and account area. The iWeb integration layer wires it into the ERP, PIM, OMS, WMS and payments systems it depends on. The estate map helps agree ownership before anything is built.
Sits at the front of your estate. We wire Centra into the finance, stock and product systems it depends on.
- Storefront experience and product presentation for DTC and wholesale
- Customer account journey, login, registration and reorder flows
- Checkout and commerce-side order capture
- DTC and wholesale commerce workflows on one platform
- Commerce-side pricing, display and merchandising rules where appropriate
- DTC and wholesale storefront experience
- Product presentation and merchandising
- Customer account journey and reorder flows
- Checkout and commerce-side order capture
- Commerce-side pricing display and promotional rules
Systems this integration usually sits next to.
Examples, not a closed list. iWeb wires Centra into whatever ERP, PIM, OMS, WMS, payments and operational systems your estate already runs.
- ERP (Business Central, NetSuite, SAP, Sage 200)
- PIM (Akeneo, Salsify, Syndigo, custom product database)
- OMS / WMS / 3PL
- Payments providers (Adyen, Stripe, Klarna, Worldpay)
- Marketplaces and channel connectors (Amazon, Zalando, eBay)
- CRM and customer data platforms
- Reporting, BI and data warehouse
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.
The data flows we wire.
Each flow has a direction and an owner. We agree both before a line of code is written.
How iWeb configures the integration around your business.
Same method on every integration. The decisions come before the code.
- 01Product data and catalogue mapping
We map PIM product families, variants, attributes, media and taxonomy into Centra's catalogue model so DTC and wholesale storefronts publish with the right content and category structure.
- 02ERP pricing, stock and account integration
We build the flows that move base pricing, wholesale price lists, on-hand stock, customer accounts and credit terms from ERP into Centra on a governed cadence with monitoring.
- 03Wholesale customer and account workflows
We design wholesale account journeys in Centra: registration, credit-checked onboarding, per-account catalogues and price lists, reorder pads and approval workflows tied back to ERP or CRM.
- 04Order handoff to ERP, OMS or WMS
We hand orders captured in Centra off to ERP for finance posting, and to OMS, WMS or 3PL for allocation, pick, pack and dispatch, with idempotent retries and exception queues.
- 05Payment and fulfilment integration
We wire Centra into the payments provider for authorisation, capture, refunds and settlement, and back-fill dispatch and tracking events from OMS, WMS or 3PL into the storefront customer view.
- 06Monitoring, reconciliation and exception handling
We put observability around every flow: sync status, order posting, payment reconciliation and dispatch events, with alerting and exception queues so integration failures never sit silent.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built this before
iWeb designs Centra integration patterns around the way commerce teams actually trade: DTC storefronts, wholesale accounts, product data, stock, pricing, order handoff, fulfilment and reporting. We treat Centra as the commerce platform layer and design the operational systems around it to match.
What we test before launch.
Every one of these is rehearsed before a customer ever sees the integration.
Common risks and where they bite.
We name these on day one. A risk written down is a risk you can plan around.
Attributes, media and taxonomy updated in PIM can lag on the Centra storefront, leaving DTC and wholesale customers seeing inconsistent product content across catalogues, price lists and category pages.
If ERP-to-Centra stock and pricing feeds are infrequent or unmonitored, the storefront can show old prices or availability that no longer matches the source system, driving oversell and cancellations.
Wholesale customer accounts, credit terms and per-account price lists that live in ERP or CRM can drift from Centra, so wholesale buyers see the wrong pricing, terms or catalogue on login.
Orders captured in Centra may not post cleanly to ERP for finance or to OMS or WMS for fulfilment if error handling is not idempotent, leaving unmatched, duplicated or stuck orders in the estate.
Authorisation, capture, refund and settlement events between Centra, the payments provider and finance can drift out of reconciliation if webhooks and retries are not monitored, hiding refund failures and settlement errors.
Where marketplace and channel feeds are bolted on without a clear ownership model, catalogue, stock and order data can be fought over between Centra, PIM and each channel connector instead of governed cleanly.
Relevant services and sectors.
Common questions about Centra integrations.
How does Centra connect to our ERP?
We build the flows that move base pricing, wholesale price lists, on-hand stock, customer accounts and credit terms from your ERP into Centra on a governed cadence, and post DTC and wholesale orders, customer updates and order lifecycle events from Centra back to ERP for finance and reporting. Cadence, error handling and reconciliation are designed per ERP (Business Central, NetSuite, SAP, Sage 200 and similar) rather than assumed by a generic connector.
How does product data flow from PIM into Centra?
PIM stays the governed source for product families, variants, attributes, media and taxonomy. We publish that content into Centra's catalogue model on a governed cadence so DTC and wholesale storefronts show consistent product data. Merchandising overrides in Centra are scoped to commerce-side presentation rather than replacing the PIM record.
Can Centra support both DTC and wholesale workflows?
Yes. Centra runs DTC storefronts and wholesale accounts on the same commerce layer. We design per-account catalogues, price lists, credit-checked checkout, reorder pads and approval workflows in Centra, tied back to the customer, account and credit record in ERP or CRM. Both audiences see the right pricing, terms and product visibility on login.
How do stock and pricing updates reach Centra?
ERP is the source of truth for base pricing, wholesale price lists and stock ledger. We publish those updates into Centra on a governed cadence with monitoring on freshness and failed feeds. Where the business needs channel-specific display rules, they live as commerce-side rules in Centra and do not overwrite the ERP source data.
How are Centra orders handed off to fulfilment?
Orders captured in Centra hand off to OMS, WMS or 3PL for allocation, pick, pack and dispatch, with idempotent retries and exception queues rather than fire-and-forget calls. Dispatch confirmations, tracking numbers and stock movements flow back into Centra so the storefront and customer service teams see the same fulfilment status as operations.
How do payments, refunds and returns flow?
Centra orchestrates payment authorisation and capture with your payments provider (Adyen, Stripe, Klarna, Worldpay and similar). Refund and settlement events flow back to Centra and into ERP finance for reconciliation. Returns are captured against the original order in Centra, then routed to OMS, WMS or 3PL for physical handling and to ERP for credit notes.
How do marketplace and channel feeds fit around Centra?
Marketplaces and channels are neighbouring workflows around Centra, not the core role. We publish selective catalogue, pricing and stock from Centra (or from PIM directly) to marketplace and channel connectors, and route marketplace orders back into the commerce, ERP and fulfilment stack. Ownership of listings and feed status stays with each channel connector.
What happens if we change ERP, PIM or fulfilment systems?
Centra stays the commerce platform layer, so replatforming ERP, PIM, OMS, WMS or payments mainly affects the integration boundaries into and out of Centra. Because the integration is designed around explicit ownership per system, swapping a downstream system becomes a scoped project rather than a rebuild of the storefront and wholesale experience.
Where does Centra sit in the estate?
Centra sits as the commerce platform layer. The integration work is about connecting storefront, product, customer, pricing, order and fulfilment workflows with the operational systems around it: ERP, PIM, OMS, WMS, payments, marketplaces, CRM and reporting.
Can Centra handle international and multi-market commerce?
Yes. Centra supports multi-market storefronts, currencies and languages. We model markets, price lists and catalogues per region or brand while ERP, PIM and CRM stay authoritative for accounts, product content and finance, so international expansion does not require duplicating masters or forking the platform.
How do we monitor that integrations are healthy?
We put observability around every flow: sync status for product, pricing and stock feeds, order posting into ERP and fulfilment, payment reconciliation and dispatch events. Alerts and exception queues surface failed publishes, stuck orders and unmatched payments so integration issues become tickets rather than silent drift.
Is Centra a marketplace or channel connector?
No. Centra is a DTC and wholesale ecommerce platform for fashion, lifestyle and brand-led commerce. Marketplaces and channels sit around Centra as connected workflows for reach; Centra itself is the commerce platform layer running the storefront and wholesale experience.
Other commerce platforms integrations.
Adjacent integrations in the same category. Same shape of work, different vendor.
Projects with a similar shape.
A VW camper parts platform rebuilt around catalogue depth, search and specialist ordering.
Specialist parts purchasing updated through deeper catalogue structure and stronger search journeys.
A product data platform shaped around catalogue accuracy and downstream commerce.
Multi-depot foodservice wholesale supported by Akeneo PIM, Adobe Commerce and Aptean ERP integration.
An industrial tools platform rebuilt around specialist procurement, product search and trade buying.
Industrial product purchasing supported by stronger search activity and updated checkout activity.