Turn product specifications into product descriptions
We build software that turns your approved specifications, price lists and documentation into product descriptions for your online shop and catalogues, in Italian and English. The workflow covers review, publication and updates. Every product claim must be backed by the source data.
How we turn catalogue data into content
This is a software project, not a copywriting service. The system reads approved data, generates drafts and sends them for review. Once approved, the content is published where it is needed. When the source data changes, the affected content goes back through the update and approval process.
The problems to solve
Your catalogue grows, but descriptions fall behind
Product pages are left blank or filled with supplier copy. Your sales team keeps answering the same questions because the descriptions do not contain the information customers need.
Rewriting every draft wipes out the savings
If a draft is generic or technically wrong, someone who knows the product has to rewrite it. Corrections eat up the time saved on drafting. An incorrect feature claim can also lead to a return.
Product data changes, but descriptions stay the same
You update dimensions, materials or certifications in your ERP, but the old descriptions stay on your website. It becomes hard to tell which descriptions are still accurate.
What we build
Descriptions based on approved data
We start with what you have already validated: specifications, bills of materials and certifications. Product claims must be supported by the approved data. Missing information is not an invitation to guess.
Review before publication
Every draft goes to a designated reviewer. Nothing is published until they approve it. We use their corrections to refine the rules for future drafts.
Updates linked to your ERP
When a dimension or certification changes in your ERP, the system flags the affected descriptions for updating. Revised drafts go through approval before publication.
Italian and English from the same data
Both language versions use the same approved data and follow the same updates. We generate the English copy directly from the product data, rather than translating the Italian.
What we do not do
We are not a content agency
We do not set your editorial strategy, manage your social accounts or supply weekly articles. We build software that produces content from your business data.
No publication without human approval
A person must read and approve any text that makes a commitment to a customer. If you want to publish thousands of pages without anyone reviewing them, this is not the right project for us.
We do not produce pages just to rank
We do not generate hundreds of pages that rephrase the same information just to take up space in search results. Each page needs to answer a question a potential customer has about the product.
The work your team still needs to do
A generated draft still needs work. Your team must review it, make corrections and keep the source data complete and up to date. Automation makes gaps in your technical specifications visible; someone still has to fill them.
Reading and approving the content
Reviewers need to check claims about performance, certifications and compatibility in particular. This work belongs with someone who knows the product and is accountable for those claims. You need to allow time for it.
Filling the gaps in the data
If the specification is missing a detail, the description will be missing it too. Someone has to find the information, check it and add it to the source data. The system cannot fill that gap by guessing.
Setting the tone and the boundaries
Your team needs to agree how to address customers, which words to use and what never to promise. Set those rules at the start and revisit them when needed, or every draft becomes another negotiation.
How to assess whether the project pays off
- How many product pages are incomplete or have not been updated for more than a year?
- How long does it currently take to write or update a product description, from request to publication?
- On average, how many corrections does a draft need before it is approved?
- How long does it take for a change in your ERP data to reach the published product description?
- How many hours a month does your team spend approving descriptions and filling gaps in the source data?
Facts and sources
Google states that appropriate use of AI or automation does not violate its guidelines and that it rewards high-quality content “however it is produced”. It penalises content created primarily to manipulate rankings, not the method used to write it.
Under the AI Act, the system provider is responsible for marking synthetic content in a machine-readable format (Article 50(2)). If you publish AI-generated text to inform the public on matters of public interest, you must disclose its AI origin (Article 50(4)). This disclosure is not required if the text has undergone human review or editorial control and an individual or legal entity holds editorial responsibility for its publication. For product catalogue text, marking remains the provider's responsibility; the publisher has no disclosure duty under this provision.
Questions we often hear
- Does Google penalise AI-generated product descriptions?
- Not because they are AI-generated. Google penalises content created to manipulate rankings. An accurate description based on product data helps the reader, regardless of how it was written.
- Do you have to disclose that descriptions are AI-generated?
- It depends on what you publish. The AI Act requires disclosure for text intended to inform the public on matters of public interest. For a product page, the marking duty rests with the AI system provider. We check how this applies to your case.
- Can the AI invent product features?
- We set up generation to use approved fields, with a rule that missing details must be left out. A product expert still has to check the draft. Using approved data does not replace review.
- Why choose a software project over an off-the-shelf tool?
- An off-the-shelf tool may be enough for occasional descriptions. A software project makes sense when you need to keep a large catalogue aligned with your ERP and manage approvals, publication and updates. Assess the savings across that whole workflow, including the time spent on review.
- Can it connect to Odoo and an online shop?
- We check those connections first. Product data needs to come from your ERP, and approved descriptions need to go back to your online shop for publication, without manual copying between systems.
- Who owns the content?
- The content and the workflow that produces it are yours. We set this out in the contract, along with where your data is processed.
- How much review work is left?
- Early reviews also help refine the generation rules. We measure review time and the corrections needed with you to see whether the workload falls, and by how much. Better drafts still need approval.
Send us ten product records
Send us ten product records as they are today, along with the data you hold in your ERP. We use them to see which descriptions your approved data can support and what information is missing.