Real-time sync
Changes in E2 Shop System or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Keep E2 Shop System and IBM AS/400 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into IBM AS/400, so IBM AS/400 always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Jobs / Work orders, Customers, Vendors, Parts from E2 Shop System into IBM AS/400 and keeps both sides consistent in real time. Whatever E2 Shop System is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in IBM AS/400 sync back into E2 Shop System with its validations respected.
Choose exactly which tables and fields may flow from IBM AS/400 back into E2 Shop System, keeping the ERP authoritative.
Records from E2 Shop System live in IBM AS/400 as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the E2 Shop System interface, limits, and retries.
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 | IBM AS/400 objects | |
|---|---|---|
| Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. | Libraries The schema-equivalent containers that scope which files a sync reads. | |
| Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. | Physical files (tables) The Db2 for i tables mapped directly to sync targets. | |
| Customers Buyer records synced to CRM or accounting counterparts. | Logical files (views) Indexed or filtered views over physical files, usable as read sources. | |
| Vendors Supplier records referenced on purchasing documents. | Members Sub-partitions of files in legacy applications, flattened or selected during syncs. | |
| Parts Part masters with routings and material definitions specific to each shop. | Rows / records The unit of read and write, accessed via SQL or record-level access. | |
| Routings / Operations Per-part operation sequences that carry estimated and actual times. | Journals and journal receivers The change log that enables log-based CDC on journaled files. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–IBM AS/400 connection.
Changes in E2 Shop System or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever E2 Shop System or IBM AS/400 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single E2 Shop System or IBM AS/400 record.
Track your E2 Shop System ⇄ IBM AS/400 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between E2 Shop System and IBM AS/400.
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.
Authenticate E2 Shop System and IBM AS/400 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the E2 Shop System and IBM AS/400 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between E2 Shop System and IBM AS/400 — 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 IBM AS/400: Journal-based CDC by reading journal receivers on journaled files; polling as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the IBM AS/400 side: Physical files (tables), Logical files (views), Members, Rows / records, plus custom fields where IBM AS/400 exposes them. On the E2 Shop System side: Jobs / Work orders, Customers, Vendors, Parts. 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 IBM AS/400. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for E2 Shop System and IBM AS/400: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from IBM AS/400 back into E2 Shop System, keeping the ERP authoritative.
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. IBM AS/400: SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access. Authentication: IBM i user profile credentials (database credentials). Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for E2 Shop System and IBM AS/400.