> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-connect/commander-connect-user-guide.md).

# Commander Connect User Guide

## Document and App Information

| **Platform**                  | iOS & Android (shared codebase) |
| ----------------------------- | ------------------------------- |
| **Version 1.0.2 CST Release** | September 3, 2026               |

## Audience

This guide is intended for three groups: Merchants and site staff who monitor site performance and day-to-day sales activity, VASCs (Verifone Authorized Service Contractors) who also perform configuration tasks, and Helpdesk / Internal Support staff who assist users in the field. Readers should already have a Verifone Central account, since the app uses those credentials to sign in.

## Introduction

This guide explains Commander Connect users on its features. Commander Connect is a secure, role-based mobile app for iOS and Android that extends the Commander Central platform to a phone. Users sign in with their existing Verifone Central credentials and access site-level data and tools based on their assigned role.

### Roles at a glance

| Role                                           | What they can do in the app                                                                                            |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| Merchant (Retailer / Site Owner / Store Staff) | View sales data, sales trend, and T-Log; view configuration; use Resources & Support; manage app settings and profile. |
| VASC (Authorized Service Contractor)           | All Merchant capabilities, plus update configuration (Fuel Prices/Initialization, PLU, Image Upload).                  |
| Helpdesk / Internal Support                    | Reference role. Use this guide to walk users through the supported features and answer questions in the field.         |

## Getting Started: Login and Site Selection

### Pre-Login screen

When the app is first opened, the Pre-Login screen appears. It offers two actions before any sign-in:

* **Login** — starts the Verifone Central authentication flow.
* **Access Help** — opens the Resources page so users can find support even if they cannot sign in.

### Logging in

1. Tap Login on the Pre-Login screen.
2. The user is redirected to the Verifone Central sign-in interface.
3. Enter the Verifone Central email and password, then tap Sign In.
4. On success, the user is returned to the app with access based on their assigned role.

{% hint style="info" %}
Users without Verifone Central access can use the registration and “Need help signing in?” links on the login screen.
{% endhint %}

### 3.4 Selecting a site

After login, you must select a site before site-specific features become available. The site list is searchable by site name, ID, or address, and each site shows a color-coded connection status:

| Status          | Meaning                                                                                     |
| --------------- | ------------------------------------------------------------------------------------------- |
| Online (green)  | Site is connected and live data is available.                                               |
| Pending (amber) | Site connection is being established; some data may be unavailable.                         |
| Offline (red)   | Site is not reachable; the app shows a consistent Commander Central-aligned status message. |

{% hint style="info" %}
This release supports single-site selection. You can change sites at any time from the three-dot menu in the header.
{% endhint %}

### Logging out

Tap the three-dot menu in the top-right corner of any screen and choose Logout. Sessions also expire automatically after 15 minutes of inactivity for security.

## Home / Dashboard

The Home screen is the navigation hub. Walk users through its two areas:

### Header

* Shows the Site Name, Service ID, and the color-coded connection status.
* The three-dot menu lets users change sites, open App Settings, or log out.

### Quick Access navigation

From Home, users reach the main sections delivered in this release: Sales, Configuration, and Resources. The bottom navigation bar mirrors these for fast switching.

## Sales

The Sales screen lets Merchants and authorized VASCs search and review transactions for the selected site.

### Transaction Logs (T-Log)

The Transaction Logs section lets users search and view T-Log data:

1. Use the search box to filter transactions.
2. Each row shows the time, transaction type (Sale, Refund, Error), reference number, amount, and status.
3. Tap a transaction to open its detail view.

{% hint style="info" %}
Error rows (for example a fuel-offline indicator) are surfaced clearly in red so users can flag issues quickly.
{% endhint %}

## Configuration

The Configuration module launches the Commander Central Configuration interface inside the app. Viewing is available to all signed-in users; updating configuration is a VASC capability.

### PLU — Add / Modify with barcode scan

1. Open the Add/Modify PLU form.
2. Tap the scan control to open the phone camera.
3. Scan the product barcode; the code populates the PLU form automatically.
4. Complete the remaining fields and save.

{% hint style="info" %}
**Good practice:** Changes are staged locally and saved together, not auto-saved per row. Make sure to save before leaving a form.
{% endhint %}

## Settings and Profile

### 8.1 App Settings

Open App Settings from the three-dot menu in the top-right corner. Settings are independent from Commander Central configuration changes and include:

* Dark / Light mode selection

### 8.2 Profile

The Profile screen displays the user's Name, Username, Email Address, and Assigned Role, and offers a Logout option.

## Resources & Support

The Resources section is available with or without login, so help always available. It brings together support channels, AI assistance, and documentation.

### Support channels

| Support Channel | Notes                                                                                        |
| --------------- | -------------------------------------------------------------------------------------------- |
| Chat Support    | Live chat with the support team. When signed in, site contact information is auto-populated. |
| Email Support   | Opens an email to the support address.                                                       |
| Phone Support   | Provides the helpdesk phone number.                                                          |
| Find a VASC     | Locator to find a nearby Verifone Authorized Service Contractor.                             |

### Commander Help Center (AI assistance)

The [Commander Help Center](https://commanderhelp.verifone.com/) provides an AI chatbot and knowledge base for automated troubleshooting, FAQs, and self-service support. Users can tap Ask AI for guided help, or search help articles directly.

### Documentation & references

The section links to key product documentation:

* [Commander Central User Guide](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central/commander-central-user-guide)
* [Commander Highlights, User Guides, Release Notes, and Certifications](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-highlights-user-guides-release-notes-and-certifications)
* Commander Connect Release Notes (Link TBD)
* [Commander Central Resources](https://docs.verifone.com/petroleum-docs/petro-and-c-store/commander-central)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-connect/commander-connect-user-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.