Can you integrate Cin7 with E2 Shop System?

Explore a Cin7 and E2 Shop System integration with a Stacksync engineer. Stacksync support for Cin7 and E2 Shop System is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Cin7 and E2 Shop System sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

How fast does the Cin7 to E2 Shop System sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Cin7 fields to E2 Shop System?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Cin7 and E2 Shop System integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Cin7 and E2 Shop System pilot start with?

Start by reviewing Contacts in Cin7 and Customers in E2 Shop System. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

What should be ready before the Cin7 and E2 Shop System initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Cin7 account, edition, environment, and business objects the integration must access. Identify the E2 Shop System account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

ERP · Two-way sync platform

Cin7 and E2 Shop System integration

Plan how Cin7 and E2 Shop System should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Set this up from Claude or ChatGPT

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Cin7

E2 Shop System

Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Cin7 Contacts or E2 Shop System Customers needs a defined result in the other system.

Start with Cin7 Contacts and E2 Shop System Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

AI assistant

Set up Cin7 and E2 Shop System from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.

Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Cin7 and E2 Shop System.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Cin7 and E2 Shop System. The assistant checks what each app supports, for example:

“Build a workflow that messages our team in Slack when a Cin7 record changes.”
“Create a Genie that answers questions about our E2 Shop System data in Slack.”

What happens next

Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Cin7 and E2 Shop System
Cin7 record	E2 Shop System record	Record matching	Field ownership
ContactsProposed record; confirm Stacksync object support.Customer identity assessment	CustomersProposed record; confirm Stacksync object support.	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.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Sales ordersProposed record; confirm Stacksync object support.Business process handoff	InvoicesProposed record; confirm Stacksync object support.	Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.	Finance owns invoice posting; the order system supplies the approved commercial context.
Purchase ordersProposed record; confirm Stacksync object support.Record matching	Purchase ordersProposed record; confirm Stacksync object support.	Retain purchase-order and line IDs together with the supplier and legal-entity context.	Keep procurement approval separate from receipt and payment states.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Cin7

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Products Inventory levels Sales orders Purchase orders Contacts Branches / locations	Confirm support for this record type and the direction you need.

Discuss Cin7 requirements

E2 Shop System

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Quotes / Estimates Jobs / Work orders Customers Vendors Parts Routings / Operations	Confirm support for this record type and the direction you need.

Discuss E2 Shop System requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Cin7	E2 Shop System
Integration interface	REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs	No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
Authentication	Confirm the credentials, API plan, and permissions required for Cin7.	Confirm the credentials, API plan, and permissions required for E2 Shop System.
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Confirm with Stacksync	Confirm with Stacksync
Write access	Confirm with Stacksync	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Cin7

Integration interface: REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication: Confirm the credentials, API plan, and permissions required for Cin7.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Cin7 account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Cin7, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Cin7 and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

E2 Shop System

Integration interface: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
Authentication: Confirm the credentials, API plan, and permissions required for E2 Shop System.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

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.

Limitations to check

Confirm Stacksync support for E2 Shop System and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Cin7 and E2 Shop System access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Cin7 setup checklist

Identify the Cin7 account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Cin7, including read/write support, authentication, and initial-load limits.

E2 Shop System setup checklist

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.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Cin7 and E2 Shop System planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Customer identity

Contacts / Customers

Before linking Cin7 Contacts to E2 Shop System Customers, check whether the customer is an individual or a company. Match the correct record type in each system.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Cin7: Object support to establish
E2 Shop System: Object support to establish
Record 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.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Business process

Sales orders / Invoices

Order-to-invoice handoff: Cin7 Sales orders provides context for E2 Shop System Invoices. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Cin7: Object support to establish
E2 Shop System: Object support to establish
Record identity: Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
Field ownership: Finance owns invoice posting; the order system supplies the approved commercial context.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Record matching

Purchase orders / Purchase orders

Compare whether Cin7 Purchase orders and E2 Shop System Purchase orders describe the same purchase order in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Cin7: Object support to establish
E2 Shop System: Object support to establish
Record identity: Retain purchase-order and line IDs together with the supplier and legal-entity context.
Field ownership: Keep procurement approval separate from receipt and payment states.

Fields to include

Source purchase-order ID
Supplier reference
Line references
Quantity
Approval status

Record dependencies: Resolve supplier, product, business unit, and delivery-location references before lines.
Validation: Test a partially received purchase order and an amendment after approval.
Recovery: Reconcile receipts already recorded before resubmitting an amended order.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Contacts / Customers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: 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. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Cin7 and E2 Shop System record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Contacts / Customers, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Sales orders / Invoices handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Cin7 / E2 Shop System migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Contacts or Customers record needs a defined result in the other system.

Start with Cin7 Contacts and E2 Shop System Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Sales order process handoff

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Sales orders or Invoices record needs a defined result in the other system.

Start with Cin7 Sales orders and E2 Shop System Invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Purchase order sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Purchase orders or Purchase orders record needs a defined result in the other system.

Start with Cin7 Purchase orders and E2 Shop System Purchase orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, product, business unit, and delivery-location references before lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a partially received purchase order and an amendment after approval.

If it fails: Reconcile receipts already recorded before resubmitting an amended order.

Reconcile Cin7 business records with E2 Shop System

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Cin7 needs operational visibility through Customers or Vendors.

Select Products or Inventory levels with the correct legal entity, period, and currency.
Define a reporting relationship in E2 Shop System; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect Cin7 Contacts and E2 Shop System Customers, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated sales order change

Investigate

Inspect Cin7 Sales orders and E2 Shop System Invoices, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Rejected or repeated purchase order change

Investigate

Inspect Cin7 Purchase orders and E2 Shop System Purchase orders, their IDs, and the destination error.

Next action

Reconcile receipts already recorded before resubmitting an amended order.

A record type or update is unavailable

Investigate

Check the Cin7 and E2 Shop System connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Cin7 and E2 Shop System

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Cin7 E2 Shop System Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in E2 Shop System.

E2 Shop System Cin7 Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Cin7.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