How to Enable Agentic Commerce for WooCommerce with Clustova Commerce

What agentic commerce means for a WooCommerce store

In conventional e-commerce, a shopper searches, opens product pages, adds an item to a cart, and completes checkout in the storefront. In agentic commerce, an AI system may interpret the shopper's request, find matching products, compare structured facts, and—where an approved transactional integration exists—coordinate checkout on the shopper's behalf.

That changes what a store must expose. A visually attractive product grid is not enough for software that needs exact product identity, availability, price, variants, canonical URLs, merchant policies, and supported capabilities. Agentic commerce readiness therefore begins as a catalog and discovery project, then advances into authenticated checkout, payment, order, and post-purchase work.

Why enabling agentic commerce is important

Shopping journeys are increasingly mediated by conversational search and AI assistants. A merchant that prepares its catalog now reduces the amount of guesswork required to understand its products and creates reusable infrastructure for multiple agent surfaces rather than building a separate feed for every new channel.

The immediate value is operational as well as promotional. Structured feeds expose missing SKUs, vague descriptions, weak attributes, stale prices, and poor category organization. Fixing those problems improves the information available to agents while also improving product pages, internal search, merchandising, and downstream advertising feeds.

• Improve machine-readable discovery of products and product categories.
• Give AI systems more reliable price, availability, image, and identity signals.
• Prepare one normalized catalog for evolving ACP, UCP, MCP, and other integrations.
• Create a measurable product-quality backlog instead of relying on vague AI-readiness claims.
• Establish the groundwork for future agent-driven checkout and attribution without overpromising current support.

What Clustova Commerce enables today

Clustova Commerce Free is the discovery foundation. It generates a public ACP-shaped catalog endpoint from published simple and variable WooCommerce products, publishes a store-oriented llms.txt resource, adds product schema carefully alongside common SEO plugins, detects baseline agent-channel signals, and scores product readiness with deterministic rules.

The plugin also creates downloadable JSONL and gzipped JSONL ACP ingestion artifacts. These files are useful for a merchant's provider onboarding workflow, but the plugin does not automatically enroll the store with an AI platform or upload the artifact using provider credentials. Each platform controls its own participation and approval process.

Step 1: prepare WooCommerce and your catalog

Use a current WordPress installation with WooCommerce 9.0 or later, enable High-Performance Order Storage, and make sure the storefront uses HTTPS. Before adding a discovery feed, review the public products that should appear in it. Clustova's feed includes published simple and variable products, ordered from newest to oldest up to the configured limit.

Every important product should have a stable name, description, price, SKU, canonical product URL, primary image, relevant gallery images, categories, and normalized attributes. Variable products need understandable variations. Publish visible shipping, returns, privacy, and terms information because transactional commerce programs evaluate the complete merchant experience, not just the JSON feed.

Step 2: install Clustova Commerce

From WordPress, open Plugins, choose Add New, search for Clustova Commerce – AI Product Feed for WooCommerce, install it, and activate it. You can also download the free plugin from WordPress.org and upload the plugin ZIP manually.

The free discovery features do not require a Clustova account or an AI-provider API key. After activation, open Clustova Commerce in the WordPress admin. If WooCommerce is missing or incompatible, resolve that dependency before treating any endpoint as production-ready.

Step 3: configure the Agent Feed settings

Open Clustova Commerce, then the Settings tab. The ACP feed is enabled by default on a fresh installation. Leave it enabled unless you intentionally do not want the public catalog surface. Choose the maximum number of products included in the feed; the default is 100 and the supported setting range is 1 to 1,000.

Set the cache TTL based on catalog volatility. The default is 3,600 seconds. A longer value reduces regeneration work, while a shorter value makes changes visible sooner. Product creation, updates, deletion, and stock changes invalidate the relevant feed cache, so the TTL is not the only freshness mechanism.

• Keep the feed enabled for public discovery.
• Set the product limit high enough to cover priority inventory without overloading the origin.
• Use a shorter cache for fast-moving stock and a longer cache for stable catalogs.
• Save settings, then verify the status shown under Discovery Endpoints.

Step 4: verify the discovery endpoints

Open the Discovery Endpoints tab. The free plugin lists the ACP Product Feed and llms.txt with their generated public URLs and status. Open each URL in a private browser window so you test the public response without relying on an administrator session.

The normal ACP feed path is /wp-json/clustova/v1/feed/acp. The store discovery file is available at /.well-known/llms.txt. WordPress installations without pretty permalinks may need index.php or rest_route forms. A valid response should contain real public products and current store information, not only return HTTP 200.

