Enrichment and channel delivery are different jobs
First, Central builds the verified product record. That work uses tokens.
Then Central can keep a channel output or hosted feed available for products that are active in that destination. That recurring delivery is priced as a channel add-on by active SKU band.
Channel add-on pricing
| Active SKUs | Monthly price per channel |
|---|---|
| Up to 500 | $29 |
| Up to 2,000 | $49 |
| Up to 5,000 | $79 |
| Up to 10,000 | $129 |
| Up to 50,000 | $249 |
| 50,000+ | Custom |
Use one active SKU band per channel. Enterprise contracts can scope custom volume and governance needs.
What counts as channel work
| Layer | Pricing unit | Example |
|---|---|---|
| Enrichment | Tokens | Full enrichment, simple enrichment, targeted gap fill, re-enrichment, optimization refresh. |
| Channel adaptation | Tokens when generating or refreshing output copy | Channel-shaped title, bullets, attributes, descriptions, or schema from the verified record. |
| Channel add-on | Monthly add-on by active SKU band | Hosted feed or recurring supported-channel output where enabled. |
| Custom feed | Plan and implementation dependent | CSV/XML/JSON output for destinations that can consume custom formats. |
Supported channels + custom feeds
Public language should say "Supported channels + custom feeds." The currently approved supported-channel frame includes Google Merchant Center, Bing Merchant Center, ChatGPT Shopping, and Perplexity Shopping, plus custom CSV/XML/JSON outputs where the destination can consume them.
Do not use unsupported channel-count claims or imply native support for every destination.
Proof artifact: ready record to channel preview
| Before add-on | Channel check | After add-on |
|---|---|---|
| Product record has verified facts and review states. | Central checks required fields, output formatting, and active SKU count. | Hosted feed or supported-channel output preview with ready, needs review, and blocked rows. |
| A required field is missing for a subset of SKUs. | Missing facts route back to enrichment or review. | Ready rows can publish; blocked rows stay visible. |
| Custom partner needs XML fields. | Field mapping uses canonical product facts. | XML preview from verified fields. |
When to add a channel
Add a channel when the team has:
- Verified product records ready for that destination.
- A recurring output or hosted feed need.
- Active SKU count clear enough to choose a band.
- A review path for required fields, conflicts, and unsupported claims.
- A plan that supports the channel or custom feed workflow.
Preview the feed before adding the recurring output.
Central shows readiness, missing fields, review states, and the active SKU band before you commit to channel delivery.
Questions before you start
Do I need an add-on for every output?
No. Add-ons apply to recurring hosted feeds or active channel outputs where enabled. One-off exports and internal previews can differ by plan.
Do channel add-ons replace tokens?
No. Tokens pay for catalog work. Add-ons cover recurring delivery for a channel output.
What if some SKUs are not ready?
The output should show ready, needs review, and blocked rows. Do not hide channel readiness problems.
Can custom feeds cover unsupported destinations?
Yes where the destination can consume custom CSV, XML, JSON, or JSONL and the implementation supports that format.