Vendor Delivery Receiving
Vendor Delivery Receiving SOP for checking purchase orders, counts, packaging, temperatures, and lot or expiry data before product enters inventory. Use it to catch shorts, damage, and food-safety issues at the dock.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Food Service · Warehousing And Distribution · Manufacturing · Healthcare And Labs
Overview
Vendor Delivery Receiving is a standard operating procedure for checking inbound shipments before they enter inventory. It covers the dock-level actions that matter most: matching the delivery to the purchase order, counting cases or units, inspecting packaging and product condition, checking temperatures for controlled items, and recording lot and expiry information for traceability.
Use this template when your operation needs a repeatable way to catch shortages, overages, damage, spoilage, or labeling problems at the point of receipt. It is especially useful for food operations, warehouses, manufacturing sites, and any workflow where a bad delivery can create a quality issue, a stock discrepancy, or a safety risk. The SOP also gives the receiver a clear decision path for accept, reject, or hold, so exceptions are handled consistently instead of being resolved informally.
Do not use this template as a substitute for product-specific acceptance criteria. If a delivery requires specialized sampling, lab testing, quarantine, hazardous-material handling, or a permit-to-work process, those controls need to be added separately. It is also not the right fit for blind receiving where counts cannot be verified, or for emergency intake where a supervisor must override normal checks. The template is designed to document what was received, what was verified, and what action was taken when the delivery did not match expectations.
Standards & compliance context
- The template supports ISO 9001-style documented information by recording what was received, what was verified, and what action was taken.
- For food operations, the receiving checks align with HACCP and GMP expectations for temperature control, traceability, and non-conformance handling.
- If the delivery includes hazardous materials or controlled procedures, add OSHA-oriented PPE, hazard communication, and permit-to-work requirements before acceptance.
- Lot and expiry capture supports traceability practices commonly expected in regulated supply chains and recall readiness.
- Acceptance, rejection, and hold decisions should be documented so the receiving record can support audits, vendor claims, and internal investigations.
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
-
The receiver prepares the receiving area
The receiver clears the inspection area, confirms the delivery can be safely accessed, and opens the receiving log or mobile app before the shipment is unloaded.
-
The receiver verifies the delivery against the purchase order
The receiver compares the vendor name, delivery date, item descriptions, and ordered quantities against the purchase order and packing slip. The receiver identifies any obvious mismatch before signing for the shipment.
-
The receiver counts each item and records shortages or overages
The receiver counts cases, cartons, and loose units for each line item and records the actual quantity received. The receiver notes any short shipment, overage, or partial delivery on the receiving record.
-
The receiver inspects product condition and packaging
The receiver checks cartons, cases, pallets, and individual packages for damage, contamination, leaks, broken seals, pest evidence, or signs of tampering. The receiver photographs any damage and records a clear description of the issue.
-
The receiver checks product temperatures for controlled items
The receiver measures the temperature of refrigerated, frozen, and other controlled items using the approved thermometer method. The receiver compares each reading to the site acceptance tolerance and records the result.
-
The receiver verifies lot and expiry information
The receiver confirms lot numbers, batch codes, use-by dates, and expiry dates on the product labels when required by the item specification or site policy. The receiver records any missing, illegible, or unacceptable date information.
-
The receiver decides whether to accept, reject, or hold the delivery
The receiver determines whether the shipment can be accepted in full, accepted with exceptions, placed on hold, or rejected according to site policy and product risk.
-
The receiver signs and releases accepted product to inventory
The receiver signs the packing slip or completes the electronic receipt, then releases accepted product to the designated storage area for put-away.
-
The receiver escalates non-conformances and isolates affected product
The receiver tags affected product as hold or reject, segregates it from usable inventory, and notifies the supervisor, quality lead, or vendor contact according to escalation criteria. The receiver documents the issue, including quantity affected, reason, photos, and any vendor response.
-
The receiver completes the receiving record
The receiver confirms the receiving record includes the date, vendor, purchase order number, quantities received, exceptions, temperature readings, lot/expiry details, and final disposition. The receiver retains the record per document control requirements.
How to use this template
- 1. The receiver prepares the receiving area by clearing space, gathering the purchase order, and confirming the required tools, PPE, and temperature devices are available.
- 2. The receiver verifies the delivery against the purchase order by matching vendor name, item descriptions, quantities, and any special receiving instructions.
- 3. The receiver counts each item and records shortages or overages, then documents any variance before the product is moved from the dock.
- 4. The receiver inspects product condition and packaging for damage, contamination, seal issues, or other visible non-conformance.
- 5. The receiver checks controlled-item temperatures, verifies lot and expiry information, and makes an accept, reject, or hold decision based on the findings.
- 6. The receiver signs the receiving record, escalates exceptions to the appropriate role, and releases only accepted product to inventory.
Best practices
- Verify the shipment before breaking down pallets so shortages, overages, and seal issues are still traceable to the original load.
- Record the exact variance, not just 'short' or 'damaged,' so the buyer or vendor can reconcile the issue without a second visit.
- Use a calibrated thermometer for controlled items and document the reading at the time of receipt, not after the product has been staged.
- Photograph damaged packaging, broken seals, and visible contamination before the product is moved or repacked.
- Require a clear hold path for any delivery with missing lot codes, unreadable expiry dates, or temperature excursions.
- Separate accepted product from rejected or held product immediately to prevent accidental release into inventory.
- Escalate repeated vendor discrepancies to purchasing or quality so the same receiving problem is not accepted as normal.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What deliveries does this SOP cover?
This SOP covers vendor deliveries that must be checked at receiving before they are put into stock. It works for dry goods, refrigerated items, frozen product, and packaged materials where counts, condition, and traceability matter. If your site receives regulated food, chemicals, or controlled materials, the same structure still applies with tighter verification and escalation rules.
How often should vendor delivery receiving be used?
Use it for every inbound delivery, not just when something looks wrong. The value of the template is in making dock checks consistent across shifts, vendors, and product types. If your operation has high-volume receiving, you can keep the same SOP and add a shorter checklist version for routine loads.
Who should run the receiving process?
A trained receiver, warehouse associate, or dock lead usually runs the process, with a supervisor or competent person handling exceptions. For temperature-sensitive or regulated goods, the person verifying acceptance should be authorized to place product on hold or reject it. The template makes the role and escalation path explicit so the dock does not become a judgment call.
Does this template support food safety or other regulatory checks?
Yes. It is structured to support traceability, condition checks, temperature verification, and documented acceptance or rejection, which are common expectations in food safety and quality systems. You can adapt the same workflow to align with HACCP, ServSafe-style controls, GMP practices, or ISO 9001 documented information requirements. If your site handles hazardous materials, add permit-to-work, PPE, and hazard communication steps.
What are the most common mistakes this SOP helps prevent?
The most common failures are skipping the count, accepting damaged packaging, missing a temperature excursion, and failing to record lot or expiry information. Another frequent issue is releasing product to inventory before a discrepancy is resolved. This template forces a clear accept, reject, or hold decision so exceptions do not disappear into the warehouse.
Can I customize this for different vendors or product categories?
Yes. You can add vendor-specific tolerances, product-specific temperature ranges, and special acceptance rules for high-risk items. Many teams also add fields for seal numbers, pallet counts, photos, and carrier notes. The core flow should stay the same so receivers do not have to relearn the process for every supplier.
How does this compare with ad hoc receiving checks?
Ad hoc receiving depends on memory and whoever happens to be on the dock, which makes shortages and quality issues easy to miss. A formal SOP creates repeatable verification, documented exceptions, and a clear escalation path. That matters when you need traceability for audits, vendor disputes, or inventory accuracy.
Can this template connect to inventory or ERP workflows?
Yes. The acceptance step can trigger inventory receipt, while rejected or held product can trigger a non-conformance record, supplier claim, or quality hold in your system. You can also link the SOP to PO records, barcode scans, temperature logs, and photo attachments. The template works well when the receiving record is the source of truth for downstream inventory actions.
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...
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
Discover the 5 integrations your enterprise intranet needs — from HRIS and SSO to document management and CRM — to drive adoption and reduce tool sprawl.
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
-
Frontline managers lose 40–60% of their day to coordination overhead. See what drives the Manager Tax, what it costs in engagement, and how to fix it.
Ready to use this template?
Get started with MangoApps and use Vendor Delivery Receiving with your team — pricing built for small business.
