Skip to content
E-commerce ⇄ ERP

Akeneo to SAP Business One integration — real-time, two-way sync

Keep Akeneo and SAP Business One 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 Akeneo and SAP Business One

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

Akeneo runs the storefront and takes the orders; SAP Business One 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 Families and family variants, Reference entities and records, Assets, Channels and locales in Akeneo with Business Partners, Items, Sales Orders, A/R Invoices in SAP Business One field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from SAP Business One, 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 Two-way sync of business partners between SAP Business One and a CRM so sales edits and finance records converge on one customer master.
  • 04 Create sales orders in Business One from e-commerce platforms and sync delivery and invoice status back to the storefront.

Common sync patterns

Where SAP Business One is the inventory system of record: stock stays accurate

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

New orders reach the back office

An order captured in Akeneo creates the matching record in SAP Business One with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

One product catalog

Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.

What you can sync between Akeneo and SAP Business One

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 Business One objects How this pairing syncs
Product models Parent records for configurable products; hold shared attribute values that cascade to their variant products, synced alongside Products. Journal Entries GL postings replicated for financial reporting. Product models is specific to Akeneo and Journal Entries to SAP Business One — 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. Warehouses Stock locations that scope inventory quantities in item syncs. Categories is specific to Akeneo and Warehouses to SAP Business One — 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. Price Lists Pricing data synced to quoting and e-commerce platforms. Attributes is specific to Akeneo and Price Lists to SAP Business One — 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. Activities CRM-style tasks and interactions aligned with external sales tools. Families and family variants is specific to Akeneo and Activities to SAP Business One — each maps to any object or custom field on the other side.
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. Business Partners Combined customer, vendor, and lead master records; the anchor object for most syncs. Reference entities and records is specific to Akeneo and Business Partners to SAP Business One — 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. Items Product master data including inventory levels, aligned with e-commerce and warehouse systems. Assets is specific to Akeneo and Items to SAP Business One — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and SAP Business One

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.

Akeneo SAP Business One 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 SAP Business One through its API, with automatic retries and rate-limit backoff.

SAP Business One Akeneo Interval-based propagation

DetectionStacksync polls SAP Business One for changes on an incremental schedule, reading only records changed since the previous pass. Polling on update timestamps.

DeliveryEach detected change is written to Akeneo 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 Akeneo ⇄ SAP Business One

Connect Akeneo and SAP Business One for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Akeneo or SAP Business One 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 Akeneo or SAP Business One record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Akeneo and SAP Business One.

How the Akeneo and SAP Business One connectors work

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.

SAP Business One

Integration surface
Service Layer, a REST API based on OData, plus the legacy COM-based DI API
Authentication
Session-based login with company database, username, and password against the Service Layer
Change detection
Polling on update timestamps; no general-purpose webhook mechanism on the standard surface
Capabilities
read · write
How it works

How to connect Akeneo to SAP Business One — 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 Akeneo and SAP Business One 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
    Akeneo connected
    SAP Business One connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Akeneo and SAP Business One 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 · Akeneo ⇄ SAP Business One
    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
    Akeneo SAP Business One
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Akeneo and SAP Business One 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 472 integrations available for Akeneo and SAP Business One.

Popular · 8 of 472
All Akeneo integrations All SAP Business One integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own