Category: Uncategorized

A bobtail can lose an hour before the first delivery is made. The driver waits on a paper ticket correction, a stop gets added after the route is loaded, or an office employee has to call around for a tank status. To improve bobtail driver efficiency, look at the entire path from the customer record to the printed ticket to the truck returning at the end of the day. The driver is where the delay becomes visible, but the cause often starts in the office.

For a fuel oil or propane dealer, better efficiency is not simply about pushing drivers to make more stops. It is about giving them a route they can run, accurate information at each stop, and less back-and-forth with dispatch. That reduces miles, overtime, delivery exceptions, and frustrated customer calls without sacrificing safe work.

1. Build routes from current delivery data

A route is only as good as the information used to create it. If tank sizes, consumption rates, delivery history, addresses, or special instructions are out of date, dispatch is planning around bad assumptions. The driver then has to make judgment calls in the field, and those calls cost time.

Keep customer records current throughout the year, not just when winter demand hits. When a customer changes a gate code, gets a new dog, adds a difficult driveway, or replaces a tank, put it in the record immediately. The same goes for delivery preferences, required call-aheads, and access restrictions.

For automatic customers, scheduling should reflect actual degree day usage and the customer’s established history. For propane, calendar-day scheduling may fit some accounts better. There is no single scheduling method that works for every customer base. What matters is using a system that flags the right accounts before they become emergencies.

A planned stop on a route is usually more profitable than an unplanned stop squeezed in between two other deliveries.

2. Stop treating call-ins as separate work

Daily call-in orders are part of dispatch, not an interruption to dispatch. When they are recorded on paper, in a notebook, or in a separate spreadsheet, someone has to re-enter the information later. That creates delays and opens the door to missed details, duplicate orders, and wrong-product deliveries.

Enter call-ins directly into the customer record as they come in. Dispatch should be able to see the order, delivery history, balance information, and route area without hunting through files. If a customer needs an emergency delivery, the office can make a clear decision: add it to a nearby truck, schedule it for the next run, or explain the available delivery window.

That decision should account for more than geography. A truck may be physically close to an order but already loaded for a different product, approaching driver hours, or headed toward a high-priority automatic route. Good dispatch is not just finding the nearest truck. It is fitting work into the day without breaking the rest of the plan.

3. Give drivers tickets they can trust

A driver should not need to call the office to confirm whether a customer is on budget, whether a special instruction applies, or whether the delivery quantity has changed. Every phone call takes time. More importantly, it breaks the driver’s rhythm and adds pressure to dispatch during the busiest part of the day.

Accurate delivery tickets give the driver the essentials: customer location, product, requested or estimated gallons, tank information, delivery notes, and clear payment or account instructions. Tickets should be printed after the route is finalized whenever possible, with a simple process for handling late changes.

Paper tickets are still common in the industry, and they can work well when the system behind them is organized. The problem is not paper by itself. The problem is handwritten tickets that are hard to read, get misplaced, or require office staff to enter the same information again after the driver returns.

If a ticket needs to change after a driver leaves, make sure the office records why. Was the tank inaccessible? Did the customer request fewer gallons? Was there a product issue? Those details improve the next routing decision instead of becoming another unexplained exception.

4. Reduce non-delivery miles first

The fastest way to improve bobtail driver efficiency is often to eliminate miles that do not produce a delivery. That includes crisscrossing service areas, returning for missed information, making premature automatic deliveries, and responding to avoidable runouts.

Review routes by territory and delivery density. A route with fewer stops can be more productive than a route with more stops if those stops are tightly grouped and the truck can stay in one area. On the other hand, forcing every route to be perfectly dense can delay customers who need service sooner. The right balance depends on weather, customer commitments, driver availability, and available gallons.

Watch recurring route problems. If one neighborhood regularly creates long driveway delays, schedule it with realistic time expectations. If a certain group of accounts repeatedly causes a second trip, review their delivery schedule and tank data. Small corrections to a group of customers can remove a surprising amount of wasted travel over a season.

5. Make loading and end-of-day work predictable

Driver productivity starts before the truck rolls and continues after the last stop. Long loading lines, unclear load assignments, missing tickets, and slow ticket reconciliation can turn a normal delivery day into an overtime day.

Set a consistent process for the morning. The driver should know the assigned truck, product load, route, tickets, and priority stops before leaving the yard. If splits or multiple products are involved, confirm them before loading rather than sorting it out after the truck is already staged.

At day’s end, bring delivery results back into the office quickly. The faster tickets and exceptions are entered, the sooner dispatch can see what was completed, what needs follow-up, and which accounts are still at risk. Waiting several days to update records makes tomorrow’s schedule less reliable.

This is where integrated workflows matter. When delivery records, ticket activity, payments, and accounting entries live in separate places, office staff spend their time matching paperwork instead of managing operations. A connected process reduces double entry and gives everyone a clearer picture of the day.

6. Use driver feedback to fix dispatch problems

Your drivers see the real route conditions. They know which customer notes are outdated, which turn is difficult with a loaded truck, which tanks are hard to access, and which delivery windows are unrealistic. If that information stays in the cab, dispatch keeps making the same mistakes.

Create an easy way for drivers to report exceptions and route issues. Keep it practical. A short note on the ticket, a standard end-of-day review, or a simple office checklist can be enough if someone is responsible for updating the customer record.

Drivers should not be expected to redesign routes from the road. That is dispatch’s job. But a driver’s field knowledge is valuable input. When office staff act on it, drivers spend less time working around avoidable problems and more time making safe, productive deliveries.

7. Measure the causes of lost time, not just stops per day

Stops per day is useful, but it does not tell the whole story. A driver handling rural propane accounts will look different from a driver delivering dense residential heating oil routes. Comparing them without context can lead to bad decisions.

Track a few measures that show where time and money are going: gallons per route, miles per delivery, overtime hours, undelivered tickets, repeat trips, runouts, and the number of office-to-driver calls. Review them by route area and season, not just as one company-wide number.

When a number looks off, ask what caused it. A high-mile route may be necessary because of customer geography. A low-gallon route may reflect a weather swing or an emergency day. But if the same issue repeats week after week, it is a process problem worth fixing.

Degree Days Online was built around these day-to-day fuel delivery realities: customer history, temperature-driven scheduling, call-ins, ticket printing, and the office work that has to happen around every delivery. The goal is not more software for its own sake. It is fewer manual steps between a customer needing fuel and a driver completing the stop.

A good delivery day should feel controlled, not improvised. Start with one recurring source of wasted driver time, fix the record or workflow behind it, and watch what changes over the next few routes. The best efficiency gains usually come from making ordinary work easier to do right every time.

A delivery ticket is more than a piece of paper handed to a driver. It is the record that tells the office what was delivered, tells the customer what they received, and tells accounting what can be billed. This guide to delivery ticket workflows is built for fuel oil and propane dealers who want that record to move cleanly from dispatch to the truck to the office without piles of paperwork, missing details, or rekeying the same information twice.

When ticket handling breaks down, the damage is usually not dramatic at first. A driver returns with an unreadable ticket. A delivery is posted to the wrong account. A price change never reaches billing. Then the office spends the afternoon sorting through exceptions while tomorrow’s route still needs to be built. A good workflow prevents that kind of cleanup work before it starts.

Start With a Ticket That Matches the Actual Delivery

The workflow begins before a truck leaves the yard. Dispatch needs a ticket that gives the driver the information needed to make the stop correctly: customer name, address, account number, product, planned quantity when applicable, special instructions, and pricing or delivery notes that belong on the ticket.

For automatic customers, the ticket should be tied to the delivery schedule and current account information. That matters because automatic delivery is not just about estimating gallons. The dispatcher also needs to know whether the account is on hold, whether there is a delivery restriction, whether the customer has a locked gate, or whether a new tank location has been added.

