Send the EDI 856 hierarchy that mirrors how the freight is physically built, within what your trading partner’s implementation guide allows. Use SOTPI (shipment, order, tare, pack, item) when labeled cartons ride on labeled pallets, SOPI (shipment, order, pack, item) when cartons travel as the units, and SOTI (shipment, order, tare, item) when the labeled pallet is the unit and its cartons carry no labels of their own. Build the 856 from the WMS pack confirmation, one HL loop per physical unit with the SSCC printed on its label, and validate it against the trailer before you send it.
Most pages about the 856 list the errors behind ASN chargebacks. This field note works one step earlier: it shows how packing data in your WMS becomes HL loops, how to choose the structure from the freight, and which checks to run before transmission and after the 997 comes back. The partner’s guide always wins; this is how to read it and build to it.
What the 856 hierarchy describes
The 856 Ship Notice/Manifest describes a shipment as a tree of hierarchical levels: the shipment at the top, then orders, pallets, cartons and items below it, each level an HL segment that names its parent. The hierarchy is how the receiver knows which cartons sit on which pallet and what is inside each carton before the trailer is opened.
X12’s own description is explicit about the physical side. The X12 transaction set list says the 856 can list “the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.” It “enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.”
That “ordered flexibility” is the HL segment. In version 4010, as listed in Stedi’s X12 reference, the HL has four elements:
| Element | Name | What it does in an ASN |
|---|---|---|
| HL01 | Hierarchical ID Number | A number unique within the transaction set for each HL, usually 1, 2, 3 in order |
| HL02 | Hierarchical Parent ID Number | The HL01 of the level this one sits under; empty for the shipment |
| HL03 | Hierarchical Level Code | The kind of level: S Shipment, O Order, T Shipping Tare, P Pack, I Item |
| HL04 | Hierarchical Child Code | Whether this level has children below it |
The level codes come from element 735, whose code list includes S “Shipment”, O “Order”, T “Shipping Tare”, P “Pack” and I “Item”, among others. In practice “tare” means a pallet or other unit load and “pack” means a carton or case. The 4010 usage note for the HL loop, as reproduced in Stedi’s 856 reference, is blunt about the HL itself: it is “the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.” The meaning comes from the segments that follow each HL.
SOTPI, SOPI and SOTI compared
The three common structures differ in which physical levels appear: SOTPI includes both pallets and cartons, SOPI includes cartons only, and SOTI includes pallets only. Each must match the labels actually on the freight, because the receiver scans those labels and looks them up in your ASN.
| Structure | Levels, top to bottom | Freight it describes | SSCCs in the ASN | Item quantities sit under |
|---|---|---|---|---|
| SOTPI | Shipment, Order, Tare, Pack, Item | Palletized cartons, with a label on each pallet and on each carton | Pallet and carton | Each carton |
| SOPI | Shipment, Order, Pack, Item | Cartons as the units: parcel, floor-loaded, or pallets the partner does not want described | Carton | Each carton |
| SOTI | Shipment, Order, Tare, Item | Pallets as the units, with no carton labels, often one item per pallet | Pallet | Each pallet |
The industry often uses two more terms for the same choice. “Standard pack” usually means each carton holds one item in a fixed quantity, so carton detail adds little. “Pick and pack” usually means cartons hold mixed items or odd quantities, so the receiver needs carton-level detail to receive without opening every box. Partners use these words differently, so confirm what yours means by them.
What each structure asks of the warehouse
Each structure needs a different set of warehouse capabilities, and the ASN can only be as detailed as the scans behind it. Before agreeing to a structure, check that the floor can produce the data every day, on every shift.
| Structure | Warehouse steps it depends on | Where it usually breaks |
|---|---|---|
| SOTPI | Pack to carton with a contents scan; carton label printed at close; each carton scanned onto a pallet; pallet label printed; pallet scanned onto the trailer | Cartons moved between pallets during wrapping without a rescan |
| SOPI | Pack to carton with a contents scan; carton label printed at close; carton scanned onto the trailer or parcel manifest | Cartons labeled before they are full, then topped up |
| SOTI | Pallet built from known full cases; pallet label printed; pallet scanned onto the trailer | Case counts estimated from layers instead of counted |
The carton-to-pallet scan in SOTPI is the step most often skipped. Without it, the WMS knows which cartons exist but not which pallet each one is on, and the T-to-P parent links in the ASN become guesses. If your floor cannot do that scan reliably yet, agree a SOPI structure with the partner for now, if its guide allows, rather than sending a pallet tree you cannot vouch for. Label printing and placement for each level are covered by our barcode and labeling work.
What BSN05 says, and what it cannot
The BSN segment’s fifth element, BSN05 Hierarchical Structure Code (element 1005), declares the structure. In the X12 4010 code list, the shipping codes are 0001 “Shipment, Order, Packaging, Item”, 0002 “Shipment, Order, Item, Packaging”, 0003 “Shipment, Packaging, Order, Item” and 0004 “Shipment, Order, Item”. There is no separate code for a tare level.
So the code alone does not tell you whether to include pallets. If a partner wants SOTPI, its implementation guide should say which BSN05 value to send with it; if it does not, ask before anyone writes a map. Keep a copy of the guide version you built to.
How to choose the hierarchy from the freight on the truck
Start from the labels you physically apply, then check the partner’s guide. If a unit carries its own SSCC label, it needs its own HL loop; if it carries none, it must not appear as a tare or pack level. Where the guide and your freight disagree, change the packing or labeling process, not the ASN.
| Freight on the truck | Labels applied | Usual structure | Watch for |
|---|---|---|---|
| Pallets of mixed cartons for one PO | Pallet SSCC and carton SSCC | SOTPI | Every carton label must sit under the right pallet |
| Pallets of one item, cartons unlabeled | Pallet SSCC only | SOTI | Quantity per pallet must match the case count |
| Loose cartons by parcel or floor-loaded | Carton SSCC | SOPI | Carton count must match the bill of lading |
| Pallets the partner breaks down on receipt | Carton SSCC, pallet label as the guide says | SOPI or SOTPI per guide | Do not send pallets the guide does not want |
| One pallet holding cartons for several POs | Pallet SSCC and carton SSCC | Build pallets per PO, or a packaging-above-order structure if the guide allows | In SOTPI each pallet sits under one order |
Decision rules
- Count the label types. Pallet labels only means SOTI; carton labels only means SOPI; both means SOTPI, unless the guide says to omit one level.
- Check whether pallets mix orders. In a shipment-order-tare structure, each pallet sits under exactly one order. A pallet carrying cartons for two POs would have to appear under both orders, which describes one physical pallet twice. Either build pallets per PO, or use a structure with packaging above order (BSN05 0003) if the guide accepts it.
- Check whether pallets mix items. A mixed-item pallet with unlabeled cartons fits SOTI only if the partner accepts several item loops under one tare. A receiver may want carton labels instead, which moves you to SOTPI.
- Check the mode. Parcel shipments have no pallet level, so SOPI is the natural fit. If the partner also wants each carton’s tracking number, the MAN qualifier list includes CP “Carrier-Assigned Package ID Number” alongside the SSCC codes.
- Read the guide’s examples, not just its segment list. The sample transmissions show the structure the partner’s receiving system actually parses.
Example (fictional). A housewares supplier ships to a retailer whose guide asks for SOTPI on palletized freight and SOPI on parcel. Its WMS builds mixed pallets across store orders to fill trailers, so one pallet often holds cartons for three POs. The first test ASNs list the same pallet SSCC under three order loops, and the retailer’s test system rejects them.
The supplier had two options: change the map, or change the build. Because the guide had no packaging-above-order option, it changed the build. The WMS now closes a pallet when the PO changes, and the extra pallets per trailer were accepted as the price of clean receiving.
Mapping WMS pack data to HL loops
Generate the 856 from the WMS pack and ship confirmation, not from the order or the pick list. The pack confirmation is the only record of which item went into which carton, which carton went onto which pallet, and which SSCC was printed on each, and that is exactly what the HL tree must carry.
Your WMS needs five records at the moment the trailer closes. Each maps to a level of the tree:
| WMS record | 856 level | Typical segments (check your guide) | Must contain |
|---|---|---|---|
| Shipment or load | HL S | TD1 lading quantity and weight, TD5 carrier routing, REF bill of lading, DTM ship date, N1 ship-from and ship-to | One per trailer or BOL, as the guide defines |
| Order on the load | HL O | PRF purchase order number, N1 mark-for store where used | One per PO on the shipment |
| Pallet (license plate) | HL T | MAN with the pallet SSCC | Parent order, SSCC, pallet weight if required |
| Carton (license plate) | HL P | MAN with the carton SSCC | Parent pallet or order, SSCC |
| Carton or pallet contents | HL I | LIN item identifiers, SN1 units shipped and unit of measure, PO4 pack details | Item, quantity, unit, lot where required |
A few segment details matter for the map. In 4010, PRF01 is the Purchase Order Number. SN1 carries Number of Units Shipped (SN102) and its Unit or Basis for Measurement Code (SN103). MAN carries the marks, and the qualifier list for MAN01 (element 88) includes AA “SSCC-18” and GM “SSCC-18 and Application Identifier”; your guide says which one to use. LIN product qualifiers include UP for the U.P.C. consumer package code, VN for the vendor’s item number and BP for the buyer’s part number.
The license plate is the join
In the WMS, every pallet and carton should have a license plate number (LPN) that is the SSCC, or that maps to exactly one SSCC. The GS1 Logistic Label Guideline states the principle: “Scanning the SSCC barcode on each logistic unit allows the physical movement of units to be matched with the electronic business messages that refer to them.” If the label printer draws a number from one sequence and the ASN map draws from another, every unit on the truck is a mismatch waiting to happen. How to number and print those labels is covered in our guide to SSCC pallet labels that scan at customer docks.
Customers enforce the same tie in their own specifications. One distributor’s supplier label example states that the “SSCC / GS1-128 Barcode must tie to EDI 943 Transfer Order information” (Dot Foods consignment label example). That document concerns a 943 rather than an 856, but the rule is the same: the barcode on the unit and the number in the message must be one value.
Example (fictional). The first loops of an 856 for the tree shown earlier, as a supplier’s translator might produce them. Element separators are asterisks and segments end with a tilde; the qualifiers follow this partner’s guide.
HL*1**S*1~
HL*2*1*O*1~
PRF*4500123~
HL*3*2*T*1~
MAN*GM*00006141410000000418~
HL*4*3*P*1~
MAN*GM*00006141410000000425~
HL*5*4*I*0~
LIN**VN*EX-20118~
SN1**12*EA~
Read HL43P1 as: this is HL 4, its parent is HL 3, it is a pack (carton), and it has children. The summary CTT segment at the end would count all seven HL segments, because the 4010 note for CTT01 says it “is the accumulation of the number of HL segments.”
Where lot numbers and expiry dates go
Lots belong at the item level, because a lot describes goods, not cartons. In 4010 the LIN product qualifiers include LT “Lot Number”, so a guide may ask for the lot as a qualifier and value pair on the LIN segment; other guides place it elsewhere in the item loop, and dates go where the guide says. Two rules hold whatever the placement:
- One item loop per item and lot. A carton holding two lots of the same item needs two item loops under that carton, each with its own quantity. Summing them into one loop loses the lot split the receiver needs.
- Lots come from the pack scan. If packers do not scan or confirm the lot when they close a carton, the WMS can only guess it from allocation, and a guessed lot in an ASN is worse than none.
For food on FDA’s Food Traceability List, the lot you send may be the traceability lot code your customer has to keep, which raises the cost of getting it wrong. Whether that code is yours to assign or must pass through unchanged from your supplier is a question to settle with your customer before you map it.
Totals that must agree
The 856 carries its own arithmetic, and receivers check it. The 4010 notes say the CTT02 hash total, if used, “is the sum of the value of units shipped (SN102) for each SN1 segment.” Several other counts should agree with each other and with the trailer:
- The number of HL segments and CTT01.
- The number of tare or pack levels and the lading quantity in TD1, as the guide defines it.
- The total units by item across all item loops and the quantities your ERP will invoice.
- The total weight in TD1 and the bill of lading.
Validate the ASN against the truck before you send it
Run a pre-send validation that compares the ASN with the PO, with the labels scanned at the dock door and with the trailer’s bill of lading, and that blocks transmission when a hard rule fails. A wrong ASN sent on time can do more harm than a late one, because the receiver acts on it.
| Check | Rule | Block or warn |
|---|---|---|
| PO exists | Every PRF number is an open PO from this customer | Block |
| Items on PO | Every item loop matches a line on its PO | Block |
| Quantity | Units shipped do not exceed the PO line, or the partner’s tolerance | Block or warn, per guide |
| SSCC format | 18 digits with a valid GS1 check digit | Block |
| SSCC uniqueness | No SSCC appears twice in this ASN or in any earlier ASN | Block |
| Scan match | Every SSCC in the ASN was scanned at the door onto this trailer, and every scanned SSCC is in the ASN | Block |
| Parent links | Every HL02 points to an HL in this transaction, at the level above | Block |
| Totals | CTT01 equals the HL count; TD1 matches pallets or cartons and weight | Block |
| Timing | Sent after the trailer closes and within the partner’s window | Warn, escalate if late |
The scan match is the check that makes the ASN “match what is physically on the truck.” It needs the dock team to scan each pallet or carton label onto the trailer, which also catches units left behind at the door and units loaded onto the wrong trailer. If your WMS cannot record a load scan, add one before you add more EDI rules; no map can describe freight nobody scanned.
GS1 defines the Serial Shipping Container Code as the identifier for a logistic unit, “for example a case, pallet or parcel”, and its guideline reminds you who owns the number: “The SSCC should be assigned by the company that is creating the logistic unit, using its own GS1 Company Prefix.” Its structure is an extension digit, the GS1 Company Prefix, a serial reference and a check digit, after Application Identifier (00). The serial reference is yours to manage, and the uniqueness check above is how you prove it stays unique. If you outsource packing to a 3PL, decide in writing whose prefix and whose sequence the 3PL uses.
Where to run the checks
Run business checks before the EDI translator, in the WMS or the integration layer that builds the ASN, and leave syntax checks to the translator. The translator knows segments and element lengths; it does not know that SSCC …0425 was never scanned onto trailer 14 or that PO 4500123 was cancelled yesterday. Those facts live in the WMS and the ERP.
A practical split:
- WMS at load close: load scan complete, every scanned unit has contents, no unit appears on two loads, weights captured.
- Integration layer before mapping: POs open, items on the PO, quantities within tolerance, SSCC uniqueness against the full history of sent ASNs.
- Translator: structure and syntax against the partner’s guide, envelope and control numbers.
- After sending: 997 received in time, partner acceptance reports read and matched.
Each layer should fail into a queue someone owns, with a message a shipping lead can act on: “Carton SSCC …0425 is on the ASN but was not scanned onto the trailer”, not a segment error code.
Timing rules to build in
Partners set their own timing rules for the 856, so take the window from the guide and encode it as data, not as code. Whatever the window, the ASN has to reach the partner before the freight does; that is the point of an advance ship notice. Build these rules into the send step:
- Generate the ASN when the WMS closes the load, not when orders are released.
- Hold transmission until the load scan is complete and the bill of lading is final.
- Send within the partner’s window and record the transmission time.
- If the trailer changes after sending, follow the guide’s procedure for a replacement or cancellation instead of sending a second original.
Short shipments, reprints and changes after sending
The ASN must describe what shipped, so every exception on the dock has to flow into it before transmission, and every change after transmission has to follow the partner’s replacement procedure. When an ASN does not match the truck, look first for a dock exception that never reached the message.
| Dock exception | What the ASN must show | How the WMS should handle it |
|---|---|---|
| Line short-shipped | Only the units packed; the missing units do not appear | Pack confirmation drives quantities; backorder handled in the ERP, not the ASN |
| Carton label damaged and reprinted | The same SSCC as before | Reprint from the stored SSCC; never draw a new number for a reprint |
| Carton repacked after the ASN was built | The new carton’s new SSCC and contents | Invalidate the draft ASN and rebuild from the new pack data |
| Pallet left behind at the door | Not in the ASN | Load scan excludes it; the ASN is built from scanned units only |
| Freight moved to another trailer after sending | A corrected ASN, per the guide’s procedure | Follow the guide’s replace or cancel rules; do not send a second original |
| One trailer, several ship-to locations | One shipment per ship-to, or the structure the guide defines for multi-stop loads | Build loads by stop, and ASNs by shipment |
The reprint rule deserves emphasis because it fails quietly. If a label printer draws a new SSCC every time someone presses print, the carton on the truck carries a number the ASN has never heard of, and the receiver logs an unknown unit. The fix is in the label process, not the EDI map: store the SSCC on the carton’s record when it is first assigned, and print from the record.
Example (fictional). At 3:40 p.m. a supplier’s packer finds a crushed carton on a pallet bound for a distribution center. She repacks the 12 units of EX-20118 into a new carton and prints a new label, SSCC …0449. The ASN draft built at 3:15 p.m. still lists the crushed carton, …0425.
Because the WMS invalidates any draft ASN when a carton on its load is repacked, the draft is rebuilt at load close with …0449 in place of …0425. The load scan confirms …0449 is on the trailer, and …0425 is marked as destroyed so it can never be reused.
Why ASNs get charged back
ASN chargebacks come from a short list of causes: the ASN was late or missing, it did not match what arrived, its labels did not match its SSCCs, or its structure was not what the partner’s system expects. Each cause traces to a process step, and most are prevented by the validation above.
| What the receiver sees | Usual cause at the supplier | Prevention |
|---|---|---|
| No ASN when the trailer arrives | ASN generated from a batch job that ran after arrival, or failed silently | Send on load close; alert on missing 997 |
| ASN quantity differs from receipt | ASN built from the pick list or order, not the pack confirmation | Build from pack data only |
| Scanned label not found in the ASN | Label reprinted with a new SSCC after the ASN was built | Reprints reuse the original SSCC, or rebuild the ASN |
| SSCC already used | Sequence reset after a system change or a second label printer | Central SSCC sequence and a uniqueness check across history |
| Pallet appears under several orders | Mixed-PO pallets in a tare-under-order structure | Build per PO, or a structure the guide allows |
| Units left at the dock still in the ASN | No load scan | Scan every unit onto the trailer before sending |
| Wrong structure for the mode | One map used for parcel and pallet freight | Choose the structure per shipment from the freight |
Tracing a deduction back to its cause
When a deduction or compliance notice arrives, trace it to evidence before deciding whether to dispute it or fix a process. The trace is quick if the records are kept together and slow if they live in three systems.
- Collect the partner’s detail: PO, ASN or shipment number, receipt date and the stated reason.
- Pull what you sent: the raw 856, its transmission time and the 997 that came back.
- Pull what you shipped: the load scan log for the trailer and the label print log for each SSCC on it.
- Compare unit by unit: which SSCCs were in the ASN, which were scanned onto the trailer, which the partner says it received.
- Classify the cause using the table above, and record it against the shipment.
- Dispute with evidence where your records show the ASN matched the truck, or fix the process step where they do not.
Over a few months, the classified causes become a ranked list of process fixes, which is more useful than a total of deductions.
Chargeback amounts and rules come from each retailer’s vendor agreement, so we do not quote any here. What you can measure is the effect on your own performance: on-time and in-full results by customer show whether ASN errors line up with receiving problems. The OTIF and fill rate calculator gives a consistent way to measure them.
Monitoring 997s and partner acceptance
A 997 Functional Acknowledgment confirms that the partner’s translator could parse your 856, nothing more. Monitor it for every transmission, and separately monitor the partner’s business acceptance, which arrives through other messages, portals or receiving reports.
X12 defines the 997 as acknowledging “the results of the syntactical analysis of the electronically encoded documents” and adds: “This standard does not cover the semantic meaning of the information encoded in the transaction sets.” The 999 Implementation Acknowledgment goes one step further, to “syntactical and relational analysis”, but it still says nothing about whether the PO, the quantities or the SSCCs are right.
The codes to watch in a 997, from the 4010 code lists:
| Segment and element | Code | Meaning | Action |
|---|---|---|---|
| AK5 Transaction Set Acknowledgment Code | A | Accepted | None |
| AK5 | E | Accepted But Errors Were Noted | Read AK3 and AK4, fix the map before the next send |
| AK5 | R | Rejected | Fix and resend; the partner did not take this ASN |
| AK9 Functional Group Acknowledge Code | P | Partially Accepted, At Least One Transaction Set Was Rejected | Find which ASNs in the group failed |
| AK9 | R | Rejected | The whole group failed; check envelopes and syntax |
Then watch for business acceptance. Some partners send an 824 Application Advice, which X12 says can “report the results of an application system’s data content edits”, including “acceptance, rejection, acceptance with change, or partial acceptance or rejection.” Some send an 861 Receiving Advice/Acceptance Certificate after receipt. Others publish scorecards in a supplier portal. Whatever the channel, assign an owner, a check frequency and a target time to respond.
Match each 997 to the ASN it answers by control number. The AK2 segment, Transaction Set Response Header, carries the Transaction Set Identifier Code (856) and the Transaction Set Control Number of the ASN being acknowledged, so your monitor can mark that exact ASN as accepted or rejected rather than guessing by time of day.
A monitoring routine that covers both layers:
- Expect a 997 for every 856 within the time agreed with the partner; alert when one is overdue.
- Alert on E and R codes immediately, with the ASN number and the AK3 and AK4 details in the message.
- Match every ASN to a receipt where the partner sends receiving data, and list differences by SSCC.
- Review partner scorecards weekly, and trace each ASN-related deduction to a cause in the chargeback table above.
- Keep the raw 856, the 997 and the load scan together for each shipment, so a dispute can be answered with evidence.
Reading the 856 from the receiving side
If you also receive 856s from your own suppliers, the same structure tells your receiving team what to expect: which pallets, which cartons and what is inside. A trustworthy inbound ASN lets the dock scan one pallet label and receive its contents without opening every carton.
That only works if your WMS stores the inbound tree as expected receipts by SSCC and checks each scanned label against it. A receiving process built on inbound ASNs usually follows these rules:
- Scan the highest labeled level first. For an SOTPI shipment, scanning an intact pallet’s SSCC can receive every carton under it, if your policy trusts that supplier.
- Spot-check by rule, not by mood. Open a set share of pallets from each supplier, more for suppliers with recent mismatches, and record what you find against the SSCC.
- Treat an unknown SSCC as an exception, not a reason to key the receipt by hand. Park the unit, receive the rest, and resolve it with the supplier.
- Measure ASN accuracy by SSCC: units whose contents matched the ASN, divided by units received. Share it with suppliers, with examples.
Suppliers whose ASNs fail those checks repeatedly should be measured and told, with examples. For how inbound ship notices fit into seeing supplier orders before they reach your dock, see how to see inbound purchase orders before they arrive.
When a third-party warehouse receives for you, the supplier’s 856 often drives the 943 you send the 3PL, and the 3PL’s 944 confirms what arrived. Which system owns each of those numbers is set out in our ERP and WMS system of record guide.
What to do next
Start with the partner’s implementation guide and your packing process side by side, decide the structure per shipment type, and build the ASN from pack data with a load scan behind it. Then put the pre-send validation and the 997 monitoring in place before the first live shipment.
A checklist for a new trading partner or a rebuilt 856:
- Get the partner’s current implementation guide and note its X12 version, BSN05 value and sample transmissions.
- List your shipment types (palletized, parcel, mixed-PO, single-item pallets) and the structure each needs.
- Make the WMS license plate the SSCC, or map each LPN to one SSCC, from one central sequence.
- Add a load scan at the dock door if you do not have one.
- Build the map from pack confirmation data, with HL parents taken from the pack tree.
- Implement the pre-send checks in the validation table, with hard blocks.
- Test with real shipments, including a reprinted label, a short-shipped line and a mixed pallet.
- Set up 997 monitoring and a named owner for business acceptance reports.
Test scenarios worth sending to the partner
Partner testing usually starts with whatever shipment is easiest to build. Push for test ASNs that cover your real exceptions as well, because those are the ones that will fail in production:
- One PO, one pallet, standard-pack cartons.
- One PO, several mixed pallets in SOTPI.
- Several POs on one trailer, pallets built per PO.
- A parcel shipment in SOPI with tracking numbers if the guide wants them.
- A short-shipped line.
- A carton with two lots of the same item.
- A reprinted label that keeps its SSCC, and a repacked carton that gets a new one.
- A replacement or cancellation sent according to the guide.
Keep each test ASN, the partner’s response and the 997 together as evidence of certification, with the guide version you tested against.
If your labels and ASNs need work together, our barcode and labeling service covers SSCC numbering and label printing, and our ERP, WMS and EDI integration service builds and documents the 856 map, validation and monitoring. The UAT test plan helps you script partner testing, and you can contact us to talk through a specific partner guide.
