AI assistants are starting to buy on people's behalf, using open standards such as UCP (Universal Commerce Protocol) to work with stores directly. Lutecia connects your WooCommerce store to them.<\/p>\n\n
What you get<\/strong><\/p>\n\n How it works<\/strong><\/p>\n\n When an AI platform changes its requirements, the update happens on Lutecia's servers; you do not update the plugin for it.<\/p>\n\n Channels<\/strong><\/p>\n\n UCP is on as soon as you connect, and you can turn it off under Controls. For ChatGPT, the plugin guides you through OpenAI's merchant program; once accepted, Lutecia delivers your catalog in OpenAI's format. For Google, Microsoft and Perplexity, the plugin links to each merchant program and, once they accept you, gives you a field to paste what they send you.<\/p>\n\n Controls<\/strong><\/p>\n\n For developers<\/strong><\/p>\n\n UCP version 2026-08-25. Capabilities: catalog search and lookup, cart, checkout, order, fulfillment, discounts, buyer consent, permalink. Transports: MCP (Model Context Protocol) and REST. The UCP discovery document is served on your domain. Daily catalog file in Google Shopping format. Nothing to host or update on your side.<\/p>\n\n This plugin connects your store to the Lutecia service (https:\/\/lutecia.app). It sends requests in the following situations:<\/p>\n\n With Sales attribution turned on, the plugin also sets one first-party cookie on your storefront, named Provider: Lutecia. Terms of service and privacy policy: https:\/\/lutecia.app\/legal<\/p>\n\n\n Your permalink structure must not be set to \"Plain\" (Settings > Permalinks).<\/p>\n\n\n A read-only WooCommerce API key, visible and revocable at any time under WooCommerce \u2192 Settings \u2192 Advanced \u2192 REST API. It only switches to write access when Checkout is turned on. If you attached your store to an agency, the agency can turn Checkout on from its console.<\/p><\/dd>\n A switch on the dashboard, off by default. When it is on, an assistant can create a standard order in your store with the customer's details. It appears in your Orders list awaiting payment, and you handle it as usual. Turning the switch on gives the API key write access; turning it off takes it back.<\/p><\/dd>\n Not unless you turn on Sales attribution, a switch on the dashboard. See External Services above for what the cookie stores and what is sent.<\/p><\/dd>\n No. Assistants query Lutecia's servers, not yours. Your store is only contacted to read the catalog during syncs and, if you turned on Checkout, when an order is placed; the UCP document served on your domain is cached for an hour.<\/p><\/dd>\n No. But crawling has limits, and that is why the platforms built open standards for stores to connect directly. A crawler works from a copy of your pages; the assistant can only describe what it saw there. Connected, the assistant gets your products from your store, accurate and up to date, and it can place the order.<\/p><\/dd>\n Nothing for now: the service is free while Lutecia works with its first merchants. Any paid plan will be announced to connected merchants before it applies, with the option to disconnect first.<\/p><\/dd>\n Yes, one click on the dashboard. The API key is deleted and your store stops being served to assistants. Uninstalling the plugin does the same cleanup. Your account and catalog copy stay deactivated on Lutecia's servers until you ask for their deletion, done within 30 days of the request.<\/p><\/dd>\n Write to contact@lutecia.app, or post in the support forum on this page.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
\n
External Services<\/h3>\n\n
\n
wp lutecia connect<\/code>)<\/strong>: your shop URL, shop name, admin email (or the contact email you pass), language, currency, the URLs of your privacy policy and terms pages (shown to buyers by channels that require them), the agency code, if an agency managing your store gave you one, and a newly created read-only WooCommerce API key are sent to Lutecia to register your store.<\/li>\n\/.well-known\/ucp<\/code>) on your domain<\/strong>: once your store is connected, the plugin fetches the UCP document from Lutecia and serves it (cached for one hour). Before you connect, nothing is sent.<\/li>\nwp lutecia doctor<\/code><\/strong>: your shop's domain is sent to Lutecia to check that the service is reachable and knows your store. No product or order data is sent.<\/li>\nlutecia_ref<\/code> (30 days, HttpOnly, SameSite=Lax). It stores the ?ref=lutecia_...<\/code> parameter carried by the product links Lutecia serves to AI assistants, so a resulting sale can be attributed. It is set only for visitors who arrive with that parameter, and holds no personal data. Because it is not strictly necessary to run your store, mention it in your cookie or privacy notice and collect consent where your law requires it. With Sales attribution off, the plugin sets no cookie and reports no order; turning it off also expires the cookie on a visitor's next page load.<\/p>\n\n\n
\n
What access does Lutecia get?<\/h3><\/dt>\n
What is Checkout?<\/h3><\/dt>\n
Does the plugin track my visitors or my orders?<\/h3><\/dt>\n
Does this slow my store down?<\/h3><\/dt>\n
AI assistants already crawl my site. Do I need this?<\/h3><\/dt>\n
What does it cost?<\/h3><\/dt>\n
Can I disconnect?<\/h3><\/dt>\n
Where can I get help?<\/h3><\/dt>\n
0.1.5<\/h4>\n\n
\n
0.1.4<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n