A recurring customer should make your business more predictable, not create a daily guessing game. But when delivery notes live on paper, degree-day readings are loaded late, and a driver’s last delivery is hard to find, even a good automatic-route customer can become a problem. To manage recurring fuel customers well, your office needs current records, dependable scheduling rules, and a clear process for the exceptions that always come up.
For fuel oil and propane dealers, this is not just a customer service issue. It affects truck utilization, cash flow, emergency deliveries, and how much time the office spends answering basic questions. The goal is simple: know who needs fuel, when they need it, what was delivered last, and whether there is anything about that account that should change the plan.
Start With Customer Records You Can Trust
A recurring account is only as good as the information behind it. If a tank size is wrong, the usage estimate is outdated, or a delivery instruction is buried in an old paper file, your scheduling process is working with bad information from the start.
Each customer record should give a dispatcher or office person the full picture without hunting through tickets. That includes the delivery address, tank information, product type, estimated annual usage, delivery history, pricing arrangement, payment status, and clear site instructions. Gate codes, dog warnings, steep-driveway notes, required call-ahead instructions, and preferred delivery times belong where the person building the route can see them.
Customer records also need maintenance. A household that adds a room, installs a pellet stove, changes from oil heat to propane, or replaces a tank may have a different delivery pattern than it did two years ago. Ask about these changes during routine calls, service visits, or annual account reviews. A few minutes of cleanup before heating season can prevent a lot of avoidable run-outs later.
Choose the Right Scheduling Method for Each Account
Not every recurring customer belongs on the same schedule. Trying to force every account into one method creates unnecessary work and can lead to poor delivery timing.
Degree-day scheduling is usually the best fit for heating accounts with steady consumption. It uses local temperature data, past delivery information, tank capacity, and estimated usage to predict when an account should need fuel. When the data is current, it helps a dealer fill trucks efficiently while giving customers dependable automatic service.
Calendar-day scheduling can work well for accounts with stable, predictable use or for customers who prefer a set pattern. It may make sense for certain commercial accounts, standby generators, or low-variance residential situations. The trade-off is that calendar schedules can fall behind reality when weather changes sharply or usage habits shift.
Some accounts should remain call-in only. A seasonal home, an account with irregular occupancy, or a customer who closely manages their own tank level may not be a good automatic-delivery candidate. That is fine, as long as the account is clearly marked and the office does not assume it is being watched by the routing system.
The practical answer is often a mix. Use degree days where they provide the best forecast, calendar days where the use pattern supports it, and call-in handling where customer behavior makes automation unreliable.
Keep local temperature data current
Degree-day scheduling depends on timely, local weather information. If degree days are missing or loaded inconsistently, the predicted delivery date becomes less useful with every passing day. That can leave a customer too low, or send a truck to an account that did not need a delivery yet.
Make temperature updates part of the normal daily workflow. Your office should not have to manually calculate weather impact or wait until someone has time to enter it. A system that updates local temperature readings and applies them to scheduled accounts gives dispatch a more current picture before routes are built.
Use Delivery History to Catch Problems Early
The last delivery date and gallons delivered tell a story. They show whether a customer’s usage is holding steady, whether an estimated tank size makes sense, and whether a delivery came unusually early or late.
When an account starts appearing on the route much sooner than expected, do not ignore it. It could be a cold stretch, but it could also mean a new appliance, a tenant change, a tank issue, or a leak. If the same account is repeatedly delivered with a large amount left in the tank, its usage estimate or scheduling settings may need adjustment.
Delivery history is especially useful when a customer calls with a concern. Instead of relying on memory or pulling old tickets from a drawer, the office should be able to see what was delivered, when it was delivered, and what prior notes say about the account. That makes the conversation faster and gives the customer more confidence in your answer.
Build Routes From Current Need, Not Habit
A route that looks efficient on a map can still be wrong if it is based on outdated information. Recurring customers should be reviewed according to their expected need, then grouped by geography, truck capacity, product, and delivery constraints.
There will always be trade-offs. Sending a truck to a lightly needed account may be worthwhile if it sits directly on a route with several near-term stops. On the other hand, adding too many early deliveries ties up inventory and can reduce the number of gallons delivered per stop. Good dispatch is not about following a schedule blindly. It is about using accurate account data to make sound daily decisions.
Clear route status matters, too. Once a ticket is printed or assigned, everyone should know whether it is pending, delivered, skipped, or needs follow-up. This prevents duplicate deliveries and keeps the office from promising something that has already changed in the field.
Make Exceptions Easy to See
Recurring delivery works because most accounts follow a predictable pattern. The exceptions are where the office loses time and margins.
A customer may call to postpone a delivery, report a low tank, ask for a specific day, dispute a prior delivery, or say they are leaving for the winter. These details need to be entered directly into the customer record, not written on a sticky note or left in one employee’s memory.
Create a simple rule for handling changes: update the account first, then adjust the schedule or route, then record the customer communication. This matters when the person taking the call is not the person building tomorrow’s tickets. It also protects the business when a customer later asks why a delivery was not made.
For customers on automatic delivery, set expectations plainly. Explain that deliveries are scheduled based on estimated use and weather, not a fixed tank percentage. Ask them to call if they change their heat source, add occupants, leave the property, or notice unusual consumption. Automatic service works best when both sides share useful information.
Connect Delivery, Billing, and Payment Work
A delivered ticket should not create three more manual tasks in the office. When delivery records, customer balances, credit card processing, and accounting are handled in separate places, staff end up entering the same information repeatedly. That increases the chance of errors and delays billing.
For recurring customers, quick and accurate billing is part of good account management. A customer who receives a clear invoice shortly after delivery is less likely to call with questions. A customer with a declined card or overdue balance should be easy to identify before the next delivery becomes a bigger collection issue.
This is where fuel-specific software earns its keep. Degree Days Online brings recurring scheduling, delivery tickets, customer records, payment processing, and QuickBooks Online integration into the day-to-day workflow. The point is not to add another system for the office to learn. It is to reduce duplicate entry and give dispatch, drivers, and accounting the same current information.
Review Automatic Accounts Before the Season Gets Busy
Do not wait for the first hard cold snap to find out which accounts have incomplete information. Before peak season, review automatic customers for tank size, product, usage estimates, delivery instructions, payment terms, and scheduling method. Pay special attention to accounts with recent run-outs, unusual delivery patterns, or unresolved balance issues.
This review does not need to become a major project. Work through accounts in groups, starting with the highest-use customers and the routes that create the most calls. Correcting a few hundred records may sound tedious, but it is easier than sorting out a hundred preventable exceptions in January.
The best recurring delivery operation is not the one with the most complicated rules. It is the one where the next person can open an account, understand what is needed, and act with confidence. Keep records current, let reliable scheduling data do its job, and make every exception visible before it turns into a missed delivery or an unhappy customer.