In this article
Web EDI fulfillment lets a customer who does not operate an EDI system participate in the same warehouse process as customers who do. The customer works through a browser-based interface, while your team maps the necessary business information into a consistent order, shipping and billing workflow. You can support different ways of submitting an order without creating a separate warehouse process for each customer.
At BOLD VAN, we approach this with BOLD Exchange for customers and partners who do not use EDI, alongside warehouse execution through BOLD Fulfillment when you run your own warehouse. The key design decision is where an order becomes ready for warehouse work and how actual shipment results flow back to the customer.
What a shared fulfillment workflow means
Web EDI is a browser-based way to exchange business information. Shared fulfillment means orders from web EDI and other connected channels enter a common operational process: validation, warehouse work, shipment confirmation and billing. The customer-facing entry method can differ, but the internal meaning of an item, quantity, destination and order reference must remain consistent.
Keep the boundary between customer interaction and warehouse execution clear. BOLD Exchange serves the non-EDI customer or partner. BOLD Fulfillment is a WMS Lite with EDI built in for your own warehouse. If you already use another warehouse system, mapping between that system and your EDI workflow is a separate integration decision. The aim is a clear handoff, not an assumption that a portal entry automatically becomes a pickable order.
Key control: Treat a submitted order, an accepted EDI document and a warehouse-ready order as different states. Confirm each handoff before you release work to the warehouse.
How order and shipment data map
Think of each order as a business record with a customer identity, an order reference, product identifiers, quantities, a destination and requested timing. A web EDI entry and an X12 850 purchase order may express that record differently. Mapping aligns their meanings with the fields your warehouse needs. For example, the customer's product identifier may need an approved cross-reference to your warehouse item before fulfillment can proceed.
The outbound side starts with what actually happened in the warehouse. If the shipped quantity differs from the ordered quantity, the shipment message and invoice should follow the actual result rather than copying the original request. Packaging and shipment references may also matter for an 856 advance ship notice. Check each trading partner's published EDI implementation guide for required documents, versions, packaging detail and timing; do not apply another partner's rules by default.
| Business handoff | Common X12 document | What to check |
|---|---|---|
| Customer order | 850 purchase order | Identity, references, items, quantities and destination |
| Order response | 855 purchase order acknowledgment | Whether the response reflects the business decision |
| Warehouse instruction | 940 warehouse shipping order | Usable warehouse item and delivery information |
| Warehouse result | 945 warehouse shipping advice | Actual shipped quantities and order references |
| Shipment and billing | 856 advance ship notice, 810 invoice | Shipment detail and invoice alignment with actuals |
This table describes common transaction roles, not a mandatory sequence for every customer. A 997 functional acknowledgment tells the sender whether a document passed the receiver's syntax check. It can report acceptance or rejection. It does not mean the order or its content was accepted, so your business checks still need their own owners.
A practical implementation sequence
- Choose a representative customer and order. Use the customer's published requirements and identify which documents the customer expects. Include a routine shipment and an exception, such as a short shipment, in the test plan.
- Define the common record. Agree on who owns customer identifiers, warehouse items, order references, destinations and shipment status. Record how an incoming value is matched, rejected or corrected.
- Map each handoff. Trace the order from the web interface into warehouse work, then trace actual shipment information back into the required customer response. If an ERP, WMS or platform API is involved, use that system's documentation to settle implementation-specific details.
- Test failure paths. Try an unknown item, duplicate order reference, changed destination and partial shipment. Decide who investigates each exception and when warehouse work should pause.
- Reconcile the complete cycle. Compare the submitted order, warehouse result, shipment notice and invoice. A successful transmission alone is not evidence that the customer will receive an accurate shipment or bill.
For teams connecting other systems, BOLD Integration maps EDI into an ERP, WMS or other system. BOLD VAN also connects to a platform's API for EDI-to-API and API-to-EDI workflows. That can help when your shared warehouse process serves both EDI customers and channels using systems such as Shopify or ShipHero, among others.
Pitfalls and best practices
Keep identifiers and exceptions under control
A familiar failure is accepting an order whose item identifier looks valid but points to the wrong warehouse item. Maintain a reviewed cross-reference and assign someone to approve changes. Do the same for customer and destination identifiers. If a match is uncertain, stop the handoff rather than letting the warehouse infer the intended product or location.
Partial shipments deserve a separate test. Determine how warehouse staff record what shipped and what did not, then confirm that downstream documents represent those results consistently. Retail chargebacks are an industry problem when shipment information misses a partner's requirements. Accurate mapping and testing help reduce the risk of chargebacks.
Choose the right entry method for each customer
Web EDI fits a customer who needs a browser-based way to participate without operating an EDI connection. System integration fits customers with established applications and enough order activity to justify a direct handoff. You can use both approaches around the same warehouse process. The decision should depend on who enters data, how corrections are made and whether the customer needs information returned to its own system.
In our workflow reviews, we ask you to name an owner for every failed handoff, not only every failed transmission. Every document is tracked in the portal, where customers can search, requeue and report, with notifications when something needs their attention. That visibility is useful only when someone can distinguish a document problem from a warehouse or master data problem.
Build around the warehouse handoff
Start with the order record and follow it through shipment and billing. If you can explain where each identifier comes from, when an order is released and how actual shipment data returns, you have the basis for a shared workflow that accommodates non-EDI customers. BOLD VAN can help you plan that entry point through BOLD Exchange.
Frequently asked questions
Can a customer use web EDI without installing EDI software?
Yes. Web EDI gives a non-EDI customer a browser-based way to work with business documents. You still need to define how those documents become warehouse work and how shipment information returns.
Does a 997 mean the warehouse accepted the order?
No. A 997 functional acknowledgment reports whether the receiver's syntax check accepted or rejected a document. It does not confirm that the order or its contents were accepted for fulfillment.
Which documents connect a warehouse shipment to an EDI customer?
An 940 warehouse shipping order can convey an instruction to a warehouse, and an 945 warehouse shipping advice can return shipment results. An 856 advance ship notice can then communicate shipment details to a trading partner. Check that partner's published EDI implementation guide for its requirements.
What should we test before adding a non-EDI customer?
Test a complete order through warehouse execution, shipment reporting and billing. Include an unknown item, a duplicate reference and a partial shipment so you can verify exception ownership and data reconciliation.
