> For the complete documentation index, see [llms.txt](https://help.stockeo.solvenium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stockeo.solvenium.com/data-mapping/quantity-format.md).

# Quantity format

#### Decimal separator

Comma or point. A comma is interpreted as a decimal separator only if followed by two digits to avoid ambiguity with a comma being used as a thousand separator.

The following notation will be ignored by Stockeo and will not update the stock of this product in your store.

<figure><img src="https://2071801931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz6HyRe5TyFXHKQEybH7n%2Fuploads%2Fgit-blob-e67f698100618c4315a8c7db925575e28ba5c74d%2Fstockeo-quanitty-non-interpretable-comma-notation.gif?alt=media" alt="The notation with one or three decimal places that will be ingnored by Stockeo annotated"><figcaption><p>The comma notation of quantity that will be ingnored by Stockeo</p></figcaption></figure>

Shopify only allows quantity to be stored as an integer. When the quantity in the feed is a decimal number, it will be rounded in accordance with the mathematics.

<figure><img src="https://2071801931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz6HyRe5TyFXHKQEybH7n%2Fuploads%2Fgit-blob-80ac9cf60a2df678cf5083857a8875bdb8f02721%2Fstockeo-quantity-interpretable-comma-notation.gif?alt=media" alt="The notation with two decimal places that will be ingnored by Stockeo annotated"><figcaption><p>The comma notation of quantity that will be interpreted by Stockeo</p></figcaption></figure>

The above notation will update the stock to 3 and 4 respectively.

#### Approximate values

Sometimes in the feeds from some suppliers, there is a notation that the quantity of product is greater than a certain value. Stockeo then always sets the stock equal to this value, omitting the greater than and plus signs.

<figure><img src="https://2071801931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz6HyRe5TyFXHKQEybH7n%2Fuploads%2Fgit-blob-06775cd8ae115c9b8055d39099ed9a7f1f593aec%2Fstockeo-signs-before-and-after-quantity.gif?alt=media" alt="Different quantity notations in Stockeo for Shopify annotated"><figcaption><p>Different quantity notations handled by Stockeo</p></figcaption></figure>

All of the notations above are equivalent and will result in the following results:

<figure><img src="https://2071801931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz6HyRe5TyFXHKQEybH7n%2Fuploads%2Fgit-blob-efe4077e12ef6f198c8aa79cb2576bffff6669c7%2Fstockeo-quantity-updating.png?alt=media" alt="Quantity updated by Stockeo according to notations above annotated"><figcaption><p>Quantity updated by Stockeo according to the notations above</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.stockeo.solvenium.com/data-mapping/quantity-format.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.
