Part of our series on the FF&E & OS&E procurement workflow. Start with the full workflow overview, or back up to Procurement Planning & Purchase Orders.
Everything before this point — specification, budgeting, sourcing, purchase orders, freight — has been building toward one outcome: product physically arriving at a site, correctly, on schedule, ready to install. This stage is where the entire project becomes visible to the client, which also means it’s where mistakes made earlier (a wrong quantity, a missed revision, a vendor substitution nobody flagged) finally show up.
When product arrives — whether at a job site or a consolidation warehouse — the first job is confirming that what showed up matches what was ordered: correct item, correct quantity, correct finish, and no damage in transit. This is also the point where shortages and damages get caught, or don’t. A shortage that isn’t logged against the original PO at receiving tends to resurface much later, usually as a confused conversation about why an installer is missing a case of hardware.
Teams running this manually are typically cross-referencing a packing slip against a purchase order spreadsheet by hand, then separately logging any damage or discrepancy somewhere else — a third system, or worse, an email to whoever handles claims. Every one of those handoffs is a place a shortage can get lost.
The more reliable version of this process ties receiving directly back to the same PO record that was generated during procurement, so a discrepancy is flagged against the actual order — not reconstructed from memory or a paper trail — and the vendor claim or reorder can be initiated immediately.
For large projects — a hotel with 200 identical guestrooms, a multifamily development with a dozen unit types, a corporate campus with several floors of workstations — received inventory has to be allocated to specific rooms, units, or zones, and tracked as it moves. This is exactly the kind of scale problem multi-property operators face: a management group like often isn’t allocating inventory for one building, they’re doing it across a portfolio, often simultaneously. Delivery and allocation also has to follow whatever order the building is actually going up in — a hotel built floor by floor typically needs guestroom furniture staged in that same sequence, which means the receiving and allocation plan has to track the construction schedule, not just a delivery date. It’s also common for excess inventory from one project to be transferable to another, particularly for brand-standard items that are used across a portfolio. Without a system tracking what’s been allocated where, this either turns into a spreadsheet nobody trusts, or excess product simply sits in a warehouse unaccounted for instead of being redeployed.
This is a place where a few procurement platforms, Fohlio included, extend into functionality like QR-code-based asset tracking, where each item can be scanned on-site to confirm what it is and where it belongs. It’s genuinely useful for installation-heavy projects — but it’s worth being precise about scope: installation coordination and QR-based field tracking are generally a project management function, not a procurement function, even though they sit right next to procurement in the timeline. Fit-out projects in particular blur this line, since procurement and installation teams are often working side by side. If your organization’s software stack draws a hard line between procurement and project management, this is usually where that line falls.
Installation rarely finishes without a punch list — a documented set of items that are missing, damaged, incorrect, or need adjustment before the space is considered complete. The same principle applies here as everywhere else in this workflow: a punch list that’s disconnected from the original spec and PO data means someone has to manually figure out which vendor, which order, and which line item a field issue traces back to. A punch list tied directly to the underlying procurement record answers that automatically.
Tracking installation status against a schedule — and flagging when a status hasn’t been updated in time — is what turns “we think we’re on track” into an actual, verifiable answer. A schedule or risk-tracking view that shows items as on-track, at-risk, or behind schedule (tied to real installation and delivery data, not a manually updated Gantt chart) gives project leads the time to react to a slipping timeline instead of discovering it at the walkthrough.
Depending on how a project is scoped, the procurement side of the work often ends here — with everything handed off to a project manager, installer, or the client directly for final sign-off. Handing that off well means providing more than just a delivery confirmation: the receiving party needs the specs, the documentation, and anything vendors provided alongside the product — warranties, maintenance guides, installation instructions — tied to the actual items, not sitting in a folder disconnected from which line they belong to. That handoff package, and everything it feeds into afterward, is where the next article picks up.
If it'd help to talk through your specific setup, we offer a free workflow assessment — no pressure, just a look at where the gaps are.
Next: Procurement Analytics & Project Closeout →
Catch up on the rest of the series:
If you work with installers, project management teams, or procurement portfolios and think this would be useful to your network, we’d appreciate a share — or browse the rest of our blog for more like it.