Vendor and DSD Shrink Audit

It covers the full receiving walk-through for direct-store-delivery and vendor drop-offs: check-in, document review, count reconciliation, scan accuracy, dock safety, and closeout. The template is built to identify short shipments, overages, substitutions, unscanned items, and repeated vendor-side discrepancies. It also captures the follow-up needed for credits, claims, and corrective actions.

Use it at the time of delivery, before the vendor leaves the dock, so discrepancies can be verified against the shipment and documented immediately. It is especially useful for high-shrink categories, frequent DSD routes, and stores that receive from multiple vendors in a day. It is not a back-office inventory count template and should not replace cycle counts or full physical inventories.

A receiving associate, department lead, or manager can run it, as long as they are trained on receiving records and discrepancy documentation. The person completing the audit should be the same person, or a clearly assigned owner, who can confirm counts, review the bill of lading, and escalate claims. For repeated issues, a manager should review the pattern and approve corrective actions.

Use it for every vendor or DSD delivery where shrink risk is tied to receiving accuracy, especially for high-value, high-turn, or regulated items. Some teams use it on all deliveries, while others apply it to selected vendors with a history of shortages or scan errors. If a vendor has recurring discrepancies, the audit should be used until the issue is resolved and the pattern stops.

Yes, it supports documented receiving controls that align with general industry safety expectations, food receiving practices, and internal loss-prevention procedures. If hazardous materials or regulated products are received, the audit can also capture handling and labeling checks tied to applicable safety rules and site procedures. It is a documentation tool, not a legal determination, so local policy and applicable standards still govern the final process.

The biggest mistake is counting after the vendor has already left, which makes it harder to resolve shortages or overages. Another common issue is recording a variance without tying it to a SKU, quantity, and reason code, which weakens follow-up. Teams also miss repeated patterns because they close each delivery as a one-off instead of tracking vendor-side discrepancy trends.

Yes, it can be tailored for grocery, convenience, warehouse-style receiving, or multi-department stores by adding vendor-specific fields, product categories, or approval steps. You can also add reason codes, photo fields, claim references, or route identifiers if your operation needs more detail. The core structure should stay focused on receiving accuracy, discrepancy documentation, and corrective action.

Ad hoc notes often miss key details like invoice matching, scan status, and who acknowledged the discrepancy. This template creates a consistent record that is easier to review, audit, and use for credits or claims. It also helps managers spot repeat vendor issues instead of relying on memory or scattered emails.