> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/configuration-client-forms/forecourt.md). # Forecourt ![Forecourt Tab](/files/0e80b243db7e4917aebce38dbc92e9f2d6dc8cb6) ### DCR Refer to Configuring Dispenser Card Readers ### Fuel Refer to Fuel Configuration #### Fuel Prices {% hint style="info" %} *Refer to Cash Credit Pricing for more information.* {% endhint %} The Pricing Manager form is used to set up fuel pricing, including tier pricing. Tier Two pricing can be set up at any time but does not take effect until the appropriate information is entered in the “Start Tier 2 Pricing” and “Number of Tier Hours” parameters in Fuel > Site Parameters > Fuel Site Parameters. Select the product, then double-click the Price text boxes and enter the price (0.000 - 9.999). The price of all products changes to match the price entered in the top text box after ENTER is pressed. Prices can be edited if necessary. {% hint style="info" %} *When entering a price, take care when placing the decimal point. For example, to change a price to 1.159, enter it as written here. To change a price to 1.500, enter the trailing zeros*. {% endhint %} If you only change fuel prices, for the changes to take effect, initialize Fuel Prices by selecting: * Forecourt > Initialization > Fuel Prices If you change other fuel parameters as well as prices, you will need to initialize Fuel and DCRs for the changes to take effect. To do this, select both of the following: * Forecourt > Initialization > Fuel * Forecourt > Initialization > DCRs {% hint style="info" %} *Make sure that your fueling positions are not in use when initializing any Fuel Prices, Fuel, or DCRs.* {% endhint %} ![](/files/a7114a5d31e6138b816381de94855692c012c8cf) The fuel prices have a limit of four characters and can take only a maximum of $9.999 with three decimal places. This document shows how to configure a site to set fuel prices to 2 decimal places to support price that are greater than $9.999 per gallon in the $xx.xx format. #### Configuring Fuel Prices for 2 Decimal Places Some sites need to change how fuel prices are displayed and processed — for example, moving from a 3-decimal price format ($X.XXX per unit) to a 2-decimal format ($XX.XX per unit) to support higher fuel prices. This is done by changing the site's PPU (Price Per Unit) decimal setting. 1. Go to **Forecourt > Fuel > Fuel Config Pending > Site Parameters**and disable “Force .9 Cents Per Gallon”.

2. Go to Forecourt > Fuel Prices Pending and change all existing product prices with third decimal place to 0 (eg: from $2.152 to $2.150).

3. Go to **Forecourt > Fuel > Fuel Config Pending > Site Parameters**and change “PPU Decimal Position” and “Total Decimal Position” to “2”.

4. Go to Forecourt > Fuel Prices Pending and change the prices of the product per gallon to the $XX.XX format for both Tier One and Two Prices. ![](/files/a9dd2576992b64ece738c1dd7d2d07d06bda21c1) #### Feature Limitations * Sites can be configured to take fuel prices with either two or three decimal places; $xx.xx or $x.xxx. Sites cannot have mixed decimal positions while using a single Verifone Commander. * At two decimal sites, prices that have 3 decimal places (eg. $4.299) will only be calculated at the 2 decimal amount (eg. $4.29). * By default, sites are configured for 3 decimal places in $x.xxx format. #### Correct Steps When Switching PPU Decimal Places (e.g. $X.XXX → $XX.XX) A defect was identified where, after changing the PPU decimal setting and updating fuel prices, the Price Change Notification sent to the host (used for reporting and reconciliation) could still show prices in the old format. For example, a price correctly set and displayed as $11.29 could be reported to the host as if it were $1.129 — a tenfold difference.


What the Site Configured	What Was Sent to the Host
Product 001 price set to $11.29 (correct, 2-decimal format)	Price Change Notification reported $1.129 — a tenfold error
Product 002 price set to $11.89	Reported as $1.189
Product 003 price set to $12.29	Reported as $1.229

The prices displayed correctly on the POS and at the pump — the problem was specifically in the data sent to the host for reporting and reconciliation. This could cause discrepancies between what the site charged and what the host's records showed. **Two corrections were made to resolve this:**

Change	What It Means for Your Site
Price data is now stored consistently	Fuel prices are now always stored internally using a fixed, consistent format regardless of the site's PPU decimal setting. This means the price-change reporting used for Chevron (and similar hosts) now always reflects the correct price — for example, $11.29 is now correctly reported as such, not as $1.129.
Fuel Prices Init is now blocked after a PPU format change — until a Fuel Init is done	If you change the PPU decimal setting and then try to run a Fuel Prices Init before running a full Fuel Init, the system will now block the action and show a message telling you to perform a Fuel Init first. This prevents prices from being pushed out in a way that would create a mismatch between the pump, the POS, and the host.

