# Fuel Sales reorg sample

## Overview

Use this sample to review a cleaner structure for Fuel Sales.

It keeps the same subject matter. It changes the order and grouping.

{% hint style="info" %}
This is a draft structure. It does not replace the current Fuel Sales page.
{% endhint %}

## Start by task

Choose the task that matches the sale flow:

* **Prepay fuel** — customer pays before fueling.
* **Preset fuel** — set a fuel limit, then collect payment after fueling.
* **Postpay fuel** — bring a completed fuel sale into the transaction.
* **Pump control** — approve, stop, restart, or view pump activity.
* **Exceptions** — move prepay, convert fuel MOP, add tax changes, or reprint tickets.

## Proposed page split

### 1. Fuel Sales overview

Keep this page short. Use it as the entry point.

Include:

* sale types and when to use each one
* pump status basics
* links to task pages

### 2. Prepay fuel sales

Move these tasks together:

* Prepay Fuel Sale by Amount
* Prepay Fuel Sale by Volume
* Prepay Fuel Sale with Merchandise
* Rest In Gas
* Fuel Prepay Move
* Clear Reserve

### 3. Preset and postpay fuel sales

Move these tasks together:

* Preset Fuel Sale by Dollar Amount
* Preset Fuel Sale by Volume
* Postpay Fuel Sale
* Manual Fuel Sale
* Fuel Convert

### 4. Discounts and tax handling

Move these tasks together:

* Fuel Discount with Fuel Disc Key
* Fuel Discount from Other Fuel
* Postpay Fuel Tax Exemption or Addition
* Fuel Tax Exemption
* Fuel Tax Addition

### 5. Pump control and status

Move these tasks together:

* Approve One Calling Pump
* Approve All Calling Pumps
* Disapprove a Pump
* Restarting a Stopped Pump
* Stop One Pump
* Stop All Pumps
* View Due Fuel Sales
* View Pump Status

### 6. Receipts, tickets, and troubleshooting

Move these tasks together:

* Fuel Ticket Print
* DCR Ticket Print
* fuel sale status tables
* error messages

## Sample opening rewrite

### What you can do in Fuel Sales

Use Fuel Sales to start, control, and complete fuel transactions.

Common flows are:

* **Prepay** for customers who pay before dispensing.
* **Preset** for customers who need a fixed dollar or volume limit.
* **Postpay** for customers who fuel first and pay inside.

Open [Fuel Manager](/commander-user-reference-guides/commander-user-references/commander-user-reference-57.00/fuel-manager.md) for site controls and configuration.

### Choose the right workflow

#### Use prepay when

* the customer pays before dispensing
* the site requires prepay-only operation
* the cashier needs to set a fixed amount or volume first

#### Use preset when

* the pump must stop at a target amount or volume
* payment is collected after dispensing
* the cashier needs to authorize a limited sale quickly

#### Use postpay when

* the customer already dispensed fuel
* the sale is due inside
* the cashier needs to add the fuel line to the current transaction

## Sample task section

### Prepay fuel by amount

Use this flow when the customer pays a fixed amount before fueling.

{% stepper %}
{% step %}

### Select the pump

Press **\[PREPAY]** and enter the pump number.
{% endstep %}

{% step %}

### Confirm the selection

Press **\[ENTER]**.
{% endstep %}

{% step %}

### Enter the prepay amount

Enter the amount. Then select the method of payment.
{% endstep %}

{% step %}

### Complete the sale

Finish tender. The pump is approved for the prepaid amount.
{% endstep %}
{% endstepper %}

### What happens next

* The pump stops at the prepaid amount.
* The pump can stop sooner if the tank fills first.
* If the sale needs to move, use **Fuel Prepay Move**.

## Sample support section

### Pump statuses to know first

Focus on the statuses that change cashier action:

* **Calling** — approve the pump if manual approval is required.
* **Reserved** — a prepay sale is attached to the pump.
* **Due** — bring the sale into the transaction and tender it.
* **Stopped** — the pump was stopped at the POS.
* **Offline** — the controller is not communicating with the pump.

## Why this structure scores better

This structure improves quality because it:

* starts with user tasks
* reduces duplication
* separates operations from reference tables
* makes scanning faster
* gives each workflow a clear home

## Next step

If this direction works, apply the same pattern to the live [Fuel Sales](broken://spaces/vbu5hXPd6kwo3uSpxPju/pages/9vICUyZVY4LT3qRnWLxl) chapter and split the long sections into dedicated child pages.


---

# Agent Instructions: 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:

```
GET https://docs.verifone.com/commander-user-reference-guides/test-area/fuel-sales-reorg-sample.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.