Skip to content
ERP ⇄ Accounting and finance

E2 Shop System to Pigment integration — real-time data sync

Keep E2 Shop System 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 E2 Shop System and Pigment

Keep Pigment and E2 Shop System agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Pigment, so Pigment always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.

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.

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.
  • Sync customer and invoice data to accounting or CRM so the front office is not re-keying from the ERP.
  • Land quote, job cost, and time-ticket data in a warehouse for margin analysis across jobs.

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Pigment serves a business unit and E2 Shop System is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Pigment handles billing: invoices land in E2 Shop System

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

What you can sync between E2 Shop System 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.

E2 Shop System objects Pigment objects
Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Customers Buyer records synced to CRM or accounting counterparts. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Vendors Supplier records referenced on purchasing documents. Users and permissions Access controls governing which model areas a sync can touch
Parts Part masters with routings and material definitions specific to each shop. Applications Planning models organized by domain such as finance, sales, or workforce
Routings / Operations Per-part operation sequences that carry estimated and actual times. Metrics Multidimensional values holding plans and actuals; the main target for inbound data
Purchase orders Outside material and service purchases tied to jobs. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
What ships with E2 Shop System ⇄ Pigment

Connect E2 Shop System and Pigment for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between E2 Shop System and Pigment.

How the E2 Shop System and Pigment connectors work

E2 Shop System

Integration surface
No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
Authentication
Database credentials or application-level export access on the on-premises installation
Change detection
Polling database tables or scheduled exports
Capabilities
read
Rate limits
Not API-bound; constrained by on-premises database access windows

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 E2 Shop System 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 E2 Shop System 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
    E2 Shop System connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

E2 Shop System 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 E2 Shop System and Pigment.

Popular · 8 of 386
All E2 Shop System 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