For will-call customers, the ticket should begin with the order taken by the office. The person entering the order needs a clear way to record the requested product, desired delivery date, any promised price, and instructions such as “call before delivery.” If those notes live on a sticky note or in someone’s memory, they are likely to disappear when the route is printed.

A practical rule is simple: enter customer and order information once, where dispatch, drivers, billing, and customer service can all work from the same record. That reduces double entry and gives everyone a better chance of seeing the same facts.

Build Routes Before You Print Tickets

Printing tickets too early creates avoidable problems. A driver may receive a stack of stops that no longer reflects the day’s route, while dispatch has to handwrite additions, cross out customers, or issue replacement tickets. That is workable on a quiet day. It is not a dependable process during a cold snap when phones are ringing and trucks are already rolling.

Finish the route as far as possible before ticket printing. Review the delivery list for geography, truck capacity, product type, priority customers, and special access requirements. For propane dealers, make sure the route reflects the right cylinder or bulk-delivery needs. For heating oil dealers, verify that degree day or calendar day scheduling has not pulled in a customer who was recently delivered or placed on hold.

There will always be late call-ins and emergency no-heat stops. The goal is not to pretend the route will never change. The goal is to make changes in one place, clearly, so the office can see what was added and the driver has a usable ticket for every delivery.

Use a clear cutoff for routine route changes

Most companies benefit from setting a practical daily cutoff for ordinary additions and changes. After that point, the dispatcher can still add an urgent stop, but the change should be handled as an exception rather than quietly altering a completed route.

This gives the office time to check the new order, print or send the correct ticket, and make sure the delivery will be billed properly. It also gives drivers a better chance of loading the right product and carrying enough gallons to complete their assigned work.

Give Drivers a Simple, Consistent Delivery Process

The driver should not have to guess what information the office expects back. Whether your operation uses printed tickets, mobile devices, or a mix of both, establish the same basic delivery steps for every route.

At the stop, the driver confirms the account and location, delivers the product, records the actual gallons, captures any required signature or delivery acknowledgment, and notes anything that needs office attention. A tank concern, blocked fill, access issue, or customer request should come back as a clear note attached to that delivery, not as a vague verbal message at the end of the day.

The actual quantity delivered is especially important. The office may have planned 150 gallons, but billing should reflect what went through the meter. If the driver could not make the delivery or delivered a partial due to tank conditions, that exception needs to be obvious. Do not let a planned quantity become an assumed delivered quantity.

A good ticket workflow also protects drivers. Clear tickets reduce disputes over the address, product, price, and instructions. If a customer questions a delivery later, the company has a usable record instead of trying to reconstruct what happened from memory.

Bring Completed Tickets Back Into the System Promptly

The day is not finished when the truck returns. Tickets need to be reviewed, posted, and turned into invoices while the delivery details are still current. Waiting several days may feel easier during a busy season, but it creates a backlog that makes mistakes harder to catch.

The office should compare each completed ticket against the original delivery record. Look for actual gallons, no-delivery codes, price overrides, signature requirements, tax status, and driver notes. If something does not match, resolve it before the ticket is posted to billing.

This review is where many preventable revenue leaks are found. A no-delivery ticket that gets billed by mistake creates a customer service problem. A delivery that is completed but never posted delays cash flow. A handwritten price note that is missed can leave the company arguing with a customer after the invoice has already gone out.

For companies using paper, organize returned tickets by route and date so nothing gets separated from the rest of the day’s work. For companies using delivery management software, completed delivery information should flow back to the customer record and billing process without requiring staff to type every gallon and note a second time.

Connect Tickets, Billing, and Payments

A ticket workflow is only complete when the delivery can be billed accurately and the customer balance is current. That connection is where disconnected systems cause the most office work. Dispatch may have one list, accounting may have another, and the person answering the phone may not know whether a delivery has been posted yet.

The right process lets the office review completed deliveries, create invoices, and keep customer records current from the same operational information used to dispatch the truck. If your company uses QuickBooks Online, the accounting handoff should be planned carefully. Decide which system owns the customer record, how invoices are transferred, and who handles corrections when an invoice needs to be changed.

It depends on the size of the operation and how much accounting detail is needed, but the principle stays the same: avoid creating one delivery record for dispatch and another for accounting. Every extra handoff is another chance for a mismatch.

Payment collection should also be visible to the people handling orders. If an account has an overdue balance, a credit limit issue, or a required payment before delivery, the dispatcher needs to see that before the ticket is printed. That does not mean every driver needs to handle collections. It means the office has enough control to avoid sending a truck to an account that should be reviewed first.

Set Up Exceptions Instead of Hiding Them

No workflow eliminates exceptions. Customers run out early. Driveways are blocked. Tanks cannot be filled. A driver may find that the account information is wrong. The difference between a controlled operation and a chaotic one is how those exceptions are recorded and followed up.

Create clear statuses for common outcomes, such as delivered, partial delivery, no delivery, wrong address, unable to access, or customer canceled. Require a short note when a ticket is not completed as planned. Then give one person in the office responsibility for reviewing those exceptions before the next day’s routes are built.

This step matters for automatic delivery customers. A failed delivery can change the customer’s risk level quickly, especially during severe weather. If the exception is buried in a stack of tickets, the scheduling system may assume the customer has product they never received.

Make the Workflow Easy Enough to Follow on a Busy Day

The best delivery ticket workflow is not the one with the most rules. It is the one your dispatchers, drivers, and office staff can follow when the temperature drops and the phones do not stop.

Degree Days Online was built from the day-to-day realities of a fuel delivery business, with tools for scheduling, ticket printing, delivery history, customer records, payment handling, and accounting workflows in one practical system. The point is not to add another layer of software. It is to replace paper chases and duplicate entry with a process that gives the office control of the day.

Start by looking at where tickets stall now. Maybe it is route changes after printing. Maybe it is returned tickets waiting to be entered. Maybe it is billing that does not match what the driver delivered. Fix the point where information gets lost first. A cleaner ticket process gives your team more time to serve customers and fewer reasons to stay late sorting out work that should have been right the first time.

A new dispatcher can affect every truck on the road before the first driver leaves the yard. One missed will-call order, an incorrect tank size, or a route built without checking prior deliveries can mean an emergency run, an unhappy customer, and lost margin. This propane dispatch training guide focuses on the work that keeps those mistakes from becoming routine.

Dispatch training is not just showing someone where to click. A good dispatcher needs to understand what the screen represents: real customers, real tanks, real drivers, and a limited number of hours in the day. The goal is to build confidence without teaching shortcuts that create problems later.

Start With the Flow of a Dispatch Day

Before training on software, walk a new dispatcher through the daily sequence in your office. Every company has its own habits, but the basic flow is familiar: review overnight messages and call-ins, check scheduled deliveries, build and adjust routes, print or send tickets, support drivers during the day, then close out deliveries and exceptions.

Explain why each step matters. A route is not simply a group of stops near each other. It has to account for gallons needed, truck capacity, delivery windows, access issues, customer priority, road conditions, and driver knowledge. A dispatcher who understands those factors can make a sound decision when the day does not go as planned.

Have the trainee watch an experienced dispatcher work through one full morning. Then let them repeat the same process with supervision. Training sticks better when it follows the actual workday instead of a canned demonstration that never looks like a busy January morning.

Build Customer Record Discipline First

Bad customer records create bad dispatches. Train dispatchers to review the information that affects a delivery before they add an order or put an account on a route. That includes the service address, tank size, product, estimated usage, account status, delivery instructions, and recent delivery history.

