Syndication & export jobs
Syndication is pushing approved catalog data to commerce channels and integrations. CataZenta runs exports as jobs so you can track progress and fix failures SKU by SKU.
When to syndicate
Before starting an export:
- Product status allows publish (e.g. approved)
- Completeness meets the channel threshold
- Workflow approvals are complete, if configured
- Connector credentials and mappings are valid
Skipping these steps produces partial jobs and marketplace errors.
Export from the UI
- Open the product (or select multiple products).
- Choose Export or Publish to channel.
- Select channel and locale if prompted.
- Confirm — a job is created.
- Open Jobs (or integration activity) to watch status.
- Review per-SKU results — success, warning, or error with reason.
Job statuses
| Status | Meaning |
|---|---|
| Queued | Waiting for worker |
| Running | In progress |
| Completed | Finished — check per-SKU rows |
| Failed | Job-level failure — see logs |
A “completed” job can still contain failed SKUs — always drill into line items.
Retry and fix
- Open the failed SKU in the job detail.
- Read the error (missing attribute, invalid mapping, auth).
- Fix data in the PIM.
- Re-run export for that SKU or batch.
Scheduled and bulk exports
Large catalogs typically use:
- API — trigger export endpoints — Poll export job
- Integration hub — connector-specific schedules — Integrations hub
Connectors
| Channel | Doc |
|---|---|
| Amazon | Amazon connector |
| Shopify | Shopify connector |
| WooCommerce | WooCommerce |