ASN Email Processing: Get Shipment Notices Into Your ERP

ASN email processing means taking an advance shipping notice that arrives as an email, a PDF, an Excel sheet or free text, reading the shipment data, checking it against your purchase order, and posting it to your ERP or warehouse system so receiving can start before the truck arrives. Done by hand, it is slow and error-prone. Done with automated extraction and a quick human approval, it becomes a routine step.

This guide explains what an ASN contains, how the EDI 856 relates to an ASN email, which fields to extract and validate, and how to measure whether your process is working. It is written for purchasing, warehouse and operations leads who still receive many ASNs in the inbox.

Ampwise

Move ASN Data Into Your ERP

Ampwise processes ASN-type emails and attachments from Outlook or Gmail, then lets you approve verified data into your ERP with one click.

Explore Ampwise

TL;DR

An ASN is a notice a supplier sends before a shipment arrives, listing what is on the truck so your team can plan and receive quickly.
In EDI, an ASN is the ANSI X12 856 transaction. Suppliers without EDI often send the same information by email, PDF or spreadsheet.
Reliable ASN email processing has four steps: capture, extract, validate against the PO, then approve and post to the ERP.
Large receivers hold suppliers to strict timing and data rules, so speed and accuracy in your own handling matter just as much.
Ampwise reads ASN-type emails and attachments from Outlook or Gmail without templates and lets you approve verified data into your ERP with one click.

What an ASN is and what it contains
ASN, EDI 856 and the ASN email
How ASN email processing works, step by step
Which fields to extract and validate
What receiver rules teach about timing and accuracy
Where email-based ASN handling goes wrong
Our perspective
Automate ASN and incoming goods emails with Ampwise
A practical rollout plan
FAQ
Sources

What an ASN is and what it contains

An advance shipping notice (also called an advance shipment notice) is a message from the shipper to the receiver, sent before the goods arrive. DHL’s glossary describes it as a document containing detailed shipment information, including product descriptions, lot numbers, packaging information and expected delivery times.

The Produce Traceability Initiative’s EDI 856 guidance explains that an ASN provides order and shipment information in a single electronic transaction from shipper to receiver, and compares it to a bill of lading because it carries much of the same information. The point is planning: your dock, your labor and your inventory records can get ready before the delivery shows up.

A typical ASN includes:

Purchase order number or numbers
Ship-from and ship-to details
Carrier and tracking or pro number
Item numbers, descriptions and quantities
Packaging structure, such as pallets and cartons
Lot or batch numbers where relevant
Expected delivery date and time

Some receivers make the notice mandatory. Amazon’s ASN training guide states that an ASN is required for every shipment and that its purpose is to give the destination’s receiving operations information ahead of delivery.

ASN, EDI 856 and the ASN email

The terms get mixed up, so here is the clean split.

EDI 856 is the standard format. According to SAP Business Network’s X12 documentation, the 856 Ship Notice/Manifest transaction set lists shipment contents and related details such as order information, product description, type of packaging, marking, carrier information and the configuration of goods within transportation equipment. That is the answer to the common question about the EDI code for an ASN: it is 856 in the ANSI X12 standard.

An ASN email is the same information in a different wrapper. Many smaller suppliers, regional carriers and overseas vendors do not run EDI. They send a PDF packing list, an Excel sheet or a plain message saying what shipped and when. Your team then has to turn it into a record in the ERP.

Even in a fully EDI setup, email still plays a part. In SAP Business Network, for example, an inbound 856 is validated, acknowledged with a 997, converted to a cXML ship notice and posted internally. If an application-level error occurs, an email notification goes to the supplier with the failure and its reason.

If you are deciding which channel belongs where, our piece on EDI vs email covers when EDI pays off and when AI is the better fit for the long tail of partners.

How ASN email processing works, step by step

Whatever tool you use, a dependable flow follows the same four steps.

