Unpublished products are invisible to AI assistants
Causes exclusion from Shopify Catalog
A product must be published to your Online Store, Hydrogen or Headless channel to enter Shopify Catalog. This catches almost every merchant who creates products through an app or an API, because those arrive unpublished by default.
In short
- This excludes the product from Shopify Catalog entirely, so no assistant can recommend it.
- We did not see this among the catalogs we scanned, which makes it rare rather than unimportant.
- This one needs a human decision, so Endcap finds and groups it but does not write it for you.
Why this excludes the product
The product is not published to any storefront channel, which excludes it from Shopify Catalog.
Products must be published to the Online Store, Hydrogen, or Headless channel to enter Shopify Catalog.
The default that catches integrations
Products created through the Admin API arrive unpublished unless the caller explicitly publishes them. That is a reasonable default and it is also why this finding correlates almost perfectly with having an ERP, a PIM or a supplier integration. The merchant did nothing wrong; the integration simply never set the field, and nothing in the admin raises its voice about it.
There is a subtlety worth knowing before you act on this. Publication state and store state are different things, and on a development or password-protected store products can look unpublished when they are merely unreachable. We take two independent signals before calling a product blocked for this reason, because the earlier version of this check told developers their entire catalog was broken when the only real problem was a storefront password.
How to check it yourself
- Open Products and filter by sales channel availability.
- Select the unpublished products and publish them to your Online Store channel in bulk.
The fix
Publish the product to your Online Store, Hydrogen or Headless channel.
How Endcap handles this
Endcap finds and groups every product with this problem and links each finding to the Shopify document behind it, but it does not write this one for you. Finding every instance by hand means paging through the admin; the scan lists them together.
The fix touches a field we deliberately do not automate. Endcap only ever writes vendor, product type and description, because those are the three where a wrong value is visible and reversible. Prices, identifiers, publication state and status are decisions with consequences a tool should not be making on your behalf.
Common questions
Why are products created by my ERP unpublished?
Because that is the Admin API default. A product created through the API is not published to any channel unless the caller explicitly publishes it. Nothing in the admin raises its voice about this, which is why the finding correlates so strongly with having an integration.
My store is password protected. Are my products really unpublished?
Probably not. Publication state and store reachability are different things, and a password-protected or development store can make published products look unpublished. We take two independent signals before calling a product blocked for this reason, because the naive version of this check tells developers their whole catalog is broken.
Can Endcap publish the products for me?
No, and this is deliberate. The app requests read_products, write_products and read_legal_policies, which is the minimum it needs. Publishing requires a publications scope we do not ask for, so this is one you do in the admin.
Source: Shopify documentation
Check your own store
Enter your Shopify URL and see whether the public products we can inspect show these problems. No install required for the first scan.