CX Central Every litre in the field, from producer to station, on one screen
CX Central follows AdBlue, screenwash and automatic car-wash self-service sales at fuel stations end to end. The producer sees its own product line, the distributor its network, the station owner its stations — the same data through three windows, each cut to its holder's rights.
- AdBlue · screenwash · car wash on one platform
- Producer / distributor / station: visibility by agreement
- Live tank level and sales
- Shipment and refill route
- Revenue-share report
What CX Central is
A company producing AdBlue or screenwash usually learns how much is left in which tank at which station by phoning the station. CX Central collects that from the unit instead: sale, refill and stock-count records flow to the centre, stock is computed, and a shipment is planned before the tank runs dry. The same platform shows a fuel distributor its contracted stations and a station owner its own units.
Who sees what
Visibility comes from the supply agreement, not from the company. As a party's agreements widen, so does what it sees.
AdBlue / screenwash producer
Its distributors, those distributors' stations and directly contracted stations — only for its own product. A producer with an AdBlue agreement alone does not see screenwash sales.
Fuel distribution company
Unit, tank and sales status for every station under it, on one panel. A distributor that also produces sees the union of both roles.
Station owner
One station or fifty — tank level, refills and sales for all of them on one screen, without connecting to each in turn.
At the same station, AdBlue can come from one producer and screenwash from another; a distributor can also be a station owner. The model is therefore many-to-many: party ↔ role and party ↔ product line are defined by agreement lines.
Screens
Every screen narrows to the user's scope; a producer sees the producer's data, a station the station's.
Live monitoring
Current state of each unit — selling, idle, faulted — with tank levels and last transaction time on one screen.
Operations dashboard
Role-aware summary: sales, tank and unit health, alerts — from the real register data.
Inventory tree
Dealer → station → tank / pump → the asset itself. Even across thousands of stations the top level stays a summary; lower levels load only when opened.
Tank detail
Level history, consumption rate and projected run-out; a shipment alert at the critical level.
Shipment plan and refill route
Shipment planning for tanks that are empty or about to be, with the refill route on a map.
Sales history
Sale and refill records per transaction, broken down by product line, station and unit.
Shifts
Sales and counts per shift; at handover, the source of any difference is visible.
Station map
Stations in the network on a map; colour tells the tank state.
How data comes in from the unit
CX Central does not control the pump at sub-second speed; that is the job of the unit and the automation in the field. The centre collects transaction records from units, validates them and posts them to stock. A record that arrives twice is not counted twice.
- Partner device API: a producer's own unit sends records straight to the centre
- An API key per unit, so every record is traceable to the unit it came from
- Two-way transport with ELPO AX automation: field → centre for sales and refills, centre → field for prices and definitions
- Field hardware is defined at the centre and sent to the station — one source of truth
- Count and refill documents can also be entered by form; a posted document is corrected by a reversing entry, never deleted
Revenue share: where the money comes from
A unit's sale is usually income for more than one party. The split is written in the contract; the report is produced from it.
- 01
The sale is posted
- 02
If the unit is mapped to a contract, that contract applies; otherwise the single active default split set
- 03
Parties, rates and VAT are read from the contract; base → share / remainder / VAT / cost items are computed
- 04
Written to the revenue-share ledger
- 05
Revenue-share report: who, under which contract, how much
- 06
The report opens at five levels: party → contract → station → product → attribute (share, remainder, rent, VAT, supply cost, software fee, payment commission)
Scale
The design target is 1,000–1,500 stations with 3–10 tanks each — tens of thousands of assets. Lists are therefore trees and summaries; if a query hits the ceiling the screen says so rather than trimming silently — a tank that looks absent is a refill that is already late.
Mobile
Managers and warehouse staff see on mobile everything they are entitled to on the web: deliveries, tank refills, live state. The scope rule is the same on mobile; a user cannot step outside their own stations.
Who it is for
AdBlue producers
Stock visibility across the filling network and shipment planning; which station runs out when is known in advance.
Screenwash producers
Sales and stock for self-service screenwash units; only their own line, even where another producer's AdBlue sits at the same station.
Fuel distributors
Every liquid unit across the contracted station network on one panel; revenue share from the contract.
Multi-station owners
Unit, tank and sales view for their own stations; shift-based counts.
Common questions
Are CX and CX Central the same thing?
No. CX is the central management panel of fuel station automation (pumps, tanks, tankers). CX Central is a separate product that follows the AdBlue, screenwash and car-wash self-service units along the producer–distributor–station chain. They work together, and both are ELPO products.
We have our own units; can they connect to CX Central?
Yes. Through the partner device API a unit sends records straight to the centre; each unit gets its own API key. ELPO hardware is not required.
Can a producer see another producer's data?
No. Visibility is computed from supply agreements; a party sees only the stations and product lines its agreements cover. Even with two producers' products at one station, each sees only its own.
How is stock calculated?
Sale, refill and count documents are posted to tank stock as they are processed. Once posted, a document is corrected by a reversing entry; nothing is physically deleted, so the trail is kept.
Where do revenue-share rates come from?
The split set is defined in the contract: parties, rates, VAT. When a sale is posted the share is computed under that contract and written to the ledger; the report is produced from there.
What happens to past sales if we define the contract later?
The share is written against the contract in force when the sale was posted; a sale posted with no contract stays unshared and does not correct itself. Reverse the document's accounting entry with a reason and post it again, and the share is recalculated under the current contract. If the period has been closed the operation is deliberately blocked — a closed period is not replayed.
Are car-wash machines a separate product?
No — a separate menu heading inside the same product. Definitions and reports are not repeated; car wash uses the same document and register logic as liquid sales.
See your filling network on one screen
Producer, distributor or station owner — let us set up a demo on your own network.