How to architect revenue operations for a propane distribution company in 2027

What a propane revenue architecture actually is, and why the usual playbook breaks

A propane distributor is not a SaaS company, not a contractor, and not a commodity trader — it is a recurring-delivery, asset-heavy business where the same customer generates revenue two to six times a year, forever, as long as the tank stays in the ground and the truck shows up before the gauge hits 20%. That single structural fact reshapes every revenue decision. Retention is not a churn-reduction program; it is the entire business model. Acquisition is not a volume game; it is a geography game. And pricing is not a positioning exercise; it is a spread management exercise against a wholesale cost that moves daily.

Start with the P&L shape. A distributor buys propane at a rack or terminal price, stores it in bulk plant tanks, and delivers it into customer-site tanks that the company often owns outright. The revenue line is gallons × retail price. The cost line above gross margin is gallons × wholesale cost. Everything else — trucks, drivers, insurance, tank depreciation, the bulk plant, the service techs — sits below that spread and is largely fixed in the short run. This is why the industry's operating metric is cents per gallon of gross margin, and why a company selling more gallons at a thinner spread can be less profitable than a smaller competitor with dense routes and disciplined pricing.

Three structural forces make this different from general distribution businesses:

Wholesale cost volatility is the dominant variable. Propane is a hydrocarbon gas liquid whose price tracks crude, natural gas processing economics, export demand, and regional storage levels. A wholesale price that sits at $1.10 in September can reach $1.60 during a cold snap in January. If a meaningful share of your book is on fixed-price contracts written in the fall, that swing lands entirely on your margin. The revenue architecture has to know, at any moment, how much of the next 90 days of volume is priced, unpriced, hedged, or exposed.

Route density compounds. Truck cost per day is roughly constant whether the driver makes eight stops or fourteen. Every incremental stop inside an existing cluster is nearly free margin; every stop eight miles off the cluster consumes drive time that could have served two closer accounts. This makes geography a first-class field in the CRM, not a shipping detail.

Tank ownership creates a switching cost that cuts both ways. When the company owns the tank, the customer cannot simply call a competitor — a tank swap means a pump-out, a set, and usually a fee. That stickiness produces retention rates most industries would envy. It also means a bad account is genuinely hard to fire, and that a company-owned tank sitting at a low-margin, low-volume, far-flung address is capital parked in the wrong place. Tank turns matter: a 500-gallon tank that delivers 900 gallons a year at 80 cents of margin is a very different asset than one delivering 300 gallons at 55 cents.

Layer on seasonality. In most heating markets, 65-75% of annual gallons move between October and March. Revenue operations therefore has two distinct modes: a shoulder-season mode focused on acquisition, tank sets, contract renewals, pre-buy enrollment, and route redesign; and a peak-season mode focused on execution, runout prevention, credit and collections, and margin defense. Trying to run one operating cadence across both is a common failure.

The practical implication for anyone who wants to architect this properly: the system of record is not the CRM. It is the fuel-delivery ERP — Cargas Energy, ADD Systems, Blue Cow Software, and similar platforms built for this vertical — because that is where customers, tanks, delivery history, degree-day usage factors, pricing tiers, and invoices actually live. The CRM sits upstream as an acquisition layer. Accounting sits downstream. Route optimization and tank telemetry sit alongside. If you invert that and try to make a general-purpose CRM the hub, you end up with two customer lists that disagree about which tank is where.

The step-by-step build: from lead to recurring delivery to protected margin

The core revenue process is acquire-to-recurring-delivery, and it should be engineered as one continuous chain with explicit handoffs rather than six disconnected departments.

Step one: qualify by geography before qualifying by intent. When a lead arrives — web form, referral, HVAC dealer, builder relationship, a homeowner whose current supplier missed a delivery — the first system action is a distance calculation against existing automatic-delivery accounts. Address geocodes, then measures to the nearest route cluster. A lead within two miles of an existing cluster with a 500-gallon tank and whole-home heating is a different animal from a lead eleven miles out with a 120-gallon cylinder set for a grill and a dryer.