Notes deserve special attention. A note such as “call before delivery,” “dog in yard,” “low bridge,” or “deliver before 2 p.m.” is not background information. It can change the route, the driver assignment, or whether the delivery should go out at all. Make it standard practice to read relevant notes before creating a ticket.

The same goes for changes made during a customer call. If a customer reports a new tank, a locked gate, a vacation hold, or a concern about low fuel, the dispatcher should record it immediately in the customer file. Relying on a sticky note or memory works until the person who took the call is out of the office.

Teach the Difference Between Facts and Assumptions

Dispatchers should know when to verify information instead of guessing. A customer saying they are “almost out” does not automatically mean a same-day delivery is possible or necessary. Ask about the gauge reading, appliance use, whether they have heat or hot water, and whether the tank is accessible.

Likewise, an account with an unusual usage pattern may need a review before it is scheduled. It could be a data-entry error, a leaking system, a new appliance, or simply a customer who filled elsewhere. Train people to flag exceptions rather than force every account through the normal process.

Train Scheduling by Delivery Type

Most propane offices manage a mix of automatic deliveries, calendar-day deliveries, and call-in orders. New dispatchers need to understand that each type requires a different level of attention.

Automatic delivery accounts are driven by expected usage and delivery timing. The dispatcher’s job is to review the schedule, identify accounts that do not look right, and make sensible route adjustments. Local temperature data and degree-day calculations can make this far more reliable than trying to estimate every customer’s tank level by hand.

Calendar-day accounts follow a planned interval, but they still need oversight. A delivery due every 30 days may need to go earlier during a cold spell or later when usage drops. Call-in customers require the most direct communication because their order timing is based on what they report. The dispatcher must capture the request accurately, set expectations honestly, and make sure the order does not disappear in a pile of phone messages.

A cloud-based system such as Degree Days Online gives dispatchers one place to review customer history, schedule deliveries, handle call-ins, print tickets, and keep the day moving. The training point is not that software replaces judgment. It gives the dispatcher current information so judgment is based on the right facts.

Practice Route Building With Real Constraints

Do not train route building with a perfect map and an empty schedule. Use real examples from your service area. Give the trainee a truck capacity, a group of due accounts, two will-call orders, and one customer with a restricted delivery window. Then ask them to explain their route choices.

A practical review should cover these questions:

• Does the planned load fit the truck without creating an unnecessary return to the plant?
• Are priority and low-fuel calls placed ahead of routine stops when appropriate?
• Has the dispatcher considered tank sizes, expected gallons, and room for driver adjustments?
• Are special instructions visible on the delivery ticket or driver’s device?
• Does the route make geographic sense without ignoring customer commitments?

There is no single perfect route. The closest route may not be the best route if it creates a missed appointment, puts a driver on a difficult road after dark, or leaves no capacity for a likely emergency. Good dispatchers learn to balance efficiency with service and safety.

Make Ticket Accuracy Non-Negotiable

The delivery ticket is where office work becomes field work. If the ticket has the wrong address, product, account, or instructions, the driver has to stop and call, or worse, makes the wrong delivery. Train dispatchers to check tickets before they leave the office, especially for new accounts, special orders, and edited deliveries.

A simple ticket review should confirm the customer name and location, propane product, requested or estimated gallons, tank and delivery notes, pricing or account instructions, and any message the driver needs to see. It takes less time to catch an error at the desk than to untangle it after a truck is loaded.

Also teach dispatchers how to handle ticket changes once a route is out. A driver may call with an inaccessible tank, a customer may cancel, or a delivery may be larger or smaller than expected. The office needs a clear process for recording the change so the delivery history, billing, and next scheduling decision remain accurate.

Train for Exceptions, Not Just Normal Days

A dispatcher who can process ordinary work is useful. A dispatcher who can stay organized when a truck breaks down or temperatures drop sharply is invaluable. Build exception training into the first few weeks instead of waiting for a crisis.

Use short scenarios: a driver calls in sick, a route is over capacity, a customer says they have no heat, a tank is blocked, or a payment issue prevents a delivery. Ask the trainee what they would check first, who needs to be notified, and where the outcome should be documented.

The right answer depends on your company policy, customer history, weather, driver availability, and safety concerns. What matters is that the dispatcher does not make promises they cannot keep. Clear communication protects the customer relationship and gives the operation room to make the best available decision.

Give New Dispatchers a Measurable Ramp-Up Plan

Avoid putting a new hire alone at the dispatch desk after two days of shadowing. Start with customer updates and call documentation, then let them enter orders, review scheduled accounts, build portions of routes, and finally run a full day with an experienced person available for questions.

Review their work daily at first. Look for duplicate orders, incomplete notes, missed delivery instructions, unusual gallons, route inefficiencies, and tickets that needed correction. Feedback should be specific: show what happened, explain the operational impact, and demonstrate the correct process.

When dispatchers understand the reason behind the work, they make better decisions when the phones are ringing and the weather turns. Give them accurate records, a dependable process, and enough supervised practice to handle the next busy day with control instead of guesswork.

A card payment should not create another job for the office. Yet that is often what happens when a fuel dealer uses a separate credit card terminal: the payment is run at the counter or over the phone, then someone has to find the customer record, enter the payment again, apply it to the right invoice, and reconcile the batch later. When comparing integrated payments versus terminals, the real question is not just how the card gets approved. It is how much work happens after approval.

For a fuel oil or propane company, payments touch customer service, deliveries, receivables, accounting, and month-end reconciliation. A simple terminal may be perfectly workable for a very small operation with limited card volume. But as payment volume grows, disconnected processes can create double entry, unapplied cash, and time-consuming questions about who paid what.

What a Payment Terminal Does Well

A traditional payment terminal is a standalone device used to accept credit and debit cards. It may sit on the office counter, connect to a phone line or internet connection, or travel with a driver. The employee enters the sale amount, runs the card, and receives an approval or decline.

Terminals have a few practical advantages. They are familiar, generally quick to set up, and can keep accepting cards even when the office software is not open. If you occasionally take a walk-in payment or need a backup way to process a card, a terminal is a straightforward tool.

The limitation is that the terminal usually does not know anything about your customer account. It does not know whether the payment belongs to a budget customer, an automatic delivery account, a will-call order, or a customer with several open invoices. It only knows the amount entered and the card transaction.

That means the office still has work to do. Someone must record the payment in the fuel delivery system, apply it correctly, handle any overpayment or short payment, and make sure the day’s terminal batch matches the deposit and the customer ledger. None of these jobs are difficult by themselves. The problem is doing them repeatedly during the busy season, when calls are coming in and delivery tickets need attention.

How Integrated Payments Change the Workflow

Integrated payments connect card processing directly to the software where customer accounts and invoices are managed. An employee opens the customer record, chooses the invoice or balance to pay, enters the card details, and processes the payment from that same screen. Once approved, the payment is recorded against the account.

That connection matters most in routine office work. A customer calls to pay for yesterday’s delivery. Instead of running a card on one device and posting a payment in another system, the customer service representative can handle both steps together. The account balance updates immediately, and the payment is tied to the correct customer record.

For dealers taking recurring or stored-card payments, integration can also reduce the chance of charging the wrong account or leaving a payment sitting in an undeposited-funds account with no clear customer reference. It gives the office a cleaner trail from the customer conversation to the payment record to the accounting entry.

Integrated processing does not mean a business never needs a physical card reader. If you regularly take cards at a counter, at a trade desk, or in the field, hardware may still be part of the setup. The difference is whether that card transaction flows into the customer and invoice records automatically or has to be entered again by hand.

Integrated Payments Versus Terminals: The Daily Difference

The best comparison is not a feature checklist. It is a normal winter workday.

