Skip to main content

Introducing Loss Radar: see which shift cost you money.Learn more

On requestPOS & Forecourt

StationPro + Verifone Commander

Read sales, tender, and forecourt data from the Commander/Sapphire site controller.

What Verifone Commander is.

Verifone Commander (formerly Sapphire) is the site controller running on the back office PC at the majority of US fuel-retail Verifone deployments. It owns POS sales, tender breakdown, shift open/close, voids, refunds, pump totalizer reads, and the fuel grade/price configuration. The Commander reports it produces are the canonical record of what happened at the store, but they live on the back-office PC and are exported as flat files.

What data flows between Verifone Commander and StationPro.

StationPro reads the Commander shift report, the daily-summary export, the void and refund log, and the pump totalizer reads. We support both the direct flat-file ingest (deposit to S3 or a SFTP we run) and the newer Verifone Connect cloud API where the site is enrolled. We do not write back to the Commander; the POS remains the source of truth, and StationPro is the operational view on top.

What Verifone Commanderalone doesn't give you.

Commander reports tell you what happened. They do not tell you whether the cash variance correlates with a clerk's void burst, whether the lottery serial gap on Tuesday lines up with the same shift on Friday, or whether the fuel margin compressed because dispensed-volume reconciliation drifted. Operators export Commander reports into spreadsheets to do this analysis, and that's where the workflow breaks.

How StationPro closes the gap.

StationPro ingests the Commander feed nightly (or hourly with Connect API), pre-populates the EOD form with shift tender, runs Loss Radar against void/refund/cash patterns, and reconciles pump totalizer reads against POS sales and ATG inventory. Daily-close drops from 45 minutes to roughly 5; the spreadsheet work disappears.

Current status

On request

The vendor is in scope and the integration approach is known. We turn it on for paying customers within 2 weeks of the request.

How Verifone Commander onboarding works.

  1. Scoping call

    A 30-minute walk-through of your current setup with Verifone Commander. We confirm credentials, data shape, and the workflows you need feeding into StationPro.

  2. Connection

    We wire the Verifone Commander feed into your StationPro tenant. Depending on the pos & forecourt, this is a credential paste, a webhook config, or a same-day support ticket with the vendor.

  3. Backfill

    Historical Verifone Commander data from the last 90 days is ingested so EOD, Loss Radar, and audit views have context from day one, not just data going forward.

  4. Go-live

    Clerks and managers trained on the integrated flows. We monitor the first 7 days closely and fix anything that doesn't feel right.

Questions about Verifone Commander.

Do I need Verifone Connect?

No. Verifone Connect speeds up the integration (cloud API, hourly refresh) but the flat-file export from Commander works fine for the daily cadence most independents need. We support both; you pick based on what your site is licensed for.

Does this work for V950 and V770 sites?

Yes. The Commander/Sapphire integration is software-version-specific, not hardware-specific. As long as Commander 6.10 or later is on the back-office PC, the integration is the same.

Can I run this alongside Verifone Back Office?

Yes, and many operators do during cutover. Verifone Back Office stays the official record; StationPro runs the daily reconciliation and the loss-attribution layer on top until you decide whether to decommission Back Office.

Want to see the Verifone Commander integration in action?

On the demo call, we'll show you the connected dashboard with seeded data and walk through the onboarding steps.