All solutions
KUNJUK FUELPilot available · Businesses and public organizations

Your organization authorizes. The station records.

Your business or municipality defines which vehicle can refuel, where and up to how many liters. The station attendant checks authorization and records the actual fuel supplied. If the station does not use the system, the administrator records the receipts afterward.

Public demo without registration. Clients: sign in to the application.
A fleet manager and station attendant coordinating a fuel fill. Illustrative scene created for Kunjuk.
PEOPLE + TECHNOLOGYKunjuk Fuel
Illustrated example of Fuel with fictional dataExplore the product
Illustrative scene · Example interface with fictional data.
THE CHANGE IN YOUR EVERYDAY WORK

Your organization sets the allowance. The actual fill is recorded.

The common problemAuthorizations by message and uncertainty over which vehicle can fill at each station.

With Kunjuk FuelA van has 40 liters authorized. The attendant checks the plate and records 28.5 actual liters. If the station does not use Kunjuk, the administrator may record the ticket later. Each fill is entered once.

Who it is forAdministration, fleet managers and station users.

Illustrated example of Kunjuk Fuel with fictional data. Not a system screenshot.
Every fill, with context.Illustrative example · fictional data · not a system screenshot.Explore the demo
TECHNOLOGY SERVING PEOPLE

Less paperwork. More context for your team.

The organization authorizes the allowance and the station records the actual fill. If it does not use the system, the administrator receives and records tickets. A clear workflow for the people doing the work every day.

Discover how it works: Fuel
How it works

A clear workflow from start to finish.

  1. 01

    The organization authorizes vehicle, station and liters.

  2. 02

    The attendant checks and records, or the administrator enters the ticket.

  3. 03

    The organization reviews fills and allowance used.

Available tools

All the context for better work.

Vehicles and departments

Identify vehicles and equipment by plate or internal code, using your organization’s names and groups.

Stations by vehicle

Enable one or more branches according to each vehicle’s area, including different brands.

Days and allowances

Define one-time, daily or weekly fills, allowed days and limits per fill or period.

Station and attendant panel

The operator searches for the plate or internal ID, views the authorization valid for that station and records actual liters within the available maximum.

Tickets and photos

Record the actual date, liters, station and receipt number. Attach a photo and transcribe tickets received days later.

Difference review

Review observations by station, day, allowance or possible duplicate. A difference requires review; it does not prove wrongdoing.

History and export

Review records and download CSV. Cancellations preserve the original operation, reason and responsible user.

Current pilot scope

Two recording workflows are available: authorized station users, or an administrator entering receipts supplied by drivers. Both use the authorization allowance; each refueling must be recorded only once. The administrative workflow does not require station attendants or drivers to have accounts. Actual liters are recorded even when below the maximum. The pilot does not include OCR, pump integration, pricing or invoicing.

A connected workflow

From authorization to recording. Keeping the whole journey clear.

01

Your organization

The administrator defines vehicles, departments, fuel, allowances, enabled days and permitted stations.

02

The station checks

If the station uses Kunjuk, the attendant searches by plate or internal ID and sees the authorization, fuel and maximum available at that station.

03

One fill, one record

The attendant records actual liters; otherwise the driver delivers a ticket for the administrator to enter. Fills can be smaller than the authorized maximum.

04

Control and follow-up

The organization reviews how much, when and where fuel was filled, fills used and available allowance.

TRY BOTH WORKFLOWS · NO REGISTRATION

The organization authorizes.
The actual fill is recorded.

Public demo with fictional data. Choose who records the fill and follow an authorization through the workflow. No action changes the real panel.

Kunjuk FuelAUTHORIZATION → ACTUAL FILL → REVIEW
TWO OPTIONS FOR YOUR OPERATION

The attendant sees the limit and records the actual fill.

The business or municipality decides the authorization. Actual liters are recorded even when less than the maximum is filled.

WHO DECIDES

The authorization belongs to your organization.

Set the vehicle, station, fuel and maximum allowed. Station accounts view their applicable current authorizations.

  1. DEMO clientBusiness or municipality · Administration
  2. DEMO station userAccess to this station and its authorizations
  3. Shared allowance controlStation fills and administrative tickets consume the same authorization.
EXAMPLE AUTHORIZATION

Authorize this fill

FuelGasolineExample validityOne authorized fill
GROW WITH YOUR ORGANIZATION

Your applications.
Your identity.

Enable the applications you need according to your package. Each organization keeps separate data, users and permissions.

Customize access with your logo and colors. You can also request a custom domain. We help define scope, implementation and access.

Explore the other applications
LET’S LOOK AT YOUR CASE

How would Fuel
work in your organization?

Tell us what you need to organize. We review the workflow together and define applications, implementation, training and support in a proposal.

Before you start

Can I subscribe to one application?

Start with the tools your organization needs and expand later. Scope and conditions are defined in the commercial proposal.

Does the demo contain customer information?

Illustrative examples and public demos use fictional data. The interactive demo is a guided simulation of features without access to panel data.

Do my users see all information?

Access depends on roles and permissions. A personalized demonstration reviews what each member should record, approve or view.

Let’s talk