Download the PHP package tmonier/sylius-ai-catalog-copilot-plugin without Composer

Sylius AI Catalog Copilot Plugin

Reviewable AI suggestions for product descriptions, SEO metas and translations in the Sylius 2 back office.

Writing and translating product texts is the slowest part of catalog work. Language models are good at it, but a merchant cannot let them publish unreviewed texts: models invent facts, and in the EU some claims ("eco-friendly", "carbon neutral") are now banned when they are not substantiated.

This plugin asks the model of your choice (Mistral, OpenAI, Anthropic, a self-hosted Ollama... through Symfony AI) for suggestions. Nothing is written on a product until an administrator accepts it.

Features

Also included: translations in English, French, German, Spanish, Italian, Dutch and Polish; prompts as overridable Twig templates; Twig Hooks everywhere; MySQL, MariaDB and PostgreSQL support.

Screenshots

Requirements

Symfony 6.4 is not supported: Symfony AI requires Symfony 7.3+.

Symfony AI is 0.x. Each minor (about one a month) may break its API, so this plugin pins ^0.14 (>= 0.14.0, < 0.15) and a new plugin version follows each Symfony AI minor (a weekly CI job tests the next one). Until Symfony AI 1.0, the plugin cannot be installed next to a package that pins another Symfony AI minor.

Installation

1. Require the package, and the Symfony AI bridge of your provider when you use one:

2. Register the bundles in config/bundles.php (Symfony Flex does it automatically once a recipe exists):

3. Import the configuration in config/packages/tmonier_sylius_ai_catalog_copilot.yaml:

4. Import the admin routes in config/routes/tmonier_sylius_ai_catalog_copilot.yaml:

5. Run the migrations (two tables: tmonier_ai_copilot_suggestion, tmonier_ai_copilot_provenance):

The plugin now works with the demo generator: its fixed sentences only show the workflow. Real wording, and real translations of your texts, need a real model: plug one as below.

Plugging a model

Platforms and credentials are configured with symfony/ai-bundle, from environment variables. No credential is ever stored in the database. The plugin only needs the service id of the platform (ai.platform.<name>) and a model name.

A self-hosted Ollama keeps product data on your servers. Whatever the provider, only catalog data is sent (product name, code, categories, attributes, options, and the source text for a translation).

To use something else (a local model, a proxy, a company gateway), implement Tmonier\SyliusAiCatalogCopilotPlugin\Generator\TextGeneratorInterface and set generator: { type: service, service: app.my_generator }.

Models newer than the Symfony AI model catalog of the installed minor (e.g. claude-haiku-5-5 with Symfony AI 0.14) are refused by the platform: set model_class to the bridge model class (Symfony\AI\Platform\Bridge\Anthropic\Claude for Anthropic) to use any model id. The generator type can also be an environment variable ('%env(TMONIER_AI_GENERATOR)%', value demo or platform), resolved at runtime; in demo mode the platform is never created. When the platform cannot be created (e.g. missing API key), the admin shows an error message and nothing is generated. API keys stay in environment variables: they are never stored in the database, shown in the admin, or written in the logs (failures are logged with the exception class and message only).

Configuration

The rate limiter uses two independent sliding-window counters: one per admin user (keyed by getUserIdentifier()) and one global (keyed 'global'). Both tokens are consumed on every generation; if either counter is exhausted the request is denied with a flash error and the product page is reloaded — nothing is generated. The admin can retry once their quota refills. Set enabled: false if your infrastructure already throttles these routes, or if you run the plugin in a context without a persistent cache (the CLI command is never rate-limited).

The cache.rate_limiter pool comes from Symfony's Rate Limiter component defaults. To use a dedicated pool (recommended in production):

Usage

• Product page (Catalog > Products > Edit, Translations tab): in each locale, Generate writes a field from the product facts; Translate from ... translates the field of the source locale. Save your changes first: the page is reloaded. The Pending AI suggestions card under the form lists the suggestions with Accept, Reject and Compare.
• AI suggestions grid (Catalog > AI suggestions): filter, accept or reject one row, or select rows and Accept selected / Reject selected (100 at most at once).

• Command line:

  Products must already exist in the target locale. Products that already have a suggestion for the field in the locale (pending, accepted or rejected) are skipped; add --include-processed to regenerate the decided ones. --only-empty treats whitespace or markup-only texts as empty, and blank source texts are skipped. When a run reaches its limit it prints --after-id=<id> to continue with the next products. --limit must be a positive integer (capped by max_products_per_run).

Customisation

• Prompts are Twig templates: system.txt.twig (rules), one template per field, translate.txt.twig and _facts.txt.twig. Override them in templates/bundles/TmonierSyliusAiCatalogCopilotPlugin/prompts/. Keep the rules of system.txt.twig (facts only, no environmental claims, plain text).
• Product facts: decorate tmonier_ai_copilot.facts_extractor (ProductFactsExtractorInterface) to add catalog data. Never add customer data.

• Provenance in your templates:

  PHP code can use ProvenanceProviderInterface. A field rewritten by a human after the acceptance is reported as edited (data-ai-generated="false"); line endings and surrounding whitespace do not count as an edit. Texts of the demo generator are reported with data-ai-generator="demo" and data-ai-generated="false", and never get the shop notice.

• Events: listen to Tmonier\SyliusAiCatalogCopilotPlugin\Event\AiSuggestionAccepted (suggestion, product, previous text, new text, administrator), dispatched after the flush.