{% hint style="info" %} ℹ Note: Available from Base 057.01.00, Base 056.03.02, and Base 057.00.02. {% endhint %} **New Warning Message** If you attempt a Fuel Prices Init while the PPU decimal setting is out of sync between what's configured and what the site is currently running on, the Configuration Client will now show the following message and block the action: **“Cannot update prices. PPU decimal format has changed. Please perform a Full Fuel Init.”** {% hint style="success" %} ✔ Good to know: If you see this message, it is working as designed — it is telling you exactly what to do next: run a Fuel Initialisation (Full Init) instead of a Fuel Prices Initilisation. After the Fuel Initialisation is completed successfully, perform a Fuel Prices Initialisation as normal for any further price changes. {% endhint %} #### Correct Procedure — Changing the PPU Decimal Format Whenever your site changes the PPU decimal setting (for example, moving to 2 decimals to support prices of $10.00 or more), follow these steps in order:


1	Plan for forecourt downtime	Changing the PPU decimal format requires every dispenser to be reprogrammed. Expect the forecourt to be closed for at least an hour, possibly longer depending on the number of dispensers.
2	Update the PPU decimal setting	Change the PPU decimal configuration (e.g. from 3 to 2 decimals) in the site configuration.
3	Update fuel prices to the new format	Set your new fuel prices in the format that matches the new decimal setting (e.g. $11.29 instead of $1.129).
4	Run a Fuel Init (Full Init) — not a Fuel Prices Init	This is the critical step. A Full Init reprograms every dispenser with the new price format and synchronises the POS, the pump display, and the price data sent to your host, all at once.
5	Verify prices at each dispenser	As each pump is reprogrammed, visually confirm it displays the correct price in the new format before reopening that pump to customers.
6	Reopen the forecourt	Once all dispensers show the correct price and format, reopen the forecourt for business.
7	Future price changes	After the Full Init above has completed successfully, you may go back to using the normal Fuel Prices Init for any subsequent price changes, as usual — no Full Init is needed for routine price updates that don't involve a PPU format change.

{% hint style="danger" %} ⚠ Important: Do not attempt a Fuel Prices Init immediately after changing the PPU decimal setting. The system will now block this and prompt you to run a Fuel Init first — this is expected and required to keep pricing correct and consistent across the pump, POS, and host. {% endhint %} **Why the Order of Steps Matters**

If You...	What Happens
Run a Full Fuel Init after changing the PPU decimal setting (correct)	Every dispenser is reprogrammed with the new price format. The POS, the pump display, and the price data sent to the host all stay in sync and show the correct price.
Try a Fuel Prices Init only, after changing the PPU decimal setting (blocked)	The system now blocks this action and displays the warning message, because a Prices Init alone does not reprogram the dispenser's price format — this would leave the pump showing the old format while the POS shows the new one, and could send incorrect price data to the host.
Run routine price changes without changing the PPU format	A normal Fuel Prices Init works exactly as before — no Full Init is required for everyday price changes that do not involve a format change.

**What Site Staff Will Notice**

What You May Notice	Explanation
A warning message appears when trying to update prices after a PPU format change	This is expected. It means a Full Fuel Init is needed first. Follow the on-screen instruction.
Prices reported to the host now match what customers are charged	This was the core of the fix — price-change data sent to Chevron (or similar hosts) now correctly reflects the actual price, in any PPU decimal format.
No change to everyday price updates	If you are not changing the PPU decimal format, price updates continue to work exactly as before — no extra steps needed.
The forecourt must close briefly whenever the PPU format itself is changed	This is a hardware requirement — every dispenser must be reprogrammed. This is not new behaviour caused by this fix, but it is the reason the Full Init step exists.

**Frequently Asked Questions**

Question	Answer
Why do I need to change the PPU decimal format at all?	Some fuel products now cost $10.00 or more. The traditional 3-decimal display ($X.XXX) can't correctly show prices of $10.00 and above at the pump, so sites move to a 2-decimal format ($XX.XX) to display these prices correctly.
What happens if I try to update prices right after changing the PPU format, without a Full Init?	The system will block the action and show a message asking you to perform a Full Fuel Init first. This is intentional — it prevents incorrect pricing data from reaching the pump display or your host.
Do I need to do a Full Init every time I change a fuel price?	No. A Full Init is only required the first time after you change the PPU decimal format. After that, routine price changes go back to using the normal Fuel Prices Init.
Will customers see the wrong price at the pump if I don't follow these steps?	If you skip the required Full Init after a PPU format change, the pump could continue showing the old price format until a Full Init is completed — which is why the system now blocks Fuel Prices Init in this situation until you do it correctly.
Does this affect prices at the register (POS) too, or just the host report?	The core defect was in the data reported to the host. Prices at the POS were already showing correctly. However, following the correct Full Init procedure after any PPU format change keeps the pump, POS, and host completely in sync.
Is this specific to Chevron sites?	The defect was reported by Chevron and the price-reporting fix directly affects the Chevron host interface. The underlying storage fix and the Full-Init requirement apply more broadly and were also validated on Buypass-connected sites.
What should I do if I already changed the PPU format before this fix was installed and the host prices look wrong?	Performing a clean Full Fuel Init corrects the situation going forward — once completed, subsequent price changes will report correctly to the host.
Who do I contact if I'm not sure whether my site needs this Full Init step?	Contact your VeriFone service representative or help desk before changing the PPU decimal format — they can confirm the correct sequence of steps for your site and base version.