With a standalone terminal, an office employee may take ten card payments between customer calls. Each transaction is approved quickly, but each one still needs to be posted. If the customer has multiple deliveries or an old balance, the employee must decide how to apply the payment. At the end of the day, someone compares the terminal total with the posted payments. A missed entry may not show up until a customer calls asking why the account still shows overdue.

With integrated payments, the payment begins from the customer record. The employee can see the balance, select the invoice, and post the card payment in the same workflow. The transaction is still subject to card approvals, processor rules, and occasional declines. But the administrative step after the approval is smaller because the system already knows whose account is being paid.

That can be especially useful when one person handles phones, payment questions, will-call orders, and dispatch support. In a small fuel business, the person taking a payment is often the same person answering a delivery question thirty seconds later. Fewer screens and fewer handwritten reminders help that person keep moving without losing track of the account.

Cost Is More Than the Processing Rate

A terminal can appear less expensive because the device cost or monthly fee is easy to see. Integrated processing may involve software-related fees, gateway fees, or a different processing rate. Dealers should ask for clear pricing and compare the full cost before making a decision.

But the processing rate is not the only cost. Time spent posting payments, correcting misapplied transactions, tracking down missing entries, and reconciling batches has a cost too. So does the risk of releasing an account from credit hold based on a payment that was approved on a terminal but never entered in the delivery system.

For some dealers, a standalone terminal remains the right financial choice. If card payments are infrequent, invoices are simple, and one person can reconcile them in a few minutes, the savings from integration may be limited. For a company processing cards daily across many customer accounts, the labor savings and cleaner records can outweigh a modest difference in transaction costs.

The right question to ask is: what does each payment actually cost after office time is included? Measure the time from the customer giving a card number to the payment being fully reflected in the customer balance and accounting records.

Reporting and Reconciliation Matter at Month-End

Fuel dealers depend on accurate receivables. You need to know who owes money, which invoices remain open, which customers are on credit hold, and whether the payment deposit matches what was posted.

A separate terminal creates two sources of information: the terminal report and the customer ledger. They must agree, but they do not automatically agree. Refunds, voids, duplicate charges, and payments applied to the wrong account all require someone to investigate the difference.

Integrated payments can make reporting more useful because transaction details are connected to the customer record. The office can see a payment, the invoice it paid, the date it was processed, and the remaining balance without switching between systems. When the fuel delivery software also sends payment information to QuickBooks Online, there is less duplicate data entry between the office ledger and the accounting file.

That does not remove the need for controls. Someone should still review daily card activity, confirm deposits, and make sure refunds or chargebacks are handled promptly. Integration reduces repetitive entry. It does not replace sound bookkeeping.

Security and Customer Convenience

Payment security is another reason to look beyond the terminal itself. A terminal may reduce exposure because card numbers are entered directly into a payment device instead of written on paper. Integrated systems can also help limit who sees or handles sensitive card data when they are designed to tokenize and securely store payment details through the processor.

Ask the provider exactly how stored cards, receipts, refunds, user permissions, and payment data are handled. Avoid keeping card numbers in customer notes, spreadsheets, or paper files. No payment setup can protect a business if employees are still writing full card details beside the phone.

Convenience also affects collections. When an employee can take a payment while looking at the customer’s balance and delivery history, the conversation is clearer. The customer gets confirmation that the right invoice was paid, and the office is less likely to promise a delivery release before the account has been updated.

When a Terminal Is Still the Better Fit

There is no prize for buying more technology than your operation needs. A terminal may be the better fit if you take only a handful of card payments each week, do not need payments tied to invoices automatically, or need a simple backup method during a temporary software or internet issue.

It can also make sense for a business that takes most payments by check, ACH, or cash and only uses cards for occasional walk-ins. In those cases, the discipline of posting payments promptly may matter more than adding integration.

The decision changes when employees spend meaningful time re-entering payments, when open balances are often disputed, or when payment posting affects delivery decisions. Those are signs that the separation between the terminal and the customer ledger is creating operational friction.

What to Ask Before You Choose

Before selecting either option, walk through your own payment process from the first phone call through bank reconciliation. Find out whether payments can be applied to specific invoices, whether customer balances update right away, how refunds are handled, and what reports are available at the end of the day.

Also ask about processor pricing, contract terms, equipment costs, support, and what happens if an internet connection fails. A low advertised rate is not helpful if the workflow leaves the office with extra work or the support team cannot answer questions during heating season.

For dealers using Degree Days Online, integrated payment processing can keep card payments connected to the same customer, delivery, and accounting workflow used every day. The point is not to add another system. It is to remove a step that does not need to be manual.

Choose the payment method that lets your office answer the phone, collect the money, update the account, and get back to serving customers without a stack of payment slips waiting at the end of the day.

A fuel dealer can spend months comparing screens, features, and price sheets, then still make the wrong choice if the software does not hold up during a cold snap. That is why fuel software reviews are useful – but only when you read them with your own daily operation in mind. A glowing review from a large regional marketer may not mean much to a 10-truck heating oil company that needs faster ticket printing, cleaner call-in order handling, and less double entry in the office.

The right system should make the daily work easier. It should help your team know who needs a delivery, get tickets to drivers, keep customer records current, take payments, and move financial information into accounting without creating another pile of work. Reviews can point you toward that kind of system, but they rarely tell the whole story on their own.

How to Read Fuel Software Reviews Like an Operator

Start by looking at who wrote the review. A propane dealer with commercial accounts, a full-service heating oil company, and a company delivering mostly automatic residential accounts can all have different priorities. Their comments may be honest, but their needs may not match yours.

Pay closer attention when a reviewer describes a workflow that sounds familiar. For example, a dispatcher who says scheduling is easier after temperature data is loaded into the system is giving you more useful information than someone who simply says the product is “great.” The same goes for comments about printing delivery tickets, finding delivery history during a customer call, handling COD orders, or cutting down on end-of-day paperwork.

Also read negative reviews carefully. A complaint is not always a deal-breaker. Sometimes it shows that a company expected enterprise-level customization from an affordable system built for small and mid-sized dealers. Other times, it reveals a real operational problem, such as poor support, slow access during busy hours, or accounting records that do not transfer correctly. The difference matters.

Look for patterns instead of reacting to one extreme opinion. If several users mention that support answers the phone, training is practical, and dispatch is easy to learn, that is meaningful. If several users report the same issue with tickets, scheduling, or payment processing, ask the vendor direct questions before you commit.

What Good Fuel Software Reviews Should Tell You

The best reviews explain whether the software handles actual fuel delivery work, not just whether the interface looks modern. Fuel delivery is a specialized business. Your software has to account for degree days, tank sizes, delivery intervals, will-call customers, weather changes, route planning, price changes, and the reality that the phone starts ringing when temperatures drop.

Scheduling that matches how you deliver

Automatic delivery scheduling is often the first place a dealer sees the difference between general business software and fuel-specific software. A useful review should tell you whether the system supports degree day scheduling, calendar day scheduling, and daily call-in orders. You need the flexibility to manage different customer types without maintaining separate spreadsheets or guessing who is getting low.

Ask whether the software lets you review suggested deliveries before tickets are printed. Automation is valuable, but the dispatcher still needs control. A good system helps you build an efficient delivery list while leaving room for local knowledge, unusual usage, storm forecasts, customer requests, and truck capacity.

Customer records that answer the phone faster

When a customer calls, your staff should not have to search through paper tickets or switch between several programs to answer basic questions. Reviews should mention whether users can quickly see account details, delivery history, balances, tank information, notes, and past service activity.

This is not just an office convenience. Clear customer records can prevent unnecessary runouts, reduce repeat calls, and help your team give customers a straight answer. If an office manager says the software eliminated hunting for old tickets, that is a practical benefit worth paying attention to.

Tickets and driver paperwork that do not slow the day down

