Shopify Catalog Eligibility and Knowledge Base Audit for Indian D2C

How should an Indian D2C brand audit Shopify Catalog eligibility?

Start in Sales channels > Agentic and record evidence rather than relying on a green summary.

1. Capture the store's current eligibility status and any ineligibility reason.
2. Record how many active products are included in Shopify Catalog.
3. Compare that count with active, market-ready products in Shopify admin.
4. Sample excluded products across revenue tiers and categories.
5. Classify every exclusion as store, account, product, policy or temporary-processing related.
6. Assign an owner and a verification date to each fix.

For a product-level sample, inspect title, description, images, price, inventory, product status, publication channel, URL, category and sensitive-content classification. Do not “fix” a genuinely excluded product by disguising its category. The goal is accurate eligibility, not evasion.

Shopify also says account standing is reviewed over time. Email verification, two-step authentication, genuine order history, fulfilment, chargebacks, invoices and policy issues can affect eligibility. That means this is not a one-time feed task; it belongs in ongoing commerce operations.

What product data should be mapped for AI shopping?

Shopify Catalog uses structured fields including titles, descriptions, options, images, prices and availability. Shopify's optimization guidance also calls out product organization, barcodes and variants.

Audit whether each field answers a buying question:

If important data lives in metafields, metaobjects or custom title patterns, review Shopify's Channel mapping rather than copying everything into the main product description. Group products only when they are genuinely variants of one customer choice; incorrect grouping can hide meaningful differences.

The Shopify agentic storefront product-data checklist covers field-level cleanup in more detail. The Shopify AI shopping readiness checklist connects that work to broader crawlability and store evidence.

How should search preview results be tested?

Shopify's agentic storefront management guide says the search preview shows raw Shopify Catalog search results and listing-quality indicators. Shopify also warns that individual AI channels may re-rank those results, so preview results are directional rather than a promise.

Build a query set from real customer language, not internal category names. Include:

• exact product and brand queries;
• category queries;
• use-case and problem-led queries;
• material, size, ingredient or compatibility queries;
• price and value constraints;
• gifting and occasion queries; and
• exclusion-sensitive queries where the product should not appear.

For each query, record whether the right product appears in the top 10, which wrong product appears instead, and which missing field could explain the mismatch. Re-run the same query set after changes. Do not alter ten fields at once and then claim one field caused the movement.

Use the agentic AI glossary to align product, marketing and engineering teams on what an agent can do versus what a conventional search index does.

What belongs in Shopify's new Knowledge Base?

Shopify's 26 October changelog says Knowledge Base now sits at Sales channels > Agentic > Knowledge base. It contains non-product facts such as contact details and gift services. Shopify drafts facts from published storefront pages, links them to their source and withholds them from AI agents until a merchant publishes them.

That approval gate is valuable. Treat it like a content-governance queue.

Publish a fact only when it is:

• supported by a current public source page;
• written without a contradiction or missing condition;
• appropriate across the markets where the store sells;
• owned by a named team or role;
• dated for review when it can expire; and
• clearly separate from product-specific data maintained elsewhere.

High-risk facts include return windows, delivery promises, warranty coverage, cancellation rules, subscription terms, geographic availability and promotional conditions. A technically valid fact can still be commercially harmful if it omits an exception.

Stores migrating from Shopify's former Knowledge Base app should also inspect migration behavior. Shopify says stores with 1,000 or fewer facts had edited or added facts transferred and published, while stores with more than 1,000 facts need to decide what to retain before the old app's stated 15 January 2027 deprecation date. Verify the current admin state rather than assuming the migration was complete.

What does a worked audit look like?

Consider a fictional Indian skincare store with 120 active SKUs. The following results are synthetic and illustrate the method; they are not HML or Shopify benchmarks.

Method: export active products, compare them with the Catalog count, inspect every excluded SKU, sample 30 included SKUs across revenue tiers, run 25 representative queries, review 30 Knowledge Base facts, and reconcile channel-referred sessions and orders for the same period.

The observed attributed conversion rate is 19 ÷ 640 = 2.97%. Use the conversion-rate calculator to check the arithmetic, but do not optimize from that figure alone. Review landing pages, net revenue, returns, discounts and contribution margin before deciding whether the channel is commercially useful.

For a first-party example of building the measurement foundation before optimization, see HML's Shopify analytics implementation case study.

Which fixes should happen first?

Prioritize by gate and customer risk:

1. Resolve store-level ineligibility and genuine policy issues.
2. Restore missing high-value products that should be eligible.
3. Correct price, availability, variant and policy contradictions.
4. Verify or unpublish high-risk Knowledge Base facts.
5. Improve mapping for products already eligible but poorly represented.
6. Test query-level discoverability using a stable query set.
7. Improve conversion paths only after the recommendation and landing page agree.

Do not start with decorative copy changes when the product is excluded, and do not start with Catalog data when the real problem is a weak product page or checkout journey.

How should results be reported without overstating impact?

Use separate layers:

Shopify's reporting can connect sessions and sales with agentic storefronts, but attribution is not causation. Report both, and label them correctly.

What should the team do next?

Run a 90-minute evidence capture before changing product copy: screenshot the eligibility state, export active and included product counts, select a 30-SKU sample, define 25 customer-language queries, and export all published Knowledge Base facts with their sources and owners. That creates a baseline the team can re-run after fixes.

If the audit spans product architecture, theme evidence, analytics and conversion paths, request a Shopify AI-commerce audit. HML's website development service can connect the product-data, storefront and measurement work without treating a redesign as the default solution.

Sources

1. Exponential: Shopify's Fall '26 Edition — Shopify Newsroom; published 28 October 2026; accessed 29 October 2026.
2. Requirements for being included in Shopify Catalog — Shopify Help Center; accessed 29 October 2026.
3. Shopify Catalog and product discovery for agentic storefronts — Shopify Help Center; accessed 29 October 2026.
4. Knowledge base is now built into your admin — Shopify Changelog; published 26 October 2026; accessed 29 October 2026.
5. Managing agentic storefronts — Shopify Help Center; accessed 29 October 2026.
6. Optimizing your products for AI platforms — Shopify Help Center; accessed 29 October 2026.