ASN and EDI Inbound Receiving SOP
ASN and EDI Inbound Receiving SOP template for matching scheduled deliveries to the ASN, scanning pallets, verifying quantities, and handling variances before putaway.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Warehousing And Distribution · Retail And Wholesale Logistics · Manufacturing · Third Party Logistics
Overview
This ASN and EDI Inbound Receiving SOP template documents the dock-to-putaway process for shipments that arrive with an Advance Shipping Notice. It is built for teams that need to confirm the appointment, inspect the trailer and seal, open the ASN in the receiving system, scan each pallet, verify line quantities, and decide what to do when the physical freight does not match the expected receipt.
Use this template when your warehouse relies on EDI or ASN data to receive inventory accurately, post receipts in the WMS or ERP, and release freight to putaway without rework. It is especially useful where multiple roles touch the receipt, such as a receiver, supervisor, inventory control, or quality representative, because it makes the handoff and escalation path explicit.
Do not use this as a generic unloading checklist. If your inbound flow is ad hoc, unplanned, or not tied to an ASN, you will need a different receiving procedure. It is also not the right fit for situations where the shipment must stay in quarantine, requires laboratory sampling, or is governed by a separate hazardous materials or permit-to-work process. In those cases, this SOP should be paired with the site-specific control procedure rather than used alone.
Standards & compliance context
- The template supports ISO 9001 documented information practices by creating a repeatable, reviewable record of receipt verification and exception handling.
- If the inbound freight includes regulated or hazardous materials, pair this SOP with the applicable OSHA process controls, permit-to-work rules, and site hazard communication requirements.
- The inspection and damage documentation steps can be aligned with ANSI Z535.6-style hazard communication practices when warning labels, symbols, or safety notices are involved.
- For food, pharmaceutical, or other controlled goods, the same structure can support GMP, HACCP, or customer quality requirements by adding the required hold and release checks.
- If your operation uses ITIL-style service or warehouse support workflows, this SOP can serve as the operational runbook for receipt exceptions and system posting issues.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns dock receiving into a controlled sequence with clear ownership, verification, and escalation points.
-
Confirm the inbound shipment matches the receiving appointment
The receiver verifies the appointment number, carrier name, trailer number, purchase order or shipment reference, and expected arrival time against the ASN and dock schedule. The receiver stops the process and escalates any mismatch before unloading.
-
Inspect the trailer and seal condition
The receiver verifies the trailer seal number, seal integrity, trailer condition, and visible damage before breaking the seal. The receiver documents any broken seal, missing seal, water intrusion, odor, or visible freight damage and escalates the issue to the supervisor or carrier representative.
-
Open the ASN in the receiving system
The receiver searches for the ASN using the shipment reference, PO number, or carrier reference. The receiver confirms the supplier name, item list, expected quantities, and any special receiving instructions before starting pallet scans.
-
Scan each pallet to the ASN
The receiver scans the pallet label, license plate, or SSCC code for each pallet and assigns it to the open ASN. The receiver verifies that the scanned pallet count matches the physical pallet count unloaded from the trailer. The receiver flags any unreadable label, duplicate label, or missing pallet ID as a deviation.
-
Verify line quantities against the ASN
The receiver compares the received quantity for each item or pallet against the ASN line quantity. The receiver records the actual quantity received, confirms unit of measure, and checks for shortages, overages, substitutions, or mixed pallets. The receiver does not close the receipt until all line variances are reviewed.
-
Inspect freight condition and identify non-conformance
The receiver inspects cartons, pallets, labels, and product condition for damage, contamination, wetness, crushed packaging, or tampering. The receiver captures photos when required, records the affected line items, and marks the shipment or line as non-conforming when the issue affects product integrity or count accuracy.
-
Escalate variances beyond tolerance
The receiver compares shortages, overages, damages, and label issues against the site tolerance and receiving rules. If the variance is within tolerance, the receiver documents it and continues. If the variance exceeds tolerance or affects product quality, the receiver holds the freight and escalates to inventory control, quality, or the supervisor.
-
Complete the receipt and release freight to putaway
The receiver posts the verified quantities in the system, closes the ASN receipt, and releases the accepted freight to the putaway queue. The receiver ensures the receipt record includes any approved variance notes before the freight moves to storage.
-
Hold the affected freight and create a non-conformance record
The receiver tags the affected pallets or cartons, moves them to the designated hold area, and creates a non-conformance or discrepancy record. The receiver includes the ASN number, PO number, item number, quantity variance, damage details, and photos if available. The receiver notifies the supervisor, inventory control, or quality team for disposition.
-
File receiving records and close the transaction
The receiver saves the ASN receipt, variance notes, photos, and supporting paperwork in the approved system or document repository. The receiver confirms the record is retained according to site document control requirements and ISO 9001 documented information practices.
How to use this template
- 1. The warehouse manager configures the template with the site’s receiving appointment rules, ASN fields, tolerance thresholds, escalation contacts, and system names.
- 2. The receiving lead assigns a competent person to perform the dock checks, pallet scans, quantity verification, and exception logging for each inbound shipment.
- 3. The receiver follows the steps in order, confirming the appointment, inspecting the trailer and seal, opening the ASN, and scanning each pallet against the expected receipt.
- 4. The receiver records any deviation, damage, or non-conformance immediately and escalates shipments that exceed tolerance before the receipt is completed.
- 5. The supervisor reviews unresolved variances, approves the final receipt decision when required, and releases only verified freight to putaway.
Best practices
- Confirm the appointment before touching the freight so the team does not receive the wrong load against the wrong ASN.
- Treat seal damage, seal mismatch, or missing seal information as a verification failure that requires escalation before unloading continues.
- Scan each pallet to the ASN one at a time and resolve mismatches immediately instead of waiting until the end of the trailer.
- Set a clear quantity tolerance in the SOP so receivers know when a shortage, overage, or mixed pallet becomes a deviation.
- Photograph visible freight damage at the dock and attach the images to the receipt record before the trailer is released.
- Use the same terminology for non-conformance, variance, and escalation across receiving, inventory control, and customer service.
- Release freight to putaway only after the receipt is complete and any open exception has an assigned owner.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this ASN and EDI inbound receiving SOP cover?
This template covers the full receiving flow from appointment match and trailer inspection through ASN lookup, pallet scanning, quantity verification, damage review, variance escalation, and receipt release to putaway. It is designed for inbound warehouse receiving where the shipment is expected to arrive against an Advance Shipping Notice sent by EDI. It does not replace your warehouse management system logic, but it gives the team a controlled, repeatable process for what to do at the dock.
Who should run this SOP at the dock?
The receiving clerk, dock associate, or warehouse operator typically runs the procedure, with a supervisor or inventory control role handling exceptions. A competent person should review seal issues, freight damage, and any quantity variance that exceeds tolerance. If your site handles regulated or hazardous goods, the escalation role should be defined before rollout.
How often should this SOP be used?
Use it for every inbound shipment that is received against an ASN, especially when the site depends on EDI accuracy for inventory posting and putaway. It is most useful for daily operations because it standardizes the dock check, scan, and verification sequence. If you receive mixed freight or partial shipments, the same SOP can be used with a defined exception path.
What happens if the pallet count or line quantity does not match the ASN?
The SOP should require the receiver to stop at the point of deviation, document the mismatch, and escalate according to the site tolerance rules. Minor variances may be held for review, while larger discrepancies should trigger a non-conformance record and supervisor approval before receipt completion. This prevents accidental over-receipt, short-receipt, or inventory posting errors.
How does this relate to ISO 9001 or other quality requirements?
The template supports ISO 9001-style documented information by making the receiving process consistent, traceable, and reviewable. It also helps create an auditable record of verification, deviation handling, and release decisions. If your operation follows GMP, HACCP, or customer-specific quality rules, you can add the required checks and approvals without changing the core receiving flow.
What are the most common mistakes when using an ASN receiving SOP?
Common mistakes include scanning pallets before confirming the appointment, skipping seal inspection, accepting damaged freight without documenting the non-conformance, and closing the receipt before quantity verification is complete. Another frequent issue is using vague tolerance rules, which leads to inconsistent escalation decisions. The template helps reduce those errors by assigning each step to a role and making verification explicit.
Can this SOP be customized for different warehouse systems or EDI setups?
Yes. You can adapt the system names, scan fields, tolerance thresholds, and escalation contacts to match your WMS, ERP, or EDI workflow. The structure also works if your ASN arrives through a portal instead of direct EDI, as long as the receiver can compare the physical shipment to the expected receipt record. Keep the verification and exception steps intact even if the software changes.
How should this SOP be rolled out to the receiving team?
Start by aligning the dock, inventory, and supervisor roles on the same definitions for match, variance, damage, and release. Then train the team on the step sequence and the exact escalation trigger for exceptions, using a few live or shadowed receipts before full adoption. A short review after the first week usually reveals where the form needs clearer fields or tighter tolerance language.
Is this better than ad-hoc receiving notes or a checklist?
Yes, when you need traceability and consistent exception handling. Ad-hoc notes often miss the link between the ASN, the physical freight, and the final receipt decision, which creates inventory and claims problems later. This SOP gives you a repeatable process with verification points, escalation criteria, and a clear handoff to putaway.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
Learn how organizations with hourly workers, union contracts, and shift differentials can apply compensation rules consistently and accurately at scale.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Learn how task management and real-time collaboration tools create an efficient business workflow — keeping teams connected, accountable, and productive.
-
Spring '26 brings AI course creation, Power BI agent queries, LMS automation, Google Workspace integration, and enterprise survey tools to MangoApps.
Ready to use this template?
Get started with MangoApps and use ASN and EDI Inbound Receiving SOP with your team — pricing built for small business.