Step 5: generate the ACP ingestion export

Open the ACP Ingestion Export tab and generate the first artifact. Clustova writes one product object per line to JSONL and also creates a compressed .jsonl.gz version. It records the generation time and product count so the merchant can verify that the intended catalog was included.

The export is regenerated daily through WooCommerce's Action Scheduler when it is available. Downloading the artifact is not the same as being listed in ChatGPT or another agent. The merchant must follow the target platform's current onboarding instructions, receive any required approval or credentials, and submit the feed through that platform's supported process.

Step 6: improve weak products with GEO Health

Go to GEO Health and review the lowest-scoring products first. The score is deterministic and does not make an AI-provider call. It evaluates description depth, images, product attributes, a valid price, SKU presence, and category assignment, then produces a percentage, grade, and specific issues.

Treat the score as an editorial queue. Add concrete materials, dimensions, compatibility, care instructions, buyer use cases, and variant differences instead of padding descriptions with generic keywords. When Clustova Commerce Pro and the separate Clustova AI Writer plugin are active, GEO Health can hand a product into Writer's protected rewrite workflow for administrator review.

Step 7: run an external readiness check

After the endpoints are live, test the public store with Clustova's AI Agent Readiness Checker. The scan checks public discovery signals and applies ACP and UCP results only when storefront evidence is present. Use the focused ACP checker to validate feed reachability, structure, version evidence, and product availability.

A public scan cannot create a checkout, submit customer information, or verify payment. Its purpose is to find discovery and structural gaps safely. Repeat the scan after feed, permalink, cache, security, CDN, or product-model changes.

When to add Clustova Commerce Pro

Add Pro when the store needs UCP discovery, store-local MCP metadata, licensed operations controls, deeper agent-channel measurement, inventory synchronization, or server-side reconciliation into analytics and advertising platforms. Activate and verify the Pro license from the plugin settings before expecting gated endpoints to respond.

The current Pro UCP profile at /.well-known/ucp advertises the implemented read-only catalog-search capability. It intentionally does not advertise UCP checkout, identity linking, orders, or payment handlers. Google-powered UCP checkout remains a separate technical and Merchant Center onboarding program with geographic, account, testing, and approval requirements.

What the plugin does not do automatically

Installing Clustova Commerce does not guarantee that any AI platform will crawl, list, recommend, rank, or sell a product. It also does not turn the existing WooCommerce checkout into a provider-approved agentic checkout. ACP and UCP transactional integrations require authenticated endpoints, idempotent state changes, payment-token handling, inventory and tax correctness, order lifecycle synchronization, security review, and platform onboarding.

This distinction is a strength, not a limitation to hide. Merchants can improve catalog readiness and public discovery now without exposing premature transactional capabilities. When a supported checkout program becomes appropriate, the normalized product foundation and evidence-based health process are already in place.

Ongoing maintenance checklist

Agentic commerce is an operating practice, not a one-time plugin activation. Assign ownership for feed health, product quality, protocol changes, and measurement. Review the official specifications and platform onboarding requirements before every material protocol release because these standards continue to evolve.

• Check public endpoints after plugin, permalink, CDN, firewall, and cache changes.
• Review feed product counts and sample several simple and variable products.
• Keep prices, stock, images, attributes, policies, and canonical URLs synchronized.
• Work through low GEO Health scores as part of the catalog-editing calendar.
• Regenerate and inspect the ACP ingestion artifact before provider submission.
• Measure agent-attributed orders carefully and avoid inferring causation from a referrer alone.

Do I need an API key for Clustova Commerce Free?

No. The free ACP feed, llms.txt, product schema, GEO Health scoring, and baseline channel detection work without an AI-provider API key or external content-generation service.

Where is the WooCommerce ACP feed?

The normal public endpoint is /wp-json/clustova/v1/feed/acp. The Discovery Endpoints tab shows the exact URL for the current WordPress installation and whether the feed is active.

Does activating the plugin make products appear in ChatGPT automatically?

No. The plugin prepares public discovery and an ingestion artifact. Each AI platform controls merchant participation, ingestion, eligibility, ranking, and approval through its own process.

Does Clustova Commerce enable agentic checkout?

It enables the discovery foundation. The current Free plugin does not advertise transactional ACP checkout, and the current Pro UCP profile advertises read-only catalog search only. Provider-approved checkout requires a separate implementation and onboarding process.

Why should I improve GEO Health before applying to an AI commerce program?

AI shopping systems need reliable product descriptions, images, attributes, prices, identifiers, and categories. Fixing weak products improves the feed and reduces ambiguous matches before a provider evaluates the catalog.