| 开发者 | lutecia |
|---|---|
| 更新时间 | 2026年9月12日 21:00 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
A read-only WooCommerce API key, visible and revocable at any time under WooCommerce → Settings → Advanced → 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.
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.
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.
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.
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.
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.
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.
Write to contact@lutecia.app, or post in the support forum on this page.