Sibling plugins

• tmonier/sylius-audit-log-plugin records the product change made by an accepted suggestion, like any other admin change.
• tmonier/sylius-bulk-actions-plugin could offer a "Generate AI suggestions" bulk action on the products grid (not done yet).

Both are optional: this plugin depends on neither.

Legal notes

This section is information, not legal advice. Check your obligations with a lawyer.

• EU AI Act, article 50(2): providers of AI systems generating text must mark the output in a machine-readable way. A merchant who runs this pipeline on its catalog may be considered a provider, and the open source exemption of article 2(12) does not cover article 50. The plugin therefore records the provenance of every accepted field by default (model, generation and acceptance dates) and can expose it as data-ai-* attributes and a shop notice. Article 50(4) (texts published to inform the public on matters of public interest) does not target product pages. The application date of article 50 may be postponed by the "Digital Omnibus"; at the time of writing that postponement was not published in the Official Journal.

• Directive (EU) 2024/825 (empowering consumers for the green transition), applicable since 27 September 2026: generic environmental claims ("eco-friendly", "green", "climate friendly", "biodegradable"...) are banned unless the product has a recognised excellent environmental performance (EU Ecolabel, an EN ISO 14024 type I ecolabel...), and claims of climate neutrality based on offsetting are banned outright (Annex I point 4c). The prompts forbid such claims, and the content guard looks for them in seven languages (stems with their inflections). By default (mode: flag) an unsubstantiated claim is kept and highlighted: the suggestion page, the product page and the grid mark it and warn the reviewer before acceptance, so that the reviewer decides (keep it only if it is substantiated, otherwise edit or reject). Carbon or climate neutrality, net zero, emissions-free and offsetting / compensation claims are always removed, in every mode. mode: remove also removes the sentences with other unsubstantiated claims. A generic claim is kept only when one of the ecolabel_attributes names a recognised label (e.g. Certification: EU Ecolabel) and the value contains no denying, expiry or pending word ("no", "not", "expired", "candidate", "pending", "abgelaufen"...); "biodegradable" or "compostable" only when one of the biodegradable_attributes starts with an explicit "yes" (oui, ja, sí, tak, certified...) or names a compostability standard (EN 13432...). Colour words are claims only in eco phrases ("green product", "greener", "produit vert"), never as plain colour adjectives, and not when the product name, attributes or option values give that colour. OEKO-TEX is not a claim. A kept claim is shown to the reviewer with the attribute that supports it.

  The guard is a best-effort keyword filter, not legal advice. It misses claims phrased in other ways and can flag (or, for neutrality claims and in remove mode, remove) a legitimate sentence: check the warnings. The administrator who accepts a suggestion remains responsible for the published text: read every suggestion before accepting it. National transpositions vary (France was still discussing it in October 2026).

• Data protection: prompts contain catalog data only, never customer data. Your provider's terms still apply to the product data you send; a self-hosted model avoids sending it.

Limitations

• Environmental claims guard: known gaps. It is a best-effort keyword filter in seven languages; the reviewer stays responsible. Known gaps:
  • claims phrased as whole sentences ("we care about the planet", "inspired by nature", "a small step for the Earth") or in other languages are not detected;
  • a bare "öko" is not a claim (only "Öko-…" compounds); a bare "eco" is ignored next to "mode", "programme", "de"/"dell'" (echo) and similar words, so "Eco" used as a claim in such a context is missed;
  • "energy efficiency class / Energieeffizienzklasse / classe d'efficacité énergétique" is treated as the energy label, not as a claim;
  • colour phrases are limited to common nouns ("green product/choice/alternative"…); a colour given by the product exempts them, even when the text means the eco sense;
  • evidence values are read with word lists: a denial phrased differently ("we gave up the EU Ecolabel") can still be taken as evidence, and a value stating an unrelated restriction before the label name ("not tested on animals, EU Ecolabel") is rejected.
• One field at a time; no preview modal, no streaming. Generation is synchronous (a few seconds with a hosted model).
• No rate limiter or budget cap yet: only max_products_per_run for the command. Token counts are stored when the platform returns them.
• The content guard is keyword-based; it does not detect every invented fact or claim.
• A locale must exist on the product (name and slug saved) before texts can be generated in it.
• Product names, slugs, taxons and images are out of scope; no automatic publication.
• Sylius Plus RBAC is not integrated: every administrator can generate, accept and reject.

Development

The test application uses the demo generator: no test, CI job or dev environment calls an AI service. The Symfony AI adapter is tested against Symfony AI's InMemoryPlatform.

Trying with a real model (Anthropic Claude)

The test application is wired to Anthropic but uses the demo generator unless told otherwise (the tests and the CI always force the demo generator: no API call).

1. Put these lines in tests/TestApplication/.env.local (gitignored, never commit it):

2. Clear the cache: vendor/bin/console cache:clear.
3. In the admin, generate or translate a field again (Generate / Translate from in the product Translations tab), then review the pending suggestion.

Each click is one paid API call (a few hundred to a few thousand tokens). Only catalog data is sent to Anthropic: product name and code, categories, attributes, options and, for a translation, the source text; never customer data. Remove the lines (or set TMONIER_AI_GENERATOR=demo) and clear the cache to go back to the demo generator.

License

MIT. See LICENSE.