LUTECIA FOR WOOCOMMERCE
Lutecia for WooCommerce compatibility with REEID Translate
Lutecia for WooCommerce compatibility with REEID Translate is being evaluated from available plugin evidence. Connects a WooCommerce store to Lutecia so AI assistants can read the store catalog in real time and place orders in the store. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Lutecia for WooCommerce.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Lutecia for WooCommerce is documented in the WooCommerce category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Lutecia for WooCommerce compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Connects a WooCommerce store to Lutecia so AI assistants can read the store catalog in real time and place orders in the store.
- Provides a live catalog via UCP, including a store-specific UCP address at `/.well-known/ucp`.
- Supports “Orders prepared by AI assistants” as an opt-in switch that allows an assistant to place an on-hold order in the store.
- Performs product data checks in the dashboard for missing “brand” or “GTIN (the product barcode number, required by the channel programs)”.
- Creates a read-only WooCommerce API key on connection, with write access only when “Orders prepared by AI assistants” is enabled.
- Optionally enables “Sales attribution” via a dashboard switch and a first-party cookie named `lutecia_ref` (30 days, HttpOnly, SameSite=Lax).
CONTENT BOUNDARY
Lutecia for WooCommerce capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
Lutecia for WooCommerce and REEID Translate FAQ.
What does Lutecia for WooCommerce do according to the available plugin evidence?
Lutecia for WooCommerce has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Lutecia for WooCommerce?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Lutecia for WooCommerce?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Lutecia for WooCommerce in a multilingual WordPress workflow.
REEID documents Lutecia for WooCommerce functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.