Waquod وَقود
العربية Back office Fleet portal

Fleet fueling, authorized at the nozzle.

RFID tags on vehicles and contactless cards in drivers' hands authorize fuel, C-Store and car-wash sales at the station. The back office and the customer portal keep every litre, card and invoice in one ledger, in Syrian pounds, in English and Arabic.

Open the fleet portal See how it works

Built for fuel companies, station networks and the fleets they serve.

Site 1104, pump 3, nozzle 2 OnlineReader
Vehicle tag04A3 7F21, Sham Transport Co.
AccountPostpaid, fleet North
Rule checkAuthorized
Litres
42.500Diesel, SYP 1,275,000
Two-phase: pre-authorized, then completedReceipt 2026-000418
  • Two-phase tag fuelingPre-authorize at the pump, complete with the metered volume, auto-expire when nothing is pumped.
  • Cards with PINSingle-step contactless cards for drivers, gift and VIP customers, with a PIN on the pad.
  • Three lines of businessFuel, C-Store and car wash, each with its own products, limits and rules.
  • A tax invoice for every saleBilingual receipts and invoices, printed at the station or downloaded as PDF.

How a sale is authorized

Every id unit sits in a hierarchy: customer, account, fleet, group, vehicle or card. Business rules hang off that tree and the authorization engine evaluates them along the path of the tag or card presented at the station.

  1. Present the tag or card

    The pump reads the vehicle's RFID tag, or the driver taps a contactless card and enters the PIN. The terminal calls the Waquod terminal API.

  2. Rules are evaluated on the path

    Balance or credit limit, product and station allow-lists, daily and monthly caps, time windows and odometer checks are resolved from the account down to the unit. A decline says exactly which rule blocked it.

  3. The sale completes into the ledger

    The metered volume settles the pre-authorization, the account is charged, the receipt is issued and the transaction appears live in both portals.

What the platform manages

One modular system for the fuel company and its customers, from onboarding a corporate fleet to the monthly statement.

Customers and accounts
Individual and corporate customers with prepaid or postpaid accounts, credit limits, top-ups and a full ledger per account.
Fleet hierarchy
Fleets, nestable groups, vehicles with Syrian plates and card subgroups, so limits can apply to a whole region or a single truck.
Media lifecycle
Tag banks, printable RFID tags, installation and verification, card issuance with PIN, blocking, replacement and offline whitelists.
Business rules
Product, station, volume, amount, schedule and odometer rules per node of the tree, with a simulator to test a scenario before it goes live.
Workflows and requests
Configurable approval flows for new accounts, media requests and limit changes, with notifications at every step.
Billing
Invoices, credit notes and statements for postpaid accounts, service charges, tax lines and payment recording.
Stations and terminals
Sites, pumps, nozzles and API keys, heartbeats and connectivity, a station simulator that drives the real terminal API.
Reports and notifications
Scheduled and ad-hoc reports, exports, e-mail and SMS notifications, live dashboards in both portals.

Two portals, one platform

Internal users work in Waquod Operations; customers manage their own fleets in Waquod Fleet. Both switch between English and Arabic at runtime.

Waquod Operations

admin.waquod.com

The back office for the fuel company: customers, accounts, fleets, media, rules, workflows, billing, stations, settings and reports.

  • Live authorization feed and station status
  • Card issuance wizard and tag installations
  • Roles, permissions and audit trail
Sign in to the back office

Waquod Fleet

fleet.waquod.com

The customer portal: balances and credit, vehicles, cards and tags, transactions with receipts, statements and requests.

  • Top up prepaid accounts and follow postpaid limits
  • Block a card or tag the moment it goes missing
  • Download invoices and statements as PDF
Sign in to the fleet portal
Station terminals authenticate with an API key against https://api.waquod.com/terminal/v1; the integration reference is provided to station operators on request.