Skip to main content

ERP systems

CataZenta sits above ERP product masters. Your ERP keeps financial truth, inventory, and material numbers. CataZenta keeps sellable content, channel rules, completeness, and syndication.

Why not syndicate directly from ERP?

ERP strengthERP weakness for commerce
SKU, UoM, price, plantAmazon A+ content, per-locale SEO
Stable material numbersImage rights and renditions
Inventory syncWorkflow approvals for copy
Per-channel completeness gates

Teams that export ERP text straight to marketplaces see high suppression rates and rework in seller central.

Integration patterns

PatternWhen to useCataZenta primitives
Nightly batchLarge catalog, stable masterImport job → delta by changed-at
Event-drivenFrequent new SKU from PLM/ERPWebhook or queue → single-SKU import
HybridERP codes; PIM contentERP import + manual/AI enrichment
Reverse feedApproved copy back to ERPExport or custom API after workflow

System-specific guides

ERP / sourceGuide
SAP (ECC, S/4)SAP integration
OdooOdoo integration
Microsoft DynamicsContact solutions — same patterns as SAP/Odoo
Oracle ERPID/API batch — map to families first
Spreadsheets / supplier portalImport job + AI extraction

Field mapping principles

  1. One product family per material type — do not mix apparel and chemicals.
  2. Stable external key — material number, default_code, or GUID.
  3. Locale explicit — never assume single-language ERP text covers all channels.
  4. Channel-scoped attributes — Amazon bullets ≠ B2B spec sheet.
  5. Pilot 50–200 SKUs before full load — catalog fundamentals.

Jobs and APIs

TaskResource
Bulk ingestJob API
Upsert one SKUCreate product · Update attributes
Monitor failuresPer line item in job detail — poll export job
Automate pipelineService account

AI after ingest

Sparse ERP descriptions are normal. Use:

Migration from legacy PIM + ERP

Many enterprises run a legacy PIM or spreadsheets alongside SAP/Odoo. See Migrating from legacy PIM for cutover phases while keeping ERP as master.

Security and access

  • ERP credentials live in integration connections — not in product APIs.
  • Service accounts for jobs use least privilege — API authentication.
  • Enterprise review: Security.

Next steps