> 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/system-admins/administration/company/manage-shopify-shop.md).

# Shopify connections

Use this page after a Shopify shop is connected to HotWax Commerce. It covers reviewing and maintaining an existing connection, not initial setup.

For a new connection, follow [Set up HotWax Commerce with Shopify](/documents/system-admins/implementation/product-store-onboarding.md).

## Find a connection

1. Open the **Company App**.
2. Go to `Shopify`.
3. Search for the shop when needed.
4. Filter the list by connection status.
5. Select a connection.

The connection page groups configuration into three areas.

| Area                 | Contents                                                            |
| -------------------- | ------------------------------------------------------------------- |
| Configuration        | Instance details, Product Store, API credentials, and access scopes |
| Products & Inventory | Inventory locations and product types                               |
| Orders & Fulfillment | Order Sync, shipping methods, payment methods, and sales channels   |

Product Sync appears with the products and inventory workflow when available for the connection.

## Review instance details

1. Open the connection.
2. Select `Instance details`.
3. Review the shop name, Shopify domain, and timezone.
4. Review the refund-upload setting.
5. Save only the intended changes.

The Shopify domain identifies the remote shop. Confirm it before changing another connection setting.

## Review or change the linked Product Store

1. Open the connection.
2. Select `Product Store`.
3. Confirm the Product Store that owns the Shopify shop.
4. Change it only when the implementation owner approves the downstream catalog, inventory, and order impact.
5. Save the link.
6. Return to the connection page and confirm the Product Store.

A Shopify shop can be linked to only one Product Store.

## Manage API credentials

Use the credentials page only when the implementation team provides a current Shopify credential change.

1. Open `API credentials`.
2. Confirm the Shopify shop.
3. Enter the approved credential values.
4. Save the change.
5. Verify the connection before starting a synchronization task.

Keep credentials out of tickets, screenshots, and documentation.

## Review access scopes

1. Open `Access scopes`.
2. Refresh the scope list when instructed.
3. Compare the available scopes with the integration requirements.
4. Resolve missing scopes in Shopify before retrying the affected task.

## Related post-launch tasks

Use these references to operate an existing connection:

* [Review Shopify mappings](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-mappings.md)
* [Manage Shopify Product Sync](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-product-sync.md)
* [Manage Shopify Order Sync](/documents/system-admins/administration/company/manage-shopify-shop/manage-shopify-order-sync.md)

Exclude the development-only Debug area from operator workflows.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hotwax.co/documents/system-admins/administration/company/manage-shopify-shop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.