At 5:30 a.m., a delivery ticket is not just paperwork. It tells a driver where to go, what to deliver, which tank to fill, and what to do when something is different at the account. When tickets are missing details, printed out of order, or changed after the truck leaves, the office spends the day chasing answers instead of dispatching loads.
Knowing how to print delivery tickets properly starts before you touch the printer. The ticket is the final output of your customer records, delivery schedules, call-in orders, route planning, and pricing. If those details are right, printing tickets should be one of the quickest parts of the morning. If they are wrong, a faster printer will not fix the problem.
Start with delivery information you can trust
Before printing a route, dispatch should review the information that will appear on each ticket. For a heating oil or propane dealer, that usually means the customer name, delivery address, account number, product, scheduled quantity or estimated gallons, price or price plan, tax status, tank location, and special delivery instructions.
The details that save drivers the most time are often the ones entered in a short note field. A gate code, a warning about a low wire, a request to call before delivery, or a note that the fill is behind the garage can prevent an unnecessary call back to the office. Keep those notes current. A ticket that carries a five-year-old instruction is not much better than a blank one.
Customer records also need a clear delivery status. Do not print accounts that are on credit hold, marked do-not-deliver, or awaiting a customer callback unless someone has approved the exception. This is especially important during a cold snap, when the office is moving quickly and a small mistake can turn into a delivery dispute.
How to print delivery tickets by route
The best workflow is to print tickets by truck and route, not as one large stack sorted by customer name. Your driver should receive tickets in roughly the same order as the day’s planned stops. That reduces sorting at the rack and makes it easier for the driver to spot a missing ticket before pulling away.
First, finalize the day’s deliveries. This can include automatic degree-day deliveries, calendar-day deliveries, and call-in orders. Then assign those deliveries to the appropriate truck or route. Once assignments are set, review the route for duplicate deliveries, accounts with unusual quantities, out-of-area stops, and customers whose account notes call for special handling.
After that review, print the route as a batch. Batch printing matters because it gives the office a complete, consistent set of documents for that truck. Printing one ticket at a time may work on a light day, but it creates more opportunities for tickets to be skipped, mixed between drivers, or printed with changes that were never communicated.
A practical morning check should confirm three things: every assigned delivery has a ticket, every ticket is assigned to the correct truck, and the ticket count matches the route count in dispatch. This takes a few minutes and can save hours of cleanup later.
Print after the route is stable, not before
There is a trade-off here. Printing early gives drivers more time to load and organize paperwork. Printing too early means a late call-in order, price change, or route reassignment can leave outdated tickets in the driver’s hands.
For many dealers, the right approach is to build routes ahead of time but print after the route has been reviewed and approved. If a route changes after printing, do not rely on a verbal instruction alone. Print a replacement ticket or clearly mark the original, then make sure the driver knows which version controls.
Use a ticket layout that works at the delivery location
A clean ticket layout should be easy to read in a truck cab, at a customer’s tank, and back in the office. It does not need to look fancy. It needs to put the right information where the driver can find it quickly.
The top of the ticket should make the customer and delivery location obvious. Product, quantity, price information, delivery date, and route or truck identification should be clear without forcing the driver to hunt through a crowded form. Account notes should stand out enough to be noticed, but not so prominently that routine instructions overwhelm the page.
If you print tickets for customers to sign or retain, include the information needed for a clear record of what was delivered. That may include delivery quantity, unit price, total amount, taxes, delivery date, and any required company or regulatory information. Your exact format can depend on your operation, state requirements, and whether the ticket is used as an invoice, delivery record, or both.
Paper size is also a practical decision. Full-page tickets give you room for notes, pricing, and signatures. Smaller formats can reduce paper handling and fit better with certain truck setups. There is no universal answer. Choose the format that your drivers can use reliably and your office can file or scan without extra work.
Check the printer setup before the busy season
A ticket process is only as dependable as the equipment behind it. A printer that jams twice a week may seem like a minor annoyance in July. On the first hard-freeze morning, it can delay every truck in the yard.
Make sure the office has a designated printer for delivery tickets, enough paper or forms on hand, fresh toner or ink, and a backup plan if that printer fails. Test the layout whenever you change printers, update operating systems, or revise the ticket form. A field that looks fine on screen can print too close to the edge, cut off account notes, or split important information across pages.
It also helps to set a standard for who can reprint tickets and how replacements are labeled. Duplicate tickets can cause confusion when they reach the wrong driver or get processed twice. A simple reprint record protects the office when someone asks later why two documents exist for the same delivery.
Keep ticket printing connected to dispatch
Manual ticket preparation creates double entry. Someone writes or types the delivery list, another person prepares tickets, and a third person later enters completed deliveries into accounting or customer records. Every handoff is a place where gallons, prices, or account details can be changed by mistake.
A fuel-delivery management system should let dispatch build the route from live customer and delivery data, then print tickets directly from that route. When delivery records, scheduling, and ticket printing are connected, the ticket reflects the same information the dispatcher used to plan the day.
That is especially useful when you manage automatic delivery customers alongside call-ins. Automatic deliveries can be scheduled from degree-day or calendar-day usage patterns, while call-ins are added as needed. Both should end up in one dispatch view so the office can assign, review, and print them without maintaining separate paper lists.
Degree Days Online is built around this type of daily workflow, including delivery scheduling, customer records, route-based ticket printing, and the operational details fuel dealers deal with every day. The point is not to add another system for the office to manage. It is to stop re-entering the same information across schedules, tickets, and delivery records.
Give drivers a simple process for exceptions
Even a well-printed ticket cannot prevent every issue in the field. A customer may have an inaccessible tank, a locked gate, a different requested quantity, or a payment question. The ticket should give the driver enough information to make the right first call, but the office needs a consistent way to handle exceptions.
Ask drivers to clearly mark undeliverable stops, partial deliveries, unusual tank conditions, and customer instructions that differ from what is printed. If your operation uses electronic delivery confirmation, make sure the office can still see the original scheduled details alongside the completed delivery information. That comparison helps resolve questions about estimated gallons versus actual gallons delivered.
Do not treat handwritten driver notes as an afterthought. Review them before the next schedule is built. A note that says “new tank on east side” or “dog loose after 3 p.m.” belongs in the customer record, not buried in a completed ticket stack.
Make the last check part of the routine
The goal is not to create a long morning meeting around a printer. It is to build a repeatable process that catches the errors that cost real time and money. Before tickets leave the office, verify the route order, customer notes, product and quantity, pricing rules, and ticket count. Then hand each driver one organized route package instead of a stack that needs sorting in the cab.
A good delivery ticket process is quiet. Trucks leave on time, drivers know where they are going, customers get the right delivery record, and the office is not rebuilding the day from handwritten corrections. That is the standard worth printing toward.