Two-way sync
Changes in Akeneo or Amazon DynamoDB instantly reflect in both systems. No stale data, no manual imports.
Keep Akeneo and Amazon DynamoDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.
Stacksync mirrors Assets, Channels and locales, Media files, Products from Akeneo into Amazon DynamoDB and keeps both sides consistent in real time. Whatever Akeneo holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in Amazon DynamoDB, such as new prices, stock levels, or fulfillment status, sync back into Akeneo with its validations respected.
Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.
Records from Akeneo, whether products, orders, customers, or inventory, live in Amazon DynamoDB as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Akeneo API, rate limits, and retries.
Updates in Akeneo arrive as row changes in Amazon DynamoDB, so jobs and triggers can respond the moment an order, price, or stock level changes.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Akeneo objects | Amazon DynamoDB objects | How this pairing syncs | |
|---|---|---|---|
| Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. | Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. | Assets is specific to Akeneo and Global secondary indexes (GSIs) to Amazon DynamoDB — each maps to any object or custom field on the other side. | |
| Channels and locales Target-market settings that scope attribute values; read to resolve which localized or channel-specific value to map on each side of a sync. | Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. | Channels and locales is specific to Akeneo and Local secondary indexes (LSIs) to Amazon DynamoDB — each maps to any object or custom field on the other side. | |
| Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. | DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. | Media files is specific to Akeneo and DynamoDB Streams to Amazon DynamoDB — each maps to any object or custom field on the other side. | |
| Products Core catalog records addressed by UUID (recommended) or identifier/SKU; synced two-way with databases, ERPs, and storefronts. Values are scoped per channel and locale. | Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. | Products is specific to Akeneo and Global Tables to Amazon DynamoDB — each maps to any object or custom field on the other side. | |
| Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. | Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. | Product models is specific to Akeneo and Time to Live (TTL) to Amazon DynamoDB — each maps to any object or custom field on the other side. | |
| Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. | Tables Top-level containers, each with a partition key and optional sort key; Stacksync syncs a table as a stream of items with full read and write via PutItem, UpdateItem, and DeleteItem. | Categories is specific to Akeneo and Tables to Amazon DynamoDB — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionAkeneo notifies Stacksync of record changes through webhook events. Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents.
DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.
DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.
DeliveryEach detected change is written to Akeneo through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Akeneo–Amazon DynamoDB connection.
Changes in Akeneo or Amazon DynamoDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Akeneo or Amazon DynamoDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Akeneo or Amazon DynamoDB record.
Track your Akeneo ⇄ Amazon DynamoDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Akeneo and Amazon DynamoDB.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Akeneo and Amazon DynamoDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Akeneo and Amazon DynamoDB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Akeneo and Amazon DynamoDB: authenticate both systems, choose the objects to sync (such as Akeneo's Assets and Channels and locales), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Amazon DynamoDB side: Global Tables, Time to Live (TTL), Tables, Items, plus custom fields where Amazon DynamoDB exposes them. On the Akeneo side: Assets, Channels and locales, Media files, Products. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Akeneo and Amazon DynamoDB: Read the store's data with a query; Internal tools and automations without API code; React to store changes. Records from Akeneo, whether products, orders, customers, or inventory, live in Amazon DynamoDB as ordinary tables or collections, joinable with the rest of your data.
Akeneo: REST API (plus a GraphQL API) and an Events API for webhooks. Authentication: OAuth2 password grant: client_id/secret plus an API user's username/password exchanged at /api/oauth/v1/token for a bearer access_token and refresh_token; Apps use the OAuth2 authorization-code flow. Amazon DynamoDB: AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture. Authentication: AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level. Stacksync manages authentication, retries, and rate limits on both sides.
Amazon DynamoDB: A single item can be at most 400 KB. BatchWriteItem handles up to 25 items or 16 MB per call and BatchGetItem up to 100 items or 16 MB, so large syncs are chunked into batches. Akeneo: Attribute values are scoped by channel (scope) and locale, so a single product field can hold many channel- and language-specific values. Stacksync's field mapping accounts for these differences between Akeneo and Amazon DynamoDB without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 496 integrations available for Akeneo and Amazon DynamoDB.