Things to consider when implementing ASNs & the mistakes that cost your business

A single misaligned SSCC, a missing batch number or expiry date, or an ASN sent minutes too late can turn a routine delivery into rejected loads, manual rework and penalties that erode margin. Most of these issues aren’t technical curiosities; they’re predictable outcomes of unclear ownership, brittle master data and warehouse processes that haven’t been tested against buyer rules.

This article cuts through this noise.

Each section opens with a key question that frames the decision you need to make, develops the operational and data implications in plain terms, and closes with the mistake(s) to avoid so you can de-risk implementation before day one. The result is a practical guide for implementing ASNs that meet buyer expectations, protect cash and keep operations flowing, without turning compliance into a cost centre.

Key question

Have you operated/processed ASNs before?

Past experience changes the risk profile. Teams that have worked with ASNs tend to know where things go wrong, optional fields that act like mandatory ones in live trading, how to structure case and pallet data, and what to do with products that need batch, expiry or serial numbers.

If this is your first ASN rollout, you may not have considered some of the steps in the process. Put time into a short discovery phase with the people who will pick, pack and print; it will surface issues early and save rework later.

• Use a short pilot shipment to prove the end-to-end flow (from pack rules to labels to the ASN message) before scaling up.
• Document what “good looks like” (a single page with examples) so training is fast and consistent.

Mistake(s) to avoid

Assuming your previous ASN map will work unchanged with a new buyer is a fast route to delays and penalties. Even when two buyers use the same standard, their implementation guides and warehouse rules may differ in subtle but important ways. Reusing old assets can save time, but only after you have proved they match the new buyer’s rules end-to-end.

Key question

How technical is the ASN allocation hierarchy?

Your packaging hierarchy sets the tone for everything else. Decide early whether you will declare shipments as:

Shipment → Pallet → Case → Item

Shipment → Case → Item

Shipment-only

More levels mean more identifiers to manage, more labels to print and more places a mismatch can occur; fewer levels may be non-compliant or slow down receiving. Choose the hierarchy you can reliably pack and scan every day, then make your mapping and label design follow that choice.

• Align hierarchy with what your warehouse can actually build. Don’t design a pallet structure that you cannot maintain during peak times.
• Walk a real order through the hierarchy with operations to check counts, label placement and scanning steps.

Mistake(s) to avoid

Underestimating the time needed to test parent/child packaging relationships – especially when introducing pallets for the first time – will bite you later.

Hierarchies affect how you pick, pack, label and scan, so you must test mixed cases, partial pallets and returns, not just the perfect outcomes. Build test runs on the floor, capture where labels go, and confirm scanners read first time. If you skip this, mismatches between what was packed and what the ASN declares will show up at the dock as rejections.

Key questions

Does the retailer need shipping labels?

Do they need to match the ASN?

Many retailers require labels on all consignments, with specific rules for size, layout and barcodes. The crucial detail is that the data on the label must match the data in the ASN, the same SSCC, case count and product identifiers. Decide where SSCCs will be created, where they will be stored, and which system will generate label content, so you avoid disparities between systems.

• Keep one “source of truth” for SSCCs and feed both the ASN and the printer from that source.
• Create a simple label placement guide with photos for operators; consistency helps acceptance on delivery.

Mistake(s) to avoid

Ignoring retailer label rules or printing labels from a different system than the one that generates SSCCs almost guarantees mismatches. The SSCC, case count and product codes on the label must mirror the ASN exactly – same numbers, same structure, same logic. Keep one source of truth for SSCCs and feed both the label printer and the ASN from it.

Key questions

Which application owns line-item allocation?

Which application generates SSCCs?

Where are labels printed?

Clear ownership reduces errors. Find the answers to all three questions and agree on these decisions up front. Write down responsibilities and processes for easier onboarding and departmental integration.

Line-Item Allocation – Decide if pack sizes and case/pallet splits come from ERP/WMS, auto-allocation logic, or manual input. Build checks that stop the flow when data is missing or contradictory, rather than letting bad data reach the ASN. Put checks at the start of the flow to catch missing or conflicting data. If a product can be sold in different pack sizes, agree on a simple rule for which one applies to the ASN and make the system enforce it, rather than leaving it to manual judgment.

Mistake to avoid: Trusting units-per-case without validation is risky. If the ERP holds the wrong pack sizes, every downstream calculation is off, from how many cases you build to which SSCC appears on which label.

SSCC Generation – Choose a single owner (ERP/WMS or integration platform) for SSCC creation so that number discrepancies are avoidable. Expose SSCCs to every downstream step through one controlled interface. Keep a running list of used numbers and block reuse. When you add a new packing step or site, extend the same approach, avoiding local workarounds that break the single-source model. Choose one system to generate SSCCs and expose them to all other steps through a single, controlled interface.

Mistake to avoid: Letting multiple systems create SSCCs produces duplicates and confusion quickly.

Label Printing – Keep label templates and print payloads in the same ecosystem that holds the SSCCs. Version them properly, and lock down edits. Add a simple pre-ship check that compares what was printed to what will be sent, so you catch issues before the trailer leaves. This ensures that what is printed always matches the ASN.

Mistake to avoid:Generating SSCCs in one system and printing labels elsewhere leads to drift. Over time, templates fall out of sync, payloads change, and operators create “quick fixes” that don’t match the ASN.

