What a TrueCommerce integration gives you.
Buyers log in through their procurement platform, initiate PunchOut, and browse your product catalogue and pricing without leaving their workflow. iWeb ensures the session stays buyer-linked and contract pricing is applied throughout.
Orders from buyer procurement systems arrive in your ERP with the right buyer account, cost centre, approval codes and contract pricing. Fulfillment and invoicing can proceed without manual rework or data cleanup.
After your ERP receives and acknowledges an order, the acknowledgement flows back to the buyer via cXML, EDI or PEPPOL within your SLA. Buyers have confidence that their order has been received.
When orders ship, ASN and invoice data flow back through TrueCommerce in the buyer's expected format and schema. Buyer accounting can reconcile without manual matching or dispute escalation.
Pricing changes in your ERP propagate to the PunchOut catalogue so buyers always see accurate contract rates. Discount tiers and minimums are kept in step with your trading agreement rules.
Where a TrueCommerce 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.
TrueCommerce supports multiple EDI dialects (X12, EDIFACT, PEPPOL) and procurement protocols (cXML, OCI). Without explicit mapping, order data may not parse correctly into your ERP's cost-centre, approval or account fields.
Buyer-specific pricing and contract rules must be maintained in sync between your ERP and the PunchOut catalogue. TrueCommerce alone cannot guarantee that a price change in the ERP appears in the buyer's next session without explicit governance.
Buyers expect real-time or near-real-time feedback on order acknowledgement, pick status and shipment. TrueCommerce does not automatically push status back to the buyer without explicit outbound flows from your ERP or OMS.
Many buyers require that orders pass internal approval rules before reaching your ERP. TrueCommerce can route orders but does not enforce buyer-side approval without explicit pre-validation logic in the integration layer.
Buyer-initiated returns must map back to the correct purchase order and cost centre in your ERP. TrueCommerce does not automatically link credits back without explicit reverse-flow mapping.
Procurement workflows expose the tension between buyer-initiated ordering (async, approval-dependent, multi-party) and seller fulfillment logic (synchronous, inventory-dependent, cost-centre-driven). Without explicit governance of order routing, pricing and exception handling, procurement channels quietly accumulate queued orders and missed acknowledgements.
Where this integration sits in your estate.
TrueCommerce 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.
Built for your platform, not a specific one. TrueCommerce integrates with any ecommerce core through the same contract.
- Procurement protocol routing (cXML, OCI, EDI, PEPPOL)
- PunchOut session management and buyer-catalogue delivery
- Inbound purchase order receipt and queuing
- Outbound acknowledgement and ASN messaging
- Buyer-account linkage and cost-centre routing
- Product catalogue and inventory visibility
- PunchOut session rendering and buyer-session state
- Availability data for PunchOut responses
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.
- Magento Open Source
- Adobe Commerce
- Shopify Plus
- BigCommerce
- Other storefronts
- ERP (SAP, Infor, NetSuite, Dynamics 365)
- OMS (Flexport, TraceLink, inRiver)
- PunchOut and cXML handler
- EDI translator and mapping engine
- Buyer account and cost-centre master
- Invoice and reconciliation system
- Order acknowledgement and ASN system
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.
- 01Procurement protocol and EDI mapping
iWeb designs the parsing and transformation of incoming cXML, OCI, EDI and PEPPOL messages so that purchase order data maps cleanly into your ERP schema with buyer account, cost centre and approval routing pre-filled.
- 02PunchOut catalogue and pricing layer
iWeb builds the integration so that buyer-initiated PunchOut sessions pull current inventory and contract pricing from your ERP or PIM. Session state is buyer-aware and pricing rules are enforced in real time.
- 03Order acknowledgement and ASN return flows
iWeb configures TrueCommerce to receive order acknowledgements and shipping confirmations from your ERP or OMS, transform them into the buyer's expected EDI or cXML format, and route them back on schedule.
- 04Invoice and credit-note exchange
iWeb maps invoice and credit-note data from your ERP into EDI or cXML format, routes them through TrueCommerce and ensures buyer accounts, line details and totals match procurement expectations for clean reconciliation.
- 05Exception handling and observability
iWeb instruments the integration so that unmatched orders, pricing conflicts, format errors and missing buyer rules surface in a queue where operations can investigate, resolve and reprocess. Observability covers order flow, transformation and status return.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built B2B order exchange before
iWeb has designed and supported multiple TrueCommerce implementations across manufacturing, automotive and trade sectors. We understand how procurement workflows differ from consumer ecommerce, where buyer approval, cost-centre routing and EDI format variety all matter.
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.
A buyer's procurement system sends a PO in a format variant or schema version your integration does not recognize. Without validation before ERP handoff, the order lands incomplete or in an exception queue and never reaches fulfillment.
A buyer's contract pricing is updated in your ERP but the PunchOut catalogue does not refresh for hours or days. The buyer sees outdated rates and places orders expecting a discount that your system no longer honors.
A buyer's procurement system holds a purchase order pending internal approval while your integration tries to push it immediately to your ERP. Orders pile up in TrueCommerce, and fulfillment misses SLAs because the integration does not know to wait.
Your ERP sends order acknowledgements and ASNs correctly, but TrueCommerce cannot transform them into the buyer's expected EDI dialect or the buyer's endpoint is temporarily down. The buyer has no visibility of order status and escalates with support.
An invoice is sent to the buyer but the cost centre or line-item details do not match what was on the purchase order. Buyer accounting cannot match invoice to PO and disputes the payment, requiring manual investigation and rework.
Orders or messages stuck in TrueCommerce error states are not surfaced or escalated. Days later, operations discover that critical buyer orders never reached your ERP or acknowledgements never reached the buyer.
Relevant services and sectors.
Common questions about TrueCommerce integrations.
What procurement protocols does iWeb support through TrueCommerce?
iWeb supports cXML, OCI, EDI (X12, EDIFACT) and PEPPOL. iWeb designs the parsing and mapping for each protocol so that purchase orders from different buyers land in your ERP with correct cost centres, approval codes and contract pricing regardless of the incoming format.
How does contract pricing get published to the buyer?
iWeb integrates your ERP's pricing tables with the PunchOut catalogue so that when a buyer initiates a session through their procurement system, they see current contract rates, discount tiers and minimum order quantities. Price updates in the ERP propagate to PunchOut on your defined refresh schedule.
What happens when a buyer places an order via PunchOut or EDI?
The buyer's procurement system sends the purchase order via cXML, OCI, EDI or PEPPOL to TrueCommerce. iWeb's integration layer parses the order, enriches it with the buyer's account, cost centre and approval routing rules, and passes it to your ERP. The ERP then processes fulfillment as normal.
How do order acknowledgements and ASNs get back to the buyer?
After your ERP receives and processes a purchase order, it generates an acknowledgement and (after picking and packing) an ASN. iWeb's integration layer retrieves these from your ERP, transforms them into the buyer's expected EDI or cXML format, and sends them via TrueCommerce. Buyers see order status without manual intervention.
How are invoices and credit notes sent to the buyer?
After shipment or return, your ERP generates invoices or credit notes with line details, totals and cost-centre codes. iWeb transforms them into the buyer's expected EDI or cXML format and routes them via TrueCommerce so the buyer can reconcile against their purchase order and cost-centre ledgers.
What if a buyer's procurement system requires approval before the order reaches us?
iWeb's integration layer can hold orders in TrueCommerce pending buyer-side approval signals. When the buyer's procurement system confirms approval (either through a separate handshake or by sending the PO in a confirmed state), iWeb releases the order to your ERP. This prevents premature fulfillment and cost-centre disputes.
How does iWeb handle different buyer requirements or EDI variants?
Each buyer can have different protocols, pricing rules, cost-centre schemes and approval workflows. iWeb configures per-buyer routing rules so that orders from buyer A (cXML with approval hold) are treated differently from buyer B (PEPPOL with immediate fulfillment). Operations can add and manage buyer rules without redeploying.
What happens if an order or message fails to parse or transform?
iWeb instruments exception queues so that malformed orders, unmatched pricing, format errors and missing buyer rules surface immediately. Operations can investigate, correct the rule or buyer configuration, and reprocess. This prevents silent loss and ensures transparency.
How does iWeb ensure buyer accounts and cost centres are mapped correctly?
iWeb designs a buyer-account mapping so that each procurement-system buyer links to the correct account, cost centre and pricing contract in your ERP. During integration design, you define which buyer ID in TrueCommerce maps to which account number and cost centre in the ERP. This happens before the first PO arrives.
Can iWeb handle returns and credit notes from buyers?
Yes. iWeb can capture buyer-initiated return requests from procurement systems, route them to your ERP or OMS with the correct original purchase-order reference, and after the return is processed, send a credit note back to the buyer in their expected EDI or cXML format.
How does iWeb monitor the procurement channel for failures?
iWeb instruments observability across inbound purchase orders, outbound acknowledgements and ASNs, and invoice flows. You can see order volumes, transformation times, exception counts and delivery status. Alerts surface if parsing fails, messages get stuck, or acknowledgement delivery lags behind your SLA.
What happens if TrueCommerce or your ERP goes down during a buyer's order?
iWeb designs the integration with graceful degradation and rollback paths. If TrueCommerce is temporarily unavailable, the buyer's procurement system receives a hold message via cXML/EDI. If the ERP is down, incoming orders queue in TrueCommerce. Once the system is back, messages are reprocessed in order and the buyer can see status updates.
How often are price and availability updates pushed to buyer PunchOut sessions?
iWeb configures a refresh schedule based on your needs. PunchOut catalogue and pricing can be updated on every buyer session, hourly, or on a schedule you define. Real-time availability (stock levels) typically refreshes more frequently than pricing. You control the trade-off between freshness and system load.
Can iWeb support buyers with different languages or regional pricing?
Yes. iWeb can configure per-buyer or per-region PunchOut catalogues so that a buyer in France sees prices in EUR and product descriptions in French, while a buyer in the UK sees GBP and English. This is layered into the PunchOut session logic and maintained from your ERP or PIM.
Projects with a similar shape.
A DIY and trade tile platform rebuilt around search, branch stock and customer ordering.
Tile retail trading supported by stronger search activity, mobile journeys and customer sessions.
A building plastics self-service portal built around trade accounts and product data.
Trade customers supported by self-service account access, cleaner product data and faster ordering.
A workwear retail platform focused on product merchandising and trade customer purchasing.
Integrated retail commerce for workwear and apparel operations.