Skip to content
ERP ⇄ E-commerce

Acumatica to Akeneo integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Acumatica and Akeneo

Keep the storefront in step with the back office: Akeneo and Acumatica share products, inventory, and orders in real time, in both directions.

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.

Common use cases

  • 01 Two-way sync Products and product models with an operational Postgres database or ERP so SKUs, prices, and localized descriptions stay aligned across systems.
  • 02 Push enriched Products and their Assets into an ecommerce storefront or commerce database when product.created and product.updated webhooks fire.
  • 03 Align Acumatica's built-in CRM opportunities and cases with an external sales or support platform.
  • 04 Two-way sync of customers, orders, and invoices between Acumatica and a CRM so sales sees ERP truth without ERP logins.

Common sync patterns

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Acumatica, tracking and status flow back to Akeneo so buyers see accurate updates.

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Acumatica is the inventory system of record: stock stays accurate

Available quantities from Acumatica publish to Akeneo, so the store shows what can actually ship and stops overselling.

What you can sync between Acumatica and Akeneo

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.

How changes propagate between Acumatica and Akeneo

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.

Acumatica Akeneo Sub-second propagation

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.

Akeneo Acumatica Sub-second propagation

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.

Rate-limit considerations

  • Akeneo: REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
What ships with Acumatica ⇄ Akeneo

Connect Acumatica and Akeneo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Akeneo connection.

Real-time

Two-way sync

Changes in Acumatica or Akeneo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Acumatica or Akeneo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Acumatica or Akeneo record.

Observability

Monitoring

Track your Acumatica ⇄ Akeneo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Acumatica and Akeneo.

How the Acumatica and Akeneo connectors work

Acumatica

Integration surface
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
Change detection
Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
Capabilities
read · write · webhooks

Akeneo

Integration surface
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
Change detection
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
Capabilities
read · write · webhooks
Rate limits
REST protection triggers above roughly 100 requests/second per PIM instance (HTTP 429 with Retry-After); the Events API caps at 4000 requests/hour with a 500ms webhook ack timeout.
How it works

How to connect Acumatica to Akeneo — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Acumatica connected
    Akeneo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Acumatica ⇄ Akeneo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Acumatica Akeneo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Acumatica and Akeneo integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 474 integrations available for Acumatica and Akeneo.

Popular · 5 of 474
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.