> For the complete documentation index, see [llms.txt](https://ova-themes.gitbook.io/tripgo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ova-themes.gitbook.io/tripgo/tripgo-menu/custom-checkout-field.md).

# Custom Checkout Field

Go to Tripgo >> Custom checkout field

## 1: Create custom checkout fields

Custom Checkout Field will be displayed in Booking Form and Enquiry Booking Form.

**Go to Tripgo >> Custom checkout field >>** Click **Add Field**

* **Types**: The theme supports 9 different types of Custom Checkout fields including Text, Password, Email, Phone, Textarea, Select(dropdown), File, Checkbox, Radio
* **Slug:** This name will be show in List of Custom Checkout Fields in backen&#x64;**.** You should add Unique Name, Not Space and Lowercase.
* **Price:** The Price Field only use for some types of Custom Checkout Field such as Radio, Checkbox and Select.
* **Label:** Label of Custom Checkout Field will be displayed at frontend
* **Default Value:**
* **Class:**
* **Required**: Mark Custom Checkout fields as required/non-required
* **Enable**: Enable/Disable Custom Checkout field in the form. This value is overridden in each product.

<div><figure><img src="/files/EaUQ7mxpmYpXsHkQdrPE" alt=""><figcaption></figcaption></figure> <figure><img src="/files/GfMPz0QG5aLS5V2dvYQI" alt=""><figcaption><p>Select type</p></figcaption></figure></div>

<div><figure><img src="/files/fjaxW3XzVcFPSiwx0pR5" alt=""><figcaption><p>Checkbox type</p></figcaption></figure> <figure><img src="/files/V9eYftVd4GEsT2Deniiw" alt=""><figcaption><p>Radio type</p></figcaption></figure> <figure><img src="/files/6cP8aOeJNHlRMJ97M0Tp" alt=""><figcaption><p>Text type</p></figcaption></figure> <figure><img src="/files/FsQ1wxxPkmp0qfUi2unf" alt=""><figcaption><p>Phone type</p></figcaption></figure></div>

<div><figure><img src="/files/QwySWfISBZHgatlMRYF8" alt=""><figcaption><p>Email type</p></figcaption></figure> <figure><img src="/files/pEn5KpD2byhHXm21kWja" alt=""><figcaption><p>Password type</p></figcaption></figure> <figure><img src="/files/ClKGTqxY82aLrKRkPGQP" alt=""><figcaption><p>Textarea type</p></figcaption></figure> <figure><img src="/files/HjrAxlheCMeBLXtJ2vGD" alt=""><figcaption><p>File Type</p></figcaption></figure></div>

## 2: Use Custom Checkout Field

If you want to create a new product and like to add separate Custom Checkout Fields for that product:

Go to P**roducts >> Add New >> Advanced Options >> Custom Checkout Fields**

In Display Custom Fields From Drop-down, there are 2 options to choose:

* **Category Setting :** Get fields that setup in [category](/tripgo/tripgo-menu/categories.md)
* **New:** You can choose some fields only for this product
* **No:** Don't use custom checkout field for this product.

<div><figure><img src="/files/qgzmutwLqsZAaVCuHnng" alt=""><figcaption></figcaption></figure> <figure><img src="/files/5Ue1fkIHF8PLcRoaR63k" alt=""><figcaption></figcaption></figure> <figure><img src="/files/eMrPDOnM5tM7qJ7uhNfs" alt=""><figcaption></figcaption></figure></div>

## 3: Display at frontend

The custom checkout fields will display in Booking Form and Request Form

<figure><img src="/files/1R1XsioM3bHGldC1ygGv" alt=""><figcaption></figcaption></figure>


---

# 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://ova-themes.gitbook.io/tripgo/tripgo-menu/custom-checkout-field.md?ask=<question>&goal=<endgoal>
```

`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.
