Inventory Operations

Closing a Wholesale Transfer When the Manifest Count Does Not Match

DispensaryVA Editorial TeamPublished
Closing a Wholesale Transfer When the Manifest Count Does Not Match

A wholesale transfer can arrive with a manifest count that does not match the units on the receiving table. The gap may come from a short pick, a mislabeled case, a damaged unit, or a data entry error at the sender. Whatever the cause, the receiving team needs a sequence that protects the physical inventory, the traceability record, and the vendor relationship. Start by stopping the transfer from closing until the difference is described in plain language. A rushed close hides the one detail the next reviewer will need.

Count the physical units before opening the transfer

Assign two people to the count when staffing allows. One person counts sealed cases and the other counts open units, then both sign the tally sheet. Photograph the pallet, the manifest line, and any damaged packaging before anything moves to the sales floor. Do not edit the manifest during the first count, because the original record is the baseline for the correction. A second count from a different starting point catches most transcription errors.

Record the vendor name, the manifest number, the product, the package size, and the expected versus counted units. Write each difference as a separate line rather than a single total, since two opposite errors can cancel out in an aggregate. Keep the tally sheet with the transfer paperwork even if the correction is resolved the same day. A reviewer should be able to see which lines were short and which were over without opening the inventory system.

Classify the difference before changing any record

Separate a physical shortage from a record error. A shortage means the unit is not on the premises, while a record error means the unit is present but the manifest or package label is wrong. A damaged unit needs its own category because the product may still be saleable after inspection or may need destruction. The category determines who owns the next step and what evidence the file needs.

Use a short list of categories that the receiving team can apply without debate. Typical categories include short shipment, over shipment, mislabeled package, damaged in transit, and duplicate manifest line. Add a free-text note for anything that does not fit, but do not let the free-text note replace the category. Review the categories monthly so the list stays small enough to use at the door.

Document the adjustment in both systems

Enter the correction in the inventory platform with the manifest reference and a short reason. Use the same reason code in the receiving log so the two records can be joined later. If the platform requires a vendor credit before it accepts the adjustment, record the pending state rather than waiting to finish the file. A pending correction with a date is easier to audit than an untracked promise.

Do not overwrite the original received quantity. Add a correction line, a timestamp, and the name of the person who approved it. If the system only allows an edit, capture a screenshot of the before state and attach it to the transfer record. This is the same discipline described in the near-expiry markdown routine, where the original value must remain visible.

Coordinate with the vendor without promising a resolution

Send the vendor the manifest number, the affected lines, the count evidence, and the category. Ask for a credit, replacement, or corrected manifest, but do not promise the store will accept a specific remedy before the buyer reviews it. Put the request in writing even when the conversation happens by phone. A written summary prevents the next shift from reopening the same question.

Set a response window and name the person who will follow up. If the vendor does not respond in time, escalate to the buyer rather than quietly writing off the difference. A small unresolved line can become a recurring shrink item if no one owns it. The vendor sample intake routine shows how to keep a physical sample separate from the transfer record.

Close the transfer and leave a readable trail

Close the transfer only when the correction, the vendor request, and the physical disposition are recorded. Attach the tally sheet, photos, and the vendor reply to one folder or case number. Write a closing note that states what changed, who approved it, and what remains open. A closed transfer with an open question should be flagged as open, not marked complete.

The Virginia Cannabis Control Authority sets the licensed retail context in which these records are kept, though it does not prescribe a local correction form. Use the authority's current guidance as the outer boundary and the store's own procedure as the operating rule. Check the procedure when the inventory platform or the vendor portal changes. A record that cannot be read by the next receiver is not closed in practice.

Review the pattern at the end of the week

Count the correction lines by vendor, category, and receiving shift. A cluster of short shipments from one vendor may justify a different receiving window or a pre-delivery confirmation. A cluster of mislabeled packages may point to a vendor packaging problem rather than a counting problem. Share the pattern with the buyer and the receiving lead, not only with the person who entered the correction.

Choose one change for the next week and compare the correction rate before and after. Do not change the category list, the count method, and the vendor at the same time, because the result will not tell you which change worked. Keep the review short enough to happen every week. The goal is a receiving record that a new employee can follow without asking for the story behind it.

wholesale transfersmanifest reconciliationreceiving records