Capture. The ASN lands in a shared inbox in Outlook or Gmail. The message is recognized as a shipment notice, not an order or an invoice, and labeled so the right person or workflow sees it.
Extract. The system reads the email body and every attachment (PDF, scan, Excel) and pulls out the fields: PO numbers, items, quantities, carrier, tracking, expected arrival.
Validate. The extracted data is matched against your open purchase orders and item master. Microsoft’s Dynamics warehouse walkthrough states that ASN information must match the PO the vendor shipment is going to fulfill. Once it matches and processes successfully, an inbound shipment, load and packing structure are created.
Approve and post. A person reviews anything flagged, approves, and the data goes into the ERP as an inbound shipment or expected receipt.

Step 3 is where most manual processes fail. A typed quantity that does not match the PO, or a PO number with a transposed digit, only shows up at the dock. For a closer look at checks before release, see validating purchase orders before ERP release.

Which fields to extract and validate

Not every field carries equal risk. Start with the ones that drive receiving and matching.

Field	Why it matters	What to validate
PO number	Links the shipment to the order	Exists in the ERP and is still open
Item number or GTIN	Identifies what is on the truck	Matches the item master or PO line
Quantity	Drives receiving and inventory	Does not exceed the open PO quantity
Carrier and tracking number	Lets the dock follow the delivery	Present and in a plausible format
Expected delivery date	Sets dock and labor planning	Falls after the ship date
Packaging and pallet or carton IDs	Speeds up scanning at receipt	Unique, no duplicates
Lot or batch number	Supports traceability	Present where the item requires it

Large receivers show how seriously they treat this. Kroger’s ASN startup document says it validates case GTIN codes and purchase order numbers after loading, and that receiving is then performed against purchase orders, license plates, case GTINs and the quantities sent in the ASN. Even if you are not a retailer, borrowing that logic is wise: receive against the notice, so the notice has to be right.

Handling missing or inconsistent data

Supplier emails are rarely perfect. A good process treats gaps as exceptions rather than guesses:

Missing PO number: hold the record and ask the supplier, or match on supplier plus item and quantity and let a person confirm.
Quantity above the open PO: flag it for purchasing instead of posting it.
Unit mismatch (cases vs pieces): validate against the item master’s units.
Duplicate notice for the same shipment: detect before posting, so you do not create two expected receipts. Our guide to duplicate order detection in ERP explains the checks.
No pallet-level detail: General Mills notes that receivers should be ready to receive a load without pallet detail when transmissions are late or unavailable. Plan a fallback for receiving at the load level.

If the ASN arrives as a spreadsheet, the same logic applies; see how to import an Excel attachment into your ERP without retyping.

What receiver rules teach about timing and accuracy

Whether you send ASNs or receive them, published customer requirements show what “good” looks like.

Speed. Amazon’s 856 business requirements say vendors must send the 856 within 30 minutes of departure, or at least 6 hours before the appointment time, whichever is sooner, and that missing or delayed notices result in chargebacks.
Uniqueness. Amazon’s training guide states that failing to use a unique ASN ID per shipment causes ASN data to be overwritten, and that SSCC codes must not be reused within 12 months.
Feedback loops. Kroger returns a 997 for standard violations and an 824 describing errors with codes, and expects suppliers to monitor those responses. Its ASN loads less than 90 minutes after the supplier sends it.
Correction. FCA US says suppliers must transmit ASNs immediately when material leaves, and that discrepancies flagged by an 824 should be resolved and retransmitted right away using cancel-and-resend corrections.

The lesson for inbox-based handling is the same in every case: the notice is only valuable if it is in the system before the truck is. An ASN that sits unread in someone’s mailbox for half a day has lost most of its purpose.

Where email-based ASN handling goes wrong

The usual failure points are easy to name:

Delay. Notices wait in a personal inbox until someone has time.
Retyping errors. A digit slips in a PO or quantity, and the mismatch surfaces at the dock.
Format chaos. Each supplier uses a different layout, so rigid templates break.
No status trail. Nobody can tell which notices were processed, which are waiting and which were rejected.
Duplicates and revisions. A corrected notice arrives and is entered as a second shipment.

