Custom Software for Propane and Fuel Delivery Companies

You are guessing at a number you cannot see

Most trades know exactly what work is in front of them. A plumber has a call, a roofer has a signed contract, a landscaper has a route that repeats every week. Fuel delivery is different in a way that shapes the entire business: the work exists only when a tank somewhere is low, and nothing about that tank announces itself.

So you predict. You take the tank size, the last fill, the weather since, and a rough sense of how that particular house burns, and you decide whether the truck goes today. Get it wrong in one direction and you send a bobtail down eleven miles of county road to put in ninety gallons. Get it wrong in the other and the customer runs out on the coldest night of the year, which means an emergency delivery, a pressure test, a relight, and a customer who now knows a competitor exists.

The uncomfortable part is that most companies make this prediction with a rotation schedule and a dispatcher’s memory. Both work, and both are invisible assets that walk out the door the day that person retires.

The tank is the record, not the customer

The most useful structural decision in this business is making the tank the primary record instead of the customer account. Customers move. Houses get sold. A single commercial account might have six tanks across three sites, each with a different size, a different burn pattern, and a different last-filled date.

Once the tank is the record, everything that matters hangs off it:

• Physical facts — size, serial, manufacture date, whether you own it or the customer does, and the rent you charge if you do.
• The delivery history, in gallons and dates, which is the raw material for every forecast you will ever make about this location.
• A burn rate calculated for this specific tank rather than a company average, because two identical houses on the same street routinely differ by half.
• Compliance dates — the last leak check, the regulator age, the requalification date on a cylinder — that arrive whether anyone is tracking them or not.
• Site access notes that only exist in a driver head today: the gate code, the dog, the driveway that a bobtail cannot turn around in after rain.
• The equipment downstream of it, so a service call on the furnace and a delivery to the tank feeding it are visibly the same customer relationship.

That last point about access notes sounds minor until a regular driver is out sick in February. Knowledge that lives only in one person’s head is knowledge you pay for twice.

Forecasting is ordinary math nobody is doing

Degree-day forecasting has been standard in this industry for decades, and the arithmetic is genuinely simple: gallons delivered divided by degree days accumulated gives you a consumption rate for that tank. Project forward using the forecast and you know roughly when it hits your reorder percentage.

The reason it often is not done well has nothing to do with the math. It is that the delivery history lives in the billing system, the degree days live nowhere, and the route gets built the night before from a printed list. A system that joins those three things gives you something a rotation never can:

• A daily list of tanks projected to cross the reorder threshold, ranked by urgency rather than by alphabet or by whose turn it is.
• Route building that groups due tanks by geography, so a driver is not passing three accounts that will be due in nine days to reach one that is due today.
• Flags on tanks whose consumption suddenly broke pattern, which is how you find a leak, a tenant who moved out, or a customer quietly buying from someone else.
• Tank monitor telemetry folded in where it exists, so a real reading overrides the estimate without requiring a separate portal to check.
• Will-call accounts held to a different rule than keep-fill accounts, because the liability and the service promise are not the same.
• A record of how accurate yesterday forecast turned out to be, so the model gets better instead of staying a guess forever.

Improving average gallons per stop is the quiet lever in this business. The driver, the truck, and the miles cost nearly the same whether you deliver two hundred gallons or eighty. Every stop you avoid making twice is margin you did not have to sell anything to earn.

Pricing is where the complexity actually lives

Ask an owner what makes their office slow and it is rarely the deliveries. It is that the same gallon of propane has five different prices depending on who received it.

A typical book carries retail customers on a posted price that moves with the market, budget plan customers paying a level monthly amount against an annual estimate, prebuy customers drawing down gallons purchased in July at a locked rate, commercial accounts on a fixed differential over an index, and a set of long-standing customers on a rate that exists because of a handshake in 2014.

When pricing rules live in a person rather than in the system, three things follow. Invoicing takes days instead of hours. Prebuy balances get tracked in a spreadsheet that nobody reconciles until someone runs out of gallons and argues. And nobody can tell you your margin per gallon by segment, which means the annual decision about how many gallons to hedge is being made on feel.

Attach the pricing rule to the account and the delivery ticket prices itself. That is not a sophisticated capability. It is the difference between a month-end that consumes a week and one that does not, which is the same case made in custom invoicing software.

The truck is where the data should be born

Everything the office needs is known at the moment the hose comes off the tank. Gallons pumped, meter reading, time on site, tank percentage before and after, whether the driver noticed a rusted tank leg or a regulator past its life.

