Vertical SaaS · Saas

Petroleum and Fuel Distribution Vertical on Acumatica

Petroleum and Fuel Distribution Vertical on Acumatica: a practical Acumatica fit review focused on availability, replenishment, warehouse execution, landed cost, and order allocation. It separates documented product capability from configuration, integration, and customisation work.

John Kihiu12 min read

Petroleum distribution — fuel jobbers, bulk plant operators, retail fuel networks — is the vertical in this series where I give the most qualified recommendation, and I want to lead with the qualification rather than bury it: bulk liquid fuel with metered delivery, temperature-compensated volume, and terminal-rack pricing is a specialized enough domain that native Acumatica Distribution Edition does not cover it out of the box, and the realistic path for most fuel distributors is a specialized third-party ISV solution built on or integrated with Acumatica, not a from-scratch build on core Inventory.

Why standard Inventory Management does not fit metered fuel delivery directly

Standard Acumatica inventory transactions assume discrete, countable units received and issued at known cost. Bulk fuel breaks that model in a few specific ways: volume is temperature-sensitive (a gallon of diesel at 60°F is not the same mass/energy as a gallon at 95°F, and terminal invoices are often net or gross gallons depending on contract), delivery is metered from a truck compartment with calibration and shrinkage/evaporation loss that has to reconcile against the terminal's loaded volume, and rack pricing at the terminal changes multiple times a day, requiring cost capture at time of lift rather than a static purchase price. None of that is what generic Inventory receipt/issue transactions were designed to model.

Do not let a client assume "Inventory Management handles fuel"

I have had exactly this expectation walk into a discovery call — "it's just inventory, right?" It is not. Temperature compensation tables (API gravity correction), terminal rack pricing feeds, and compartment-level truck loading are a specialized data model that generic distribution ERPs, Acumatica included, do not ship. Setting this expectation correctly in the first meeting avoids a much more expensive correction mid-project.

The realistic path: a fuel-industry ISV solution, with Acumatica as the financial backbone

The pattern that actually works, and the one I recommend, mirrors the auto-dealership answer: use Acumatica for what it is strong at — GL, AP/AR, multi-entity consolidation, and general merchandise inventory (a bulk plant's convenience-store or non-fuel product line fits Distribution Edition natively) — and integrate a specialized fuel-industry system for the fuel-specific operations: bulk terminal lifting, compartment tracking, temperature compensation, and retail site price-book management. Acumatica's Marketplace and integration partners include petroleum-focused ISV solutions built specifically for this; evaluate those rather than treating "just customize Inventory Management" as a serious option, because the volume-and-temperature math alone is a domain most ERP consultants (myself included, without partnering with a fuel-industry specialist) should not be reinventing from scratch.

C# · POSTING A FUEL LIFT AS A GL-ONLY JOURNAL (NOT INVENTORY QTY)
// For clients not ready to adopt a dedicated fuel ISV, a minimal interim
// pattern: record terminal lifts as GL-level cost, tracked by a custom
// "gallons lifted" reporting field, rather than forcing gallons through
// standard INTran quantity/cost logic that assumes stable unit cost.
var je = new PXGraph<JournalEntry>().CreateInstance<JournalEntry>();
je.BatchModule.Current.Description = $"Terminal lift {liftDate:yyyy-MM-dd} — {gallons} gal @ rack {rackPrice:C}";
// gallons and rack price stored as UDFs for reporting; GL amount is what
// actually reconciles to the terminal invoice.

What does fit natively: the non-fuel side of the business

Convenience-store merchandise, lubricants and packaged products, equipment/parts for a bulk plant's service operations, and the AP/AR/GL consolidation across multiple sites are all a good, boring Distribution Edition fit — the same Inventory/Purchasing/WMS modules covered elsewhere in this series apply cleanly to that half of a petroleum distributor's business. The fuel itself is the specialized part.

Wrapping up

Petroleum distribution is the one vertical in this series where my default recommendation is not "customize Acumatica" but "use Acumatica for the financials and non-fuel inventory, and pair it with a dedicated fuel-industry solution for bulk liquid handling." Anyone who tells a fuel distributor that core Inventory Management alone covers metered, temperature-compensated fuel delivery has not actually built it.

John Kihiu
Acumatica ERP Developer · Laravel Engineer

Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.