> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/retail-operations/products/breaking-variants-into-independent-products.md).

# Breaking Variants Into Independent Products

In Shopify, a parent product may have multiple variants defined by the combination of different features—say, different combinations of sizes and colors. The user can decide to break these combinations into separate products in a manner as described below:

#### Initial Product Setup

* **Parent Product:** HC Shoe
  * **Variants:**

| Colour | Size | SKU |
| ------ | ---- | --- |
| Black  | 7    | 7B  |
| Black  | 8    | 8B  |
| Tan    | 7    | 7T  |
| Tan    | 8    | 8T  |

#### Desired Product Setup

* **Parent Product:** HC Shoe
  * **Variants:**

    | Colour | Size | SKU |
    | :----: | :--: | :-: |
    |  Black |   7  |  7B |
    |  Black |   8  |  8B |
* **Parent Product:** HC Shoe (Tan)
  * **Variants:**

    | Colour | Size | SKU |
    | :----: | :--: | :-: |
    |   Tan  |   7  |  7T |
    |   Tan  |   8  |  8T |

Here, the user has decided to divide the initial parent product into two, each for a separate color, which are further categorized into variants of different sizes. To successfully sync such edits made in Shopify into HotWax OMS without corrupting data (specifically product duplication), the user must follow the process detailed in this manual.

## Steps to break the variants into separate products

### Step 1: Pause product import and sync jobs

* Open [Job Manager](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/README.md), then open `Catalog`.
* Search for and pause these jobs:
  * **Import Products:** imports new products from Shopify.
  * **Sync Products:** updates existing products from Shopify.

See [Manage a job](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/job-details.md) for current pause and run-now instructions.

### Step 2: Edit Variants in Shopify

* Make the required edits in Shopify to separate the variants.
* Ensure the SKUs for the separated variants remain the same as before the edit.

### Step 3: Unlink Variants in HotWax Admin

* Open the product page of the variant in HotWax Admin.
* Scroll to the Shopify Shop Product section on the page.
* Unlink the existing **Shopify Link**.

{% embed url="<https://youtu.be/hpijDK4x_Sc>" %}
Unlinking variants from Shopify in OMS
{% endembed %}

<figure><img src="https://youtu.be/hpijDK4x_Sc" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If the variants are linked to multiple Shopify shops, only unlink them from the specific shop where the edits were made. Keep the links to other shops intact.
{% endhint %}

### Step 4: Sync changes in the Order Management System

* Find and run these jobs from `Catalog`:
  * Sync Product Job: Run this job to update the old product.
  * Import Products Job: Run this job to create the separated variants as a new product.
  * Resume the Sync Product Job.


---

# 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.hotwax.co/documents/retail-operations/products/breaking-variants-into-independent-products.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.
