> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/checkout-custom-fields-builder-for-woocommerce/checkout-builder-elements/number.md).

# Number

## **Element Description**

The **Number** field allows users to input numerical data during the checkout process. It can be used to capture values such as quantities, order numbers, or any other relevant numerical information.

<figure><img src="https://1670878215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbK04jKOIhkmxYUGKxuyO%2Fuploads%2FmRawoFfXgXGqcr1pchuL%2Fimage.png?alt=media&amp;token=160c5780-6a82-469d-9c1e-1f4f5c475fad" alt=""><figcaption></figcaption></figure>

**Sample Use Cases**

* Collect the number of items for a custom order.
* Specify an order reference or ID number.
* Gather quantity details for bulk purchases.

<figure><img src="https://1670878215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbK04jKOIhkmxYUGKxuyO%2Fuploads%2FIWHS3XU71t3ReaKkIOZJ%2Fimage.png?alt=media&amp;token=5d49570a-19a1-4528-9df4-ed120b935d6f" alt=""><figcaption><p>Sample Number Field</p></figcaption></figure>

## Number Field Settings

<figure><img src="https://1670878215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbK04jKOIhkmxYUGKxuyO%2Fuploads%2F5zfcXWrhpljCud6H5gZJ%2Fimage.png?alt=media&amp;token=1ca1f963-2f89-498c-aa47-5d5ece14817a" alt=""><figcaption></figcaption></figure>

* **Label** – The name of the field displayed to customers on the checkout page.
* **Placeholder** – The text that appears inside the input box before the customer enters any number.
* **Description** – Additional information or instructions that will appear below the input box.
* **Enable/Disable Field** – Allows you to enable or disable the field based on your needs. If it is disabled, the element will not be displayed in the checkout form, you can enable it anytime from the checkout builder according to your needs.
* **Is Required** – Makes the field mandatory for customers before completing their purchase.
* **Default Value** – Pre-fill the number field with a default value when the checkout page loads.
* **Min. Value** – Specify the minimum value that can be entered in this field.
* **Max. Value** – Specify the maximum value that can be entered in this field.
* **Step Value** – Define the step increments for the numbers (e.g., increase by 1, 15, 30, etc.).

**Advanced Settings**

* **Custom Class Name** – Add [**custom CSS classes**](/checkout-custom-fields-builder-for-woocommerce/plugin-features/custom-classes.md) to style or further customize the field.


---

# 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://docs.stylemixthemes.com/checkout-custom-fields-builder-for-woocommerce/checkout-builder-elements/number.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.
