> For the complete documentation index, see [llms.txt](https://docs.optondemand.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optondemand.com/integrations-and-apps/smart-fulfillment.md).

# Shopify

Connect your Shopify store to Smart Fulfillment

With our Shopify application, we seamlessly connect your Shopify store with the OPT OnDemand solution — we take care of the entire installation and configuration process for you. There’s no need for you to handle any technical details; we’ll set everything up to ensure smooth and reliable operation without disrupting your daily business. The entire process is designed to be as convenient and efficient as possible — once we’ve completed the setup, the system is fully operational, allowing you to focus on growing your business.

## Key features

✅  Automatic order processing and order details updates, including tracking details

✅  Automatic updates of inventory stock levels

✅  Publishing new products from OPT to the Shopify store (OPT → Shopify)

✅  Linking existing product listings in Shopify with records in your printable product catalog / design library (Shopify → OPT)

✅  Automatic product synchronization and updates

✅  Compatible with multiple fulfillment locations

✅  Compatible with Shopify third party apps and vendors


---

# 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.optondemand.com/integrations-and-apps/smart-fulfillment.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.