Part of our series on the FF&E & OS&E procurement workflow. Start with the full workflow overview, or back up to Specification Management if you’re starting further upstream.
Once a specification is approved, procurement takes over — and the workflow that follows is where most commercial procurement teams either save enormous amounts of time, or lose it in a different way: juggling budgets, sourcing, bid comparisons, purchase orders, and (eventually) shipping and accounting, all while trying to keep every number aligned across a half-dozen spreadsheets.
Talk to a dedicated FF&E procurement agency about their actual workflow and it tends to sound like this:
Specs arrive from the design team as PDFs, sometimes Excel.
Every project is treated as its own thing rather than pulled from a shared catalog, because the products on a hospitality or commercial job are rarely repeatable across clients.
Areas get created first, then specs get uploaded and assigned to them.
Ccomponents get used mainly for COM (customer’s-own-material) fabrics and other separately purchased add-ons.
From there, it’s generate the RFP, collect quotes, enter pricing and lead times by hand, and create the PO.
None of that is unusual — it’s close to the default workflow for procurement-focused firms in this space, which is exactly why the bottlenecks below show up so consistently.
Some firms operate strictly as a procurement agent: a client hands over a bill of quantities, the agent sources it, and the value they add is a shorter lead time or a better price — charged either as a cut of the discount they negotiate or a flat fee (a common structure is around 4% of total purchase volume). Others go further and handle sourcing, procurement, and delivery as one bundled service. Either way, the mechanics below are largely the same.
Procurement doesn’t operate in isolation. Depending on the project, a purchase might need sign-off from a designer (does this still match the approved spec?), a client or owner (is this within budget?), and sometimes a procurement or sourcing department that wasn’t involved in the original design decisions at all. In larger organizations, this can also include an internal procurement or purchasing firm that specializes in vendor relationships and freight, working alongside the design team rather than in place of it.
The common failure mode here isn’t disagreement — it’s timing. Approvals that live in email threads or verbal check-ins are easy to lose track of, and a purchase order that goes out before a budget approval is finalized is a hard thing to walk back once a vendor has started production.
Money moves in a fairly predictable pattern behind these approvals, too: many vendors require a 20–50% deposit up front to hold pricing and secure quantity, which typically means the client funds roughly half of the estimated project budget before an agent can start placing orders. Proposals, and the partial or full invoices that follow, can be generated directly from the specification and its preliminary numbers — though the actual movement of money still happens outside whatever system is tracking the work, whether that's Excel or a dedicated platform. A spec-to-invoice tool speeds up the paperwork; it isn't a payment processor.
Procurement planning typically starts with an estimated Bill of Quantities (BOQ) — unit costs, extended costs, and quantities by item type, built from the approved spec but without needing every specification detail locked yet. In practice, this estimate often starts from the other direction: a client gives a top-line FF&E budget (say, $1M for a spec running a couple hundred items), and the agent uses market knowledge to allocate that budget across categories before a single vendor has been contacted. This estimated BOQ usually needs its own client or stakeholder approval before sourcing even begins, because it’s the number everyone downstream is going to be held to.
Once real sourcing starts and actual vendor pricing comes back, that preliminary number and the real one rarely match exactly — a variance in the range of roughly 7–12% between estimate and confirmed cost is common once freight, import fees, and other landed costs get factored in, though this varies a lot by region and category. That’s a normal part of the process, not a sign something went wrong — but it only stays manageable if the client is seeing that gap update in real time (ideally on a weekly or monthly cadence) rather than finding out at the end that more funding is needed. It’s also common for the budget to be incomplete at project kickoff, with value-engineering rounds afterward that require editing dozens of line items at once — which is its own argument for keeping the budget tied to the underlying spec data rather than a static export. If the BOQ lives in one spreadsheet, the vendor quotes live in another, and the actual purchase orders live in a third, “the budget” stops being a single number and starts being three numbers that are all supposed to match but frequently don’t.
With a budget approved, procurement moves into sourcing: finding vendors who can supply the specified items, at the right price, matching the required specification, within an acceptable lead time. Price and spec match are typically the two dominant factors — lead time matters, but usually as a tiebreaker rather than the primary filter, unless a hard installation deadline makes it otherwise. Matching against the right material — the exact veneer, finish, or fabric a spec calls for — is part of this too, which is where a maintained materials library earns its keep.
A specific, often-overlooked pain point here: an outside designer will typically hand over a spec — say, a chair with a particular look — without naming a vendor for it. It's then on the procurement agent to know (or figure out) which of their vendors even make that category of product. A standard email inbox doesn't filter contacts by what they sell, so agents often end up keeping a separate list, sorted by category, just to know who the ten chair vendors are before they can even start reaching out. This is exactly what a categorized vendor contact book is for — sorting suppliers by product type so "who makes chairs" is a filter, not a memory exercise.
For organizations without an enterprise vendor-management system, this step often happens entirely in spreadsheets: manually tracking which vendors were contacted, what they quoted, and how those quotes compare. Even teams that do have a dedicated PO or purchase-tracking tool frequently find it doesn’t handle sourcing or logistics well, so they end up maintaining a spreadsheet alongside the software anyway — which reintroduces the exact duplicate-data-entry problem the software was supposed to solve.
Once vendors are identified, the specified items convert into a Request for Quotation (RFQ) — sometimes called a “supplier quote request,” a term more common outside the U.S. In larger or more complex projects, this may instead be an RFP (Request for Proposal), where the vendor is also proposing services, installation support, or product substitutions alongside pricing, not just a price on a known item.
The fully manual version of this looks like: attaching a spec sheet and individually emailing it to each of ten vendors, one at a time, then waiting — while still trying to source everything else in the meantime — for replies that come back in ten different formats, sometimes not even as a document (a screenshot, a photo of a handwritten quote, a message on WhatsApp). Someone then has to manually re-key every vendor’s pricing into a comparison spreadsheet before anyone can actually evaluate the bids side by side. Quote ingestion in particular tends to be the single biggest time sink procurement teams describe: every vendor formats a quote differently, especially outside standard fabric and finish categories, so even teams already experimenting with AI tools to parse incoming PDFs find the field extraction unreliable for anything non-standard.
Purpose-built platforms fold this into the same system the spec already lives in. In Fohlio, for instance, an approved specification converts directly into an RFQ that can go out to every relevant vendor at once instead of one at a time, with the option for a vendor to note an alternative product, not just a price, within their reply. The system also tracks whether a vendor has opened the request, which cuts down on chasing people just to confirm a quote landed. And because not every vendor will use the platform — some will always reply by email or send a quote as a photo — those manually collected quotes can be entered directly into the same comparison table, so a mix of digital and manually-added quotes still gets compared side by side rather than living in two different places. For firms sourcing internationally, that comparison also handles multi-currency conversion automatically, converting each vendor's local-currency quote into the project's working currency, rather than requiring someone to build and maintain that conversion themselves.
Either way, the pricing lands in a bid comparison table — sortable by unit cost, total cost, or lead time, with the fastest or most affordable options surfaced automatically — instead of being rebuilt by hand for every project. That one shift (comparison table generated and highlighted automatically vs. built manually in a spreadsheet) is a small thing on any single RFQ, and a significant one across a year of projects.
One underrated benefit of keeping RFQ and PO history in a single system: it gives procurement real negotiating leverage. A single project might only represent a modest order with a given vendor — not enough to justify asking for a volume discount. But a procurement team with visibility across all of its projects with that vendor — total historical spend, total quantity purchased, and current open orders — can walk into a pricing conversation with a very different argument: “we’ve purchased $X from you across Y projects over the last two years.” Without that cross-project visibility, that leverage simply doesn’t exist, because nobody can see it.
Once a supplier is selected and approved — sometimes requiring a third-party or internal sign-off, particularly for large orders — the winning price should flow directly into the project’s live cost tracking, without anyone re-entering it. This is the moment a “budget” becomes “actual committed spend,” and it’s also where real-time budget visibility matters most: if a category is trending over budget, the team needs to see it now, while there’s still time to find an alternative vendor, substitute a product, or renegotiate — not three weeks later when the invoice arrives.
From there, the same underlying spec and pricing data generates the purchase order itself — again, ideally without re-keying information that was already entered during specification and RFQ stages. PO formatting is genuinely one of the messier parts of this work: different clients, different entities being purchased under, different tax treatment, different contract terms — which is why many firms keep several different PO templates in Word or Excel depending on the deal. A well-built procurement system lets a firm curate its own set of PO templates once and generate a draft directly from the winning bid — populating the same spec data rather than copy-pasting it in — with the client able to approve the request digitally, from a phone or a desktop, before it goes out. It also layers in:
One thing worth flagging honestly: change orders — when a price shifts, a quantity changes, or a vendor substitutes a product after a PO has already gone out — aren't a dedicated, purpose-built workflow in most procurement tools, including Fohlio today. The practical workaround is closing out the original PO and issuing a new one, which works but is still a manual step, not an automated one.
Once a PO is placed — especially for custom manufacturing — a new set of milestones begins: shop drawing approval, sample approval, factory production, and eventually freight and import logistics. This stage is arguably where procurement teams have the least visibility, because it depends on communication with vendors and carriers rather than anything the team directly controls. International shipments add another layer: a vendor is often only responsible for getting product to their own region's border, at which point a freight forwarder takes over, and the procurement agent may then be responsible for the final leg — getting the item onto a local truck and to the actual address. That's three separate parties to stay in contact with for a single shipment, not one.
The practical risks here are familiar to anyone who’s run a commercial FF&E project: a factory delay that isn’t reported until it’s already too late to adjust the installation schedule, a shipment stuck in customs with unclear timing, or a landed cost (freight, duty, tariffs) that comes in well above the original estimate because it wasn’t tracked alongside the unit cost from the start. Delivery timing also has to follow the construction and installation schedule, not just arrive whenever it's ready — if a hotel's guestroom furniture is going in floor by floor as construction finishes each level, shipments need to land in that same order, which takes real coordination with vendors to get right.
The fix isn’t more phone calls to vendors — it’s automating the parts of tracking that don’t require a human judgment call. Real-time shipment tracking that pulls ship and delivery dates directly from the courier (rather than requiring someone to check a vendor’s tracking portal manually) means a delay shows up the moment it happens, giving the team time to find an alternate supplier or adjust the installation schedule — instead of finding out during the week of install, when there are no good options left. Expediting still requires human follow-up in plenty of cases, but it should be triggered by an alert, not discovered by accident.
Getting product delivered on time and correctly specified sets up the next — and often most visible — stage of the project: getting it into the building.
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: Receiving, Inventory & Installation →
Procurement and purchasing firms, ERP and accounting partners, and vendor networks working alongside design teams are welcome to share this one with your audience — happy to return the favor.