A build-to-order ERPNext app for petrol stations and forecourts that ties pump/nozzle meter reconciliation, shift handovers, tank wet-stock and fuel-card sales into one auditable ledger. ECOSIRE builds it to your scope, installs it, and supports it after go-live. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $799.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app for petrol stations and forecourts that ties pump/nozzle meter reconciliation, shift handovers, tank wet-stock and fuel-card sales into one auditable ledger. ECOSIRE builds it to your scope, installs it, and supports it after go-live.
ابھی کوئی ادائیگی نہیں۔ یہ ہماری ٹیم کو قیمت کی درخواست بھیجتا ہے — ہم قیمت اور اگلے اقدامات کے ساتھ ای میل کے ذریعے رابطہ کریں گے۔
Fuel retail is a wet-stock business, not a boxed-goods business. Every litre pumped has to reconcile back to a nozzle meter reading, a tank dip, and cash or fuel-card settlement at shift close — and a variance of even a fraction of a percent across a busy forecourt is real money leaking or being over-charged. ERPNext gives you a solid Sales Invoice, Stock Ledger, and Payment Entry backbone, but out of the box it has no concept of an opening/closing nozzle reading, a calibrated tank dip converted to litres, a pump-to-tank mapping, or a shift cash handover. Operators end up reconciling all of this in spreadsheets that never tie back to the accounting ledger.
Pump/nozzle meter reconciliation: closing minus opening reading, net of test and calibration pours, reconciled against dispensed sales per nozzle
Site modelled as first-class DocTypes — `Fuel Tank`, `Pump`, `Nozzle`, with each nozzle bound to its source tank and fuel product
Shift-wise workflow: opening/closing `Shift Reading`, attendant assignment, and supervisor-authorised cash and card handover at close
Tank dip entry converted to volume through per-tank calibration (strapping) charts and compared to ERPNext book stock
Wet-stock variance report exposing shrinkage, evaporation, temperature swing, and delivery discrepancy per tank per day
Fuel-card and fleet-account sales with credit-limit and account-balance checks against the customer's fleet master
ECOSIRE builds a proper Frappe app that adds the forecourt domain on top of ERPNext rather than bolting it on. We model the physical site as DocTypes — Fuel Tank, Pump, Nozzle (with its bound tank and product), Shift, Shift Reading, Tank Dip, and Fuel Card Account — and post the resulting movements through native ERPNext Stock Entries, Sales Invoices, and Journal/Payment Entries so your GL and stock valuation stay canonical. Nozzle throughput (closing meter minus opening meter, adjusted for test/calibration pours) is computed and reconciled against dispensed sales; tank dips are converted through per-tank calibration charts into volume and compared to book stock to surface shrinkage, evaporation, or delivery discrepancies as a variance report.
The logic lives where it belongs in Frappe. hooks.py doc events (validate, on_submit) enforce that a shift cannot close with an unbalanced meter-vs-sales or cash-vs-collection delta beyond your tolerance; whitelisted server methods expose reconciliation and dip-entry endpoints for the forecourt POS and any handheld dip app over the Frappe REST API; scheduler events roll up daily wet-stock variance and can flag tanks trending toward reorder. Client Scripts drive the attendant-facing POS — nozzle selection, litres/amount entry, fuel-card lookup against the customer's fleet account and credit limit — and combine dispensed-fuel and convenience-store (shop) lines on a single ticket. Role Profiles and permission rules separate the attendant, the shift supervisor who authorises handovers, and the accountant who reviews variance, with the full audit trail ERPNext already provides.
Because this is build-to-order, you receive an app scoped to your actual site layout, product slate, fuel-card partners and reporting needs — not a generic template you have to bend. After a short scoping call we confirm the DocType model and reconciliation rules, build against ERPNext v15/v16, and run UAT on a staging bench with your data before go-live. Typical delivery is 2–4 weeks from confirmed scope, and you get the full git repository, installable source for your version, and a post-go-live support window so real forecourt edge cases get handled, not left to spreadsheets.
Runs one or a few petrol stations and needs pump readings, tank dips and shift cash to reconcile against ERPNext accounting without maintaining parallel spreadsheets or a separate wet-stock tool.
Operates several stations under one ERPNext instance and wants standardised shift handovers, per-site variance reporting and consolidated fuel-card/fleet-account billing across the network.
Manages corporate fleet accounts and card-based fuelling; needs credit-limit enforcement at the pump and clean per-account statements posted straight into ERPNext receivables.
Owns month-end and needs an auditable line from nozzle meter to tank dip to GL, with variance thresholds and role separation between attendants, supervisors and accountants.
Buy the license on ecosire.com and download the Fuel Station / Forecourt POS for ERPNext app ZIP from your account dashboard.
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Fuel Station / Forecourt POS for ERPNext and apply its schema.
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Wet-stock reconciliation | Built-in nozzle meter, tank dip and variance model | Possible but you specify and build it all | Partial or generic, rarely dip-to-GL | |
| Shift handover | Opening/closing readings + supervisor-authorised cash/card handover | Depends on your build effort | Basic shift close if offered | |
| Fuel-card / fleet accounts | Credit-limit checks at pump, posts to receivables | Must be built and tested from scratch | Varies; often add-on or absent | |
| ERPNext GL/stock integrity | Posts through native Stock/Sales/Payment entries | Correct only if you enforce it | Sometimes bypasses core ledgers | |
| Fit to your site | Scoped to your pumps, tanks, products and cards | Fully bespoke, at full cost and time | Generic template you bend to fit | |
| Delivery time | 2–4 weeks from confirmed scope | Months of in-house discovery and build | Fast to install, slow to actually fit | |
| Ownership | Full git repo + installable source handed over | You own it but carry all the risk | Vendor-locked, limited source access | |
| Support after go-live | Defined support window + optional ongoing | Your team maintains everything | Tiered subscription support |
No. It is build-to-order. ECOSIRE builds the Fuel Station / Forecourt POS app to your specific site layout, product slate and reconciliation rules on top of ERPNext, then installs and supports it. There is no instant marketplace download.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we agree the DocType model and reconciliation rules; the timeline depends on the number of sites, fuel-card integrations and any custom reports. Complex multi-site rollouts are staged and quoted accordingly.
We build against ERPNext and Frappe v15 and v16. We target the version your bench runs, keep changes to a proper installable app rather than core edits, and confirm the exact version during scoping so upgrades stay clean.
Manual or metered dips are converted to volume through per-tank calibration charts and compared against ERPNext book stock. A daily variance report per tank surfaces shrinkage, evaporation and delivery discrepancies, and shift close can be blocked when meter-vs-sales or cash deltas exceed your tolerance.
Yes. Fuel-card and fleet-account sales check the customer's account balance and credit limit at the pump, post to ERPNext receivables, and produce per-account statements. We map your specific card partners and account rules during scoping.
Every build includes a post-go-live support window for defect fixes and real forecourt edge cases. Because you receive the full git repository and installable source, you own the code; we also offer ongoing support and enhancement engagements beyond the initial window on request.
No. It posts through native ERPNext Stock Entries, Sales Invoices and Payment/Journal Entries so your GL and stock valuation stay canonical. The forecourt logic lives in a separate Frappe app using DocTypes, hooks and whitelisted methods — not core modifications.
A build-to-order ERPNext app for petrol stations and forecourts that ties pump/nozzle meter reconciliation, shift handovers, tank wet-stock and fuel-card sales into one auditable ledger. ECOSIRE builds it to your scope, installs it, and supports it after go-live.