Turn every forecourt visit into useful network intelligence.

Read a vehicle registration at entry, enrich it only through access approved for the oil company, and combine it with station activity. The result is a clearer picture of demand, repeat visits, loyalty opportunity and site performance.

Concept only · Synthetic records · No live camera, customer or government connection

Synthetic editorial view of a fictional Indian mobility forecourt with cars and two-wheelers

From individual visit

To network intelligence

How it works

Four steps. Nothing complicated.

Read the registration

An entry camera captures the vehicle number and visit time.

Use authorised access

The oil company requests only the VAHAN/NTR fields approved for this purpose.

Add station context

Site, time, visit frequency and transaction context turn a read into a useful signal.

See the network

Aggregated patterns support operations, loyalty, planning and marketing.

Business value

Four things become measurable.

The value is not a long list of vehicle details. It is the pattern created across visits and stations.

Returning customers

Know how many vehicles return and how often, including visits that never touch a loyalty card.

Day-to-day operations

See the real busy hours and vehicle mix. Staff and stock the forecourt to match.

Planning across stations

Compare stations properly. Spot which ones are stretched and which have room.

Non-fuel sales

Understand who returns regularly, and test offers on fuel, convenience and services against real patterns.

Rough numbers

Want a rough sense of scale?

None of this is a forecast — it’s a small model built on public fuel-retail figures so the size of the idea can be sanity-checked rather than taken on trust. Move the sliders and see how the shape of the opportunity changes.

Adjustable assumptions · illustrative, not projected

The support we need

A small Kerala pilot would answer the real questions.

Three contrasting stations, six to eight weeks, suitable camera access and help pursuing the data access required for the approved use case.

The pilot measures read quality, repeat-visit usefulness and operational value. It does not require a live customer-facing launch.

A busy urban station

Peak demand, queues, regular customers

A highway site

Passing traffic, longer stops, different mix

A two-wheeler-heavy site

The hardest case, and the most common one

Data boundaries

One registration in. Only approved data out.

The oil company—not an individual developer—would apply for access. The exact fields and usage would be determined by MoRTH or the relevant State authority.

01 · InputKL 07 DEMO 4821

The camera supplies the registration number and station event.

02 · Controlled lookupAuthorised VAHAN / NTR service

Credentials, whitelisted systems, logs and purpose limitation sit with the approved recipient.

03 · Approved responseOnly fields granted for the use case

Vehicle classMake / modelFuel typeRegistration status

Owner identity is not assumed or required for this proposal. API PII is masked by default unless MoRTH specifically authorises otherwise. Even insurer access is purpose-specific; it does not establish what an oil company will receive.