When operations managers start reviewing their documentation processes, two terms come up quickly: goods received note and photo documentation. They sound like they might overlap. Some teams treat them as alternatives. They're not — and the confusion about how they relate to each other is where a surprising amount of liability risk lives.
This article explains what each one is, what it can and can't do, and why having both — in a form that's actually usable — is the baseline for a defensible warehouse operation.
A goods received note (GRN) is a document generated when goods are received into a warehouse or facility. It records the key facts of the inbound event: what was delivered, in what quantity, when, and by whom. In most WMS or ERP systems, the GRN triggers downstream processes — updating stock levels, matching against purchase orders, initiating payment processes for verified deliveries.
The GRN is fundamentally a record of what happened administratively. It answers: did the delivery occur, and did the quantity match the order?
What it doesn't answer — and was never designed to answer — is: what condition were the goods in when they arrived?
Photo documentation is a visual record of the physical condition of goods at specific points in the handling process — typically at inbound receiving, at outbound dispatch, and at any point where damage or discrepancy is identified.
Where a GRN captures administrative facts, photo documentation captures physical reality. It answers: what did the goods, packaging, and pallets actually look like at the moment of handover?
This distinction matters because it's the physical reality — not the administrative record — that determines liability in a dispute. A GRN can confirm that 20 pallets were received. It cannot tell you whether pallet 14 arrived with a crushed corner and a compromised seal.
The gap between what a GRN records and what photo documentation records is exactly the space where liability disputes live.
Consider the sequence: goods arrive, a GRN is created confirming receipt of the correct quantity, and delivery is signed off. Three weeks later, a customer reports that items from that delivery are damaged. The question becomes: when did the damage occur?
The GRN shows that the delivery happened. It says nothing about condition. If there is no photo documentation from the inbound event, the warehouse is the last handler with any record at all — and in most legal and commercial dispute frameworks, that defaults to liability.
Photo documentation taken at receiving — before goods are handled, showing pallet condition, packaging integrity, and any visible damage — would answer the condition question directly. With it, the same dispute resolves in hours. Without it, it drags for weeks and often resolves against the warehouse.
The most operationally sound approach treats GRN and photo documentation as complementary layers of the same receiving event — not alternatives to choose between.
The GRN provides the administrative scaffold: what was received, when, and in what quantity. Photo documentation provides the physical evidence: what it looked like. Together, they create a complete record that answers both the administrative and the liability questions.
In practice, this means photo documentation should be triggered at the same point the GRN is created. When a delivery is being received and the GRN is being generated in the WMS, photos should be taken and linked to that same reference. The two records are then permanently connected — the administrative event and the visual evidence of what that event actually looked like.
Tools like Blimp enable this by linking photos to shipment or delivery references through barcode scanning — so that every photo taken during a receiving event is automatically associated with the correct GRN reference without any manual step.
The GRN is the right document for:
Photo documentation is the right evidence for:
Neither replaces the other. The GRN without photos leaves the condition question unanswered. Photos without a GRN reference are unanchored — they're images without provenance.
For more on how inbound documentation connects to outbound quality control, see Closing the loop: IQC and OQC.
A GRN alone provides limited protection in a damage claim because it typically records quantity but not condition. Unless the GRN explicitly notes damage or discrepancy at the point of receipt, it doesn't establish whether goods arrived damaged. Photo documentation taken at the point of receipt is what establishes condition and therefore determines liability.
Yes, and this is the recommended approach. Using the GRN reference number — or the associated PO or delivery note number — as the reference when capturing photos creates a permanent link between the administrative record and the visual evidence. Purpose-built tools like Blimp do this automatically through barcode scanning.
In most jurisdictions, photo documentation isn't legally mandated, but it's becoming a de facto requirement in commercial contracts, insurance policies, and quality certification frameworks. More practically, without photo documentation, winning a liability dispute against a supplier or carrier is extremely difficult — making it a commercial necessity even when it's not a legal one.
As a baseline: exterior of the trailer or container before unloading, overall load condition before handling, any visible damage in situ (photographed before goods are moved), and label/identifier shots for any items with discrepancies. This typically takes two to three minutes per delivery and provides meaningful protection for the vast majority of dispute scenarios.
The GRN tells you the delivery happened. Photo documentation tells you what the delivery looked like. Both are necessary. Neither is sufficient on its own.
Warehouses that treat them as redundant — or assume the GRN provides protection it was never designed to offer — are leaving a liability gap that will eventually cost them. The ones that treat them as complementary layers of a single receiving event are the ones who resolve disputes quickly and recover costs from the correct parties.
Setting up photo documentation that links automatically to your GRN process isn't a large project. It's a workflow change that takes days to implement and months to pay back.
To see how it works in practice, try Blimp free — no setup costs, no personal logins required.
Blimp lets you easily capture, organise and share photo documentation and professional photo reports. Available on mobile and web, Blimp simplifies reporting, reduces manual work and streamlines claims handling across industries.
Contact us
