> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/field-guides/variant-settings.md).

# Inventory, tax, shipping and customs

Bulk edit inventory tracking, selling when out of stock, tax, physical product flag, customs data, weight and unit price.

These variant fields change settings that live on each variant. All of them can be limited with **Apply to variants**, and all can be reverted.

## Inventory tracked

Choose **Track quantity** or **Don't track quantity**. Turning tracking off lets a variant be sold without a stock count.

## Continue selling when out of stock

Choose **Continue selling when out of stock** or **Stop selling when out of stock**. This is Shopify's inventory policy for the variant.

## Charge tax

Choose **Charge tax** or **Don't charge tax**.

## Is physical product

Choose **Physical product** (requires shipping) or **Digital product** (no shipping).

## Country code of origin

Edit methods: **Replace entire text** or **Set to null/blank**. With **Replace entire text**, pick the country from the searchable list. The code is stored as a two-letter ISO code such as `US`, `VN` or `CN` and is used for customs and duties.

## Province code of origin

Edit methods: **Replace entire text** or **Set to null/blank**. Pick the province or state from the list. This value is used when the country of origin is United States, Canada or Australia.

## Harmonized System (HS) code

Uses the text edit methods plus **Set to null/blank**. Enter a numeric code of 6 to 13 digits, for example `610910`. Values shorter than six digits or containing letters are rejected.

## Weight

| Edit method                      | Inputs                      |
| -------------------------------- | --------------------------- |
| **Set to fixed value** (default) | Value                       |
| Decrease by percentage           | Value (%)                   |
| Increase by percentage           | Value (%)                   |
| Decrease by amount               | Value                       |
| Increase by amount               | Value                       |
| Change weight unit only          | none, only the unit changes |
| Set to null/blank                | clears the weight           |

The **Weight unit** list offers **Don't change unit**, **g**, **kg**, **oz** and **lb**. **Rounding** offers **Round to nearest .01** and **Round to nearest whole number**.

{% hint style="info" %}
**Example.** All variants weigh 250 g and you want them in kilograms: choose **Set to fixed value** `0.25` and **Weight unit** `kg`. To convert only the unit label without touching the number, use **Change weight unit only**.
{% endhint %}

## Unit price

Sets the unit price measurement that some regions require (for example price per 100 g).

* **Set unit price measurement**: enter the **Total measurement** and its unit (how much the variant contains), and the **Reference measurement** and its unit (the base amount the unit price is shown for). Both units must belong to the same group: Weight (mg, g, kg), Volume (ml, cl, L, m³), Size (mm, cm, m), Area (m²) or Per item.
* **Clear unit price**: removes the measurement.

The reference measurement must be a whole number greater than zero.


---

# 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.samita.io/bulk-price-editor-sami/field-guides/variant-settings.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.