How to choose a POS as an independent operator in 2026.

What this guide is and isn't

This is not a POS feature checklist. The PDI and Petrosoft websites publish those. This is the buying lens of an operator who has bought POS twice and would do it differently the second time. The questions below are the ones that actually differentiate buyer regret from buyer satisfaction at the 18-month mark.

Question 1: which forecourt do you have?

This is the only forced choice. Verifone Commander talks natively to Verifone dispensers. Gilbarco Passport talks natively to Gilbarco dispensers. You can technically mix. Commander supports Gilbarco via the Wayne integration, Passport supports Verifone via the legacy protocol, but the edge cases are real. Pump-totalizer-to-POS reconciliation gets messier. Card-on-file at the pump gets less reliable. The list of small bugs you live with grows.

If you're building a new station and you don't have either yet, the answer is usually whichever your local fuel supplier's install team is most experienced with. The implementation matters more than the brand.

Question 2: what are your inside-sales mix and category breadth?

If you're fuel-heavy with a small inside footprint (200–400 SKUs), any of the four handle you fine. If you're running an inside store with full grocery, beer/wine, food-service, and lottery (2,000+ SKUs), the differences start to matter. NCR Voyixhas the deepest inside-sales pedigree (it's descended from the Radiant retail POS). Toshiba TCxis competitive on the same dimension, especially for c-stores with food-service operations.

Question 3: who's installing and supporting it?

Local. Always local. The actual person who shows up when your card processor rejects a settlement at 11 PM on a Saturday matters far more than the corporate feature roadmap. Before you sign, ask the POS vendor to put you in touch with the local install partner. Then ask the local partner for three references at independent stations within 50 miles of you. If you can't get three local references, that's your answer.

Question 4: how good is the back-office integration?

Most POS vendors will tell you their back office “does everything.” In practice, the POS-side back office is usually adequate for one-station operators and increasingly limiting as you scale. Independent operators with 3+ stations almost always pair their POS with a dedicated back-office platform (StationPro, PDI, Petrosoft, Series2K).

The right question is not “does the POS have a back office?” but “how good is the POS's data feed to a third-party back office?” The two POS systems with the best third-party feeds are Verifone Commander and Gilbarco Passport (via Net2 export). NCR and Toshiba are catching up but the integration path is more involved.

The honest matrix

With those four questions in mind, here's how the choices map for typical operator profiles:

• Single station, Verifone forecourt: Commander. The local install network is the largest, the back-office feed is mature.
• Single station, Gilbarco forecourt: Passport. Same logic in the opposite direction.
• Multi-station, mixed forecourt: Match per-station to the forecourt. Don't try to standardize.
• Heavy inside-sales c-store with food-service: NCR Voyix or Toshiba TCx if forecourt allows. The inside-store depth is materially better.
• Travel center (TC/TCS): NCR Voyix has the strongest commercial fuel-card support; Verifone Commander is competitive with the right configuration.

What you don't need to worry about

• EMV / chip-card compliance. All four are compliant. Old non-compliant equipment is mostly out of the field by 2026.
• PCI scope. All four keep cardholder data out of the back office by design. Your PCI scope stays narrow regardless of which you pick.
• Mobile payments. Apple Pay, Google Pay, contactless, all supported on all four.
• EBT. Supported across the board. Configuration is the same exercise on any system.

What you absolutely need to confirm

1. Your card processor and the POS work together. Get the processor on a call with the POS vendor before signing.
2. Your back-office choice integrates with the POS. Ask the back-office vendor for a live demo against the specific POS version you're buying, not the latest version.
3. The local install partner has done at least 5 installs of the specific configuration you're buying. POS deployments fail on local installer experience, not vendor reputation.
4. The contract has a defined exit clause. Three years or shorter is fine; auto-renewal that requires 180 days' notice is not.