Documentation

Known Limitations

Understand the current limitations, performance boundaries, and unsupported features.

Transparency First
We believe in being upfront about what SyncPIM can and cannot do. This page documents known limitations to help you make informed decisions.

Performance Limits

MetricRecommended LimitNotes
Catalog size< 300,000 productsLarger catalogs may experience slower exports and require Enterprise plan
Concurrent exports3 parallel exportsTo avoid Akeneo API rate limiting
Enrichers per exportPlan-dependentStarter: 5, Professional: 20, Enterprise: Unlimited
Export timeout4 hoursLong-running exports may timeout; use incremental mode for large catalogs
Variants per productUnlimitedFlat storage architecture handles any number of variants
Large Catalogs
For catalogs exceeding 300,000 products, we recommend using incremental exports after an initial full sync. This significantly reduces export time and API load.

Akeneo API Constraints

SyncPIM operates within Akeneo's API constraints. These are imposed by Akeneo, not SyncPIM.

Rate Limits

Akeneo imposes API rate limits based on your plan. SyncPIM respects these limits with automatic throttling and retry logic.

Pagination Limits

Akeneo limits results per page (max 100). SyncPIM handles pagination automatically using search_after for efficiency.

Token Expiration

OAuth tokens expire after 1 hour. SyncPIM handles re-authentication automatically during long exports.

Scope Restrictions

Some Akeneo features require Enterprise Edition. SyncPIM gracefully handles missing permissions.

Unsupported Akeneo Features

The following Akeneo features are currently not supported or have limited support:

FeatureStatusDetails
PAM (Product Asset Manager) - LegacyNot supportedUse Asset Manager (new) instead. PAM was deprecated by Akeneo.
Asset Manager (Enterprise)SupportedRequires Akeneo Enterprise Edition with appropriate scopes.
Reference EntitiesSupportedFull support with enrichment capabilities.
Proposals / DraftsNot supportedOnly published products are exported.
Product AssociationsSupportedCross-sell, upsell, and custom association types.
Completeness / Quality ScoresSupportedIncluded in export metadata.
Rules EngineN/ASyncPIM exports the result of rules, not the rules themselves.
Tailored ExportsAlternativeUse SyncPIM enrichers for data transformation instead.

Database Limitations

🍃

MongoDB

  • No document size limit (flat storage)
  • Automatic index creation
  • Requires MongoDB 4.4+
  • Atlas shared clusters may have connection limits
🐘

PostgreSQL

  • Full JSONB support for attributes
  • Automatic schema migration
  • Requires PostgreSQL 13+
  • Large JSONB columns may impact query performance

Enricher Limitations

No external API calls

Enrichers cannot make HTTP requests to external services during export. Data transformation is limited to the data available in Akeneo.

No cross-product logic

Each product is enriched independently. You cannot reference other products' data within an enricher (e.g., "copy price from related product").

Template complexity

Mustache templates support basic logic (conditionals, loops) but not complex programming constructs.

Scalability Considerations

Multi-Channel Architecture

SyncPIM uses a database-per-channel strategy. Each Akeneo channel exports to a separate database (e.g., acme_ecommerce, acme_marketplace).

Physical isolation between channels
No cross-channel query overhead
Reference data duplicated per channel
Multiple databases to manage
Need Higher Limits?
If your use case exceeds these limits, contact us to discuss Enterprise options with dedicated support and custom configurations.

Version Compatibility

ComponentSupported Versions
Akeneo PIM5.0, 6.0, 7.0 (SaaS and on-premise)
MongoDB4.4, 5.0, 6.0, 7.0
PostgreSQL13, 14, 15, 16