UCP profile publishing
Expose a Universal Commerce Protocol profile with supported services, capabilities, versions, and payment handler metadata.
Agent-ready commercefor WooCommerce stores
Make WooCommerce readable, testable, and safe for shopping agents.
Add UCP discovery, clean product metadata, and controlled checkout handoff while your store stays on WordPress.
WooCommerce readiness
92
CanAgentUse for WooCommerce
WordPress admin / UCP readiness
Readiness scan
92
Discovery profile ready
UCP liveSafe fields
Commerce signalStatus
UCP profile
Catalog surface
Cart preview
Checkout handoff
4
commerce surfaces mapped
0
private fields exposed
3
plugin controls reviewed
Capabilities
What the plugin adds to a WooCommerce store.
The storefront keeps working for buyers. The plugin adds the machine-readable contract agents need for discovery, catalog reading, cart creation, checkout handoff, and safety review.
Readiness surface
UCP profileLive
Catalog surfaceReady
Cart previewReview
Checkout handoffControlled
Product and variant mapping
Map WooCommerce products, variations, prices, inventory state, images, and canonical URLs into machine-readable responses.
Cart and checkout handoff
Let approved flows create carts and send shoppers to the right checkout URL with the selected items already attached.
Agent-readiness checks
Run checks for robots access, llms.txt, structured data, UCP shape, metadata safety, and commerce flow coverage.
WordPress-native controls
Configure exposed capabilities, allowed origins, store policies, and rollout mode from the WordPress admin area.
Evidence for technical teams
Send developers a report with failing fields, affected endpoints, and specific fixes instead of a vague readiness score.
Want to see how your catalog maps?
Bring a staging URL and we will walk through the plugin setup.
/.well-known/ucp
publishedstore.type: "woocommerce"services: catalog, cart.preview, checkout.handoffcapabilities: variants, inventory, coupons, regionspolicy: public fields only
Protocol layer
Agents read UCP, not theme HTML.
Stable discovery
Capabilities sit in one public profile.
Store-owned controls
Teams choose what stays closed.
Familiar checkout
The buyer still lands in WooCommerce.
Rollout
Start read-only. Open deeper flows when the store is ready.
Most stores should publish discovery first, validate the exposed commerce contract, then add cart and checkout flows after policy and checkout behavior are reviewed.
Rollout control stays with the store team
Discovery can go live before cart creation, so engineering, ecommerce, and legal can review each capability before it becomes available to agents.
Install on staging
Connect the plugin and run the first scan against catalog, cart, checkout, and metadata.
Choose what is public
Keep sensitive flows closed while the team reviews policy and extension behavior.
Publish when ready
Go live with discovery first, then open cart handoff after checkout signoff.
Need a rollout plan for a customized store?
Bring your extensions, checkout rules, and staging URL to the demo.
Demo and pricing
Bring your WooCommerce edge cases to the demo.
We will review catalog shape, checkout extensions, rollout mode, and integration work before discussing pricing. We map fit before pricing.
FAQ
Questions WooCommerce teams usually ask.
Short answers for the decisions that usually come up before a store publishes agent-readable commerce metadata.
Does the WooCommerce Plugin replace checkout?
No. It publishes agent-readable discovery and can hand shoppers to your existing WooCommerce checkout.
Can we start without cart creation?
Yes. Many teams start with discovery-only mode, then enable cart and checkout handoff after testing.
How is pricing handled?
Pricing is discussed after a demo because WooCommerce stores vary by catalog size, checkout customization, hosting, and integration needs.