**Quick Reference Summary**

Topic	Summary
What this fix addresses	Price Change Notifications sent to the host (e.g. Chevron) now correctly reflect the site's fuel prices, in any PPU decimal format.
Golden rule	After changing the PPU decimal format, ALWAYS run a Full Fuel Init before any Fuel Prices Init.
What's blocked	Fuel Prices Init is blocked if the PPU decimal setting differs between what's configured and what's currently running — until a Full Init is done.
Warning message (English)	“Cannot update prices. PPU decimal format has changed. Please perform a Full Fuel Init.”
Warning message (Spanish)	“No se pueden cambiar los precios. El formato decimal del PPU ha cambiado. Realice una inicialización de combustible completa.”
Routine price changes	Unaffected — continue using Fuel Prices Init as normal when the PPU format is not changing.
Forecourt impact	Expect the forecourt to close temporarily whenever the PPU decimal format itself is changed, so every dispenser can be reprogrammed.
Available from	Base 057.01.00, Base 056.03.02, Base 057.00.02.

### DCR Keys Each DCR should be assigned to a DCR key configuration. If sites have a mix of DCRs with and without alphanumeric capabilities, sites will require to create 2 or more DCR key configurations. The configuration for DCRs that are alphanumeric should have the “Enable Alphanumeric” checked, and NOT checked for the DCRs that only accept number input. Use to configure DCR keys for the different DCR positions. ![](/files/3b8d8340eeca08665c14d5ae65be0964cb688f14) | Field/Button | Allowable Value/Function | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Add | Click Add to configure new DCR Keys layout. | | Delete | Select to delete the selected DCR Keys layout. | | Label | Label the new DCR Keys layout. | | Enable Alphanumeric | The configuration for DCRs that are alphanumeric should have the “Enable Alphanumeric” checked to use the alphanumeric keys layout. This field should NOT be checked for the DCRs that only accept number input. | | Assign Positions | Click assign positions and select the DCR that can be used for entering alphanumeric characters. The DCRs that do not have alphanumeric capabilities are grayed out. | | #Rows | Number of rows for the DCR Keys layout. | | #Columns | Number of columns for the DCR Keys layout. | | Assign Positions | Select to assign the DCR Keys layout to the DCRs in the site. | {% hint style="info" %} *Click on the keys to configure the values.* {% endhint %} ### DCR Idle Screen The DCR Idle Screen Configuration form is used to set up what displays on the DCR screen when not in use. ![](/files/7d1f756f8579ae3455ccb845a1aa9f135b6e3d4c) ![](/files/c810623fa973e1caac37d186eca25dada4a88721) | **Field/Button** | **Allowable Value/Function** | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Add | Click Add to configure new DCR idle screen. | | Delete | Select to delete the selected DCR idle screen. | | Name | Enter a name for the DCR idle screen. | | DCR Non-Graphic Idle Screen |

These are the text lines that the user would like to appear on a Non-Graphic DCR’s Idle Screen.

If it’s a 4-Line display DCR, then the 4 configured lines would appear on the screen on one-line each.
If it’s a 2-Line or Single-Line display DCR, then the 4 lines could scroll one after the other in that order.

| | Graphic Enabled | Select if the DCR has a Graphic Keypad. If this field is disabled, the panel below would show the “DCR Non-Graphic Idle Screen” configuration. If it is enabled, it would show the “DCR Graphic Idle Screen” configuration. | | DCR Graphic Idle Screen |

If the “Graphics Enabled” is selected, the Graphic Idle Screen configuration opens. The Left and Right keys allow the user to configure what is displayed on each of the keys. The middle lines provide the user the option of displaying some lines in the middle for the top two rows and use the bottom 2 rows for the keys. If the Middle Text Line is configured, the keys on those lines are not displayed on the DCR. On clicking each of the key buttons, the following pop-up to configure the key is displayed.

Softkey Type: Tags the key text to one of the pre-defined types.
Softkey Text: The text that is displayed for this key on the DCR. After the text is entered here, the text next to the button changes to reflect this text.

