Two-way sync
Changes in Akeneo or Infor WMS instantly reflect in both systems. No stale data, no manual imports.
Keep Akeneo and Infor WMS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Akeneo runs the storefront and takes the orders; Infor WMS owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Categories, Attributes, Families and family variants, Reference entities and records in Akeneo with Tasks, Locations, Shipments, Appointments in Infor WMS field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Infor WMS, order and customer detail from Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
Available quantities from Infor WMS publish to Akeneo, so the store shows what can actually ship and stops overselling.
An order captured in Akeneo creates the matching record in Infor WMS with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
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 | Infor WMS objects | How this pairing syncs | |
|---|---|---|---|
| Media files Product images and files uploaded via the media endpoint; referenced by products and pushed to downstream commerce and content systems. | Appointments Dock appointment data coordinates carriers and yard operations with external schedules. | Media files is specific to Akeneo and Appointments to Infor WMS — 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. | Items Item definitions keep the WMS aligned with the ERP or OMS item master. | Products is specific to Akeneo and Items to Infor WMS — 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. | Inventory On-hand quantities by location feed available-to-promise in order-taking systems. | Product models is specific to Akeneo and Inventory to Infor WMS — 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. | Receipts / ASNs Advance shipment notices and receipt confirmations sync with procurement systems. | Categories is specific to Akeneo and Receipts / ASNs to Infor WMS — each maps to any object or custom field on the other side. | |
| Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. | Shipment Orders Outbound orders arrive from the ERP or OMS for allocation and picking. | Attributes is specific to Akeneo and Shipment Orders to Infor WMS — each maps to any object or custom field on the other side. | |
| Families and family variants Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems. | Waves Wave assignments group orders for fulfillment and can be reported outward. | Families and family variants is specific to Akeneo and Waves to Infor WMS — 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 written to Infor WMS through its API, with automatic retries and rate-limit backoff.
DetectionInfor WMS notifies Stacksync of record changes through webhook events. ION event publishing or scheduled polling of API endpoints.
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–Infor WMS connection.
Changes in Akeneo or Infor WMS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Akeneo or Infor WMS 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 Infor WMS record.
Track your Akeneo ⇄ Infor WMS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Akeneo and Infor WMS.
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 Infor WMS 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 Infor WMS 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 Infor WMS: authenticate both systems, choose the objects to sync (such as Akeneo's Media files and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Akeneo: Events API webhooks (product.created, product.updated, product.deleted, plus product-model equivalents; product.updated.delta carries old and new values); falls back to polling the 'updated' datetime search filter where the Events API is unavailable. On Infor WMS: ION event publishing or scheduled polling of API endpoints. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Akeneo side: Categories, Attributes, Families and family variants, Reference entities and records, plus custom fields where Akeneo exposes them. On the Infor WMS side: Tasks, Locations, Shipments, Appointments. 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 Infor WMS: One customer master; Where Infor WMS is the inventory system of record: stock stays accurate; New orders reach the back office. Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
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. Infor WMS: REST API via the Infor OS / ION API gateway (cloud deployments run inside Infor CloudSuite). Authentication: OAuth 2.0 via Infor OS. Stacksync manages authentication, retries, and rate limits on both sides.
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 350 integrations available for Akeneo and Infor WMS.