> 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/fleet-cards-general-fuel-configuration-and-usage/configuring-commercial-fleet-cards/configuring-primary-fuel-products-as-secondary-products.md).

# Configuring Primary Fuel Products as Secondary Products

To enable to fuel a primary product as a secondary product with a different name, configure Secondary Products from **Configuration Client > Forecourt > Fuel Config > Fuel Products**tab.

For Example, Tractor and Reefer are dispensed from the diesel hose and is Diesel but named as Tractor and Reefer.

Tank and Price for the secondary products is same as Primary product. Secondary Product has its own product code.

The advantage of using the primary product as a secondary product with a different name is that the product when used as a secondary product can save tax or/and can be eligible for a discount.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/QdbsMooo8CQfMb9ULQmy/Unknown%20image)

1. Enable Secondary Product
2. In the Name feild, enter a name for the secondary product. *The name given for the fuel product in this field is what is displayed to the customer and cashier, so choose name appropriately.*
3. From the Primary Product drop-down list, select the primary product that is used as the secondary product.
4. Click **Save**.


---

# 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/feature-references/features-and-products-references/fleet-cards-general-fuel-configuration-and-usage/configuring-commercial-fleet-cards/configuring-primary-fuel-products-as-secondary-products.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.
