Home / Features

Nothing made up. Everything sourced.

Fichewise writes your WooCommerce product pages from established facts. Every published specification is tied to its source; whatever cannot be confirmed does not appear.

01

Every attribute carries its provenance

On the review screen, every value shows where it comes from: the manufacturer datasheet, an identified web page, or your own store data. You know what each line rests on before it is published.

Web pages receive a reliability score according to their nature, from the brand website down to a forum. A page that describes another model or a variant is set aside before anything is extracted from it.

Review screen for a USB hub: form for the specifications resting on a single source, panel of the four sources with their reliability score, refused sources named, list of corrections made by the automatic proofreading passAttribute table with reliability and source for every value: uploaded datasheet, store data or web page, then the values proposed by the writer without a source, the image alt text and the GTIN
02

Your datasheet counts as a manufacturer source

Upload the manufacturer PDF to the product: it is read at once, tables included, then compared with the sources already gathered, without running a new search. It counts as a manufacturer source, at the highest rank.

A copy of that same document found on the web is not counted as a second confirmation. A source does not confirm itself.

03

An unconfirmed fact is never published

A value that no reliable source confirms, or that two sources contradict, is kept off the product page. It is not erased for all that: the review shows it, along with the reason it was excluded.

A single fragile source, an unsettled conflict, a value worked out by calculation rather than read in a document: each case is named, so that you know what to provide.

04

You review before anything is published

The proposed page appears next to the current content. You edit whatever you wish, settle the conflicts, then publish. The previous content is backed up and can be restored in one click.

When no source exists for a specification, a form built from your category lets you enter it. Your entry counts as store data and takes precedence on publication.

05

Your data comes before the web

A value you entered is never overwritten by a value found online. When they disagree, yours is kept and the discrepancy is flagged to you. The GTIN held by your store is never replaced.

Fichewise does not proofread itself: from one pass to the next, what it published is not taken back as your store data. It therefore cannot confirm its own copy.

Product content

What Fichewise writes for you.

Everything starts from the verified attributes, your editorial line, your category.

Review screen: unsourced claims removed from the description by the automatic proofreading pass, writer notes, SEO section and action bar with the Publish to product button
Description

The long description

Structured, with a specification table that only carries established values.

Short description

The essentials in a few lines

The summary of the product page, written in the voice of your store from the same facts.

SEO meta

Title, meta description, keyword

Written into the fields of Rank Math, Yoast SEO, All in One SEO or SEOPress, or handled by Fichewise when none is installed.

Attributes

WooCommerce attributes

Global attributes, with the label and unit your category declares. Variation attributes are never modified.

Tags

Product tags

Proposed from the product and your catalog, editable in the review.

Interface

Six languages

The plugin is displayed in French, English, German, Spanish, Italian or Portuguese, following the language of your admin.

Catalog audit

Three analyses of your catalog, with no AI call.

The Audit tab of the dashboard reads your store once and returns three lists. No model is called, no credit is counted, and each list exports to CSV.

Catalog audit: number of products with a missing field, values to harmonize and probable duplicates, then the missing fields per category with, for each product, the fields it lacks and a CSV export
Missing fields

What is missing, category by category

Description, short description, SEO meta, GTIN, and the attributes declared by the category schema: every incomplete product is listed with the fields it lacks.

Values to harmonize

"75 cl" and "750 ml" are the same value

Spellings of one attribute that name the same quantity are grouped, the most frequent spelling is proposed as the reference, and you correct the groups of your choice in bulk. USB-A and USB-B remain two values: nothing is matched by resemblance.

Likely duplicates

Same GTIN, same SKU or near-identical title

Products that share an identifier are always flagged. Very close titles are flagged too, so that you decide whether it is a variant or a duplicate.

Translation

Your product pages in every language, with WPML or Polylang.

Fichewise translates an established product page into the languages declared by your multilingual plugin. Nothing is made up when switching language: what was not in the source does not appear in the translation.

Bottom of the review screen: attributes with their reliability and source, then the Translations block with a written English draft, to be approved before it is written to the translated product
Translated content

Title, descriptions, SEO, attributes

The title, the long and short descriptions, the SEO title and meta, and text attributes are translated. An attribute term already translated in WPML or Polylang is reused as is, without a model call.

Never translated

Figures, units, references, brands

Numbers, units, GTIN, SKU, brands and the terms of your Store Profile are copied as they are. A quantity is not translated, it is copied.

Verification

Every figure in the source must be found again

A figure from the source that is missing from the translation marks the draft "to check", with the list of what is missing. You review each draft before it is written to the translated product. With the managed service, a translation costs one credit per language and per page.

Two modes

Your API keys, or none at all.

The same license opens both modes. You switch from one to the other in the settings, at any time.

Account screen: active license and its expiry date, API access mode set to the managed service with the site key fingerprint, credit balance, packs of 50, 250 and 1,000 pages, movement history
Your own keys

Anthropic and Tavily, at cost

You enter an Anthropic key for writing, a Tavily key for search, and pay your providers directly. No product data is stored outside WordPress, and nothing is sent to Fichewise.

Managed service

No key at all, with credits

You open no account with any provider. One credit covers one enriched product page; it is only counted once the page has been reviewed or published. Product data is kept only for the time it takes to process.

Interface

Three screens of the plugin.

Screenshots of Fichewise 1.10.2 on a demo store.

Fichewise dashboard: published pages, pages awaiting review, average estimated completeness, credits used, catalog health field by field, priority categories, progress and most used sources
Dashboard
Schemas screen: for one category, the attribute list with key, label, type and unit, the description outline section by section, and the Learn the outline from this product button
Schemas: attributes and description outline of a category
Four-step setup assistant: access mode, store profile, starting category, first product; first step shown with the choice between your own API keys and the managed service
Setup assistant

Accurate product pages, sources attached.

One license for the whole plugin, with your own keys or through the managed service. You review every page before it goes live.

See pricing