Skip to content
ERP ⇄ Accounting and finance

Körber WMS to Pigment integration — real-time, two-way sync

Keep Körber WMS 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 Körber WMS and Pigment

Keep Pigment and Körber WMS agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Scenarios, Data imports, Users and permissions, Applications in Pigment with Inventory, Receipts / ASNs, Orders, Shipments in Körber WMS in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • Sync headcount and compensation data from an HRIS into workforce planning models.
  • Consolidate warehouse task and throughput data into a BI warehouse for operations reporting
  • Sync inventory positions from Körber WMS to an OMS or e-commerce platform so sellable stock reflects the warehouse

Subsidiary to headquarters

Where Pigment serves a business unit and Körber WMS is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Pigment handles billing: invoices land in Körber WMS

Invoices and payment activity from the billing side post through to the enterprise system automatically.

Migration without a hard cutover

When one system is replacing the other, run both in parallel with records matching until the switch is complete.

What you can sync between Körber WMS 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.

Körber WMS objects Pigment objects
Items Item definitions keep the WMS aligned with the ERP item master. Tables Row-based transactional data loaded into models from source systems
Inventory On-hand quantities by location feed availability in order-taking systems. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Receipts / ASNs Inbound notices and receipt confirmations sync with procurement systems. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Orders Outbound orders arrive from the ERP or OMS for allocation and fulfillment. Users and permissions Access controls governing which model areas a sync can touch
Shipments Ship confirmations and tracking references return to the order source system. Applications Planning models organized by domain such as finance, sales, or workforce
Locations Bin and zone definitions scope inventory data during mapping. Metrics Multidimensional values holding plans and actuals; the main target for inbound data
What ships with Körber WMS ⇄ Pigment

Connect Körber WMS and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Körber WMS–Pigment connection.

Real-time

Two-way sync

Changes in Körber WMS or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Körber WMS 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 Körber WMS or Pigment record.

Observability

Monitoring

Track your Körber WMS ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Körber WMS and Pigment.

How the Körber WMS and Pigment connectors work

Körber WMS

Integration surface
Varies by deployment; typically host-interface messages, file exchange, or vendor APIs via middleware
Authentication
Credentials issued per deployment
Change detection
Polling or message/file-based export from the WMS host interface
Capabilities
read · write
Rate limits
Constrained by deployment architecture rather than published API rate limits

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 Körber WMS 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 Körber WMS 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
    Körber WMS connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Körber WMS and Pigment integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Körber WMS and Pigment.

Popular · 8 of 386
All Körber WMS 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