Two-way sync
Changes in Akeneo or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Akeneo and SAP Hana 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 Attributes, Families and family variants, Reference entities and records, Assets from Akeneo into SAP Hana 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 SAP Hana, 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.
Orders and their status become rows in SAP Hana for routing, fulfillment, and reporting, without polling the platform.
Choose exactly which tables and fields may flow from SAP Hana back into Akeneo, keeping the store authoritative on what it owns.
Records from Akeneo, whether products, orders, customers, or inventory, live in SAP Hana as ordinary tables or collections, joinable with the rest of your data.
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 | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Reference entities and records Structured lookups like brands, manufacturers, or ingredients with their own records (Enterprise Edition); synced two-way or read into a warehouse for reporting. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Reference entities and records is specific to Akeneo and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Assets is specific to Akeneo and SQL views to SAP Hana — 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. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Channels and locales is specific to Akeneo and Schemas to SAP Hana — 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. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Media files is specific to Akeneo and Sequences to SAP Hana — 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. | Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. | Products is specific to Akeneo and Triggers to SAP Hana — 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. | System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. | Product models is specific to Akeneo and System-versioned temporal tables to SAP Hana — 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 SAP Hana as a row-level write, with types converted between the two schemas.
DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.
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–SAP Hana connection.
Changes in Akeneo or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Akeneo or SAP Hana 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 SAP Hana record.
Track your Akeneo ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Akeneo and SAP Hana.
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 SAP Hana 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 SAP Hana 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 SAP Hana: authenticate both systems, choose the objects to sync (such as Akeneo's Reference entities and records and Assets), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 SAP Hana: Order data where your code can use it; Controlled write-back; Read the store's data with a query. Orders and their status become rows in SAP Hana for routing, fulfillment, and reporting, without polling the platform.
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. SAP Hana: SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access. Authentication: Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting. Stacksync manages authentication, retries, and rate limits on both sides.
SAP Hana: Polling change detection requires a last-modified timestamp column; without one, triggers or system-versioned temporal tables are needed to catch updates and deletes. Akeneo: The product endpoint comes in two forms: a UUID variant (recommended, stable) and an identifier/SKU variant; identifiers can change while the UUID never does. Stacksync's field mapping accounts for these differences between Akeneo and SAP Hana without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Akeneo and SAP Hana records are not retained after a sync operation.
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 498 integrations available for Akeneo and SAP Hana.