> 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/feature-references/features-and-products-references/handling-fuel-prices-over-usd9.999-gal.md).
# Handling Fuel Prices Over $9.999/Gal
### Revision History
| Date | Description |
| ---------- | -------------------------------------- |
| 01/10/2023 | Initial Documentation Release |
| 07/28/2026 | Updated guide with Full Initialization |
### Introduction
This guide explains how to configure a Verifone Commander Site Controller point-of-sale system to support fuel prices above $9.999 per gallon. It also covers the correct initialization sequence required after changing the price format.
#### Background
By default, the Verifone Commander stores fuel prices in **$X.XXX format** (three decimal places), with a maximum value of **$9.999** per gallon. When fuel prices exceed this threshold, the system must be reconfigured to use **$XX.XX format** (two decimal places), which supports prices up to **$99.99** per gallon.
#### Audience
* VASCs performing PPU decimal format changes
* Forecourt managers configuring fuel prices on the Verifone Commander
* Helpdesk troubleshooting price initialization issues
{% hint style="warning" %}
Changing the PPU decimal format requires closing the forecourt and reprogramming all dispensers. Plan for at least one hour of downtime. Follow this guide in full before reopening.
{% endhint %}
### Prerequisites & Limitations
#### System Requirements
* Verifone Commander Site Controller
* Access to the **Forecourt** menu in the Commander Configuration Client
* Ensure all dispensers are online and bagged or blocked off
#### Feature Limitations
Be aware of the following constraints before making any changes:
* **No mixed decimal positions:** A single Commander cannot run some fuel grades in $X.XXX and others in $XX.XX format simultaneously.
* **Decimal truncation:** At two-decimal sites, any price entered with three decimal places (e.g., $4.299) will be calculated and charged at only two decimal places (e.g., $4.29).
* **Default format:** All Verifone Commander systems ship configured for three decimal places ($X.XXX format).
* **Dispenser reprogramming required:** A PPU format change is not complete until all dispensers have been physically reprogrammed and a Full Fuel Initialization has been performed.
* **Fuel Price Initialization restriction:** When a PPU decimal format change is pending, the system will block a Fuel Price Initialization and require a Full Fuel Initialization instead.
### Configuration Procedure
Follow these steps in the exact order shown. Do not skip or reorder steps.
#### Before Beginning
Ensure all dispensers are online and bagged or blocked off before proceeding. Changing the PPU decimal format while the forecourt is active may result in incorrect prices being displayed or transmitted to the host.
{% stepper %}
{% step %}
### Zero Out the Third Decimal in Existing Prices
This step prepares existing prices for the format change by eliminating the third decimal place.
1. Navigate to **Forecourt > Fuel Prices Pending**.
2. For **every** product, change the third decimal place to **0** for both **Tier One** and **Tier Two** prices.
Example: Change $2.152, $2.150, $3.459, $3.450
3. Click **Save**.
{% hint style="info" %}
**WHY THIS STEP MATTERS**
Prices with a non-zero third decimal (e.g., $2.152) cannot be directly represented in 2-decimal format. Zeroing the third decimal first ensures no rounding errors occur when the format switches.
{% endhint %}
{% endstep %}
{% step %}
### Update PPU and Total Decimal Positions
1. Navigate to **Forecourt > Fuel > Fuel Configuration Pending > Site Parameters**.
2. Set **PPU Decimal Position** to **2**.
3. Set **Total Decimal Position** to **2**.
4. Click **Save**.
{% endstep %}
{% step %}
### Enter New Fuel Prices in $XX.XX Format
1. Navigate to **Forecourt > Fuel Prices Pending**.
2. Enter the new prices in **$XX.XX format** (e.g., $11.29) for all products.
3. Update both **Tier One** and **Tier Two** prices for each product.
4. Click **Save**.
{% hint style="info" %}
For more details on Cash Credit Pricing, refer to the Cash Credit Pricing section of the Verifone Commander User Reference, available on Premier Portal.
{% endhint %}
{% endstep %}
{% endstepper %}
### Performing a Full Fuel Initialization
After completing all configuration steps, a **Full Fuel Initialization** is **mandatory**. A Fuel Price Initialization alone is not sufficient when the PPU decimal format has changed — it will not reprogram the dispensers with the new decimal setting.
#### Why a Full Fuel Initialization is Required
* **Fuel Price Initialization:** Updates fuel prices only. Does **not** update the PPU decimal format on the dispensers. Performing a Fuel Price Initialization when the PPU decimal differs between pending and in-effect configuration is now **blocked by the system**.
* **Full Fuel Initialization:** Updates both fuel prices **and** the PPU decimal format on all dispensers. This is the only initialization that fully synchronizes the POS, dispensers, and host reporting.
{% hint style="warning" %}
If a Fuel Price Initialization is attempted when a PPU decimal format change is pending, the Configuration Client will display the following message and the initialization will be blocked:
*“Cannot update prices. PPU decimal format has changed. Please perform a Full Fuel Initialization.”*
{% endhint %}
#### Performing the Full Fuel Initialization
{% stepper %}
{% step %}
### Ensure dispensers are ready
Ensure all dispensers are online and bagged or blocked off.
{% endstep %}
{% step %}
### Initialize fuel
Navigate to the Fuel Initialization function on the Commander.
Select **Initialize Fuel**.
{% endstep %}
{% step %}
### Confirm and perform initialization
Confirm and perform the initialization.
{% endstep %}
{% step %}
### Verify dispenser prices
Verify that all dispensers display the correct prices in the new **$XX.XX** format.
{% endstep %}
{% step %}
### Resume fuel sales
The dispensers can now be unbagged or unblocked to begin fuel sales using the new two-digit pricing.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
After a successful Full Fuel Initialization has been completed, future routine price changes can be applied using a regular Fuel Price Initialization— no Full Initialization will be required unless the PPU decimal format is changed again.
{% endhint %}
### Troubleshooting
Fuel Price Initialization Is Blocked After PPU Change
* **Symptom:** Configuration Client displays “Cannot update prices. PPU decimal format has changed.”
* **Cause:** A PPU decimal format change has been saved to pending configuration but a Full Fuel Initialization has not yet been performed. The system blocks Fuel Price Initialization to prevent incorrect price data from being stored or transmitted to the host.
* **Resolution:** Perform a Full Fuel Initialization. Fuel Price Initialization will be available again once the Full Initialization completes successfully.
Dispenser Shows Incorrect Price Format
* **Symptom:** After changing the PPU decimal format, dispensers still display prices in the old $X.XXX format.
* **Cause:** Only a Fuel Price Initialization was performed, which does not reprogram the dispenser PPU decimal setting.
* **Resolution:** Check the dispenser programming to be sure that PPU is configured for two decimal positions.
Host Receives Incorrect Price Change Notifications
* **Symptom:** After switching to $XX.XX format, the Price Change Notification sent to the host shows prices in $X.XXX format. For example, a configured price of $11.29 is received by the host as $1.129.
* **Cause:** The host interface requires modifications to support the new decimal place handling.
* **Resolution:** Upgrade to Release 056.03.02, 057.01.00, or 057.02.00 or later. No configuration workaround exists for affected versions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/handling-fuel-prices-over-usd9.999-gal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.