One catalog. Every system of record and sale.
Connect ERP and PLM (systems of record) and marketplaces and storefronts (systems of sale) to one governed CataZenta catalog — enriched by specialist agents, approved by your team, syndicated with per-SKU job results.
Import and export run as jobs with connections, export profiles, and attribute mappings — poll via the Job API, webhooks, or the PIM UI.
How integrations fit together
CataZenta sits between master data and channels — not replacing your ERP, not bypassing approval gates.
| Layer | What flows | CataZenta primitives |
|---|---|---|
| Ingest | Material master, supplier CSV, PLM deltas | Import profiles · import jobs |
| Govern | Enrichment, completeness, approvals | PIM workflows · Agent Control Center |
| Publish | Channel-ready listings | Connections · export profiles · export jobs |
Who we serve across the ecosystem → Commerce ecosystem
Commerce channels
Publish approved, channel-ready SKUs to marketplaces and storefronts.
| Platform | Guide | Notes |
|---|---|---|
| Amazon | SP-API syndication | LWA credentials, product-type mapping, export jobs |
| Shopify | Store connections & export jobs | Connection + profile + job monitoring |
| WooCommerce | Roadmap / partner | Custom connection patterns |
| Magento, BigCommerce | Integration API + custom connection | Attribute mapping via export profiles |
Amazon SP-API
Listing schema, marketplace IDs, per-SKU job items and suppression feedback.
Shopify
Store sync, export profiles, and async job polling.
Recipes
Copy-paste flows for Amazon and Shopify syndication.
Business workflow → Publish complete products · Amazon-ready content
ERP & back office
Your ERP keeps financial truth and material numbers. CataZenta keeps sellable content, channel rules, completeness, and syndication.
| Platform | Guide |
|---|---|
| SAP | Material master, IDoc/API, nightly delta |
| Odoo | XML-RPC / CSV sync, variant mapping |
| ERP patterns | Batch, event-driven, hybrid ownership |
| Migrate from legacy PIM | Staged cutover while ERP stays master |
ERP excels at SKU, UoM, and plant data — not per-locale SEO, image rights, or marketplace product-type rules. Teams that export ERP text straight to Amazon see high suppression rates. See ERP integration patterns.
| Pattern | When to use |
|---|---|
| Nightly batch | Large catalog, stable master — import job with delta |
| Event-driven | Frequent new SKUs from PLM — webhook or queue → single-SKU import |
| Hybrid | ERP codes + PIM content — import then AI enrichment |
| Reverse feed | Approved copy back to ERP — export after workflow |
Content & assets
| Platform | Guide |
|---|---|
| DAM integrations | Asset pipelines into CataZenta DAM |
| Cloud storage (S3, SFTP) | Import jobs + DAM upload APIs |
| Link media to SKUs | Recipe: link DAM assets · DAM guide |
How syndication works
Tenants create connections (channel credentials), then export profiles that map PIM attributes to channel fields. Exports run as jobs with per-SKU line items.
| Step | What you configure |
|---|---|
| 1. Connection | Credentials — Amazon LWA, Shopify token, SFTP, custom REST |
| 2. Export profile | Channel schema, category / product-type rules, locale |
| 3. Mapping | PIM attributes → channel fields |
| 4. Job | Product scope, start job, monitor status |
| 5. Results | Per-SKU success, warning, or error — fix and retry |
| Connector type | Examples |
|---|---|
| Marketplaces | Amazon SP-API, Shopify |
| Storage / feed | S3, SFTP |
| Custom | REST / ERP adapters via Integration API |
Before export: product status, completeness gate, and workflow approvals (if configured). Skipping gates produces partial jobs and marketplace errors.
→ Export to channel tutorial · Poll export job · Syndication guide
Agentic PIM & integrations
Specialist agents and syndication share the same catalog — agent findings inform readiness; approved data flows to export jobs.
| Capability | Integration touchpoint |
|---|---|
| Syndication agent | Channel readiness insights before export |
| Approvals | Agent-proposed attribute fixes before publish |
| Completeness | Publish gates per channel — Product intelligence |
| MCP | list_connections, quick_publish, create_export_job — MCP tools |
→ Agentic PIM · Catalog quality
Build & automate
| Surface | Best for |
|---|---|
| PIM UI | Merchandisers — export, job monitoring, connection setup |
| Integration API | Programmatic connections, profiles, triggers — API reference |
| Job API | Poll job status, item-level results — Job API |
| Webhooks | Event-driven import/export notifications — Webhooks |
| MCP | Conversational publish in Claude or Cursor — MCP overview |
→ Core Commerce APIs · Recipes
Start by scenario
Launch on Amazon
Sync Shopify
Connect SAP or Odoo
Migrate from legacy PIM
Get started
- Confirm tenant access to Integrations in PIM or via Integration API.
- Create a connection for your first channel (Amazon or Shopify recommended).
- Build an export profile with attribute mappings for one category pilot.
- Run a small export job — review per-SKU items before scaling.
- Wire import jobs from ERP if master data lives outside PIM.
- Add Agent Control Center monitoring for syndication readiness insights.
Need a connector not listed? Contact CataZenta — custom REST and ERP adapters use the same job model.
GO DEEPER