The gap between "the vendor dispatched it" and "the right material is on site, in good condition, in the right quantity" is where a surprising amount of a project's stress lives. Deliveries slip, a crate arrives with two tiles cracked, the carpenter's ply comes 5 sheets short, and nobody notices until the installer is standing there with nothing to install. This is for studios that want deliveries to stop being a series of small emergencies, so let me lay out how I track material coming to site so the surprises land while you can still do something about them.
Why "it's been dispatched" is not the same as "it's here and correct"
Vendors love the word dispatched, because it moves the problem off their desk and onto yours. But a dispatch is a promise, not a delivery, and between the two sit a dozen things that can go wrong: the truck is delayed, the wrong batch got loaded, half the order shipped and half is "coming next week", or the goods arrive fine but the site isn't ready to receive them and they sit in a corridor collecting damage.
The studios that run smoothly treat delivery as an event they actively manage, not a notification they passively receive. That means knowing what's expected, when, against which purchase order, and having someone accountable for checking it the moment it lands. If your purchase orders aren't clean to begin with, this all gets harder, which is why I'd start with purchase order best practices for studios, because you can only verify a delivery against a PO that actually specifies what you ordered.
Check every delivery against the order, not against your memory
When material arrives, the person receiving it should be checking against a document, never against a vague sense of what was supposed to come. That document is your purchase order, and ideally it traces back to the bill of quantities the whole project was costed from, so the quantities you're verifying are the same numbers your quote was built on.
The check itself is quick when it's structured. Count the units against the PO quantity, confirm the spec matches (the right finish, the right size, the right model, not a "similar" substitute the vendor slipped in), and inspect for damage before you sign anything. The signature is the leverage point here, because once you've signed the delivery note, disputing a shortage or a crack gets much harder. A two-minute inspection before you sign is worth an hour of arguing after.
What to verify before you sign the delivery note
- Unit count matches the PO quantity, no shortages
- Spec and finish match the approved item, no silent substitutions
- No visible damage, cracks, dents or water marks on the packaging or goods
- Batch or shade is consistent across boxes for tiles, stone and laminate
- Partial delivery is clearly noted as partial, with the balance quantity recorded
- The delivery note references the correct PO number
Record the shortfalls and damage as a snag the moment they land
When something is wrong, write it down immediately and specifically, because "some tiles were broken" is useless three weeks later and "6 of 60 tiles from batch 4 cracked, photographed, reported to vendor same day" is a claim you can win. This is effectively a punch list for incoming goods, a running note of what wasn't right on arrival, tied to the delivery and the vendor.
Photograph the damage on the spot, log the shortage against the PO, and flag it to the vendor the same day. The reason this matters beyond the immediate claim is that these small shortfalls are exactly what derail your project timeline: the installer arrives, the material is 5 sheets short, the day is lost, and the client sees a delay that was actually a delivery you didn't verify hard enough. Catch it at the door and you can chase the balance before it becomes a stalled site.
The delivery calendar is really a timeline problem
A single delivery is easy to track in your head. Fifteen deliveries across three projects, each with its own lead time and install date, is not, and that's where a spreadsheet quietly falls apart, because it can't tell you what's late until you go looking. I've made the fuller argument in why Excel is quietly costing you margin, and delivery tracking is a clean example: a static sheet doesn't chase anyone, it just sits there being out of date.
What you actually want is every expected delivery sitting on the same timeline as the site work that depends on it, so a slipped delivery visibly pushes the install that was waiting on it. Here's the difference in practice.
| Approach | What you see | What it misses |
|---|---|---|
| WhatsApp + memory | The last message from the vendor | Everything you didn't ask about |
| Standalone spreadsheet | A list, if someone updated it | What's late, until you check manually |
| One connected timeline | Deliveries against the install dates they feed | Nothing, the dependency is visible |
Keep the client informed without the panic calls
Clients don't actually mind that a marble slab is delayed by a week. What they mind is finding out about it on the day it was supposed to install, from a flustered call, with no plan. Delivery tracking is quietly a client-trust tool, because when you can see a slip coming, you can tell the client early, calmly, with a revised date, and that's the difference between "my designer is on top of it" and "my designer is winging it".
The cleanest way to do this is to let the client see approved milestones and status in their own portal rather than pinging them ad hoc, which I covered in how to get faster client approvals with a client portal. The same portal that carries their design approvals can carry the reassurance that the furniture, fixtures and equipment they signed off on is tracked to their door.
Where delivery tracking should actually live
By now the pattern is obvious: delivery tracking isn't a standalone task, it's the last leg of procurement, and it only works when it sits next to the PO it verifies, the vendor you're chasing, and the site timeline it feeds. That's the case for keeping it in one connected system rather than scattered across a chat thread, a sheet and someone's memory. If you're still comparing tools for this, the best software for interior designers in India guide is the broader view.
In Designa, a purchase order tracks all the way through to delivery, you record what arrived and what didn't against the order, and the whole thing sits on the project timeline, so a slipped delivery shows up next to the install it was going to feed instead of surfacing as a nasty surprise on site.
Key takeaways
- Dispatched is a promise, delivered-and-correct is the thing you actually manage
- Inspect and count against the PO before you sign, because the signature is your leverage
- Log damage and shortages specifically and immediately, with photos, tied to the order
- A delivery on the same timeline as the work it feeds turns surprises into early warnings
Frequently asked questions
What should I check when material is delivered to site?
Count units against the purchase order, confirm the spec and finish match what was approved, and inspect for damage before you sign the delivery note, because signing makes disputes much harder.
How do I handle a partial or short delivery?
Record it as partial on the delivery note with the exact balance quantity, log the shortage against the PO, and confirm the vendor's date for the remainder before it stalls your install.
What is a goods received note?
It's the record of what actually arrived, checked against your order, which forms the middle document in matching your PO, the delivery, and the vendor's invoice.
Can Designa track deliveries against a purchase order?
Yes, a PO in Designa tracks through to delivery and sits on the project timeline, so you verify what arrived against what you ordered and see slips next to the work they affect.
The fastest way to see delivery tracking sitting on the same timeline as your site work is to click through a live setup at demo.designa.work, and if it fits, it's one flat founding price for your whole studio, billed in rupees with unlimited free client logins, over at go.designa.work.