Planning entitlements
Entitlements are the products you can enrich. The support article covers purchasing. This page covers planning.
Entitlements are consumed when products are sent for enrichment, not when you apply results. A product counts once whether or not it has variants. Retrying errored products is free; re-running a product that generated successfully consumes another entitlement.
Two facts that shape planning
A product counts once. Simple products and products with variants or modifier options each consume a single entitlement. Variant count does not multiply cost.
Entitlements expire 365 days after purchase. Unused entitlements are lost at that point, which makes buying well ahead of a plan a way to lose them.
Planning a purchase
- Count the products you intend to enrich, not the products you own. Thin records you have not fixed yet are not ready to enrich.
- Add an allowance for re-runs. Assume some portion of your first batches will be re-run after you tune inputs. Ten to twenty percent is a reasonable starting assumption.
- Buy for a defined window. Twelve months of planned work, not the whole catalog indefinitely.
Keeping costs down
- Tune on a small batch. 25 products to validate inputs costs far less than discovering the problem across 250.
- Fix source data before enriching. A thin record consumes an entitlement and returns weak output or an error.
- Edit rather than re-run where the content is close. Editing is free.
- Check your selection count. Category and filter selections make it easy to send more products than intended, and only the first 250 are included.
When you run out
Enrichment stops rather than continuing and billing you. You cannot start a task that includes more products than your remaining balance, so either reduce the selection or purchase more.