Consolidating Facility Vendors Across Multiple Sites

Multi-site vendor bases usually grow by accident. Each site hired its own electrician, found its own source for plumbing spares and renewed its own housekeeping contract, and the group ends up with many small relationships and no single view of what it spends. Consolidation is the deliberate fix, and it works when it is done in stages.

Why consolidate

• Less admin. Every vendor means an onboarding file, a vendor code, invoices to process, renewals to track and documents to keep current. Fewer vendors reduces that load.
• Consistent specifications and pricing. When the same item is bought at every site from one source, it can be bought to one specification at one agreed rate, and a substitution at one site is visible to all of them.
• Single accountability. One party owns delivery across sites and there is one escalation path when something fails. Site teams stop mediating between several vendors.

The real risks, and how to mitigate them

Consolidation trades one set of problems for another. Name them before you start, and put the mitigation into the contract or the process.

A phased approach

1. Baseline current vendors and spend. From invoices and POs, list every vendor by site and category: what each supplies, the rates you pay and the contract end dates. The aim is one view of what you buy, from whom, at what price.
2. Prioritise categories. Start with categories that are repeat, well specified and spread across many sites, such as electrical consumables, plumbing spares, PPE and housekeeping items. Leave complex or specialised trades for later, or leave them out.
3. Pilot at one or two sites. Choose sites that are representative but not the most critical or the most difficult. Run the pilot long enough to cover a full ordering cycle, including a return and a substitution.
4. Agree KPIs and a review cadence. Delivery against the agreed date, completeness of deliveries, invoice accuracy against the PO, response to urgent requests and closure of service issues are typical measures. Fix the review dates before the pilot starts.
5. Roll out. Extend site by site using the pilot’s catalogue and terms, and confirm coverage for each new site before it goes live.
6. Review. Compare against the baseline: spend, number of vendors, invoice volumes and feedback from sites. Decide what to extend, what to rebalance and what to leave alone.

Commercial models, described generally

Three structures cover most cases. Rates and terms depend on the requirement, so no figures are given here.

• Rate contract. Agreed rates for specified items or services over a defined period, with orders placed against it as needed. It suits repeat purchases where volumes are hard to predict, and it works best with clear specifications and a stated method for reviewing prices.
• Catalogue pricing. A defined list of items with item codes and agreed prices that sites order from. It brings consistency across sites and speeds up ordering, but someone must own the catalogue and approve additions. See building a maintenance catalogue.
• Retainer for services. A scheduled service scope, such as periodic maintenance, for an agreed fee, with extra work handled separately. Define what sits inside the retainer, what counts as extra and how urgent calls are handled. See managed maintenance.

Governance that keeps it working

• A single point of contact on each side. One named person at the vendor and one at your company, each with a named deputy. Site teams raise requirements through them or through an agreed process, not through personal phone calls.
• A monthly review. KPIs by site, open issues, spend against the baseline and upcoming requirements. Keep it short and fixed on the calendar.
• A written escalation path. Who to contact for a missed delivery, a disputed invoice or a recurring problem, and what response each level owes, agreed with the vendor in advance.
• Change control. Changes to specifications, catalogue items or sites go through one owner, so every site stays aligned.

When not to consolidate

• Highly specialised trades. Work that needs specific licences or niche skills is usually better held with a specialist. Manage specialists on the same review cadence rather than forcing them into a general contract.
• Sites with no coverage. If the consolidated vendor cannot support a site with an acceptable response, keep a local vendor there for now.
• Where the incumbent is performing. A site whose local vendor is reliable, fairly priced and well documented may gain little from being moved.

How SupplycZar can help

SupplycZar is a Bengaluru-based vendor of recurring facility supplies, managed maintenance services and minor site projects, offered through a single commercial relationship. Coverage, scope and response options are confirmed site by site, which is why a pilot at one or two sites is a sensible first step. Read about multi-site delivery and MRO procurement, or share your site list and categories through our RFQ form.