> 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/learn-shopify/shopify-reference/orders/kit-products-download.md).

# Kit Order Download

Learn how HotWax Commerce downloads kit orders from Shopify.

## How kit orders download from Shopify

HotWax Commerce imports orders for kit products from Shopify through the [order download process](/documents/learn-shopify/shopify-reference/orders/order-download.md).

When HotWax Commerce imports an order, it identifies the kit in the database. For each item, the system retrieves its associated product ID.

These product IDs are predefined in HotWax Commerce and mapped to specific product types. For example:

| Product ID | Product Type         |
| ---------- | -------------------- |
| 1001       | `FINISHED GOOD`      |
| 2010       | `MARKETING_PKG_PICK` |

Once the product type is identified as `MARKETING_PKG_PICK`, HotWax Commerce associates it with the right kit. The system then recognizes it as a kit order.

## Kit order brokering

After identifying the product type as a [kit product](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/learn-shopify/shopify-integration/product-sync/kit-products/download-kit-products/README.md), HotWax Commerce brokers the entire kit order to the facility where the inventory is available rather than brokering each component separately.

Fulfilling all items within a kit from the same facility maintains the integrity of the kit and simplifies fulfillment.


---

# 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/learn-shopify/shopify-reference/orders/kit-products-download.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.