> For the complete documentation index, see [llms.txt](https://docs.quickreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quickreply.ai/overview/messaging-channels/whatsapp/concepts/whatsapp-catalog/shopify-vs-non-shopify-catalog-1.md).

# Shopify vs Non-Shopify Catalog

Both product sources publish to the same Meta Catalog and produce the same end state on the Catalog tab. They differ in how product data enters the system, which settings are configurable in the platform, and how updates are applied.

#### Configuration Comparison

| <p><br></p>                        | Shopify                                 | Non-Shopify (XLSX)                               |
| ---------------------------------- | --------------------------------------- | ------------------------------------------------ |
| Product source                     | Synced from the connected Shopify store | Imported from an uploaded XLSX file              |
| Entry action                       | Connect Now                             | Upload catalog items                             |
| Configuration steps                | Settings → Select product               | Upload → Map fields → Validate → Settings        |
| Meta Catalog ID                    | Set in Step 1                           | Set in Catalog Settings                          |
| Availability                       | Set in Step 1 (three options)           | Derived from the availability column in the file |
| Google / Facebook Product Category | Optional fields in Step 1               | Optional mapped fields                           |
| Show catalog on                    | Set in Step 1                           | Set in Catalog Settings                          |
| Product curation                   | Deselect products to exclude from sync  | Determined by file contents                      |
| Field-level mapping                | Not applicable                          | Required before import                           |
| Import validation                  | Not applicable                          | Row-level validation with a downloadable report  |
| Ongoing sync                       | Automatic, daily                        | Manual re-upload                                 |
| Post-setup control                 | Settings                                | Upload & Settings                                |

#### Settings Fields by Source

| Field                     | Shopify                | Non-Shopify            |
| ------------------------- | ---------------------- | ---------------------- |
| Choose Meta Catalog Id    | Required               | Required               |
| Availability              | Required               | Not present            |
| Google Product Category   | Optional               | Not present            |
| Facebook Product Category | Optional               | Not present            |
| Show catalog on           | Required, at least one | Required, at least one |

ℹ️ Note: Availability and product category fields are absent from the non-Shopify settings form because those values are supplied by the uploaded file rather than configured in the platform.

#### Update Model

Shopify. Product data is pulled from the store on a daily schedule. Changes made in Shopify — pricing, stock, product additions — are reflected in the WhatsApp catalog on the next sync without further action. Use Settings to change configuration or adjust the product exclusion list.

Non-Shopify. The catalog reflects the last successfully imported file. Product changes require uploading a revised file through Upload & Settings; the mapping and validation steps run again on each upload.

<br>


---

# 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.quickreply.ai/overview/messaging-channels/whatsapp/concepts/whatsapp-catalog/shopify-vs-non-shopify-catalog-1.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.