Skip to content
E-commerce ⇄ CRM

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

Keep Akeneo and Close 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 Close

Keep the customers and orders that Close and Akeneo share aligned in real time, so sales works from live purchase history and the store works from current account details.

Close holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Akeneo runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.

Stacksync links Contacts, Opportunities, Activities, Tasks in Close to Categories, Attributes, Families and family variants, Reference entities and records in Akeneo with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.

Common use cases

  • 01 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • 02 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • 03 Write Categories, Families, and Attributes from an ERP or supplier feed into Akeneo to build and maintain catalog structure.
  • 04 Read Reference entities records such as brands and manufacturers into a data warehouse for cross-catalog reporting.

Common sync patterns

Where both keep product records: catalog and CRM products aligned

Where Close tracks products or line items and Akeneo holds the catalog, shared items are matched on SKU so quotes, deals, and orders reference the same products.

One customer identity across sales and store

A person who exists as a contact in Close and a buyer in Akeneo is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.

Where Akeneo records orders: purchase history on the account

Orders and their status from Akeneo appear on the matching contact or account in Close, so reps see what a customer has bought and what is in flight before the next conversation.

What you can sync between Akeneo and Close

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 Close objects How this pairing syncs
Categories The category tree used to classify products; read out for storefront navigation or written in from an ERP to seed catalog structure. Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Categories is specific to Akeneo and Contacts to Close — 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. Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. Attributes is specific to Akeneo and Opportunities to Close — 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 Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Families and family variants is specific to Akeneo and Activities to Close — 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. Tasks Follow-up items assigned to users; synced for workload and SLA reporting. Reference entities and records is specific to Akeneo and Tasks to Close — 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. Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Assets is specific to Akeneo and Custom Activities to Close — 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. Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Channels and locales is specific to Akeneo and Custom Fields to Close — each maps to any object or custom field on the other side.

How changes propagate between Akeneo and Close

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

Close Akeneo Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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.
  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Akeneo ⇄ Close

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Akeneo ⇄ Close 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 Close.

How the Akeneo and Close 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.

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers
How it works

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

    Choose tables

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

Akeneo and Close 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 487 integrations available for Akeneo and Close.

Popular · 8 of 487
All Akeneo integrations All Close 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