Growth is where Central becomes an operating workflow
Starter is enough for focused cleanup. Growth is for teams that keep improving the catalog: new products, old gaps, schema, product-page depth, channel output, and periodic refreshes.
The plan is still self-serve, but it gives active teams enough token room to use Central repeatedly instead of treating enrichment as a one-off project.
What 8,000 tokens can do
| Workflow mix | Token math | What it means |
|---|---|---|
| Full enrichment | 160 SKUs x 50 tokens | Deep enrichment for a substantial launch or category. |
| Simple enrichment | 400 SKUs x 20 tokens | Fill empty fields across a broader catalog set. |
| Targeted gap fill | 800 SKUs x 10 tokens | Repair one missing attribute group at scale. |
| Optimization refresh | 1,000 SKUs x 8 tokens | Refresh output copy from verified records. |
Most teams will mix these workflows. The calculator should show the blend.
Growth plan fit
Use Growth when:
- The catalog has recurring enrichment and cleanup work.
- Product pages, schema, FAQs, and channel output all need the same verified record.
- You want Channel Studio and feed workflows where enabled.
- You need enough monthly tokens for more than a small launch queue.
- You want the default self-serve route before Professional or Enterprise.
Proof artifact: Growth operating month
| Catalog work | Tokened work | Output |
|---|---|---|
| New category launch needs 80 full enrichments. | 4,000 tokens. | Verified records, source trail, confidence, review queue, product-page copy, and schema output preview. |
| 300 existing products need missing material fields. | 3,000 tokens for targeted gap fill. | Material state by SKU: ready, needs source, needs merchant decision. |
| 100 products need title/description refresh. | 800 tokens for optimization refresh. | Updated output copy from verified facts. |
| Total | 7,800 estimated tokens. | Fits inside Growth before channel add-ons. |
Growth vs Professional
| Choose Growth when | Choose Professional when |
|---|---|
| You can self-serve and 8,000 tokens fit monthly work. | You need 20,000 tokens, larger teams, agency/client operations, API/webhooks, or more operational controls. |
| Channel work is active but not high-volume. | Channel work, integrations, and recurring workflows are core to the operation. |
| You are proving Central as the catalog operating layer. | Central is already a production workflow for larger volume. |
Start Growth when catalog work is no longer occasional.
Use Growth for active enrichment, schema, product pages, widgets, and channel output from one verified record.
Questions before you start
Why is Growth recommended?
It gives self-serve teams enough monthly token room for recurring catalog work without moving straight to Professional or Enterprise.
Can Growth use channel add-ons?
Yes where enabled. Channel add-ons are priced separately by active SKU band.
Do unused Growth tokens roll over?
Subscription tokens roll over for up to 3 months under the active pricing policy.
What happens if 8,000 tokens is not enough?
Set an overage cap, buy top-up tokens, move to Professional, or talk to sales for Enterprise.