Template

Free receiving log template (Excel and Google Sheets), and when to outgrow it.

A receiving log is the first thing anyone asks for when something goes wrong: when did it come in, who signed for it, what shape was it in. Here is a template you can copy today, the reasons behind each column, and an honest list of when a spreadsheet stops being enough.

Published Nov 15, 2026 · Updated Nov 15, 2026

The template

Copy these columns into the first row of a new sheet, in this order. Every column is there because someone, at some point, will ask the question it answers. If a column never gets asked about in your warehouse, delete it: a shorter log that gets filled in beats a long one that doesn't.

Receiving log columns, with an example row
ColumnWhat goes in itExample
Date receivedThe day it came off the truck, not the day you entered it2026-11-12
TimeRoughly when the truck was unloaded10:40
Received byThe person who signed the delivery receiptJ. Ortiz
CarrierWho delivered itRegional LTL carrier
PRO / BOL numberThe carrier's tracking number from the paperworkPRO 0123456789
VendorWho shipped itLinden & Oak
PO numberThe purchase order it belongs to4471
CustomerWhose goods these are (the client, retailer or brand)Studio Avery
SidemarkThe customer's own reference, often the end client's nameMORRIS / LIVING
Pieces expectedFrom the BOL or packing list3
Pieces receivedWhat actually came off the truck3
CartonWhich carton of which pieceSofa, carton 2 of 3
ConditionPick from a fixed list (see below)Damaged: corner crushed
Noted on delivery receipt?Was the damage written on the carrier's paperwork before signingYes
PhotosTaken? Where are they stored?Yes, shared drive / 4471
LocationWhere it went in the warehouseRack B-12
NotesAnything that will matter laterPackaging kept for inspection
Customer toldDate the customer was told it arrived2026-11-12
OutDate delivered or picked up, and by whom2026-11-20, delivery

Setting it up in Excel or Google Sheets

  • Freeze the header row so the column names stay visible as the list grows (View > Freeze in both programs).
  • Use a dropdown for Condition. Data validation with a short fixed list, for example: Good, Damaged, Needs minor repair, Refused. Free text turns into twenty spellings of "damaged" within a month.
  • Use a dropdown for Customer too, from a second sheet with your customer list, so one customer doesn't appear under three names.
  • Format the date column as a date, not text, so you can sort and filter by it.
  • One row per carton, not one row per delivery. A three-box sofa is three rows with "carton 1 of 3", "2 of 3" and "3 of 3". That's the only way to say which box was damaged.
  • Never delete rows. When something leaves, fill in the Out column. The history is the point.

Rules that keep it honest

A template is easy. Keeping it filled in at four o'clock on a Friday is the hard part. These rules help:

  1. Fill it in at the dock, from the paperwork in your hand, not from memory at the end of the day.
  2. Count pieces before you sign the delivery receipt, and write any shortage or damage on the receipt itself.
  3. Photograph before anything goes on the rack. A photo taken after it's been moved proves less.
  4. Record the photo location in the log the same day, or the photos become a camera roll nobody can search.
  5. One person checks yesterday's rows each morning for blanks: missing condition, missing photos, missing location.

Photos are the weak spot

The log says a carton arrived damaged. The proof is the photo, and in a spreadsheet the photo lives somewhere else: on a phone, in a text thread, in a shared folder with a name like IMG_4471. When a customer asks three weeks later, someone has to find it, and the person who took it may be off that day.

If you stay on a spreadsheet, make a folder per PO or per customer, name the photos with the PO and carton number, and put the folder path in the Photos column. It's slower, but it means the answer exists. Our photo checklist covers which shots to take.

When to outgrow it

A spreadsheet is fine for a handful of deliveries a week, when the person receiving is the person answering the phone. These are the signs it's starting to cost you:

  • Customers ask for photos, and finding them takes longer than taking them did.
  • More than one person receives, and rows are missing or filled in differently.
  • You can't tell who changed a row, or when.
  • Customers call to ask whether something arrived, several times a day.
  • A carrier wants concealed damage reported within days, and the evidence is scattered. See our concealed damage guide.

When you see those signs, the next step is a receiving log built for the dock: photos stored on the carton they belong to, a fixed condition list, a record of who did what, and a login for each customer so they can check for themselves. That's what CartonLedger is. There's a free plan, no card is needed, and you can keep the spreadsheet running alongside until you're sure. See spreadsheets compared with a receiving log.

See how dock photos work →

Try it on your next delivery.

Free plan, no card. Photograph one real delivery and invite one customer.

14 days of Growth free · No card · Then the Free plan, never a locked screen