Warehouse Receiving Best Practices for Small Teams
October 2, 2026
Receiving is the first time your system meets the stock. Every count, lot, and location you record at the dock is the starting point for everything after it: production, cycle counts, shipping, and any trace you might need to run. If the receipt is wrong, every later record inherits the mistake.
Small teams feel this more than large ones. The person unloading the truck is often the same person who puts stock away and answers the phone. That makes a simple, repeatable receiving routine more valuable, not less. This guide walks through the habits that keep inbound stock accurate without adding a lot of steps.
Prepare before the truck arrives
Good receiving starts before anything reaches the dock. Someone in planning should create a receiving order for each expected delivery. It lists the customer, the supplier, the expected delivery date, and each SKU with the quantity you expect. In a customer portal, the same record is often called an ASN, short for Advanced Shipping Notice.
A receiving order gives the dock crew a checklist instead of a guess. They know what is coming, roughly when, and how much. They can clear floor space, line up the right labels, and flag anything unusual before the driver leaves.
A few things to settle when you set up each receiving order:
- Use the exact SKU, not a description someone has to interpret at the dock.
- Enter the expected quantity in the unit you will count in: cases, bags, or each.
- Add notes for anything special, such as a cold item or a new supplier.
- Link the work order number if the material is for a specific production run.
Check quantities against what was expected
When the delivery arrives, count it against the receiving order line by line. Do not just sign the driver’s paperwork and sort it out later. Once a pallet is broken down and spread across the building, a short shipment is very hard to prove.
Record the actual quantity next to the expected quantity for every line. A difference is not automatically a problem. Suppliers ship partials, round to full cases, or split a delivery across two trucks. What matters is that the difference is written down at the moment you find it, by the person who counted.
Some habits that make counts more reliable:
- Count the physical units before you look at the expected number, so the number does not bias the count.
- Count by SKU and lot, not by pallet, because one pallet can hold more than one lot.
- Have a second person recount any line with a large difference before you record it.
- Note short, over, and damaged quantities separately, because each one leads to a different follow-up.
In Swift WMS, receiving orders are part of the Core plan (and an add-on on Essentials). You bulk receive against a receiving order with the expected and actual quantity side by side for each line, so a difference is visible right away instead of at month end. If your customers use the customer portal, they can create ASNs for you, so the expected list arrives before the stock does.
Capture lot and expiration at the dock
If you make food, supplements, or cosmetics, the lot number and expiration date are as important as the quantity. They are the link between a supplier’s batch and every finished good you make from it. If you skip them at receiving, you will spend hours later trying to work out which lot went where. Our page on lot tracking for food manufacturers shows how Swift WMS keeps the lot and date on every pallet.
Capture the supplier’s lot number exactly as printed on the case. Do not shorten it, reformat it, or swap in your own code unless you also keep the original. Record the expiration or best-by date at the same time. If a delivery holds two lots of the same SKU, receive them as two separate lines.
This is also the right moment to collect paperwork. If the supplier sends a certificate of analysis, attach it to the lot as you receive it. Our guide to managing certificates of analysis covers what to check on a COA and where to keep it.
In Swift WMS, lot name and expiration date are required when you receive an ingredient SKU, so the dock crew cannot skip them. COA files and notes can be attached at receipt. There is also an option to place new ingredient lots on hold automatically. A held lot cannot ship, and with lot holds turned on it cannot be used in production either, until quality releases it. That record of lots is what powers lot traceability later.
Label each plate before it moves
The safest rule in receiving is simple: nothing leaves the dock without a label. Once an unlabeled pallet is put away, it becomes a mystery. Someone has to remember what it is, and memory is not a system.
Most warehouses handle this with a license plate. A license plate is a unique ID for one unit of stock, usually a pallet or a case, printed as a barcode. It ties that physical unit to its SKU, lot, quantity, and location. Our article on what a license plate number (LPN) is explains the idea in more detail.
Print and apply the plate label while the stock is still at the dock. Put it where it can be scanned without moving other pallets, ideally on two sides. When stock is later moved, split, or used in production, the scan of that label is what keeps the record accurate.
Receiving in Swift WMS creates license plates with automatically assigned IDs. After a bulk receive, you can print all labels at once and apply them before anything is put away. You can read more about how plates work on the license plate inventory page.
Choose the first location on purpose
Every plate needs a location from the moment it exists. Leaving stock in a vague “receiving area” for days is how inventory goes missing. If the stock cannot go to its final spot yet, give it a real staging location with a real name, and record it there.
When you choose the first location, think about how the stock will be used. Ingredients for a production run next week can go near staging. Slow-moving reserve stock can go higher or further back. Items that carry allergens may need to stay apart from others. Whatever the choice, the person putting the stock away should scan the location label so the record matches the shelf.
Location names matter a great deal here. If two spots look alike or the labels are hard to read, putaway errors follow. Our guide to setting up a warehouse location naming system covers how to name and label locations so they are easy to scan and find.
In Swift WMS, the location is chosen or scanned at receipt, and the plate can be moved later as needed. On Floor Mode, the large-text screen built for scanners, the receive flow ends with scanning the location, so the crew sets it in the same motion as the rest of the receipt.
Handle unplanned items and damage
Not every delivery matches the plan. A supplier adds an item you did not expect, sends a substitute, or ships a case that arrives crushed. The goal is to record what really came in, not what you hoped would come in.
For unplanned items, add them as new lines on the receipt rather than forcing them onto an existing line. Then flag them for someone in planning to review. They may be a supplier error to return, or a real order that was never entered.
For damage, take a photo before anything is moved and attach it to the record. Decide on the spot whether the damaged units go into stock, onto hold, or back to the supplier. Some practical rules:
- Never mix damaged units into a good plate. Receive them on their own plate so they can be held or adjusted alone.
- Hold the lot if you are not sure whether the product is still usable, and let quality decide.
- Write a clear reason on any quantity adjustment, so the next person understands why the number changed.
- Tell the supplier the same day, while the evidence is fresh.
Swift WMS lets you add unplanned items to a receiving order during a bulk receive. Plates can be held and released by lot, and any quantity adjustment requires a reason, so the history explains itself later.
Close out the receipt
A receipt is not finished when the truck leaves. It is finished when the record is complete and someone has confirmed it. Leaving receiving orders open for weeks makes it hard to tell what is still expected and what is done.
Before you close a receipt, check that every line has an actual quantity, every lot has a name and date, and every plate has a label and a location. Review any line that came in short or over and decide what happens next: wait for a backorder, contact the supplier, or accept the difference. Then mark the receiving order completed.
A clean close-out also makes counting easier later. If receipts are complete and accurate, your cycle counts start from a true baseline. Our comparison of cycle counting vs physical inventory explains how regular counts keep that accuracy over time.
The short version for small teams
You do not need a large team to receive well. You need a routine that everyone follows the same way, every time. Here is the checklist to post at your dock:
- Create a receiving order with exact SKUs and expected quantities before the delivery.
- Count each line and record the actual quantity next to the expected one.
- Capture the lot number and expiration date for every lot, exactly as printed.
- Label every plate before it leaves the dock.
- Scan a real location for every plate, even if it is a temporary staging spot.
- Add unplanned items as new lines and keep damaged units on their own plate.
- Close the receiving order only when every line is complete.
If you want to see how this works on a scanner, contact our team. You can ask about a 30-day trial set up by our team, and nothing is charged until the trial ends.
