Skip to content
ERP · Two-way sync platform

E2 Shop System integration.

Connect your E2 Shop System workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Customers, Invoices and Vendors.

  • Review your systems with an integration engineer
  • Get a scoped implementation and validation plan

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
Record types

E2 Shop System records to discuss.

These E2 Shop System record examples help scope a technical review. They are not a list of verified Stacksync operations.

Quotes / Estimates
Identify this record type and the operation you need to review with Stacksync.
Jobs / Work orders
Identify this record type and the operation you need to review with Stacksync.
Customers
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
See 3 more record examples
Vendors
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Parts
Identify this record type and the operation you need to review with Stacksync.
Routings / Operations
Identify this record type and the operation you need to review with Stacksync.
Connection setup

E2 Shop System connection requirements.

Review E2 Shop System access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion.

Prepare access and scope for the engineering review
  • Identify the E2 Shop System account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for E2 Shop System, including read/write support, authentication, and initial-load limits.

Integration design

Match records and fields for your E2 Shop System integration.

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

Explore record matching and field-mapping checks
E2 Shop SystemSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Load related records in the right order
Resolve person or company type, legal entity, business role, and any billing account before transactions.

Mapping checks by record type

Customers

Confirm object support with Stacksync

Identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Fields to consider
Source customer ID · Person/company classification · Legal entity or business unit · Destination identity reference
Related records to resolve first
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test before going live
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Invoices

Confirm object support with Stacksync

Identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Fields to consider
Source invoice ID · Customer or supplier reference · Line totals · Currency · Posting/payment status
Related records to resolve first
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test before going live
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Vendors

Confirm object support with Stacksync

Identity
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Fields to consider
Source supplier ID · Legal name · Entity reference · Payment terms · Active status
Related records to resolve first
Resolve business-unit and payment-term references before purchasing transactions.
Test before going live
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.

Purchase orders

Confirm object support with Stacksync

Identity
Retain purchase-order and line IDs together with the supplier and legal-entity context.
Fields to consider
Source purchase-order ID · Supplier reference · Line references · Quantity · Approval status
Related records to resolve first
Resolve supplier, product, business unit, and delivery-location references before lines.
Test before going live
Test a partially received purchase order and an amendment after approval.

Time tickets

Confirm object support with Stacksync

Identity
Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases.
Fields to consider
Source ticket ID · Requester reference · Status · Priority · Assigned team
Related records to resolve first
Resolve requester, organization, team, and status references before ticket updates.
Test before going live
Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the E2 Shop System integration in four steps.

Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

View the four setup tests and expected results

  1. Verify E2 Shop System connectivity and database privileges

    After confirming an implementation path, validate the selected access method from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture.

    Expected result: The approved role can access the selected data and capture later changes without depending on an administrator’s personal session.

  2. Test record matching for Customers

    Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

    Expected result: Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

  3. Test the operation your workflow needs

    Review one E2 Shop System record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your E2 Shop System integration.

Diagnose record matching, delayed changes, and rejected operations
A E2 Shop System record appears under the wrong destination record
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Resolve person or company type, legal entity, business role, and any billing account before transactions. Repair the ID relationship before repeating the operation.
The first load looks correct but later results differ
Confirm the selected E2 Shop System implementation’s change-detection method for Customers, Invoices and Vendors. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture.
One operation succeeds while another is rejected
Check the specific E2 Shop System object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your E2 Shop System workflow with an engineer

E2 Shop System integration guides

FAQ

E2 Shop System connector FAQ

How should I plan an integration with E2 Shop System?

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the E2 Shop System connector write changes back?

Write-back support is not established for this connection. Review the E2 Shop System records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Which identifiers should I preserve for E2 Shop System data?

Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.

Which related records should I load first for E2 Shop System?

Resolve person or company type, legal entity, business role, and any billing account before transactions.

How do I validate E2 Shop System changes after the initial load?

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

What will we cover in a E2 Shop System integration demo?

Start with one workflow and a sample record from Customers, Invoices and Vendors. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore E2 Shop System connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

9 integration guides

CRM · 1

ERP · 3

Database · 2

Data warehouse · 3

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.

Learn more about security
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:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started