Tokens make catalog work visible before it runs
The calculator should answer a plain question: how much work is this catalog asking Central to do?
A 200-SKU launch, a 2,000-SKU refresh, and a targeted attribute cleanup should not be priced with the same vague "AI credits" language. Central estimates the run by workflow type, SKU count, channel output, and monthly cadence.
Calculator inputs
| Input field | UI guidance | Why it matters |
|---|---|---|
| SKU count | Number input with preset chips: 10, 50, 200, 1,000, 5,000. | Multiplies the workflow token cost. |
| Workflow mix | Segmented controls or sliders for full, simple, targeted, refresh, optimization. | Different jobs use different token amounts. |
| Monthly cadence | One-time, monthly, quarterly, seasonal. | Helps plan subscription vs PAYG/top-up. |
| Channel outputs | Checkboxes for supported channels, custom feeds, schema, widget. | Separates tokened work from channel add-ons. |
| Cap preference | Toggle and amount input. | Shows whether overage is disabled or opt-in. |
Token reference
| Workflow | Tokens | Calculator label |
|---|---|---|
| Full enrichment | 50 / SKU | Deep discovery, verification, enrichment, and outputs. |
| Simple enrichment | 20 / SKU | Fill empty fields from available context. |
| Re-enrichment | 15 / SKU | Refresh an already enriched product. |
| Targeted enrichment | 10 / SKU | Fill a specific missing field or attribute group. |
| Optimization refresh | 8 / SKU | Refresh title, description, or channel copy from verified facts. |
Calculator outputs
| Output | Copy behavior |
|---|---|
| Estimated tokens | Show total tokens and the formula in human language. |
| Plan fit | Recommend Free/PAYG, Starter, Growth, Professional, or Enterprise based on monthly need. |
| Token gap | Show whether included tokens cover the run or require top-up/upgrade. |
| Channel add-ons | Show active SKU band and per-channel monthly add-on where enabled. |
| Proof of work | Show what the run returns: source trail, confidence, review states, and output preview. |
Example estimates
| Scenario | Estimate | Plan signal |
|---|---|---|
| 50 SKUs full enrichment | 2,500 tokens | Starter covers a focused one-month run. |
| 160 SKUs full enrichment | 8,000 tokens | Growth fits the full run. |
| 400 SKUs full enrichment | 20,000 tokens | Professional fits the full run. |
| 1,000 SKUs targeted gap fill | 10,000 tokens | Growth plus top-up or Professional depending on cadence. |
Proof artifact: estimate to verified output
Show the calculator result tied to a product run artifact.
| Calculator result | Run preview | Output preview |
|---|---|---|
50 SKUs x 50 tokens = 2,500 tokens | Full enrichment selected. Source discovery and verification included. | Verified records with source/confidence, held claims, product-page copy, schema, and channel preview. |
100 SKUs x 10 tokens = 1,000 tokens | Targeted gap fill selected for missing material fields. | Material ready, needs source, or needs merchant decision by SKU. |
| Channel add-on selected. | Active SKU band shown separately. | Hosted feed/output preview where enabled. |
Estimate the run before Central starts spending tokens.
Set the SKU count, choose the workflow, and see which plan fits the work.
Questions before you start
Is the estimate exact?
It should be presented as an estimate before the run. Actual usage should be confirmed in-app based on the selected workflow and completed work.
Do channel add-ons use tokens?
Channel add-ons are recurring monthly fees by active SKU band. Tokened work covers enrichment, refreshes, optimization, and related catalog work.
Can I stop overages?
Yes. Overage should be opt-in through a cap. Keep disabled if the team wants the run to pause when tokens are exhausted.
Where should I start?
Use 3 products for proof, then calculate the bigger run after you inspect source trails and output quality.