Real-time sync
Changes in E2 Shop System or MarkLogic instantly reflect in both systems. No stale data, no manual imports.
Keep E2 Shop System and MarkLogic 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 MarkLogic, so MarkLogic 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 Purchase orders, Time tickets, Invoices, Quotes / Estimates from E2 Shop System into MarkLogic 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 MarkLogic sync back into E2 Shop System with its validations respected.
Worker and org records stay current in MarkLogic for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from MarkLogic back into E2 Shop System, keeping the ERP authoritative.
Records from E2 Shop System live in MarkLogic as ordinary tables or collections, joinable with the rest of your data.
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 | MarkLogic objects | |
|---|---|---|
| Vendors Supplier records referenced on purchasing documents. | TDE Views Relational projections of documents that let syncs read document data as SQL rows. | |
| Parts Part masters with routings and material definitions specific to each shop. | Document Metadata & Properties Permissions, quality, and property fragments carried with each document. | |
| Routings / Operations Per-part operation sequences that carry estimated and actual times. | Databases & Forests Storage units that define the scope and placement of synced content. | |
| Purchase orders Outside material and service purchases tied to jobs. | Users & Roles Security principals that govern what an integration credential can read or write. | |
| Time tickets Labor collection records used for job costing. | Documents JSON and XML documents, the primary records read from and written to the database. | |
| Invoices Billing records synced to accounting for AR reporting. | Collections Named groupings used to scope which documents a sync reads or updates. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–MarkLogic connection.
Changes in E2 Shop System or MarkLogic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever E2 Shop System or MarkLogic 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 MarkLogic record.
Track your E2 Shop System ⇄ MarkLogic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between E2 Shop System and MarkLogic.
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 MarkLogic 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 MarkLogic 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 MarkLogic — 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 MarkLogic: No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MarkLogic side: Users & Roles, Documents, Collections, Semantic Triples, plus custom fields where MarkLogic exposes them. On the E2 Shop System side: Purchase orders, Time tickets, Invoices, Quotes / Estimates. 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 MarkLogic. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for E2 Shop System and MarkLogic: Where E2 Shop System is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in MarkLogic for provisioning, access, and reporting systems that read from the database.
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. MarkLogic: REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries. Authentication: Username/password (digest or basic), with certificate-based options. 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 MarkLogic.