Our article on how operations teams can reduce data entry errors goes deeper on keeping people focused on exceptions rather than routine typing.

How to measure improvement

Pick a few simple numbers and track them monthly:

Time from email received to ERP posting. The target is to be well ahead of the truck.
Share of ASNs posted without edits. This shows how clean extraction and supplier data are.
Dock mismatches per 100 receipts. Count receipts where the physical load differed from the notice.
Exceptions per supplier. This tells you which partners need a nudge or a better process.
Manual minutes per ASN. Sample a week before and after automation.

Tell the team the baseline before you change anything. Without it, the improvement is a feeling, not a result.

Our perspective

We hear the same story from wholesale and manufacturing teams: EDI covers the biggest partners, and everyone else still sends shipment details by email. Those PDFs, spreadsheets and one-line messages are exactly the ones that end up retyped.

Our view is that you should not have to ask suppliers to change formats or rebuild your workflow. Ampwise is designed to work inside Outlook and Gmail, to read free-text emails, PDFs, Excel files and scans without templates, and to hand your team verified data instead of raw documents.

The human stays in control. We like one-click approval because it keeps accountability with your people while removing the tedious part, and the exceptions are the only things that need real attention. That is how teams get relief from data entry without trusting a black box.

Evert

Automate ASN and incoming goods emails with Ampwise

Ampwise AI automates the extraction, validation and entry of orders, inquiries, invoices, PO confirmations and incoming goods from Outlook and Gmail into your ERP. It handles emails, PDFs, Excel files and scanned documents without templates, labels messages smartly, tracks status and extracts metadata, so shipment notices stop waiting in individual inboxes.

If shipment notices and other email documents slow your team down, see how Ampwise connects your email and ERP and what it can take off your plate.

A practical rollout plan

You do not need to automate everything at once. A sensible order looks like this:

Inventory your ASN sources. List which suppliers send EDI and which send email, PDF or Excel. Rank the email senders by volume.
Define the required fields. Use the table above and add anything your warehouse needs, such as lot numbers.
Set validation rules. Decide what blocks posting (no open PO, quantity over PO) and what only warns.
Start with human approval. Review every record at first, then narrow review to exceptions as confidence grows. Our guide to automating email orders with human review uses the same approach.
Close the loop with suppliers. Send clear status messages when a notice is accepted or rejected. See status update emails from your ERP for what to send and when.
Review the metrics monthly and fix the top exception source first.

If you also exchange data with partners through APIs, running EDI at the partner boundary and APIs for real-time data shows how the channels fit together.

FAQ

What does ASN stand for in logistics?

ASN stands for advance shipping notice, sometimes written advance shipment notice. It is a message a shipper sends to a receiver before a delivery arrives, listing contents, quantities, packaging and carrier details so the receiver can plan and check the goods in quickly.

What is the EDI code for an ASN?

In the ANSI X12 standard, an ASN is the 856 Ship Notice/Manifest transaction set. Receivers typically answer with a 997 functional acknowledgment, and some also send an 824 application advice that describes errors in the notice.

Can an ASN be sent by email instead of EDI?

Yes, many suppliers send shipment details as an email, PDF or spreadsheet. The information is the same, but someone or something has to read it and enter it into your ERP. Some large customers do require EDI or their own portal, so check each receiver’s own requirements.

How do I get an ASN from an email into my ERP?

Capture the message, extract the shipment fields, validate them against the open purchase order, then approve and post. Tools like Ampwise automate the capture, extraction and validation steps and leave the approval to your team.

What happens if the ASN does not match the purchase order?

It should not be posted automatically. Microsoft’s warehouse documentation states that ASN data must match the PO it fulfills, so a mismatch goes to a person who can contact the supplier or purchasing to correct it.