If you use an enrichment/validation layer (e.g., copying product codes, defaulting missing delivery/tax fields, converting units, calculating totals/VAT, holding duplicates), you’ll send ERP-ready documents and cut exceptions down sharply.

Key question

Do your ASNs need conditional elements like batch, expiry or serial numbers?

Different products carry different rules. Perishables and regulated items often require lot/batch numbers, expiry dates, and temperature data; electronics may need serial numbers or part revisions. Treat these as standard where relevant, not edge cases. Identify where each data point comes from (WMS, production, LIMS) and enforce it before the ASN is sent. If the data is missing, fail fast rather than guessing.

• Build simple rules: “if product category = chilled, then batch and expiry are required”.
• Test a few real SKUs from each category so you can prove the path for conditional fields.

Mistake(s) to avoid

Treating conditional data (batch, expiry, serial numbers or temperature) as edge cases is a common failure.

Key question

How does the retailer run testing and sign off?

Testing styles vary. Some buyers use structured phases with quick feedback; others rely on portals or offshore support with slower response times. Before you commit dates, find out which scenarios must be proved (e.g., partial shipments, mixed pallets), what evidence is required, and typical turnaround times. Build scans and acknowledgement monitoring into your plan, not just message validation. Some buyers review daily; others weekly. Some insist on scanned label photos and sample payloads; others want live receipts. Ask early, plan to their rhythm, and agree on exit criteria in writing.

• Agree on exit criteria for go-live in writing with both sides understanding what a “pass” means.
• Keep a single log of questions and defects to maintain momentum.

Mistake(s) to avoid

Promising timelines without understanding the retailer’s onboarding cadence and evidence needs is avoidable pain. This can lead to you announcing go-live dates you cannot meet and spending weeks chasing feedback across tickets and portals.

Key question

Can your warehouse and carriers deliver what the ASN promises?

The best mapping cannot rescue a weak physical process. Confirm the warehouse can pack to the chosen hierarchy, operators understand GS1 labels, printers and scanners are set up correctly, and collection windows align with ASN timing rules (some partners require the ASN before departure). Run a “day-in-the-life” dry-run to prove the steps from pick-to-pack-t-print-to-ship.

• Create a short operator guide with photos showing correct label placement and a checklist for each load.
• Measure scan read-rates on full pallets and mixed cases; tune printers and placement until read-rates are reliable.

Mistake(s) to avoid

If the physical steps cannot deliver what the ASN promises, the buyer will reject the load.

Key question

Which master data checks will you enforce before the ASN is sent?

Most errors trace back to master data: unit of measure differences (EA/Case/Pallet), GTIN ↔ SKU mismatches, packaging specs that don’t match reality, or invalid GLNs. Put validation in front of the ASN: hold messages with unknown GTINs, suspect UoM conversions or unmapped locations and route issues to data owners, giving clear reasons as to why there has been an error in order to fix the source. This is a small investment that prevents a long tail of rework. A short delay to correct the data is cheaper than a rejected trailer and a chargeback.

• Keep a simple cross-reference table for GTINs and internal SKUs; review changes weekly during rollout.
• Audit a sample of GLNs against live orders to remove obsolete locations.

Mistake(s) to avoid

Letting “just this once” data exceptions through for speed always costs more later. Unknown GTINs, invalid GLNs or shaky unit conversions will pass validation in one place and fail at the buyer or in your ERP.

The patterns are consistent: SSCC mismatch, ASN not sent on time, missing case-level detail, wrong quantities, and incorrect GTINs. Each one is preventable with the controls above – single ownership of SSCCs and labels, clear hierarchy, firm validation, and warehouse rehearsal. Assign an owner, make a small process or data change, and measure the impact the following week. Track exceptions weekly and fix root causes rather than firefighting.

• Use a short dashboard with five metrics (late ASNs, SSCC mismatches, missing case detail, quantity variances, invalid codes) to focus the team.

Mistake(s) to avoid

Accepting penalties as a “cost of doing business” hides fixable problems. Treating fines as noise means you keep paying for the same avoidable errors.

Many organisations ask how to reduce manual effort. A modular enrichment/validation layer can copy product codes between buyer/seller formats, default missing delivery or tax details, convert units, calculate totals and VAT at line level, remove invalid or zero-value lines, reference original orders or delivery notes, and hold or archive duplicates before anything reaches the ERP. The result is fewer exceptions, faster onboarding and cleaner ASNs that match labels every time.

Done well, ASNs speed up receiving, reduce disputes and protect margin. Retailers process loads faster and with fewer touches; your team spends less time fixing issues after the fact; cash is not drained by avoidable fines.

The side-benefit is better data discipline across products, locations and pack sizes, which helps every other EDI flow too. Expect improvements in supply chain efficiency, retailer satisfaction, chargeback avoidance and operational accuracy when controls are embedded, not bolted on.

Seeing ASN work as a one-off IT task misses where value is created. Sustainable gains come from simple rules, clear ownership and routine checks across data, labels and the warehouse. If you only “do the map”, you’ll get a file that passes a validator but fails in operations. Tie the digital steps to the physical steps, refresh training, and keep a short list of health metrics so improvements stick after go-live.