Many dealers are moving away from handwritten tickets, but a digital system still has to work with the way drivers and dispatchers operate. Find out how delivery tickets are created, printed, corrected, and retained. A ticket process that takes extra clicks for every stop can become a real burden over a full heating season.

Reviews are especially helpful here because users tend to be specific. They may mention whether tickets are easy to read, whether route paperwork is ready on time, and whether the office can locate a completed delivery without digging through filing cabinets. Those details tell you more than a feature list ever will.

Payments and accounting that reduce double entry

Your dispatch system should not create more accounting cleanup. If you take credit card payments, check whether the software handles payment activity within the same customer workflow your office already uses. Then ask how that information moves into your accounting system.

For many small fuel dealers, QuickBooks Online integration is a major consideration. The question is not simply whether an integration exists. Ask what transfers, when it transfers, and what your staff must still enter by hand. A system that reduces duplicate data entry can save time every day and reduce the chance of billing mistakes.

Reviews Cannot Replace a Real Demonstration

A review can tell you what another dealer experienced. It cannot show you how the software will handle your own customer list, delivery area, pricing structure, and office routine. Before choosing a system, make the vendor walk through the jobs your team performs every day.

Bring real questions to the demonstration. Show them how you currently schedule automatic accounts. Ask how a call-in delivery gets onto the truck list. Ask what happens when a customer changes payment information, needs a copy of an old ticket, or has a delivery question while the driver is already out. Ask how local temperature readings are updated and how you can adjust a delivery before the ticket is printed.

A vendor that understands the fuel business should be able to answer these questions plainly. You should not need a technical translator to understand how the system handles a basic dispatch task.

Training deserves the same attention. Even good software creates frustration if your team is left to figure it out during the busiest month of the year. Ask whether training is included, whether support is available when you need it, and whether the people answering support questions understand fuel delivery operations. A low monthly price is only a bargain if the system gets used correctly.

Price Matters, but So Does the Cost of Working Around Software

Fuel dealers are right to watch costs. Software should pay for itself through less paperwork, fewer repeated entries, faster office work, and better control of deliveries. Still, comparing monthly subscriptions alone can lead you in the wrong direction.

A cheaper system is not cheaper if it forces your staff to keep separate spreadsheets, re-enter invoices, or track customer notes outside the program. On the other hand, an expensive enterprise platform may be more than a local dealer needs if it comes with a long implementation, complicated settings, and features nobody uses.

Look for transparent pricing and ask what is included. Find out whether training, support, updates, payment processing, accounting integration, and additional users change the monthly cost. You should know what the bill will be before you move customer records and commit your operation to a new system.

Degree Days Online was built from experience inside a family-owned fuel delivery business, with a focus on the everyday work that smaller fuel oil and propane dealers need handled: scheduling, tickets, customer records, temperature updates, payments, and accounting connections. That background matters because the best software decisions are made around the dispatcher’s desk, not a generic feature checklist.

Questions to Ask After Reading Reviews

Once reviews have narrowed your options, use them to build a better vendor conversation. Ask whether the system supports your mix of automatic and will-call accounts. Ask how quickly a new employee can learn the dispatch process. Ask how customer delivery history is displayed, how tickets are generated, and how corrections are handled after a delivery.

You should also ask what happens when the weather changes quickly. Can the office update temperature information and adjust scheduling without starting over? Can dispatchers add same-day orders without losing track of the planned route? These are the questions that separate software that looks good in a demo from software that helps on a busy winter morning.

Finally, ask for a clear explanation of support. Fuel delivery does not run on a nine-to-five schedule during peak season. You want to know who will help when a ticket issue, payment question, or scheduling problem interrupts the day.

The most useful review is the one that leads you to test the software against your own operation. Put your busiest day on the table, ask the hard questions, and choose the system that helps your people get the next truck out the door with less paper, less rework, and more confidence.

The truck has already made the delivery, the signed ticket is back in the office, and someone still has to turn that work into an invoice. When that step depends on a stack of paper tickets, a spreadsheet, and rekeying information into accounting software, automated heating fuel billing is not a luxury. It is a practical way to stop completed deliveries from sitting around waiting to become cash.

For a fuel oil or propane dealer, billing touches nearly every part of the operation. Customer pricing, tank rental, delivery quantities, taxes, discounts, account balances, credit cards, and accounting records all need to line up. The right system reduces repeat entry and gives the office a clearer view of what has been delivered, billed, paid, and still needs attention.

What automated heating fuel billing should do

Automation should not mean giving up control of your billing. It should mean the system carries information forward from the work your team has already completed.

A delivery ticket should become the starting point for an invoice, not a separate clerical project. The customer record should supply the correct billing address, payment terms, tax settings, and pricing rules. The delivered gallons and delivery date should flow in from dispatch. Once the invoice is created, it should be available for payment processing and ready to move into your accounting workflow.

That is the basic chain: customer record, scheduled or call-in delivery, ticket, invoice, payment, and accounting entry. When those steps live in disconnected programs or on paper, employees have to bridge the gaps by hand. Every handoff creates an opportunity for a missed ticket, wrong price, duplicate invoice, or payment posted to the wrong account.

A useful billing system also needs to handle the work that does not follow a perfect pattern. A driver may return with a short delivery. A customer may call with a pricing question. A commercial account may need a purchase order on its invoice. A customer may pay by card after the delivery is complete. Good automation makes routine work faster while leaving the office staff able to review exceptions before they become problems.

Where manual billing costs fuel dealers

The obvious cost is labor. An office employee who enters delivery data in one program, creates invoices in another, and then posts payments separately is doing the same job more than once. During a cold stretch, that extra work piles up quickly.

The bigger cost is often delay. If tickets are waiting to be entered, invoices go out later. If invoices go out later, payments arrive later. That can put pressure on cash flow at exactly the time you are buying more product and running more trucks.

Manual work also makes it harder to answer simple customer questions. When a customer calls asking whether a delivery was billed, the person taking the call may have to search a ticket file, check accounting software, and look through payment records. With connected records, the answer should be available from the customer account: what was delivered, when it was invoiced, what is due, and whether a payment has been received.

Mistakes matter, too. A billing error can be more than an annoyance. Underbilling costs margin. Overbilling creates a customer service problem and can make a long-term customer question every future invoice. Automation cannot prevent every error, but it can eliminate common causes such as typing the wrong number of gallons or using an outdated customer address.

Start with clean customer and pricing records

Billing automation works only as well as the information behind it. Before changing the billing process, take a hard look at customer records. Make sure active accounts have the right delivery address, billing address, contact information, tax status, payment terms, and price plan.

Pricing deserves special attention. Fuel dealers may use fixed pricing, market-based pricing, budget plans, contract pricing, cash discounts, or different rates for different locations under the same account. The system needs rules that fit how you actually sell fuel. If the office has to override pricing on every other invoice, the problem is not the billing clerk. The setup does not match the operation.

This cleanup takes time, particularly when moving from paper files or aging software. It is worth doing carefully. Bad data moved faster is still bad data. Start with active customers and current price agreements, then build a process for cleaning older records as they come back into use.

Connect dispatch, tickets, invoices, and payments

The best time to capture delivery information is when the delivery is being planned and completed, not days later when someone is trying to read handwriting from a ticket. Dispatch records should support billing by keeping the customer, location, product, price, and delivery details together.

After the ticket is completed, billing staff should be able to review it and create the invoice without re-entering the basics. That review step still matters. Automation is not a reason to bill blindly. It is the chance to catch a no-delivery, partial delivery, price exception, or note that needs to appear on the invoice.

Payment processing should also fit the same workflow. If a customer pays by credit card, office staff should not need to jump between unrelated screens and then manually mark the invoice paid. Integrated payment processing reduces that back-and-forth and gives the customer account a more current balance.

