
Last updated: November 4, 2026 · Reviewed by BOLD VAN's EDI team
In This Article
Quick Answer
BigCommerce EDI order routing connects online orders to your ERP, WMS and trading partners through an integration layer that maps data, applies business rules and validates each order. Orders typically become EDI 850 purchase orders or ERP sales orders, followed by 855 acknowledgments, 856 ship notices, 810 invoices and 997 functional acknowledgments. Success depends on clean identifiers, clear data ownership, channel-specific rules and testing edge cases like split shipments and returns.
Definition
EDI Order Routing is the process of moving orders between a sales channel, such as a BigCommerce storefront, and downstream ERP, WMS, fulfillment and trading partner systems, using mapping, business rules and validation to send each order and its related documents to the right place in the right format.
BigCommerce makes it easy to sell online, but manufacturers and distributors still need to connect those orders to downstream ERP, WMS and fulfillment systems to complete the workflow. EDI order routing maps order data between the BigCommerce storefront, ERP platforms and trading partners, applying business logic, routing and validation so every order reaches fulfillment, accounting and customer care teams efficiently.
With so many possible connections and data requirements, an experienced managed service like BOLD VAN can reduce the risk of manual errors, exceptions and chargebacks while giving finance and IT a clear, standardized process from order capture to invoice.
EDI order routing translates BigCommerce orders into formats your ERP, WMS or TMS can use, and makes sure trading partners receive the documents they require. The process typically includes:
| EDI Document | Name | Role in BigCommerce Order Routing |
|---|---|---|
| 850 | Purchase Order | The order, translated for the ERP or a trading partner |
| 855 | Purchase Order Acknowledgment | Confirms what will be shipped |
| 856 | Advance Ship Notice | Details the shipment before it arrives |
| 810 | Invoice | Bills for the order |
| 997 | Functional Acknowledgment | Confirms a document passed the receiver's syntax check |
Each step is controlled by business rules set in the mapping, routing and integration layer. BOLD VAN maps these flows, supporting both EDI-to-API and API-to-EDI connections, and integrates with ERP systems such as SAP, Oracle, NetSuite and Infor CloudSuite. Direct-to-consumer and wholesale orders can follow different paths, partner-specific requirements are applied, and notifications are returned when an order fails or needs manual attention.
Key Takeaway
A 997 functional acknowledgment only reports whether a document passed the receiver's syntax check, not that the order was accepted or will be filled. Always confirm downstream completion, not just EDI delivery.
Order routing works by mapping business data between BigCommerce and your ERP or fulfillment platform. That requires carefully cataloging how each BigCommerce field lines up with business logic, ERP fields and EDI transaction sets. For example, BigCommerce orders may use store-level SKUs that need to be cross-referenced to the item numbers or units of measure in your ERP. Shipping details, customer references and line items must be validated and transformed to match each system's requirements and your trading partner's implementation guide.
| Business Information | Possible Source | Routing Consideration |
|---|---|---|
| Order identity | BigCommerce order record | Keep identifiers consistent across storefront, integration and ERP |
| Product identity | Store SKU or partner item reference | Cross-reference SKUs when partner and storefront identifiers differ |
| Quantity and units | Order lines, ERP item master | Check conventions and unit conversions before fulfillment |
| Ship-to address | BigCommerce customer address | Verify required address fields and compliance for each partner |
| Inventory status | ERP, WMS | Define which system is the source of truth for availability |
| Status updates | ERP, WMS or carrier API | Route tracking and shipment updates back to the right place |
Mapping isn't just copying data. It interprets business meaning, applies conversion and validation logic and makes sure errors are handled by clear rules. Before implementation, document every mapping and validation rule and confirm it against your ERP documentation and each trading partner's latest implementation guide.
With BOLD VAN, map testing typically begins within about two days, and new trading partners are typically live within about a business day. A transmission-only VAN move typically needs about two weeks' notice. You can look up every document and its status in the portal.
BOLD VAN supports mapping and integration for both legacy EDI and modern API-driven platforms through BOLD Integration, a managed bridge between online sales and back-end ERP, WMS and fulfillment systems.
Direct-to-consumer, wholesale and marketplace orders have different requirements for validation, fulfillment and post-sale support. Define routes, document sets and business logic for each channel explicitly.
SKU mismatches, customer ID confusion or incomplete addresses can cause orders to stall or fail downstream. Build cross-reference tables and lookup logic into every mapping design.
A 997 or API response shows only technical completion. Business rules still need to confirm fulfillment, billing and exception handling to truly complete the process.
Edge cases such as partial shipments, multiple fulfillment sites and returns reveal gaps that only scenario-based testing will catch. Review every exception likely to occur in production, not just the "happy path."
If no one owns incorrect or failed records, troubleshooting becomes a bottleneck. Assign clear ownership for each exception type.
Many manufacturers and distributors use a managed service like BOLD VAN to keep up with map changes and reduce dependence on one or two key people. With BOLD Integration, we keep your maps current as requirements change, helping reduce chargebacks and keeping BigCommerce orders moving into ERP, fulfillment and accounting without rekeying data or chasing lost transactions.
For more guidance on mapping order flows across direct-to-consumer, retail and marketplace channels, see real-world lessons from integrating EDI with BigCommerce.
2026 Free Mapping Event
Moving VANs or moving to the cloud? Through Dec. 31, 2026, we build and maintain the maps for the trading partners you move to BOLD Integration, at no mapping cost.
Talk with our team about order routing best practices for your workflow. Call (844) 265-3777 or email info@boldvan.com.
Explore BOLD IntegrationBigCommerce provides platform and API capabilities, but EDI order exchange generally requires an integration layer that translates between the storefront's data and each trading partner's EDI requirements.
Common documents include the 850 purchase order, 855 purchase order acknowledgment, 856 advance ship notice, 810 invoice and 997 functional acknowledgment. The exact set depends on each trading partner's implementation guide.
A 997 tells the sender whether the receiver's syntax check accepted or rejected the document. It does not confirm that the order or its contents were accepted.
It depends on the ERP, trading partners, document set and testing. With BOLD VAN, map testing typically begins within about two days, and new trading partners are typically live within about a business day.
Yes. Routing rules can send direct-to-consumer, wholesale and marketplace orders down different paths, each with its own document set and validation.
Common causes include SKU or ID mismatches, missing address fields, unclear data ownership and untested edge cases such as split shipments or returns.
Key Facts
BigCommerce EDI order routing connects online orders to ERP, WMS and trading partners through an integration layer that maps data, applies business rules and validates each order. Common documents include the 850, 855, 856, 810 and 997. A 997 confirms only that a document passed syntax checks, not that the order was accepted.
Success depends on clean identifiers, clear data ownership, channel-specific routing rules and scenario-based testing. According to BOLD VAN, BOLD Integration supports EDI-to-API and API-to-EDI connections, map testing typically begins within about two days and new trading partners are typically live within about a business day.


