UCO collection for multi-site operators: how data changes the economics
The multi-site problem
A multi-site client — a restaurant chain with 15 locations across a city, a hotel group with properties in three districts, a contract catering company serving six corporate offices — does not fill containers on a predictable schedule. The fast food outlet near a school generates more UCO during term time than holidays. The hotel's breakfast operation drives most of the volume, but a weekend event can change the fill trajectory entirely. The corporate canteen follows office occupancy — lower on Fridays, much lower in August.
Each site has its own fill rate profile. Across 15 or 20 sites, the combination produces a collection planning challenge that does not respond well to fixed intervals or calendar-based schedules. Without current fill level data, you cannot tell which sites need collection this week without visiting them or calling the client — neither of which scales.
What happens without fill level data
Without monitoring, UCO collection from multi-site operators tends toward one of two inefficient patterns. The first is over-collection: regular visits to every site on a fixed schedule, regardless of fill level. This keeps overflow incidents low but generates a high proportion of partial-load trips. The per-litre cost of collection rises accordingly.
The second is reactive collection: less frequent scheduled visits, supplemented by client-initiated calls when containers are approaching capacity. This reduces some wasted trips but creates unplanned route disruptions and increases the risk of overflow incidents — which damage the client relationship and, in food-service environments, create hygiene and compliance problems. Both patterns share the same root cause: decisions are made without knowing what is in the containers.
How daily fill level data changes the planning
Each container at each site gets a sensor that takes one automated reading per day and transmits to a central platform. For multi-site clients, the platform provides a single view across all locations — current fill level, fill rate trend, and projected time to collection threshold at each site.
Stop selection is based on readiness. The service queue shows which containers across the entire network are approaching threshold in the planning window. Sites that are not ready stay off the route. For a client with 15 sites, a single tour covers the 6 or 8 that are actually at collection threshold — instead of all 15 on a fixed schedule. Geographic clustering works properly: containers that are geographically proximate and simultaneously ready can be grouped into a single efficient route.
The compliance dimension
UCO collection has a regulatory layer that does not apply to most other collection verticals. UDB requirements for traceability, RED3 documentation for renewable fuel qualification, transfer proofs, and SAF supply chain documentation all require systematic record-keeping at the point of collection.
FoxInsights supports digital compliance documentation at the point of collection via FoxMobile: photo evidence, seal IDs, hygiene checks, and UDB/RED3-compliant exports. For collections from chains or franchise operators who require audit-ready documentation, this reduces the administrative overhead significantly while improving compliance reliability.
What the field pilot data shows
The 2026 field pilot data from UCO operators using FoxInsights: +45% margin per tour through data-driven logistics optimisation — the combined effect of collecting at higher fill levels, covering more productive stops per route, and reducing partial-load trips. Approximately one-third fewer collection tours overall at the same collection volume. Doubled margin per truck through higher tour utilisation. 15–25% fewer km per cubic metre collected in city centre operations.
One additional data point: a Swiss UCO partner reference documents approximately 20,000 kg of UCO per year that would otherwise have been lost to theft or illegal disposal, identified and prevented through GPS tracking and geofencing on containers.
Deployment
FoxInsights sensors for UCO containers use a standardised lid and adapter system for quick installation. For multi-site rollouts, the system is designed to be deployed by your own collection team — no external technical support required. Installation takes under a minute per container.
The standard deployment approach for multi-site UCO operators starts with one or two client accounts — typically the largest or most complex — to establish the operational workflow before rolling out across the network. The platform integrates with existing ERP and dispatch systems, including X-Oil, Microsoft Dynamics Navision, and SAP.
Ready to plan UCO collections from actual fill levels?
30-minute demo for UCO collection operations — multi-site and compliance.
Talk to a specialist