For many dealers, accounting integration is the next critical piece. A billing system should not create a new round of data entry at the end of the day. When invoices and payments transfer cleanly to QuickBooks Online, the office avoids maintaining two versions of accounts receivable. The bookkeeping team can focus on reviewing exceptions and reconciling activity instead of retyping transactions.

Degree Days Online was built around these connected daily workflows, including delivery scheduling, ticket printing, billing, payment processing, and QuickBooks Online integration. The goal is straightforward: let a completed delivery move through the office without being entered over and over.

Decide what to automate and what to review

Not every billing step should run without a person looking at it. The right balance depends on your customer mix and the way you price fuel.

Routine residential deliveries with established pricing are good candidates for a fast, automated invoice process. The information is predictable, and the office mainly needs to watch for exceptions. Commercial accounts, will-call deliveries, contract accounts, and accounts with unusual tax or purchase-order requirements may need more review.

Use clear rules for the situations that deserve a hold. For example, flag tickets with a price override, a quantity outside the normal range, a new account, a past-due balance, or a delivery note from the driver. This keeps the team from inspecting every ordinary transaction with the same level of effort while still protecting against expensive mistakes.

It also helps to decide when invoices should be sent. Some companies bill immediately after ticket review. Others run a daily batch after the last tickets arrive. Neither approach is automatically better. Immediate billing can improve speed, while a daily batch may fit an office that needs a supervisor to review activity first. The important point is consistency and a process that does not leave work stranded over a weekend or holiday.

Measure the result in the office and on the bank balance

You do not need a complicated dashboard to know whether billing is improving. Track the age of unbilled tickets, the time from delivery to invoice, the number of invoice corrections, and the time required for daily posting. Watch accounts receivable aging as well. Faster, more accurate billing does not guarantee faster payment, but it gives customers fewer reasons to delay.

Ask the people doing the work where time is still being lost. Dispatchers may see tickets that do not make it to billing. Customer service staff may be fielding calls caused by unclear invoices. Bookkeepers may be fixing duplicate entries after the fact. Those details tell you where the process needs attention.

Automated heating fuel billing pays off when it removes repeat work without forcing your operation into a process that does not fit. Get the customer and pricing records right, connect each step from delivery through payment, and keep people focused on the exceptions that actually need judgment. Then the office can spend less time chasing paperwork and more time serving customers and collecting for fuel already delivered.

A customer calls at 8:10 a.m. asking when their propane will arrive. Before you can answer, the driver needs a ticket, a will-call order has to be entered, and someone is checking whether an account is past due. That is where the difference between propane software vs generic CRM becomes real. One system is built around getting fuel delivered correctly. The other is built around managing sales relationships.

A generic CRM can keep names, notes, and follow-up reminders. For some businesses, that is enough. But propane dealers are not just tracking prospects. They are managing tanks, gallons, routes, degree days, delivery history, payment status, and a busy office that cannot afford to enter the same information three times.

What a Generic CRM Does Well

Generic customer relationship management software is designed for broad use. A contractor, insurance agency, manufacturer, or sales team can use it to track leads, record phone calls, manage opportunities, and set reminders. If your main goal is to organize sales activity, it can be a useful tool.

For a propane company, a CRM may help your office document a new customer inquiry or remind a salesperson to call on a commercial prospect. It can provide a cleaner view of contacts than a spreadsheet and give managers a basic record of communication.

The problem starts when the CRM is asked to run daily delivery operations. Most generic systems do not understand what a tank monitor reading means, how degree days affect a customer’s next delivery, or why a route must be built before tickets are printed. They can often be customized, but customization is not the same as having the right workflow from the start.

A dealer can spend months adding fields for tank size, product type, estimated usage, delivery zone, pricing plan, and service notes. Even then, the dispatch board, ticket process, and accounting workflow may still live in separate programs or on paper. That creates more handoffs, more double entry, and more chances for a mistake during the busiest part of the heating season.

Propane Software vs Generic CRM in the Dispatch Office

Purpose-built propane software starts with the work your office already does every day. It is not trying to turn a fuel delivery business into a sales department. It is designed to help you see who needs fuel, schedule deliveries, create tickets, record completed deliveries, and keep customer records current without hunting through separate systems.

The practical difference comes down to context. A generic CRM sees a customer as a contact with an account record. Propane software sees a customer as a delivery account with a location, tank details, fuel history, payment information, delivery requirements, and a place in the day’s workload.

Scheduling is more than setting an appointment

In a generic CRM, scheduling usually means putting a call, meeting, or task on a calendar. That is useful for a salesperson. It does not solve automatic delivery scheduling.

Propane delivery scheduling has to account for actual usage patterns. Depending on the account, that may mean degree day scheduling, calendar day scheduling, or handling a customer who calls in when they need fuel. The office needs a workable delivery list, not a reminder that says, “Check in with customer.”

When the system tracks delivery history and local temperature data, it can help the dispatcher make better decisions before a customer runs low. That is the kind of automation that reduces emergency calls and gives your drivers a more organized day.

Tickets and delivery records cannot be an afterthought

A CRM can store an attachment or a note after a delivery. But that is backward from how a fuel dealer operates. The ticket needs to be available before the truck leaves, and the completed delivery needs to update the customer record when the route is done.

Purpose-built software supports the daily ticket workflow. Your office can prepare and print delivery tickets, drivers have clear information for each stop, and completed deliveries become part of the account history. That matters when a customer calls with a question about their last fill, their current balance, or a delivery instruction from last winter.

Paper tickets and disconnected software create their own cost. Someone has to sort them, key them in, file them, and find them later. The office may get through the day, but it is spending time on work the system should handle.

Fuel delivery data has to be useful to the people answering the phone

A customer record is only valuable if your staff can act on it quickly. When the phone rings, the person answering should be able to see recent deliveries, account notes, order history, and payment status without opening several tabs or asking someone in the back office to look it up.

Generic CRMs are good at collecting notes. Fuel delivery software is built to make those records operational. It puts the information in the context of the next delivery, the current order, and the customer’s account. That makes a difference on a cold Monday morning when every caller needs an answer now.

The Hidden Cost of Making a CRM Fit

A generic CRM may look less expensive at first, especially if you already use one for marketing or sales. But the monthly subscription is only part of the cost. You also need to count setup time, custom fields, integrations, user training, outside consultants, and the ongoing work required to keep information matched between systems.

Then there is the cost of workarounds. Maybe dispatch keeps a separate spreadsheet because the CRM cannot build delivery lists the way the office needs. Maybe tickets are created in another application. Maybe payments are taken in one system and entered again for accounting. Each workaround adds steps and gives errors a place to enter.

That does not mean every propane dealer must replace a CRM. If you have a dedicated sales team pursuing new commercial accounts, a CRM can still be useful alongside your delivery system. The key is to give each tool the job it does best. Do not expect a lead-management platform to carry the operational load of a fuel business.

When Propane Software Is the Better Fit

Propane software is usually the better choice when deliveries are central to your business and your office is still depending on paper, spreadsheets, or aging programs to hold the process together. It is especially valuable if you need to automate delivery scheduling, manage daily call-in orders, print tickets, process credit cards, and connect operational records with QuickBooks Online.

Small and mid-sized dealers often do not need enterprise software with a long implementation project and a price that keeps climbing. They need a system that their dispatcher can learn, their office can trust, and their owner can afford. That is why industry-specific tools matter. They are built around the work instead of forcing the work to fit the software.

Degree Days Online was developed from inside a family-owned fuel delivery business, and that background shows in the details: delivery scheduling, local temperature updates, ticket printing, customer records, payment processing, and accounting integration are part of the same operating picture. For most companies, clear monthly pricing and free training also make the decision easier to evaluate.

