Accurately structuring advance ship notices is critical for retailers and suppliers who want to avoid chargebacks, streamline inbound operations, and keep EDI compliant. According to Octasyn, the choice between carton-level, pallet-level, or order-level ASN structures depends on each retailer's requirements, your physical processes, and the constraints of your warehouse systems.
Definitions: what are carton, pallet, and order level ASNs?
Carton-level ASN: provides item-level detail for every individual carton shipped, with each carton tied to its own SSCC. Pallet-level ASN: groups cartons under their associated pallets, reporting hierarchy from pallet down to carton. Order-level ASN: summarizes all items shipped for the order as a whole, with no carton or pallet breakdown reported.
How to decide which ASN structure to use
The right ASN structure is driven by retailer mandates, shipment complexity, and your operational capacity.
-
01
Understand retailer requirements. Review each trading partner's EDI implementation guide to confirm whether carton, pallet, or order-level detail is mandated.
-
02
Review your warehouse workflows. Confirm your pick, pack, and scan processes can actually capture the level of detail the required structure demands.
-
03
Consider customer experience and downstream processes. Factor in how the receiving retailer's DC or store will use the ASN data once it arrives.
-
04
Implement with technology for compliance. Use a platform that automatically builds the correct ASN structure from real pack and carton data, rather than assembling it manually.
Comparison: carton vs. pallet vs. order level ASN
| Structure | When it's required | Benefits | Challenges |
|---|---|---|---|
| Carton-level | Most major retailers for warehouse/DC shipments | Highest detail, improves receiving speed, enables chargeback protection, supports cross-docking | More complex to execute, requires robust scan/pack software |
| Pallet-level | Retailers with palletized, bulk inbound processes | Optimizes DC handling, supports large-volume logistics | Requires associating cartons to pallets, risk of mismatch if manual |
| Order-level | Small retailers, drop-ship, or some ecommerce flows | Easiest to execute, minimal data requirements | Limited retailer acceptance, higher risk of receiving and invoice disputes |
Octasyn insights: why structure matters for chargebacks and compliance
Structuring your ASN correctly eliminates a huge percentage of common EDI chargebacks. Mistakes often happen at these choke points:
- Carton-to-pallet association: Manually linking cartons to the wrong pallet is one of the most common pallet-level ASN errors.
- Quantity roll-up mismatches: Item counts that don't sum correctly from carton to pallet to order trigger automatic rejections.
- SSCC assignment errors: A duplicated or missing SSCC breaks the carton-level detail retailers depend on.
- Structure mismatched to retailer expectation: Sending order-level detail to a retailer expecting carton-level guarantees a rejection.
Using Octasyn's platform, companies like Razor USA and Nakoma Products have automated the association of items to specific cartons and pallets, ensuring 100% EDI compliance and greatly reducing staff hours spent on rework or exception handling. Both companies shipped over 10,000 orders per day during peak with remarkable accuracy and on-time delivery rates.
Best practices for ASN structure selection
- Default to carton-level unless a retailer explicitly allows less. It's the safest structure across the widest range of trading partners.
- Document each retailer's required structure in one place. A centralized reference prevents applying the wrong structure by mistake.
- Automate carton-to-pallet association. Manual linking is the most common source of pallet-level ASN errors.
- Validate structure against a test shipment before going live. Confirm the ASN hierarchy matches what the retailer's system expects.
- Revisit structure choice when retailer requirements change. A routing guide update can shift which structure is actually required.
Common ASN structure pitfalls (and how to avoid them)
- Assuming order-level is always acceptable: Confirm explicitly with each retailer rather than defaulting to the easiest option.
- Manual carton-pallet mapping at scale: This breaks down quickly as order volume grows; automate it instead.
- Ignoring quantity roll-up validation: A mismatch between carton, pallet, and order totals is one of the most common rejection triggers.
- Failing to update the ASN structure after a retailer policy change: Routing guides change more often than most teams expect.
Frequently asked questions
What is the main difference between carton-, pallet-, and order-level ASNs?
Carton-level ASNs provide item-level detail for every carton shipped. Pallet-level ASNs group cartons under their associated pallets. Order-level ASNs summarize all items shipped for the order, with no carton or pallet breakdown reported.
When should I use a carton-level ASN?
Use carton-level when retailers demand traceability for every carton, require UCC-128/GS1 labels on each carton, or need automated receiving at the DC. Most major US retailers expect carton-level ASNs on warehouse/distribution shipments.
Why are pallet-level ASNs sometimes needed?
Pallet-level ASNs are required for retailers that receive goods on pallets and want cartons grouped operationally. This supports bulk handling and efficient warehouse receiving processes. Check each retailer's EDI guides for specifics.
What tools help automate accurate ASN structures?
Software like Octasyn connects receiving, packing, and shipping operations, automatically tracks items per carton and pallet, generates compliant labels, and builds a correct ASN, reducing manual work and decreasing error rates.
Can I send an order-level ASN if the retailer expects carton-level?
No. Sending fewer details than required will trigger automatic errors, manual processing, and almost always leads to chargebacks.
How do I structure ASNs for drop-ship or small direct-to-store scenarios?
For these, many retailers accept order-level ASNs. Always verify the retailer's current policy and document it in your EDI playbook.
What is the risk of incorrect packing hierarchy in the ASN?
Incorrect associations between items, cartons, and pallets result in inventory discrepancies, chargebacks, delayed payments, and increased dispute resolution time.
How do I validate that my ASN matches my physical shipment?
Use system-driven packing and ASN validation workflows. Octasyn includes validation tools and workflows for ensuring data accuracy before transmission.
The right ASN structure prevents chargebacks before they happen. See how Octasyn automates carton, pallet, and order-level compliance per retailer.
Talk to a shipping expert
.png)
