> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ecommerce/sync-system-fields.md).

# Sync System Fields

System fields are essential for smooth and error-free e-commerce operations.

Step 1: Sync System Fields

1. Go to **Dashboard → Products → E-commerce**
2. Click **System Fields** (left menu)
3. Click **Sync System Fields** (top right)
4. Go to **Order** section
5. Click **Sync System Fields** again
6. Wait for the sync to complete

Step 2: Manage Order Fields

* Default system fields (like **Order Status**) are pre-added
* You can:
  * Add new status values
  * Delete unused ones
  * Save changes

Important for International Businesses

If:

* Your business is **not registered in India**, or
* Your WhatsApp number is **not +91**,

Then:

7. Go to **Origin City / Product System Fields**
8. Edit mandatory fields like:
   * Origin Country
   * Importer Name
   * WhatsApp Compliance Category
9. Remove mandatory requirement (if not applicable)
10. Save changes

Syncing system fields ensures proper order tracking, compliance handling, and smooth e-commerce functionality.

{% embed url="<https://youtu.be/1azqWUwkeBw>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ecommerce/sync-system-fields.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.