Ask These Questions Before You Choose

Before signing up for any system, walk through a normal winter day with the vendor. Ask how you will identify accounts that need delivery. Ask how a call-in order is entered, how a ticket is printed, and what happens after the driver completes the stop. Ask where payment information appears and whether the completed work reaches your accounting process without repeated data entry.

You should also ask what happens when a dispatcher is out, a customer has a special delivery instruction, or a driver returns with a ticket that needs attention. Software should make those routine exceptions easier to manage, not send your team back to paper notes.

The right choice is not the system with the most sales features or the flashiest dashboard. It is the one that helps your office get accurate deliveries out the door, keep customers informed, and finish the day with fewer loose ends.

A will call account can look simple on paper: the customer calls when they need fuel, you take the order, and a truck delivers it. In a busy heating season, that approach can turn into a stack of notes, repeat phone calls, missed promises, and drivers asking whether an order was actually approved. To manage will call customers well, your office needs a clear process from the first phone call through the completed delivery ticket.

Will call business is valuable. Some customers prefer control over when they order, and some accounts are not a fit for automatic scheduling. The problem is not will call itself. The problem is treating every order as a one-off transaction without a system that shows what was promised, what is due, and what is already on the truck.

Why Will Call Orders Create Office Problems

Automatic customers follow a planned schedule based on degree days, calendar days, tank information, or delivery history. Will call customers do not. Their needs arrive at different times, often when your phones are already busy and your delivery board is full.

A customer may call at 8:00 a.m. and say they are out of fuel. Another may request delivery “sometime this week.” One may have a credit hold. Another may have a driveway that requires a smaller truck after a storm. If those details live only in the memory of the person who answered the phone, the office is relying on luck.

The usual trouble starts with handwritten notes, loose order pads, or messages passed from one employee to another. Orders can be entered twice, delivery instructions can be missed, and a customer may call back because no one can quickly tell them where their delivery stands. During cold weather, those small gaps become expensive service problems.

Set Clear Rules Before You Take the Order

Every will call order should begin with the same questions. That does not mean making the call feel scripted or impersonal. It means giving your staff a reliable way to collect the information dispatch needs.

First, confirm the delivery address, product, requested gallons, and when the customer needs delivery. “Need it soon” is not a delivery commitment. Ask whether the customer is out, how much fuel is likely in the tank, whether the system has been shut down, and whether there are any access issues. A no-heat call deserves different handling than a customer who simply wants to top off before the weekend.

Next, check the account before promising a truck. Review the balance, credit status, payment method, prior delivery history, and any account notes. A long-standing customer with a regular payment history may be handled differently from a new account or one with an overdue balance. The point is not to make every call difficult. It is to prevent the dispatcher from finding a problem after the order has already been placed on a route.

Your policy should also define what “will call” means at your company. For example, establish whether orders are handled first-come, first-served; whether minimum gallon requirements apply; whether emergency deliveries carry an extra charge; and how late in the day an order can be accepted for next-day delivery. Customers do not need a lecture on policy, but employees need the authority and consistency to apply it.

Keep Every Will Call Order in One Place

The strongest improvement most fuel dealers can make is moving orders out of paper notes and into the same system used for customer records, deliveries, and tickets. When order information is entered once, the dispatcher sees the same details the office person heard on the phone.

A complete order record should show the date and time of the request, the product and gallon amount, the requested delivery date, order priority, pricing instructions, payment status, and delivery notes. Notes matter. Gate codes, dogs in the yard, a hard-to-find fill pipe, a restricted bridge, or a request to call before delivery can all affect whether the driver completes the stop.

It also helps to use clear statuses. An order should not disappear into a general list where nobody knows whether it has been reviewed. Use simple working stages such as received, approved, scheduled, dispatched, delivered, or held. The exact names are less important than making them visible to everyone who touches the order.

When a customer calls back, your staff should be able to answer a basic question in seconds: Is the order scheduled, and when can we reasonably expect delivery? That level of visibility cuts down on repeated calls and gives the office more confidence during the busiest days.

Manage Will Call Customers by Priority, Not Volume

Not every call-in order belongs at the top of the delivery board. A customer who is truly out of fuel, an elderly customer with no heat, or an account with a confirmed runout should receive immediate attention. A top-off request with plenty in the tank may need to wait until it fits an efficient route.

This is where practical dispatch judgment matters. Sending a truck across the territory for a small, non-urgent order may satisfy one customer while throwing off an entire day’s route. On the other hand, delaying a verified no-heat customer can damage a relationship that took years to build.

Give office staff a few priority categories and define them plainly. Emergency or no-heat calls are one group. Same-day requests that can fit the route are another. Routine orders with flexible timing are a third. A fourth group may be accounts that need payment approval, updated credit information, or a conversation with management before delivery.

Priority should be based on urgency and service commitment, not on who calls the most. That protects your team from pressure at the phone counter and makes the dispatch board easier to manage.

Give Customers a Realistic Delivery Window

Many will call frustrations start with a promise that was never realistic. Saying “we will get there today” may sound helpful, but it creates a problem if the order was taken after the trucks were loaded or if weather changes the route.

Use language that matches the actual status of the order. If the order is approved but not routed, say that it is on the list for the next available delivery day. If it is assigned to a truck, provide a reasonable window without promising an exact arrival time unless your operation can support it. If a same-day delivery is possible but not guaranteed, say so directly.

Customers generally handle a clear answer better than a vague promise. They become frustrated when they arrange their day around a delivery that was never firmly scheduled. A short confirmation call or text can be useful for special situations, but only if your team has a dependable way to send it and record the communication.

Connect Payment, Pricing, and Dispatch

Will call orders often require more payment attention than automatic deliveries. A customer may want to pay by card, request a cash-on-delivery delivery, or have an account balance that changes whether the order can go out. Those details cannot be left for the driver to sort out at the driveway.

Before the order reaches dispatch, make sure the payment expectation is clear. If a card needs to be processed, process it according to your policy. If the driver must collect payment, mark that instruction plainly on the ticket. If pricing is locked for the order, record it so the office and customer are working from the same number.

Separating this work from dispatch creates double entry and missed details. A fuel delivery system that keeps customer records, call-in orders, ticket printing, and payment activity together gives the office a cleaner handoff. Degree Days Online was built around that daily workflow, so an order can move from the phone call to the delivery ticket without rebuilding the information in separate systems.

Train the Team for Exceptions

A good process handles normal orders quickly, but it also gives employees a path for exceptions. New customers, abandoned accounts, emergency runouts, bad-weather access, price disputes, and requests outside the delivery area should not force the person answering the phone to guess.

Create a short internal playbook for the situations that come up repeatedly. Include who can approve credit exceptions, who decides whether to send an emergency delivery, what to do when a customer disputes a balance, and how to document a no-heat call. Keep it practical enough that staff will actually use it.

Drivers should also be part of the loop. If a driver finds a buried fill, an unsafe driveway, an empty tank that needs a restart, or a customer who was not home for a required payment, that information needs to return to the customer record. The next person taking a will call order should not be surprised by something your company already learned last week.

Review the Orders That Went Sideways

The best time to improve your will call process is not while three phone lines are ringing. Once a week, review the orders that caused extra work. Look for duplicate calls, late deliveries, credit issues found too late, missed notes, route detours, and customers who repeatedly report low fuel.

Some will call customers may be better candidates for automatic delivery. Do not force the change, but explain the benefit when the pattern is clear. A customer who runs low several times each winter may appreciate a degree day or calendar day schedule once they understand it means fewer emergency calls and less worry about running out.

For the accounts that remain will call, consistent records and honest communication are what keep the work under control. The goal is not to turn every phone order into a complicated procedure. It is to make sure each order is clear enough that the office, dispatcher, driver, and customer all know what happens next.

