Everything that goes wrong later on a furniture project is cheaper to fix at the dock than anywhere else. The dock is the only point where the carton, the packing list, the vendor reference and a person who can look inside it are all in the same place at the same time.
Which makes receiving the highest-leverage process in project warehousing, and the one where a generic receiving screen does the most damage — because a screen that only accepts a quantity and a location silently discards everything else that was available in that moment.
This walks through what a furniture receipt should capture, why each field earns its place, and how to decide how deep to inspect.
What the receipt has to hold
Group the fields by the question they answer six weeks later.
Identity — "what is this, exactly?" Item and SKU, plus the barcode. Vendor cartons rarely carry your SKU, so an item alias or a scanned barcode is what stops two similar case goods being logged as the same piece. Lot and expiry exist for items configured to use them; most FF&E is not, and those fields should stay out of the way.
Quantity — "did we get what was promised?" Expected quantity and received quantity, per line. Not a total. The gap between the two per line is the shortage or overage, and it is only observable while the delivery is being counted. Reconstructed at month end, it is a guess.
Provenance — "where did this come from?" Supplier, purchase-order line, receipt reference, country of origin, landed cost. This is what a vendor dispute is argued from, and what an import-heavy program needs for customs and cost allocation.
Custody — "who touched it?" Assigned operators on the receipt. A half-finished container should be visible as somebody's open work, not as a receipt that is mysteriously still draft.
Location — "where is it now?" The target location, and separately the receiving or staging location where one is used. These are genuinely two different things, and the difference between "it is in the building" and "it is put away" is the first thing that goes wrong in a busy week.
Destination — "where is it going?" Project reference, project name, and per-line destination, room, floor, kit code and sequence number, plus a hold-for-install date. This is the group that generic receiving screens drop, and the group that decides whether the sort has to be done twice.
Standard receiving versus enhanced inspection
Not every carton deserves an open-box inspection. A repeat domestic vendor with a two-year clean record and a first-time overseas case goods shipment are not the same risk, and inspecting them identically means you are either wasting labour on one or under-inspecting the other.
Treat inspection depth as a setting, chosen per customer, project, vendor or shipment.
| Standard receiving | Enhanced inspection | |
|---|---|---|
| Reference check | Yes | Yes |
| Quantity against expected | Yes | Yes |
| Item identification | SKU or scanned barcode | SKU or scanned barcode |
| Condition | Visible carton condition, notes and photos | Ordered inspection steps, each assignable |
| Evidence | Attached to the inbound shipment | Attached per step, attributed to the operator |
| Exceptions | Raised when visibly wrong | Raised typed, and the step is blocked on mismatch |
| Segregation | Receive to target location | Quarantine location or held quantity until disposition |
| Close-out | Trigger putaway | Trigger putaway once inspection steps complete |
The right default is usually standard receiving with enhanced inspection triggered by a rule: first shipment from a new vendor, any container with visible external damage, anything for a high-visibility scope such as a presidential suite or a lobby, and anything from a vendor whose exception rate has drifted.
Concealed damage is the reason enhanced inspection exists
Visible damage is easy. A crushed corner on a carton gets noticed by anyone walking past.
Concealed damage is the expensive category: the carton is intact, the count is right, and the piece inside has a cracked veneer, a scratched top, or is missing the hardware pack that is supposed to be taped inside the drawer.
Three things follow from that:
- A visual dock check cannot find it, so a process that only does visual checks will find it at the site.
- Whether you look is a commercial decision, not a warehouse one — someone is paying for the labour either way, in inspection hours now or in remediation later.
- When you do look, the finding has to be recorded against the piece with photographs, not mentioned to a supervisor.
The practical middle ground most operators land on: sample-inspect by vendor and scope, inspect 100% of anything going into a high-visibility area, and inspect 100% of any vendor whose sample rate turns up problems.
Scanning is what makes the record trustworthy
Manual entry on a furniture receipt is uniquely error-prone, because the failure mode is not a typo. It is a plausible wrong answer.
Two nightstands from the same collection in the same finish family, one for the standard rooms and one for the suites, differing by a drawer pull. A receiver with 600 cartons to process and a vendor packing list that uses the vendor's own codes will get some of those wrong, and every one of them surfaces as "wrong item" at the site.
Barcode scanning does not fix a bad process, but it does close this specific gap: the item on the record is the item in the operator's hands, verified rather than transcribed. Where vendors label to their own scheme, item aliases let their code resolve to your item.
The handoff to putaway
Receiving is not finished when the count is entered. It is finished when the piece is in a known location and the exception record, if any, is closed or deliberately open.
A clean handoff looks like this:
- The received quantity is recorded against the line, with the destination fields populated or deliberately blank.
- Evidence — photographs, notes, counted units — is attached to the inbound shipment.
- Any exception has a typed record, evidence, and the affected quantity segregated.
- A putaway task is generated with a source and a destination location, not just a destination.
- The putaway is executed and confirmed, so the balance reflects where the piece actually is.
Step four is the one worth insisting on. A putaway task with only a destination cannot tell you whether the move happened; a task with both endpoints can, and that is the difference between an inventory record and an inventory intention.
See how the full receiving-to-release chain works on the FF&E and project logistics page.