Centralize office purchasing across locations while keeping useful local exceptions
Create comparable purchasing data, a shared catalog and site-level exception rules without assuming one national supplier fits every location.
Centralize the rules, records and reporting first. Keep stock checks, receipt and justified exceptions close to the site. A shared purchasing process does not require an identical basket or one supplier everywhere.
Make the data comparable
Review a representative period of orders across sites. Normalize item names, units and pack sizes before comparing prices. Identify delivery charges, rush orders, returns and one-time opening purchases separately. A cheap unit price can be misleading when locations order different quantities or specifications.
Record who currently orders and who confirms receipt. Look for duplicate orders and purchases that bypass an agreed catalog. The goal is to understand the workflow, not to assume every local decision was wasteful.
Create a common catalog with an exception register
Put recurring items shared across several sites in the common catalog. Keep a named approver for local additions and substitutes. Record the reason for each exception, its site, review date and whether it should become a shared standard.
Useful exceptions can reflect building requirements, delivery availability, storage limits or the work performed at that location. Do not standardize quantities simply because item specifications are shared. A small office and a busy headquarters may need different reorder levels.
| Responsibility | Central owner | Site contact |
|---|---|---|
| Catalog | Maintains standards and approved exceptions | Reports suitability problems |
| Stock | Defines reporting and reorder rules | Confirms actual usable stock |
| Order | Coordinates approved supplier and budget | Flags local timing constraints |
| Delivery | Tracks confirmation and supplier issues | Confirms receipt and discrepancies |
| Review | Explains cross-site trends | Provides local operating context |
Choose suppliers with geographic reality in mind
One supplier may simplify invoicing but have weaker availability at a particular site. Several suppliers may improve local service while adding administrative work. Compare coverage, delivery lead times, return handling and the full basket rather than assuming a national label means consistent service.
Confirm each site's address, receiving hours, order cutoff and local contact. Use the local time zone for delivery windows. A remote coordination model still needs someone to handle physical receipt and issues at the location.
Set budgets without requiring approval for every box
Define which standard orders can proceed under the client's existing authorization and which require a prepared exception. Distinguish a site budget from authority to create new recurring commitments. Keep the approval record attached to the order.
Do not apply the same exception limit to every category without considering risk. Equipment, employee-specific needs and technical items may require another specialist review even when the price fits within a routine supply budget.
Report variation with context
Compare spend by category and site, rush-order frequency, delivery issues and catalog exceptions. If dependable attendance data exists, it may help explain differences in consumables. A cost-per-employee comparison can mislead when sites have different attendance, visitor traffic or one-time projects.
Pilot a few recurring categories across selected sites, review a complete ordering and receiving cycle, then expand. SFI can discuss maintaining the shared coordination layer with existing or agreed providers; this does not promise nationwide physical service or a predetermined level of savings.
Sources and reading limits
The workflow and templates are editorial proposals. External sources provide the context described below; they do not verify SFI results or delivery capabilities.
- Proactis — Spend management for multi-location organizations ↗
Vendor paper; global audience, not US market-size data. Search-indexed extract reviewed, not full paper. Accessed November 4, 2026.