Blog | Fohlio | Industry Tips for Architects and Interior Designers

Procurement Shouldn't Live in Ten Different Spreadsheets | Fohlio

Written by Kara Olin | Aug 17, 2026, 6:13:08 PM

Specify, procure, prototype, collaborate, and analyze at scale. Take on bigger projects with confidence and grow your firm with Fohlio. Schedule a demo or book a consultation with one of our account managers to explore these features today.

Ask most commercial design and procurement teams how they track a project, and the answer is almost always the same: a sourcing spreadsheet, a vendor spreadsheet, an item spreadsheet, a budget spreadsheet, a shipping tracker — each one updated by hand, each one slightly out of sync with the others. Nobody designed this system on purpose. It's what happens when teams outgrow a simple process one project at a time, patching gaps with a new tab instead of a new system.

For commercial teams — real estate development, hospitality, retail — this isn't just an inconvenience. Commercial specification carries more complexity than residential work: custom fabrication, multiple manufacturers per item, layered approval chains, and purchase volumes that make a missed markup or a duplicate PO expensive. A firm managing this across spreadsheets is managing risk it can't fully see.

What a Unified Workflow Should Look Like

A firm shouldn't have to move between disconnected files to answer a basic question: what's been specified, what's been ordered, and what's it costing us against budget. That information should live in one project record, updated automatically as the team works — not recreated by hand in a separate report.

This is the problem Fohlio is built to solve. Every project — its items, purchase orders, budgets, and vendor relationships — lives in a single structured record. Design and procurement teams work from the same source of truth instead of reconciling versions after the fact.

Purchase Orders Should Build Themselves From Work Already Done

A firm should be able to generate a purchase order from the items it has already specified — grouped by supplier, populated with vendor details already on file — rather than rebuilding that information from scratch every time. In Fohlio, selecting items assigned to a supplier and generating a PO pulls vendor addresses, contacts, and terms directly from a contact book, so the same details never have to be typed twice. Teams can also save PO templates with preset attachments, notes, and line-item structures, so a recurring format doesn't have to be reassembled project after project.

Approval shouldn't be a side conversation either. A firm should be able to set spending thresholds that automatically route a PO to the right approvers once it crosses a dollar amount, with the PO's status — draft, under review, approved — visible to everyone who needs to see it. A single dashboard should show every PO's status, expected arrival, and whether the vendor has even opened the email, so nothing requires a follow-up call to check.

Budget Visibility Shouldn't Require a Separate Report

A firm should always know where a project stands financially without assembling that picture manually. Fohlio's budget and finance module tracks planned, specified, and purchased amounts in real time, broken down by category, area, or vendor — because the numbers come directly from the specification and procurement work already happening in the project, not a parallel spreadsheet someone updates on Fridays. Teams that need to track markups, margins, or value-engineering savings can add those as custom fields and see them rolled up automatically at the project level.

Shipping and Receiving Shouldn't Mean a Dozen Open Tabs

Tracking a shipment across multiple carrier websites is its own kind of spreadsheet problem — just with browser tabs instead of rows. A firm should be able to enter a tracking number once and see live status pulled directly into the project, across the carriers it already uses. Fohlio integrates with more than 130 carriers, and each shipment tracks item-level status — ordered, shipped, received, damaged — without a manual status update.

Collaboration Should Come With Real Boundaries

Commercial projects mean outside collaborators: architects, contractors, purchasing agents, brand consultants. A firm should be able to bring them into a project without giving them the keys to everything. Role-based permissions in Fohlio go down to the field level — not just which modules a person can see, but which columns within them — so an external partner gets exactly the visibility they need for their part of the job, nothing more.

The Real Cost Isn't the Software — It's the Time Lost Without It

The honest question a firm should ask isn't "how many users do we need." It's how much time is lost moving between spreadsheets, how many errors come from re-entering the same data twice, and how much of that could be recovered with a system built for the way commercial procurement actually works. A unified platform doesn't just organize information — it gives a firm back the hours currently spent reconciling it.

That's the case for moving procurement out of the spreadsheet and into a system built to hold it.