If that information arrives as a stack of tickets at four in the afternoon, you have built a business that is always one day behind itself. Capture at the truck has to survive a real route:

• Delivery recorded at the tank — gallons, meter, percentage — so the invoice and the forecast both update the same evening rather than after somebody keys in a stack of paper.
• Offline tolerance as a hard requirement, because rural delivery routes lose signal constantly and a tool that stalls in a dead zone will be abandoned by week two.
• Photos of tank condition, regulator, and piping attached to the tank record, which turns a driver observation into a service lead instead of a comment nobody wrote down.
• Delivery stops that do not happen logged with a reason — blocked driveway, locked gate, dog out — so the pattern is visible rather than repeating monthly.
• Compliance events captured where they occur, since leak checks and system tests done in the field are worth nothing to you if the paperwork proving it is in a binder.
• Driver hours and truck volume tracked against the route, so you know the real cost of serving the outer edge of your territory.

The routing and dispatch half of this is a problem shared with every trade that sends trucks out, and it is covered in more detail in field service scheduling software for small companies. What is unusual here is that the route is generated from a forecast rather than from a list of customer requests.

Service is a second business sharing your trucks

Most fuel companies also install and service the equipment burning the fuel: tank sets, regulator replacements, furnace and water heater work, generator installs, cylinder exchange. It is good, profitable work, and it is frequently the worst-tracked part of the operation.

The reason is structural. Delivery is a high-volume, low-variation transaction that gets a proper system. Service is a low-volume, high-variation transaction that gets a whiteboard. So parts go on a truck and never make it onto an invoice, a service call for a delivery customer gets discounted by habit, and nobody knows whether the service side earns its own keep or is quietly subsidized by gallons.

Putting both against the same customer and the same tank is what makes the picture honest — what this relationship is worth in total, and which half is paying for the other.

Why the packaged options frustrate people

There are real fuel-industry platforms, and plenty of companies run on them well. The complaints that push owners toward a custom build are consistent:

• Pricing models are rigid — budget plans, prebuy drawdowns, and index-linked commercial contracts each get handled by an export to a spreadsheet.
• Forecasting is a company-wide setting rather than a per-tank calculation, which makes it accurate on average and wrong on the accounts that matter.
• The delivery system and the service system are separate products, so a customer with both looks like two unrelated records.
• Reporting stops at gallons and revenue, and cannot produce margin per gallon by segment, cost per stop, or gallons per mile by route.
• Adding a second or third product line — off-road diesel, kerosene, cylinder exchange, generator service — means bending fields designed for one product.
• Pricing scales with tank count or user count whether or not the capability you are paying for grows with your book.

The honest framing is that custom is not automatically right. A single-product residential keep-fill operation on one retail price should buy something off the shelf and get on with it. The case for building gets strong when the mix is real — several products, delivery alongside service, a book split across budget, prebuy, and contract pricing — because that mix is exactly what general products handle by making you work around them. That is the same test laid out in custom software versus off-the-shelf.

What this connects to

A system for this business earns its keep by joining things that are currently separate:

• Accounting, so delivery tickets, service invoices, and budget plan billing post without anyone retyping them.
• Tank monitoring hardware, where a real level reading should quietly replace an estimate rather than living in its own vendor portal.
• Automatic payment collection, since card and ACH on file turns a seasonal receivables problem into a routine one.
• A customer portal showing tank level, delivery history, budget plan balance, and remaining prebuy gallons — which removes a large share of the calls your office takes in January.
• Supply and inventory, so what you bought, what is in the bulk plant, and what went on trucks reconcile without a monthly hunt.

The accounting link is worth doing properly rather than as an afterthought. A delivery season generates thousands of small transactions, and hand-keying them is both the most repetitive job in the office and the one where an error repeats all winter — which is exactly the problem a QuickBooks integration is meant to remove.

Built around how your operation actually runs

Brad Walker has spent more than twenty years building operational software, working with dispatch-driven and route-based businesses from his base in Wake Forest, NC. Fuel delivery work always starts with the same questions: how many tanks do you serve, how is tomorrow route decided today, how many pricing plans are in the book, and what does a driver capture before the truck gets back. The answers decide what gets built and what gets left alone.

Engagements are fixed price, with the scope agreed before development starts. You know what you are getting, what it costs, and when your office and your drivers will have it.

Frequently asked questions

If tomorrow route is decided by a rotation and a dispatcher’s memory, or your prebuy balances live in a spreadsheet one person maintains, that is a fixable systems problem. Start the conversation. The first step is a discovery call to map how tanks, routes, and pricing move through your operation today and where they are costing you.