Two-way sync
Changes in Acumatica or Akeneo instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica and Akeneo 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; Acumatica 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 Assets, Channels and locales, Media files, Products in Akeneo with Sales Orders, Invoices, Purchase Orders, Stock Items in Acumatica field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Acumatica, order and customer detail from Akeneo — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
As orders are picked, shipped, or invoiced in Acumatica, tracking and status flow back to Akeneo so buyers see accurate updates.
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
Available quantities from Acumatica publish to Akeneo, so the store shows what can actually ship and stops overselling.
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.
| Acumatica objects | Akeneo objects | How this pairing syncs | |
|---|---|---|---|
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. | Invoices is specific to Acumatica and Categories to Akeneo — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Attributes Attribute definitions plus attribute options and groups; describe the shape of product data, usually mastered in Akeneo and read downstream. | Purchase Orders is specific to Acumatica and Attributes to Akeneo — each maps to any object or custom field on the other side. | |
| Stock Items Inventory master data with quantities shared with external sales channels. | Families and family variants Templates defining which attributes a product carries and how variants axis out; synced to keep catalog structure consistent across systems. | Stock Items is specific to Acumatica and Families and family variants to Akeneo — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment documents read to update tracking in storefronts and CRMs. | 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. | Shipments is specific to Acumatica and Reference entities and records to Akeneo — each maps to any object or custom field on the other side. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Assets Asset-family media (images, documents) managed in Akeneo's DAM; linked to products and synced to storefronts and commerce systems. | Payments is specific to Acumatica and Assets to Akeneo — each maps to any object or custom field on the other side. | |
| Journal Transactions GL entries replicated into reporting databases. | 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. | Journal Transactions is specific to Acumatica and Channels and locales to Akeneo — 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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Akeneo through its API, with automatic retries and rate-limit backoff.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Akeneo connection.
Changes in Acumatica or Akeneo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Akeneo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Akeneo record.
Track your Acumatica ⇄ Akeneo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Akeneo.
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 Acumatica and Akeneo 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 Acumatica and Akeneo 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 Acumatica and Akeneo: authenticate both systems, choose the objects to sync (such as Acumatica's Invoices and Purchase Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Akeneo side: Assets, Channels and locales, Media files, Products, plus custom fields where Akeneo exposes them. On the Acumatica side: Sales Orders, Invoices, Purchase Orders, Stock Items. 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 Acumatica and Akeneo: Fulfillment and shipment status close the loop; One customer master; Where Acumatica is the inventory system of record: stock stays accurate. As orders are picked, shipped, or invoiced in Acumatica, tracking and status flow back to Akeneo so buyers see accurate updates.
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. 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. 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 474 integrations available for Acumatica and Akeneo.