Real-time
Real-time sync
Changes in E2 Shop System or Kustomer instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
E2 Shop System to Kustomer integration — real-time data sync
Keep E2 Shop System and Kustomer 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 Kustomer
Flow E2 Shop System data into Kustomer in real time — no exports, no schedulers, no custom scripts.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Kustomer, so Kustomer always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
Kustomer holds the customer relationship; E2 Shop System runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Common use cases
- 01 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 02 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 03 Keep purchase order data visible to planning or supplier-facing tools without direct ERP access.
- 04 Replicate job and work order status into a reporting database to power shop-floor and delivery dashboards.
Common sync patterns
Where E2 Shop System manages people and org data: keep Kustomer aligned
Owners, territories, and org structure informed by E2 Shop System stay current in Kustomer.
Where E2 Shop System handles order-to-cash: closed-won flows through
A deal won in Kustomer creates or updates the customer in E2 Shop System with clean data, so fulfillment and invoicing start without re-entry.
Where E2 Shop System is the finance system of record: money status on the account
Invoice and payment state from E2 Shop System shows on the account in Kustomer, so reps see balances before promising the next order.
What you can sync between E2 Shop System and Kustomer
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 | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Customers Buyer records synced to CRM or accounting counterparts. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction. | |
| Parts Part masters with routings and material definitions specific to each shop. | Messages Individual messages within conversations support full-thread replication. | Parts is specific to E2 Shop System and Messages to Kustomer — each maps to any object or custom field on the other side. | |
| Routings / Operations Per-part operation sequences that carry estimated and actual times. | Companies Organization records group customers and map to CRM accounts. | Routings / Operations is specific to E2 Shop System and Companies to Kustomer — each maps to any object or custom field on the other side. | |
| Purchase orders Outside material and service purchases tied to jobs. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Purchase orders is specific to E2 Shop System and Custom Objects (Klasses) to Kustomer — each maps to any object or custom field on the other side. | |
| Time tickets Labor collection records used for job costing. | Users Agent records map conversation ownership to people in other systems. | Time tickets is specific to E2 Shop System and Users to Kustomer — each maps to any object or custom field on the other side. | |
| Invoices Billing records synced to accounting for AR reporting. | Teams Team assignments support routing parity and reporting. | Invoices is specific to E2 Shop System and Teams to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between E2 Shop System and Kustomer
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.
E2 Shop System Kustomer Interval-based propagation
DetectionStacksync polls E2 Shop System for changes on an incremental schedule, reading only records changed since the previous pass. Polling database tables or scheduled exports.
DeliveryEach detected change is written to Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer E2 Shop System Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryE2 Shop System does not accept inbound record writes, so this direction carries requests rather than records: E2 Shop System's output flows back as field updates on the originating Kustomer records.
Rate-limit considerations
- E2 Shop System: Not API-bound; constrained by on-premises database access windows.
- Kustomer: Subject to the platform's API rate limits.
What ships with E2 Shop System ⇄ Kustomer
Connect E2 Shop System and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever E2 Shop System or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your E2 Shop System ⇄ Kustomer 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 Kustomer.
How the E2 Shop System and Kustomer 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
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect E2 Shop System to Kustomer — 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.
- 01
Connect your apps
Authenticate E2 Shop System and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
E2 Shop System
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the E2 Shop System and Kustomer 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.
objects · E2 Shop System ⇄ KustomerCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
E2 Shop System KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
E2 Shop System and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between E2 Shop System and Kustomer — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Change detection on E2 Shop System: Polling database tables or scheduled exports. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kustomer side: Users, Teams, Tags, Notes, plus custom fields where Kustomer exposes them. On the E2 Shop System side: Invoices, Quotes / Estimates, Jobs / Work orders, Customers. Stacksync auto-detects both schemas and converts types between the two systems.
-
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into Kustomer. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for E2 Shop System and Kustomer: Where E2 Shop System manages people and org data: keep Kustomer aligned; Where E2 Shop System handles order-to-cash: closed-won flows through; Where E2 Shop System is the finance system of record: money status on the account. Owners, territories, and org structure informed by E2 Shop System stay current in Kustomer.
-
E2 Shop System: 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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 175 integrations available for E2 Shop System and Kustomer.
Popular · 2 of 175
No integrations match .