Step two: profile expected annual usage before quoting. Heating load, appliance count, square footage, and construction vintage produce an estimated annual gallon figure. That number, multiplied by your target margin, is the account's contribution. Quote against contribution, not against the competitor's posted price.

Step three: set the tank and capture every field the downstream systems need. Tank size, serial, ownership, location on the property, fill-point access, dog on premises, gate code, seasonal road conditions. Missing data here becomes a failed delivery in February, which becomes a runout, which becomes a leak check, a pressure test, and a very unhappy customer.

Step four: enroll in automatic delivery and set the usage factor. Automatic delivery — the distributor forecasts consumption from degree-day data and prior fills, then schedules refills — is the single highest-leverage conversion in the business. It moves the delivery date under your control, which is what makes route building possible. Will-call accounts force reactive, low-density trips.

Step five: forecast, cluster, and dispatch. The ERP projects each tank's percentage remaining by date. Route optimization builds the day's stops around the accounts crossing threshold, then fills remaining truck capacity and driver hours with nearby accounts that will need gas soon anyway — topping off a neighbor at 45% is often better economics than driving back next week.

Step six: deliver and capture. Meter reading, gallons, price applied, tank percentage before and after, driver notes. This is the data that trains the usage factor for next time.

Step seven: price, bill, collect. Apply the account's pricing program — variable market, fixed-price contract, pre-buy drawdown, budget plan, or cap. Invoice same-day or next-day. In peak season, a distributor can float an enormous receivable balance in a matter of weeks; collections discipline in January is a margin issue, not an accounting chore.

Step eight: retain and expand. Annual contract renewal, budget plan re-enrollment, service work, additional appliances, a second tank for a shop or generator. Generator accounts in particular are worth chasing: they add gallons with almost no incremental route cost because the tank is already on the stop.

Two control points in that chain protect the economics more than all the others combined. The first is automatic-delivery enrollment with an accurate usage factor, because it converts unpredictable demand into a schedulable workload. The second is the pricing-and-hedging junction, because it determines whether the gallons you worked so hard to deliver actually carry a spread.

Tank telemetry, and what the data layer is worth

The highest-return architecture decision available to a distributor in this decade is putting monitors on tanks and feeding that telemetry into the pricing and dispatch layer — not into a standalone dashboard that a dispatcher glances at.

Monitors read tank level, typically report over cellular or a gateway, and push readings into the ERP through an API. Vendors in this space include Tank Utility, SkyBitz, and Anova, among others; most price as hardware plus an annual connectivity subscription, with hardware amortized across several years of service. Treat the total per-tank annual cost as an underwriting question: if a monitored tank prevents one runout every few years and enables one additional efficient fill per season, it pays for itself quickly. Runouts are expensive in a way that does not show up on a fuel invoice — a runout requires a leak check and system restart by a qualified technician, consumes a truck slot and a service slot, and is the single most common reason a customer with a company-owned tank goes through the trouble of switching suppliers.

The integration detail matters. A monitor that only triggers "this tank is low, go fill it" recreates will-call with extra steps. A monitor whose reading flows into the ERP's forecasting and pricing engine lets you ask a better question: given current wholesale cost, this account's contract price, and the cost of this stop on today's route, what is the margin on filling this tank today versus in four days? During a wholesale spike, that question has a real answer — defer discretionary fills on variable-price accounts, prioritize fixed-price accounts only when route density absorbs the hit, and let telemetry tell you exactly how much runway each tank has before deferral becomes a service failure.

Telemetry also cleans up the usage factor. Degree-day forecasting is good but coarse; it assumes a household's consumption scales predictably with weather. Real tanks reveal the outliers — the customer who installed a wood stove, the rental that sat empty, the shop heater running twelve hours a day. Those accounts are simultaneously the biggest runout risks and the biggest wasted-trip risks. Set a coverage target and track it as an operating KPI: a majority of automatic-delivery accounts monitored within a year, the large-volume and high-variance accounts first, remote and hard-to-reach accounts next because those are where a wasted trip costs the most.