| | Assign Positions | Select to assign the DCR idle screen to the DCRs in the site. | ### Outdoor TAVE {% hint style="info" %} *Refer to the TAVE Feature Reference documentation for information on this feature.* {% endhint %} ### Cash Acceptor The Cash Acceptor Configuration form is used to set up and edit cash acceptors at the site. Site Information determines the behavior of all cash acceptors at a site. Attributes determines the behavior of a specific cash acceptor at a specific fueling point. Select the Cash Acceptor on the list on the bottom of the form, then select the value check boxes that are applicable for that Cash Acceptor. ![](/files/b6006202b892e2c90b0dae9221b2300955fba7ae)

Field/Button	Allowable Value/Function
Disable If Cheated	Select to turn off a cash acceptor when someone tries to cheat it.
Disable If Paper Low	Select to turn off a cash acceptor if the receipt tape is running out.
Disable If No Printer	Select to turn off a cash acceptor if the printer is not working.
Prompt ‘insert cash’	Select to have the phrase “OR INSERT CASH” appear at the end of the idle prompt.
$1 Bill Enabled	Select to allow acceptance of one-dollar bills.
$2 Bill Enabled	Select to allow acceptance of two-dollar bills.
$5 Bill Enabled	Select to allow acceptance of five-dollar bills.
$10 Bill Enabled	Select to allow acceptance of ten-dollar bills.
$20 Bill Enabled	Select to allow acceptance of twenty-dollar bills.
$50 Bill Enabled	Select to allow acceptance of fifty-dollar bills.
$100 Bill Enabled	Select to allow acceptance of one hundred-dollar bills.
Bill Orientation	This parameter does not apply to Tokheim dispensers. Select to require that bills are inserted face-up with the black-seal end first. (If not selected, bills can be inserted face-up in either direction.) Note: The black seal appears on the front of the bill to the left of the face.
Timeout [Seconds 10-99]	Enter the time (in seconds) between when a customer inserts a bill and when the pump shuts off if no fuel has been pumped (10 - 99).
Cash Acceptor Attributes - Cash Acceptor	Select the number of the fueling point.
Duplicate Acceptor	Click to copy the current cash acceptor’s attributes to any number of other cash acceptors. In the Duplicating Acceptor form, select the cash acceptor(s) to which you want to copy and click Done Duplicating.
Cash Acceptor In Dispenser	Select to indicate that the fuel pump has a cash acceptor.
Reset Printer Error	Note: This parameter is not currently supported. Note: Select to enable the printer after the cash acceptor has been disabled and brought back online.
Print Totals Now	Note: This parameter is not currently supported. Note: Select to print the amount of money in the cash acceptor.

### Fuel Tax Exempt The Fuel Tax Exemption Configuration form allows taxes to be removed from a post-pay fuel sale by setting up one to five fuel tax exemptions. Each exemption can either be setup by the Amount Per Gallon or the Tax File Entry that is setup in **Store Operations > Payment > Tax Rates**, or Both. The Fuel Tax Exempt Receipt Lines section is used to enter up to four lines of text that you want to print on the header of Fuel Tax Exemption receipts. ![](/files/659f6956832f4f230bc80fcc9d3f9f7fab560db4) | Field/Button | Allowable Value/Function | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Fuel Tax Exempt Record | Select a record number. | | Delete | Select to delete the selected fuel tax exempt record. | | Name | Enter a name for the fuel tax exemption. The name appears on receipts and reports. | | Amount | Enter the dollar amount per gallon of tax (0.000 – 99.000) | | Type | Select the tax type to exempt: Amount Per Gallon – The dollar amount per gallon. Tax File Entry – Taxes applied in **Store Operations > Payment > Tax Rates**. Both – A combination of Amount Per Gallon and the tax rates entry that is setup in Store Operations > Payment > Tax Rates. | | Signature Line | Select to print the receipt with a signature line to certify the customer’s eligibility for the tax exemption. | | Fuel Tax Receipt Lines (1 - 4) | Enter up to four header lines for the fuel tax exemption receipt (alphanumeric, 1 - 10 characters). | ### Rapid Change Fuel Config Rapid Change Fuel configuration is configured from **Forecourt > Rapid Change Fuel Config**. This feature allows the cashier to change the pump’s service level and auto approval rapidly at the pump using the POS without having to change the fuel configuration using Verifone Commander Configuration Client or without manager intervention. ![](/files/609517812a0d99ab5893481c988c275172622381) To change the fuel configuration level from the POS, the cashier should access *CSR Functions > Fuel Manager > Rapid Change Fuel Configuration*. ### Unattended DCR {% hint style="info" %} *Refer to the Unattended Fueling feature reference documentation for information on this feature.* {% endhint %} --- # 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://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/configuration-client-forms/forecourt.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.