> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/math-actions/rule-action-round-number.md).

# Round prices and numeric values

Round numeric product values to a chosen precision or price point.

Use **`Round number`** to round numeric field values after a calculation.

This action is useful for tasks such as:

* Rounding prices to two decimal places.
* Rounding a value up, down, or to the closest amount.
* Creating prices that end in a chosen value, such as `.95`.

### Available rounding options

Choose one of these rounding directions:

* `closest`
* `up`
* `down`

Choose one of these values to round to:

* `1 cent`
* `5 cents`
* `10 cents`
* `25 cents`
* `95 cents`
* `99 cents`
* `whole number`

***

## Example `Round number` use cases

{% hint style="info" %}

#### Important details

Choose whether to round values up, down, or to the closest result. For example, `9.3412` rounds to `8.95` when you select the closest 95 cents.
{% endhint %}

### Round a calculated price

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Round number`** of `sale_price` to `closest` `99 cents`

### Create prices ending in .95

#### How to build a rule

* Condition: **`For all items`**
* Action: THEN **`Round number`** of `price` to `closest` `95 cents`


---

# 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://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-actions-then-in-rules/math-actions/rule-action-round-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.
