A runout call rarely starts with one obvious mistake. It starts with a customer record that was a little off, a weather change that moved faster than expected, a delivery that slipped a day, or a call-in order that never made it onto the truck. Understanding what causes fuel runouts means looking at the full chain from customer data and tank size to scheduling, dispatch, and proof of delivery.
For a fuel oil or propane dealer, a runout is more than an unhappy customer. It creates emergency work, disrupts the route, adds overtime and fuel cost, and can damage a relationship that took years to build. In cold weather, it can also become a real safety issue. The good news is that most runouts are preventable when the office has current information and a process for catching exceptions before they turn into after-hours calls.
What causes fuel runouts? Usually, small gaps add up
The most common cause is an inaccurate expectation of when a customer will need fuel. Automatic delivery depends on estimating fuel use correctly enough to schedule a delivery before the tank reaches a critical level. When the starting information is wrong or operating conditions change, the estimate can fall behind reality.
A dealer may have a reasonable degree day schedule, but that schedule only works as well as the customer record behind it. Tank size, fill level at the last delivery, historical use, delivery type, and heating profile all affect the next estimated delivery date. A missed update in any of those areas can create risk.
Runouts also tend to happen during the busiest stretches of the season, when dispatchers are moving routes, drivers are covering more stops, phones are ringing, and the office has less time to investigate every unusual account. That is exactly when a system needs to point out the accounts that do not fit the normal pattern.
Bad customer data creates bad delivery dates
An incorrect tank size can put every future calculation on the wrong footing. If the record says a customer has a 275-gallon tank but the usable capacity is lower, the account may look safe on screen when it is not. The same is true when a prior delivery ticket lists the wrong gallons delivered, a partial fill was not recorded correctly, or a new tank was installed without updating the account.
Estimated annual usage deserves the same attention. Some customer records keep an old consumption figure long after the household or equipment has changed. A new furnace, a room addition, a tenant change, a heated garage, or a switch to propane for more appliances can all change demand. A record based on last year’s usage may no longer reflect the load on that tank.
Account status matters, too. A customer who was once automatic may have moved to will-call. A will-call customer may assume they are still on automatic delivery. Unless that status is clear on the account and communicated plainly, the result can be a disagreement followed by an emergency delivery request.
Weather can outrun a schedule
Degree day scheduling is one of the best tools a heating fuel dealer has, but it is not a set-it-and-forget-it process. A sudden cold snap, extended wind, or a stretch of cloudy days can increase consumption faster than a schedule based on milder conditions expects.
This is especially common early in the heating season. A tank may have been filled during moderate weather, then a hard freeze arrives before the next scheduled review. Customers with smaller tanks, high heat loss, or higher-than-average usage need closer attention during those transitions.
Local temperature data matters here. Using readings that do not represent the conditions in your service area can skew degree day calculations. The difference may look small on a single day, but over a week of cold weather it can move a delivery date enough to matter. Dispatchers should also have a way to identify accounts that are approaching a low estimated level, even if their planned delivery date is still a few days away.
Scheduling gaps and route changes cause preventable misses
A customer can be correctly scheduled and still run out if the delivery does not happen. A stop may be left off a printed ticket, moved to another truck without being tracked, or postponed because the route was too full. A driver may find an inaccessible fill, a locked gate, a parked vehicle, or an unsafe driveway and return without a clear follow-up process.
These are not rare events in a real delivery operation. They are exceptions, and exceptions need to be visible. If a no-delivery stop disappears into a stack of paper tickets or a handwritten note, it is easy for the office to assume the account was handled. The customer, meanwhile, is still burning fuel.
The risk increases when tickets, delivery history, and scheduling live in separate places. Double entry and end-of-day paperwork delays can leave dispatchers making tomorrow’s decisions with yesterday’s information. When the office cannot see completed, skipped, and unresolved stops in one place, it cannot manage the exceptions quickly.
Human changes at the customer location matter
Fuel consumption is not fixed just because the account is on automatic delivery. A customer may add family members, work from home, keep the thermostat higher, or begin using more rooms. A vacant house may become occupied again. A snowbird may return early. In propane accounts, a customer may add a generator, pool heater, fireplace, or kitchen appliance.
Equipment problems can also increase use. A poorly adjusted burner, a malfunctioning boiler, or a propane appliance issue may make the customer consume fuel faster than normal. The dealer is not responsible for every household change, but a sharp change in use should trigger a question rather than quietly becoming the new estimate.
This is why delivery history is valuable. It helps the office spot an account that suddenly takes far more gallons than expected, repeatedly orders early, or has delivery intervals that no longer match the assigned schedule.
Credit holds and communication failures can turn into runouts
Not every runout is caused by a calculation. Sometimes an account is deliberately held because of a past-due balance, an expired card, or a credit limit. That is a business decision, but it needs a clear workflow. If the customer has not been notified, or if the office assumes someone else is handling the call, the hold can become an emergency situation.
The same applies to call-in orders. A customer may leave a message, speak with a new employee, or place an order that is written down but never entered into the dispatch system. A promise to deliver tomorrow is only useful if it becomes a ticket, a route stop, and a completed delivery.
The practical lesson is simple: customer communication should be connected to the account record. Anyone answering the phone should be able to see whether the customer is automatic or will-call, when the last delivery occurred, what the estimated level is, and whether there is a hold that requires action.
Build a process that catches risk early
Preventing runouts does not require a complicated enterprise system or a dispatcher who memorizes every tank in town. It requires current records, reliable scheduling, and a daily review of exceptions.
Start by checking the accounts most likely to cause trouble: customers with small tanks, high usage, recent service changes, unusual delivery history, low estimated levels, or a missed prior stop. During cold weather, review them more often. A route that looks efficient on paper is not efficient if it leaves behind a customer who needs an emergency trip two days later.
Keep delivery tickets and delivery history current as trucks return. If a driver cannot deliver, record why and assign the next action before the ticket is closed. If gallons differ sharply from the expected amount, review the account rather than waiting for the next cycle. And when an account changes from automatic to will-call, make sure both the system and the customer reflect that change.
A practical fuel delivery management system can make this work easier by bringing customer records, degree day data, delivery scheduling, call-in orders, ticket printing, and delivery history into the same daily workflow. Degree Days Online was built around the real work of a fuel delivery office, where getting a stop onto the right truck at the right time matters more than fancy software features.
The best runout prevention is not a promise that runouts will never happen. Weather, customer behavior, and field conditions will always create surprises. The goal is to make the warning signs visible early enough that your team can act during normal business hours, on a planned route, before a customer is cold and your day is upside down.