What does an enrichment or a generation cost?
The credit cost of each enrichment step and each element of a generated product page, additional languages included.
The cost of a run depends on the steps you turn on and on the channel’s page structure. Marcus shows the Estimated cost before each launch.
Enrichment, per product
| Step | Credits |
|---|---|
| Web search | 5 |
| Image collection | 2 |
| Attributes from images | 2 |
| Document collection, whatever their number | 2 |
| Attributes from documents, collected or linked | 2 per document read |
| Aggregation | 3 |
Only the steps that are turned on and that yield data are deducted. A full web enrichment costs at most 14 credits, plus 2 per document read. The Maximum documents read per product setting caps this last item, and only the documents actually read are charged.
Product not identified: if the enrichment does not manage to identify the product, its credits are fully refunded.
Generation, per product, per channel and per language
| Page element | Credits |
|---|---|
| Product name | 1 |
| SEO tags | 1 |
| FAQ | 2 |
| Technical specifications | 1 |
| Images and alt texts | 2 |
| Documents | 0 |
| Written content | 1 per started batch of 3 fields |
Only the fields written by AI count. A field taken from the master data or a fixed text costs nothing. A complete product page on a typical structure generally costs about ten credits.
Additional languages
The first language costs the full price. Each additional language costs two thirds of that price, rounded up to the next credit. Example: a product page at 9 credits costs 9 credits in the first language, then 6 in each following language.
Good to know
- A workflow’s tests consume credits like a normal run.
- An import, an export or a publication costs no credits.
- To understand the order of consumption and validity, see how credits work.