Procurement for multi-location service businesses

A useful model is centrally governed and locally executed. The central team owns supplier strategy, approved products, commercial terms, policy, approval design, accounting dimensions, and the exceptions that require judgment. Location teams own accurate requests, receipt confirmation, and early escalation when an order will not support operations.

Centralization should not mean that every routine box of supplies waits in a headquarters queue. The design goal is straight-through purchasing for standard demand and deliberate review for exceptions, material commitments, new suppliers, or unusual products.

Start by separating demand into operating patterns. Replenishment items should be easy to reorder. Opening kits should be reusable. Repair and facilities demand needs a controlled urgent route. Local-market items need a documented exception instead of an invisible workaround.

1. Standard core.Products whose safety, brand, quality, or price benefits justify one approved specification across the network.
2. Role-based assortment.Different catalogs for managers, clinicians, facilities teams, educators, or other roles with genuinely different needs.
3. Location variation.Products made available because of geography, regulation, building type, climate, or the services delivered at that site.
4. Controlled exception.A fast route for urgent, unavailable, or novel demand that records why the standard route could not work.

Review substitutions before approving them as permanent catalog items. A cheaper item is not a saving if it fails sooner, creates inconsistent service, or transfers work to the location.

• Pre-purchase control: apply the budget, approved assortment, and authority before money is committed.
• Line-level coding: capture the product, supplier, location, entity, requester, approver, and accounting treatment together.
• Receipt discipline: record shortages, damage, substitutions, and late delivery while the evidence is available.
• Supplier visibility: aggregate performance and spend without hiding which location experienced the problem.
• Exception ownership: name who resolves a failed order, pricing discrepancy, or disputed invoice and by when.

Software should turn the operating model into the easiest path. Useful capabilities include multi-entity and location coding, configurable approvals, shared and location-specific catalogs, purchasing from existing suppliers, order tracking, exception handling, consolidated reporting, and clean transfer into the accounting system.

Order.co is a particularly relevant option when the central problem is recurring indirect and operational purchasing across many vendors and locations. Its product materials describe a unified purchasing catalog, location- and threshold-based approvals, recurring orders, line-level purchase data, and accounting integration.^[2]

That is a different problem from strategic sourcing of complex services, construction project controls, warehouse management, or public tender administration. Buyers should confirm the categories and workflows in scope rather than treating every product labelled “procurement software” as interchangeable.

In a customer story published by the vendor, Order.co reports that CorePower Yoga used its approval controls and centralized purchasing process across more than 200 locations, reducing previously reported unapproved monthly spend. The result is useful evidence of fit, but it remains a vendor-published case study rather than an independently audited benchmark.^[3]

1. Days 1–30: establish the baseline.Map locations, buyers, suppliers, categories, invoices, budgets, approval paths, accounting dimensions, and the workarounds people actually use.
2. Days 31–60: control the repeatable core.Launch the highest-frequency products and suppliers, test approval and coding rules, and define receiving and exception ownership.
3. Days 61–90: expand with evidence.Add categories based on transaction volume and operational pain, remove duplicate suppliers where appropriate, and compare adoption and exception data with the baseline.

Pilot with representative locations rather than only the most compliant site. Include a large location, a small one, a remote one, and a location with frequent urgent demand. Their exceptions reveal whether the design can scale.

• Connect the model to the procurement process
• Review the procurement software stack