| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Fleet (fleet) • Employees (hr) • Inventory (stock) • Invoicing (account) • Point of Sale (point_of_sale) |
| Community Apps Dependencies | Show |
| Lines of code | 1561 |
| Technical Name |
aminitech_petrol_fleet |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
Petrol Station Fleet
Sell fuel on account to fleets. Fleet customer accounts with a credit limit and a live receivable balance, auto-numbered fuel cards with salted admin-only PINs and daily auto-expiry, and per-vehicle monthly litres pulled straight from your POS fuel sales.
Live receivable balance and available credit on every fleet account — read straight off the customer ledger, always current.
Card PINs stored salted, iterated and admin-only, verified in constant time. Verified live on the demo.
Monthly litres per vehicle, summed from the POS fuel sales tagged to that vehicle's cards.
Fuel cards, credit and vehicles — done right
Every screenshot below is a real screen from a working Odoo 18 install — verified end-to-end on our live demo.
Every fuel card in one register
Cards are auto-numbered with an FC prefix the moment you create them — no manual numbering. The register lists each card's number, fleet customer, card type, assigned vehicle, expiry date and status at a glance, so a forecourt supervisor can see the whole card estate on one screen.
Master, driver or vehicle — time-boxed
Each card is a Master, Driver or Vehicle card tied to a fleet customer, and optionally to a specific vehicle and driver. It carries an issue and expiry date and moves through a clear status workflow — Draft, Active, Suspended, Expired, Cancelled — with one-click Suspend and Cancel buttons and a full chatter trail of every change.
A PIN that is not a plain field
Card PINs are hashed with a salted, 200,000-round PBKDF2 function and written to fields visible to system administrators only, then checked through a constant-time verify API. A 4-digit PIN that is not trivially reversible and not readable by ordinary staff — verified live on the demo station.
Spend limits and fuel restrictions on record
Set a per-transaction, daily and monthly spend limit and restrict a card to petrol only, diesel only or all fuels. In this release these are informational policy and reporting fields recorded on the card — not a hard block at the till — and the FAQ says so plainly.
Credit limit and a live balance
Flag any contact as a fleet customer and it earns an automatic FLT code, a credit limit, a billing cycle (weekly, bi-weekly or monthly) and payment terms. Current balance reads live off the customer's receivable, so available credit is always credit limit minus what they owe — no spreadsheet reconciliation.
Monthly litres, straight from POS
Vehicles hang off the fleet account with their own fuel type and monthly litre limit. Tag a POS fuel sale with a card and that card's vehicle records its last-fueling date and adds the litres to this month's usage — a running per-vehicle consumption figure with no extra data entry.
Live in an afternoon
Tick "Is Fleet Customer" on a contact and it gets an FLT code automatically. Set the credit limit, billing cycle and payment terms; the account immediately shows a live balance and available credit.
Issue cards against the customer and vehicle, set a PIN, validity and limits, then activate. Tag each POS fuel sale with the card, and the vehicle's last-fueling and monthly litres update on their own.
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
How secure are the card PINs?
Are the spend limits enforced at the pump?
Do cards expire on their own?
How is a fleet customer's balance calculated?
How does per-vehicle fuel usage get counted?
What does this module need?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Fleet (fleet) • Employees (hr) • Inventory (stock) • Invoicing (account) • Point of Sale (point_of_sale) |
| Community Apps Dependencies | Show |
| Lines of code | 1561 |
| Technical Name |
aminitech_petrol_fleet |
| 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