Petrol Station Pumps
Meter readings that actually move stock. Pumps and nozzles wired to your tanks, totalizer readings with automatic volume, a double-confirmation guard, and optional tank deduction the moment you confirm.
Pump states tracked out of the box — draft, active, maintenance and out of service — each pump code unique per station.
A reading confirms exactly once. A regression guard blocks a totalizer below the last, and a stale reading can never double-deduct the tank.
Optional tank stock move on confirm — switch it off when fuel already sells through the POS, so a litre is never deducted twice.
Nozzle to tank, meter to stock
Every screenshot below is a real screen from a working Odoo 18 install — verified end-to-end on our live demo.
Every pump and its state at a glance
Each pump belongs to a station and shows its code, name, type and nozzle count, with a colour-coded state badge — green for active, amber for maintenance, red for out of service. Pump codes are unique per station, so nobody confuses Pump 1 across two sites.
Single, dual or multi — with a service history
Set the pump type, manufacturer, serial number and installation, last-service and next-service dates. A status bar walks the pump through draft → active → maintenance → out of service, and its nozzles list right on the card — each with tank, fuel type, totalizer and price.
Each nozzle wired to a tank
Every nozzle links to one fuel tank and inherits that tank's fuel type and product automatically. The unit price defaults from the fuel's pump price the moment you pick the tank, and an "Update Price from Product" button re-syncs it in one click whenever the pump price changes.
Totalizer in, volume out
Pick a nozzle and the previous totalizer and unit price fill in for you. Enter the new totalizer and the volume sold and value compute themselves. A regression guard refuses any reading below the last, so the meter can never run backwards, and the reading opens in draft ready to confirm.
The reading moves fuel out of the tank
Confirm and, if enabled, the module books a done stock move from the tank to the customer for the exact litres sold — verified live, the tank's volume drops for real and the move is linked on the reading (here, Tank TK-01 → Customers). The nozzle totalizer advances to the new figure.
A reading can only be confirmed once
Before confirming, the module checks the nozzle's current totalizer still matches where this reading started. If another reading slipped in first, confirmation is blocked with a clear message — verified live — so the same interval of fuel is never booked, or deducted, twice.
Live in an afternoon
Petrol Station → Operations → Pumps: register each pump under its station, set its type and service dates, then add nozzles — linking each to a tank. Fuel type, product and price flow in from the tank automatically.
Take a totalizer reading per nozzle; the volume and value compute, and confirming books the tank stock move when enabled. Turn deduction off if the POS already sells the fuel, so a litre is never deducted twice.
The complete forecourt suite
Buy only what you need — every module shares the same foundation, data and security. Start with the free Base module and add the rest as you grow.
Other Odoo services we offer
Common questions
Will I double-deduct stock?
Does the meter really move inventory?
Can the same reading be confirmed twice?
How is volume sold calculated?
Where does the nozzle price come from?
What does it need?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) • Employees (hr) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1885 |
| Technical Name |
aminitech_petrol_pump |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module