Two adjacent notes. First, this same telemetry pattern is what heating oil dealers, industrial gas suppliers, and bulk chemical distributors have converged on — the operating problem is identical: an owned vessel at a customer site, a consumption rate you must predict, and a delivery cost you must amortize. If you are evaluating vendors, the heating oil side of the market is worth watching because the software often serves both fuels. Second, telemetry data has a secondary use in credit management: a customer whose consumption pattern changes sharply is often a customer whose circumstances changed, and that is a signal worth having before the receivable ages.

Costs, timelines, and what a realistic build looks like

Budget and sequencing questions come up immediately, so here is the honest shape of the work.

Fuel-delivery ERP. These are vertical platforms sold per-user or per-module, usually with a meaningful implementation engagement. Data migration is the long pole: customer records, tank records with serials and locations, delivery history needed to seed usage factors, open receivables, contract terms, and pricing tiers. Expect the implementation to run months rather than weeks, and expect it to reveal that your tank records are less accurate than you believed. Never cut over during heating season. The realistic window is a spring cutover with a full summer to stabilize before October.

Route optimization. Some fuel ERPs include routing; others integrate with dedicated optimization tools. The evaluation question is whether the tool understands the constraints that actually bind: truck capacity in gallons, driver hours, DOT hazmat requirements, bulk plant reload trips, and the fact that a partial fill is legitimate. A generic last-mile delivery optimizer designed for parcels will produce routes a propane dispatcher cannot use.

Tank telemetry. Hardware plus annual connectivity per tank, installed by a service tech during a scheduled visit rather than as a dedicated trip. Rolling installation across normal service calls is far cheaper than a monitor deployment campaign.

CRM. A general-purpose CRM — HubSpot, Salesforce, Pipedrive, or similar — is worth it if you run outbound acquisition, builder relationships, or a dealer channel. If your growth is entirely referral and inbound, the ERP's own customer records may be enough. Do not buy a CRM to store customers you already have; buy it to manage prospects you do not.

Accounting integration. QuickBooks or a mid-market platform like Sage Intacct on the back end, with the ERP pushing invoices, payments, and inventory movements. The integration exists to produce one number reliably: gross margin per gallon by period, by route, and by customer segment.

Sequencing. A defensible order is: ERP first and correct, because everything downstream reads from it; then accounting integration so margin reporting is trustworthy; then route optimization once your tank and address data is clean; then telemetry rolled out over one or two service cycles; then CRM and acquisition scoring last, because there is no point routing more leads into a system that cannot tell you which leads are profitable. Attempting all five in parallel during one calendar year is how these projects end up half-implemented with staff running shadow spreadsheets.

Hedging and pricing tooling. Smaller distributors typically manage exposure through supplier contracts and pre-buy purchases rather than financial instruments. Larger books justify swaps, caps, or futures through a broker. Either way, the architecture requirement is the same: the system must show how many gallons of forward commitment you have sold at fixed prices and how many of those gallons you have covered on the buy side. That reconciliation is the difference between a hedging program and a hope.

Where teams get it wrong

Chasing gallons instead of margin. The most common failure. A distributor grows volume 18% and profit falls, because the incremental gallons came from accounts priced to win against a competitor and located outside existing clusters. Fix the compensation plan: pay reps on first-year gross margin contribution, weighted higher for accounts inside dense zones and enrolled in automatic delivery, lower for will-call or remote accounts. Reps optimize for what you pay them for; if you pay for gallons, you will get scattered, thin gallons.

Treating fixed-price contracts as a sales tool rather than a risk position. Selling a fixed price to a customer is selling forward volume you have not yet bought. If wholesale moves against you and the position is uncovered, the loss is real and lands in your worst cash month. Every fixed-price gallon sold should increment a forward-commitment counter that the buy side sees.

