Skip to content
Accounting and finance ⇄ E-commerce

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

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

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

Shopware 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 Applications, Metrics, Dimension lists, Tables in Pigment with Sales Channels, Media, Products, Categories in Shopware field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shopware, 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 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 02 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 03 Write tracking numbers and delivery state onto `order_delivery` from a 3PL or WMS so storefront order status reflects fulfillment.
  • 04 Consolidate orders and customers from multiple `sales_channel` storefronts into one Postgres database for cross-channel analysis.

Common sync patterns

Where Shopware originates orders: sales flow into the books

A new or updated order in Shopware 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 Shopware, 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 Pigment and Shopware

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.

Pigment objects Shopware objects How this pairing syncs
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. Data imports is specific to Pigment and Sales Channels to Shopware — each maps to any object or custom field on the other side.
Users and permissions Access controls governing which model areas a sync can touch Media Media assets (`media`) such as product images; referenced by id so file URLs and metadata sync into downstream catalogs. Users and permissions is specific to Pigment and Media to Shopware — each maps to any object or custom field on the other side.
Applications Planning models organized by domain such as finance, sales, or workforce Products The product catalog (`product`), including parent/child variants, per-currency nested price arrays, and stock; synced two-way with ERP, PIM, or a database. Applications is specific to Pigment and Products to Shopware — each maps to any object or custom field on the other side.
Metrics Multidimensional values holding plans and actuals; the main target for inbound data Categories The navigation and catalogue tree (`category`); mapped to product taxonomy in a warehouse or written from a PIM. Metrics is specific to Pigment and Categories to Shopware — each maps to any object or custom field on the other side.
Dimension lists Master data like accounts, products, or employees that metrics are sliced by Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. Dimension lists is specific to Pigment and Customers to Shopware — each maps to any object or custom field on the other side.
Tables Row-based transactional data loaded into models from source systems Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. Tables is specific to Pigment and Orders to Shopware — each maps to any object or custom field on the other side.

How changes propagate between Pigment and Shopware

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.

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

Shopware Pigment Sub-second propagation

DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.

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

Rate-limit considerations

  • Pigment: Subject to the platform's API rate limits.
  • Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Pigment ⇄ Shopware

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Pigment and Shopware connectors work

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

Shopware

Integration surface
Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication
OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
Change detection
App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
Capabilities
read · write · webhooks
Rate limits
No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works

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

    Choose tables

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

Pigment and Shopware 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 Pigment and Shopware.

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