The first hard cold snap is a poor time to find out which automatic customers are running shorter than expected, which routes have too many stops, or which will-call accounts have been calling the office all morning. A solid guide to seasonal fuel delivery planning starts well before the weather turns. It gives your office, dispatchers, and drivers a workable plan for keeping customers supplied without creating unnecessary miles, overtime, and last-minute panic.

Seasonal planning is not about predicting every gallon perfectly. Weather changes, customers move, equipment fails, and call-ins will always happen. The goal is to build a delivery operation with enough control to handle those changes without losing track of your margin or your customer service.

Start Seasonal Fuel Delivery Planning With Clean Customer Data

Bad customer information creates bad delivery decisions. Before the heating season, review the records that drive your automatic delivery schedule: tank size, fuel type, estimated annual usage, heating equipment, delivery history, account status, and delivery instructions.

Pay close attention to accounts that have changed hands, added a generator, converted equipment, or had an unusually low or high prior season. A customer who insulated an attic, installed a heat pump, or spent part of last winter away from home may not use fuel the same way this year. On the other hand, a new addition, an elderly family member moving in, or a poorly performing boiler can push usage up quickly.

Tank size deserves a second look, especially when old records were entered from paper files. Scheduling an assumed 275-gallon tank as though it were a 330, or treating a 120-gallon propane cylinder bank like a larger residential tank, can leave too little room for error. Accurate account notes also save drivers from avoidable return trips. Gate codes, steep-driveway warnings, preferred delivery locations, and dogs on the property matter when the schedule is tight.

If your team is still updating one system, writing tickets in another place, and checking payment status somewhere else, seasonal preparation becomes slower than it needs to be. One current customer record should give the office the information needed to schedule, dispatch, deliver, and bill the order.

Set Delivery Rules That Match How Customers Use Fuel

Not every account should be managed the same way. Automatic delivery customers need a reliable consumption model. Will-call customers need clear communication and enough capacity in the daily schedule to be served without disrupting planned routes. Commercial accounts may require fixed delivery windows, larger drops, or more conservative minimum levels.

For automatic accounts, degree day scheduling is often the best starting point because it responds to actual local weather rather than a fixed calendar interval. When temperatures drop, projected usage rises and the next delivery moves forward. When the weather moderates, the schedule adjusts instead of sending a truck too early.

Calendar day scheduling can still make sense for steady-use accounts, certain commercial customers, or accounts where usage patterns are well understood. The key is not to force every customer into one scheduling method. A mixed customer base usually needs mixed rules.

Set sensible minimum and target delivery levels based on tank size, route frequency, and access conditions. A customer near the end of a remote route may need a larger safety cushion than one located near your yard and easily served every day. Propane accounts with difficult winter access, seasonal roads, or high-use appliances need the same practical judgment.

Do Not Treat a K Factor as Permanent

A K factor is useful, but it is not sacred. It is an estimate based on past usage, and estimates need to be checked against real deliveries. Review unusual drops throughout the season. If an account is consistently being delivered too early or too late, adjust the consumption factor before it becomes a pattern.

This is where current temperature readings and delivery history pay off. Dispatchers should not have to calculate degree days by hand or search through old tickets to understand what happened at an account. The faster you can see actual usage against the schedule, the faster you can make a sensible correction.

Build Routes Around Geography, Not Just Gallons

A truck can carry enough fuel for the day and still have an unprofitable route. Too much windshield time, backtracking across town, and small out-of-the-way drops eat up driver hours and truck capacity. Seasonal route planning should group deliveries by geography first, then balance the gallons and account priorities within each area.

Look at last season’s routes before the rush begins. Identify neighborhoods that repeatedly get split between trucks, areas with frequent emergency calls, and routes that regularly run long. A small route adjustment made in October is much easier than reshuffling drivers during a January storm.

There is always a trade-off. Filling every truck to the maximum may look efficient, but it can reduce flexibility for will-calls, run-outs, and high-priority customers. Leaving some room in the daily plan is not wasted capacity if it prevents an expensive extra trip later in the day.

Set route cutoffs that reflect your real delivery area and staffing. If the office accepts late call-ins until the last minute, dispatch cannot build stable routes. Give customers clear expectations about when they need to call, while keeping room for genuine emergencies. Consistency is better for your team and easier for customers to understand.

Plan for Peak Weeks Before They Arrive

Every fuel dealer knows the weeks that test the operation. A long stretch of below-normal temperatures can turn a manageable schedule into a wall of tickets overnight. You cannot eliminate the pressure, but you can decide ahead of time how your company will respond.

Start with staffing. Know which drivers are available for extended hours, who can cover a route if someone is out, and whether office staff can handle a jump in incoming calls. Confirm truck maintenance, tire condition, spare hoses, printer supplies, and any equipment that could stop a truck at the wrong time.

Next, decide how dispatch will prioritize work when demand spikes. A practical order may put low-tank automatic customers, elderly or vulnerable customers, accounts with no backup heat, and committed commercial deliveries ahead of routine requests. The exact policy depends on your customer base, but the office should not be inventing it during a weather event.

A peak-week plan should also cover communication. Customers do not need a long explanation. They need honest expectations. If severe weather is slowing deliveries, tell them when possible. If a will-call customer is approaching a critical level, get the facts, identify whether they have backup heat, and give dispatch the information needed to make the right call.

Keep Call-In Orders From Taking Over Dispatch

Will-call business is part of the fuel business, but it should not be allowed to erase the value of automatic scheduling. When every order is handled as a fresh emergency, the office spends the day answering the same questions, drivers make more scattered trips, and dependable customers can get pushed aside.

Make it easy for staff to see a customer’s last delivery, recent usage, current balance, and route area before promising a delivery date. A caller who says they have a quarter tank may be fine for several days, while another customer with a small tank, high usage, and no backup heat needs attention sooner.

Payment status belongs in the same conversation. It is easier to handle a credit card payment or resolve an account issue while the customer is on the phone than to send a truck out with unclear instructions. Bringing payment processing, delivery records, and dispatch information together reduces double entry and gives the office a clearer picture of each order.

Make Daily Dispatch Visible and Repeatable

Seasonal planning only works if the daily process follows it. Each morning, dispatch should review scheduled deliveries, new call-ins, no-access accounts, special instructions, truck capacity, and any customers nearing a critical projected level. At the end of the day, delivered gallons, missed stops, and route changes need to update the records that drive tomorrow’s schedule.

Paper tickets and manual spreadsheets can handle a small number of stops, but they become a problem when the volume rises. Handwritten changes get missed, the office re-enters information, and nobody is fully sure which version of the schedule is current. Fuel delivery software built around automatic scheduling, ticket printing, local temperature updates, and daily call-ins can keep the moving parts in one place.

Degree Days Online was built from inside a fuel delivery operation, so the workflow reflects what dealers actually need during the season: manage accounts, load temperature data, schedule deliveries, print tickets, take payments, and keep office work moving without paying for an oversized enterprise system.

Review the Plan While the Season Is Still Underway

Do not wait until spring to learn where the plan failed. Review routes, run-outs, emergency deliveries, overtime, and repeated customer calls every few weeks. If one town is creating too many extra miles, revise the route pattern. If certain automatic accounts keep falling outside the expected schedule, check their factors and tank details.

Also watch for work that should not be manual. Repeated phone calls for payment information, duplicate entry between dispatch and accounting, or time spent hunting for old delivery tickets are operational costs. They may not show up as a line item on a route report, but they take time away from serving customers and managing exceptions.

The best seasonal delivery plan is not the one that looks perfect on paper in September. It is the one your team can follow on a cold Tuesday in February, when the phones are ringing, the trucks are loaded, and customers need a clear answer.

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.