Letting will-call persist by default. Will-call accounts feel like flexibility and are actually a tax. They generate emergency trips, break route plans, produce most of your runouts, and are disproportionately the accounts that shop on price. Run a conversion campaign each shoulder season with a concrete incentive — a per-gallon differential, a service plan inclusion, waived delivery fees — and track penetration as a headline metric.

Ignoring the cost of a runout. A runout is not one missed delivery. It is a truck trip, a technician visit for the leak check and relight, a regulatory obligation, an unhappy customer, and elevated churn risk on a customer you might otherwise have kept for fifteen years. Price the prevention accordingly.

Building reports on gallons because gallons are easy to count. If the weekly management report leads with volume, the organization will manage volume. Lead with cents per gallon, then margin per route-day, then automatic-delivery penetration, then runouts, then aged receivables. Volume belongs on the report — fourth or fifth.

Deploying telemetry as a monitoring dashboard. Covered above, but it is worth repeating because it is the most expensive version of "we did the project and nothing changed." If the readings do not reach the forecasting and pricing engine, you bought expensive gauges.

Under-managing receivables in January. In eight weeks a distributor can extend more credit than in the prior six months combined, to customers facing their highest bills of the year. Credit limits, budget plan enrollment, and prepay options are revenue architecture, not collections hygiene.

Cutting over systems in October. Someone always proposes it. The implementation slipped, peak season is coming, and going live "before the rush" sounds efficient. It is not.

A decision framework: what to fix first, and when

Not every distributor needs every layer immediately. Sequence by where margin is actually leaking.

If gross margin per gallon is acceptable but total margin is flat, the constraint is growth — invest in acquisition scoring, dealer and builder channel development, and tank-set programs targeted at zip codes where trucks already run. If gross margin per gallon is compressing, the constraint is pricing and supply — fix contract discipline, segment pricing by cohort, and build the forward-commitment-versus-coverage view before spending a dollar on marketing. If margin per gallon looks fine but margin per route-day is poor, the constraint is density and execution — routing, automatic-delivery conversion, and telemetry.

For platform choice, the deciding variables are book size, complexity, and whether you run multiple fuels or a service department. A single-branch distributor with a few thousand accounts and no service arm can run lean. A multi-branch operation with propane, heating oil, HVAC service, and a cylinder exchange program needs a platform that handles multi-branch inventory, technician dispatch, and service billing without bolt-ons. Buying up-market too early burns cash on modules nobody configures; buying down-market means a painful re-platform in three years.

One more framework worth having: buy versus build growth. Acquiring a competitor's customer book is a standard growth path in this industry, and it is a route-density decision disguised as an M&A decision. A book that overlays your existing clusters can be absorbed with existing trucks and drivers, which makes the acquired gallons dramatically more profitable than they were for the seller. A book in an adjacent county requires a truck, a driver, and possibly a bulk plant — which means the same purchase price buys much worse economics. Your route-density data is the diligence tool, and having it in a queryable form is a reason to build the reporting layer before you go shopping.

Related questions

How is this different from architecting revenue for a heating oil dealer?

Structurally very similar — owned tanks, degree-day forecasting, route density, wholesale spread — and many software platforms serve both fuels. The main differences are regulatory (propane is a hazmat with pressure-vessel rules), tank ownership norms, and propane's broader non-heating uses like generators, agriculture, and forklift cylinders.

Should the CRM or the fuel ERP be the system of record?

The fuel ERP, without exception. It owns tanks, delivery history, usage factors, pricing programs, and invoices. The CRM manages prospects and channel relationships upstream. Two competing customer lists is the most predictable failure mode in this stack.

What automatic-delivery penetration should we target?

Higher is better with essentially no ceiling on the residential heating book. Track it as a percentage of accounts and separately as a percentage of gallons — the gallon-weighted number matters more, because converting your largest-volume will-call accounts moves route economics far more than converting a hundred small ones.

