Home
Pricing About Contact Knowledge
App Login Book a Demo
Knowledge Center

Fuel Distribution Software for Packaged Products: DEF, Oil, and Additives

Beyond Bulk

Ask a fuel jobber what they sell and the answer starts with gallons. It is real revenue, it moves every week, and in most offices it lives in a completely different place from the fuel — a second spreadsheet, a second invoicing tool, sometimes a second system entirely, reconciled against the fuel business only when somebody has a spare afternoon.

But walk through most jobberships and the second half of the answer is sitting on pallets and shelves: DEF totes and jugs, motor oil by the case, additives, grease, shop supplies.

That split is where the trouble starts. A customer who buys fuel and DEF on the same week gets two invoices from two places, or one invoice that somebody stitched together by hand. Stock on hand is a guess until somebody walks the warehouse and counts. Tax on packaged goods is calculated one way in the spreadsheet and another way at the accountant's desk. And when the owner asks the simplest question — "how much money did we actually make on packaged goods last month?" — the answer takes a day to assemble, because the numbers live in two systems that never agreed on anything.

The fix is not a better spreadsheet. It is treating packaged goods as what they are: a second product line inside the same business, with the same discipline as the fuel — a catalog, a ledger, invoices, payments, tax, and reports — running in the same system as everything else.

A catalog, not a price list in someone's head

Packaged products start with a catalog of their own. Every item — a DEF tote, a case of 15W-40, a drum of additive, a box of shop towels — is a product with a name, a price, and its own tax setup, kept in one place where the whole office can see it. That matters more than it sounds: when the catalog lives in one person's notebook or in a spreadsheet only one person updates, every price change is a phone call, every new item is a favour, and every invoice is a chance to charge last month's price by mistake.

With the catalog in the system, the price on the invoice is the price in the catalog, and a change made once shows up everywhere the product is sold. The catalog is also where packaged goods stop being a side hustle in the office's mind: once DEF and oil sit in a proper product list next to the fuel products, they get sold, tracked, and reported like products, not like favours.

Inventory that is a ledger, not a count

The part most second systems get wrong is inventory. A spreadsheet that says "47 cases on hand" is a claim, not a record — nobody can say how it got to 47, or when, or who changed it.

Packaged inventory in FuelJobberX is a ledger. Stock moves only through ledger transactions — receive, sale, adjust, void and reversal — each one a dated entry with a running balance, so the quantity on hand is always the sum of everything that happened, not a number somebody typed over. A delivery received adds stock. A sale removes it. A damaged case is an adjustment with a reason, not a quiet edit. A voided sale reverses itself through the ledger instead of disappearing.

That is the same discipline the fuel side already uses, applied to the warehouse. It means the stock-on-hand report and the sales report can never disagree with each other, because they are both reading the same ledger. It means a reorder report can say, plainly, what is running low and what is not moving. And it means that when the count on the shelf and the count in the system differ, there is a trail to walk — every movement, in order, with the adjustment that explains it.

Its own invoices, its own payments

Packaged sales get their own invoice series, with their own numbering, and their own payments ledger. That separation is deliberate: a DEF invoice is not a fuel invoice with different line items, and mixing the two series is how offices end up unable to say what packaged goods are owed, or paid, or overdue.

A customer who buys fuel and packaged goods still gets handled as one customer — the receivables side sees both — but the packaged invoice stands on its own, with its own payments applied against it. The office can answer, without digging, how much a customer owes for packaged goods specifically, what has been paid, and what is still open. And because payments live in their own ledger, a partial payment or a payment across several invoices applies cleanly instead of becoming a note in the margin.

Tax, handled where the sale happens

Packaged goods carry their own tax problem, and it is not the fuel tax problem. Rates, exemptions, and what is taxable vary by product and by customer, and the tax collected on a packaged sale has to be right on the invoice — not fixed up at quarter-end when the accountant finds it.

Packaged Items Tax is set up per product in the same system, and the sales-tax-collected report shows what was actually charged, so the number the office remits is the number the invoices already carry. Purchase Locations sit alongside it — where the goods were bought is recorded with the stock, so a tote of DEF can be traced back to where it came from, not just where it went.

Twelve reports that answer the owner's questions

A packaged-goods line earns its keep when the owner can see it. The module carries twelve reports of its own: invoice register, sales tax collected, stock on hand, sales by customer, reorder, product sales, payments received, margin, inventory movement, AR aging, and the adjustments log, plus the reports hub that gathers them.

Those twelve answer the questions that actually get asked. Which customers buy the most packaged goods? Which products make money and which ones just move? What is sitting on the shelf too long? What is owed, and how old is it? A jobber who can answer those from reports — instead of from a walk through the warehouse and a trawl through the spreadsheet — can decide whether to push DEF harder, drop a slow product, or chase a balance, in the time it takes to open a page.

Frequently asked questions

We already sell DEF — why does it need its own module? Because "already selling it" usually means selling it out of a spreadsheet while the fuel runs in software. The module is the difference between selling packaged goods and managing them: a catalog, a ledger, invoices, payments, tax, and reports that tie together, instead of five habits that only tie together in one person's head.

Does packaged inventory talk to the fuel side? It runs alongside it, in the same system, for the same customers. The fuel invoicing, dispatch, and receivables work the way they always did; packaged goods get their own catalog, ledger, invoice series, and payments inside the same company, so the office works in one place and the customer is one customer.

What happens when stock is damaged or a sale is voided? It goes through the ledger like everything else. Damage is an adjustment entry, a voided sale is a reversal entry, and the running balance updates from the entries. Nothing is edited in place, so the history stays honest and the count stays explainable.

Can I see margin on packaged goods, not just sales? Yes — margin is one of the twelve reports, alongside product sales, sales by customer, and inventory movement. Sales tell you what moved; margin tells you whether moving it was worth it.

Do I have to use all of it at once? No. The module is gated per company, so it is switched on for the companies that sell packaged goods. A jobber who only moves fuel never sees it; a jobber who adds DEF next quarter switches it on and starts with the catalog.

The second business line, in the first system

Most jobbers did not set out to sell packaged goods. They started because a customer asked for DEF with the fuel, or because oil by the case was easy money sitting next to the rack. Then the side line grew, and the office kept running it the way it started — by hand, in a second place, on trust.

That works until it does not: until the stock count is wrong on a big order, until a customer's packaged balance is anyone's guess, until tax time turns into a reconstruction. The packaged-goods module exists so the second business line gets the same treatment as the first — catalogued, ledgered, invoiced, paid, taxed, and reported — without a second system, a second login, or a second spreadsheet that only one person understands.

FuelJobberX handles packaged products alongside bulk fuel: one catalog for DEF, oil, additives, and shop supplies, ledger inventory that only moves through dated transactions, a separate invoice series with its own payments, packaged-items tax with a sales-tax-collected report, and twelve reports that show what the line actually earns. If you want to see your packaged-goods line run the same way your fuel already does, you can book a demo at fueljobberx.com — a walkthrough with real data in under 30 minutes, no sales pressure.

Ready to see it in action?

We'll walk you through the full platform in under 30 minutes — with real data, no sales pressure.

Book a Demo →