Skip to content
E-commerce ⇄ Accounting and finance

Magento to Pigment integration — real-time, two-way sync

Keep Magento and Pigment 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 Magento and Pigment

Turn every Magento order into clean revenue: Pigment and Magento keep customers, orders, and payment status aligned in real time, in both directions.

Magento runs the storefront — the catalog, the orders, and the buyers placing them. Pigment records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.

Stacksync syncs Scenarios, Data imports, Users and permissions, Applications in Pigment with Configurable / variant products, Categories, Orders, Customers in Magento field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Magento, its paid-or-overdue state from Pigment — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.

The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.

Common use cases

  • 01 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 03 Sync Orders, invoices, and shipments from Magento into Postgres or a warehouse for revenue, margin, and fulfillment-SLA reporting.
  • 04 Master Products, prices, and Category assignments in an ERP or PIM and write them into Magento's catalog by SKU.

Common sync patterns

Where Magento originates orders: sales flow into the books

A new or updated order in Magento creates or updates the matching invoice or revenue record in Pigment, so billing and reporting start without re-entry.

Where Pigment is the money system of record: payment status on the order

Paid, overdue, and refunded state from Pigment lands on the order or account in Magento, so the store and support see what has actually been collected.

One customer master

Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.

What you can sync between Magento and Pigment

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.

Magento objects Pigment objects How this pairing syncs
Categories Catalog tree and product-to-category assignments; written into Magento to control merchandising and read out for taxonomy reporting. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Categories is specific to Magento and Metrics to Pigment — each maps to any object or custom field on the other side.
Orders Sales orders with line items, totals, and status; typically read out of Magento into a warehouse or ERP for fulfillment and revenue reporting. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Orders is specific to Magento and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Customers Customer accounts and address book; synced two-way with a CRM so order history and contact records stay consistent. Tables Row-based transactional data loaded into models from source systems Customers is specific to Magento and Tables to Pigment — each maps to any object or custom field on the other side.
Inventory source items (MSI) Per-source stock quantities under Multi-Source Inventory; written from a WMS/ERP so storefront stock matches the warehouse. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Inventory source items (MSI) is specific to Magento and Scenarios to Pigment — each maps to any object or custom field on the other side.
Invoices Invoice documents tied to orders; read out for finance and revenue recognition, or created via the sales API when billing downstream. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Invoices is specific to Magento and Data imports to Pigment — each maps to any object or custom field on the other side.
Shipments Shipment and tracking records against orders; created or read to drive fulfillment status between Magento and a 3PL/WMS. Users and permissions Access controls governing which model areas a sync can touch Shipments is specific to Magento and Users and permissions to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Magento and Pigment

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.

Magento Pigment Sub-second propagation

DetectionMagento notifies Stacksync of record changes through webhook events. Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at).

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Pigment Magento Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

DeliveryEach detected change is written to Magento through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Magento: No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
  • Pigment: Subject to the platform's API rate limits.
What ships with Magento ⇄ Pigment

Connect Magento and Pigment for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Magento or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Magento or Pigment 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 Magento or Pigment record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Magento and Pigment.

How the Magento and Pigment connectors work

Magento

Integration surface
REST and GraphQL Web APIs (SOAP also available)
Authentication
Token-based OAuth: an integration's access token (consumer key/secret + access token/secret) or a Bearer admin token (default 4-hour expiry); Adobe Commerce as a Cloud Service authenticates via Adobe IMS (OAuth 2)
Change detection
Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at); optional near-real-time via the Adobe Commerce Webhooks / Adobe I/O Events modules (order/created, product/updated, customer/created)
Capabilities
read · write · webhooks
Rate limits
No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Magento and Pigment 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 369 integrations available for Magento and Pigment.

Popular · 7 of 369
All Magento integrations All Pigment 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