One Card for Your Private Sites and Retail Stations
Most fleets with their own fueling hand drivers two credentials. Here is what the split costs in data and admin, and what a single card changes.
A fleet that operates its own fuel site and also buys retail fuel usually hands every driver two credentials. A fob or card for the company pump, and a fuel card for everywhere else.
Nobody designed it that way. The private site came first with its own authorization hardware, the fuel card came later from a card issuer, and neither vendor had any reason to care about the other.
The result is a split that costs more than the extra piece of plastic suggests.
01 What the split actually costs
Two credentials per driver means two systems to provision and deprovision. When a driver leaves, someone has to remember both. In practice one gets forgotten, which is how live credentials outlive employment.
Your fuel data lands in two places. Retail transactions sit in the card platform; private site transactions sit in the site system. Answering "what did this vehicle spend on fuel last quarter" means joining them, usually by hand, usually in a spreadsheet.
Controls are configured twice, in two interfaces, with different capabilities. A rule you can enforce at retail may not be expressible at your own pump, or the reverse.
And drivers carry two things, which means they lose two things.
02 The comparison you cannot make
The costliest consequence is analytical rather than administrative.
Fuel at your own site generally costs less per gallon than retail — you bought it wholesale. So every retail fill that could have happened at your own site, with a tank nearby and capacity available, is a small avoidable premium.
Spotting that requires seeing both transaction types together, with location. A driver who fuels retail three miles from a company site with fuel in the tank is a pattern worth knowing about. It may be entirely justified — routing, timing, a site closed for maintenance — or it may be habit that nobody has ever mentioned because nobody could see it.
With the data in two systems, that comparison does not get made. Not because it is difficult, but because nobody has a standing reason to assemble it.
03 What a single credential changes
One card authorizing both private and retail fueling collapses most of the problem.
One provisioning action per driver, and one deprovisioning action when they leave
One set of controls, expressed once — including where each card is permitted to fuel
One transaction stream, so total fuel cost per vehicle exists without a join
The on-site versus off-site comparison becomes a report rather than a project
One thing for the driver to carry and lose
It also makes an authorization rule possible that neither system can express alone: permitting or restricting where a given card can fuel, across both networks, from one place.
04 What it does not solve
Worth being straight about the limits.
A single card does not make retail fuel cheaper, and it does not stop a driver fueling retail when a company site was available. It makes that visible; someone still has to act on it.
It also does not remove the need for private site authorization hardware to be compatible. If your site controller cannot read the card, the single-credential model does not apply to that site until the hardware is addressed.
And for fleets without private fueling, none of this matters. This is a specific advantage for a specific configuration.
05 Who this actually helps
The fleets where this matters most share a profile: they operate at least one private fuel site, a meaningful share of fueling happens off-site because vehicles range beyond the site, and someone in finance has asked what total fuel cost per vehicle is and received an unsatisfying answer.
Municipalities, utilities, public works departments, and contractors frequently fit that description — a yard with a tank, crews working across a service area, and fuel spend split unpredictably between the two.
06 Where EKOS fits
EKOS is built for exactly this configuration. A single supported WEX card authorizes fueling at both private sites and commercial stations, and you configure where each card is permitted.
Because EKOS also runs the private fuel site monitoring and the fleet records, the resulting comparison is native rather than assembled — retail purchases appear in the context of your own fueling network, so an off-site fill near an available company site is visible as it happens rather than in a quarterly review nobody schedules. The reporting lives in fuel card analytics.
Frequently asked questions
Can one fuel card work at both private sites and retail stations?
Yes, with the right program and compatible site authorization hardware. A single supported card can authorize at company pumps and commercial stations, with permissions configured per card for where fueling is allowed.
Why do most fleets carry two fuel credentials?
Because the two systems arrived separately. Private site authorization came with the fueling equipment, and the fuel card came later from a card issuer, with no reason for either vendor to accommodate the other.
What does carrying two fuel credentials cost?
Double provisioning and deprovisioning per driver, with the risk that one is forgotten when someone leaves. Fuel data split across two systems, so total cost per vehicle requires a manual join. Controls configured twice in two interfaces. And no practical way to compare on-site against off-site fueling.
How do I know if drivers are fueling retail unnecessarily?
You need retail transactions and private site fueling in one view, with location. That lets you see fills that happened at retail while a company site was nearby with fuel available. Some will be justified by routing or timing; the rest is habit nobody has been able to see.
THE BOTTOM LINE
One EKOS-issued WEX card authorizes both your private sites and retail stations.
With permissions you set, and a single stream of fuel data behind it.
WEX CARDS INSIDE EKOS
One card for your pumps and everyone else's.
One EKOS-issued WEX card authorizes both your private sites and retail stations — with permissions you set, and a single stream of fuel data behind it.