Can a general-purpose ERP like NetSuite work instead of a fuel-specific platform?

Rarely worth it. Tank records, degree-day usage factors, partial fills, per-gallon pricing programs, budget plans, and hazmat delivery documentation all have to be built as customizations that the vertical platforms ship natively. The customization cost usually exceeds the platform premium.

How do we handle margin reporting when wholesale cost changes daily?

Cost gallons on a consistent basis — weighted average or FIFO against actual purchases — rather than against the spot price on the delivery date. Then report the spot-versus-booked variance separately as a supply performance number, so pricing and purchasing are each accountable for their own decision.

FAQ

What is the single most important metric in propane revenue operations?

Gross margin per gallon, expressed in cents. It captures both the pricing decision and the wholesale purchasing decision in one number and can be tracked by account, route, branch, and pricing program. Total gallons sold is a vanity metric that can rise while profit falls.

How do I choose between Cargas Energy, ADD Systems, and Blue Cow Software?

Evaluate on the operations you actually run rather than on feature checklists: multi-branch inventory, service and HVAC dispatch if you have a service arm, cylinder exchange, mobile driver applications, telemetry integrations, and the accounting system you already use. Ask each vendor for references at your book size, and weigh implementation and migration support heavily — the platform differences are smaller than the implementation differences.

Is tank telemetry worth it for smaller distributors?

Usually yes, but roll it out selectively rather than universally. Start with high-volume accounts, high-variance accounts, remote accounts where a wasted trip is expensive, and any account with a runout history. Install during scheduled service visits rather than dedicated trips, and expand as the data proves out.

How much of my book should be on fixed-price contracts?

There is no universal number, but the discipline is: never sell more fixed-price gallons than you can cover on the buy side, and make the coverage ratio visible to whoever approves pricing. Fixed-price programs are excellent retention tools and genuinely valuable to customers — they just have to be underwritten, not improvised.

Should we fire low-margin accounts?

Rarely outright, because company-owned tanks mean exit costs and the account may be salvageable. Reprice at renewal, move to a delivery-fee structure that reflects true route cost, or convert to automatic delivery to improve the economics. Reserve genuine exits for accounts that are remote, low-volume, chronically slow-paying, and unwilling to reprice.

When should we run system implementations?

Spring or early summer, without exception. Cutover, data migration, and staff training all need a shoulder-season runway so the organization is fluent before October. A go-live in peak season risks failed deliveries, and a failed delivery in a cold week is a runout, a service call, and a churn event.

Sources

• https://www.eia.gov/energyexplained/hydrocarbon-gas-liquids/
• https://www.eia.gov/dnav/pet/pet_pri_wfr_a_EPLLPA_PWR_dpgal_w.htm
• https://www.npga.org/
• https://propane.com/
• https://www.lpgasmagazine.com/
• https://www.cargas.com/software/propane-heating-oil/
• https://www.adsystems.com/
• https://www.bluecowsoftware.com/
• https://www.nfpa.org/codes-and-standards/nfpa-58-standard-development/58
• https://www.fmcsa.dot.gov/regulations/hazardous-materials

Related on PULSE

• [How do you architect revenue operations for a wholesale distribution platform in 2027?](/knowledge/ra0388)
• [How do you architect revenue for an Industrial Distribution business in 2027?](/knowledge/ra0182)
• [Revenue Architecture for Restaurant Supply + Hospitality Smallwares + Foodservice Equipment Distribution Software in 2027](/knowledge/ra0180)
• [Revenue Architecture for Wine + Spirits Distribution + Supplier Software in 2027](/knowledge/ra0177)
• [Revenue Architecture for Craft Beer + Beverage Distribution Software in 2027](/knowledge/ra0176)
• [Revenue Architecture for Specialty Pharma Distribution Software in 2027 (Patient Outcomes, Big-3)](/knowledge/ra0141)