Skip to content
ERP ⇄ E-commerce

Cin7 to Nuorder integration — real-time, two-way sync

Keep Cin7 and Nuorder 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 Cin7 and Nuorder

Keep the storefront in step with the back office: Nuorder and Cin7 share products, inventory, and orders in real time, in both directions.

Nuorder runs the storefront and takes the orders; Cin7 owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs Products, Orders, Companies, Line Items in Nuorder with Contacts, Branches / locations, Stock adjustments and transfers, Credit notes / returns in Cin7 field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Cin7, order and customer detail from Nuorder — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Inventory / ATS levels from a warehouse or ERP into NuORDER via /api/inventory/{id} so buyers see accurate available-to-sell quantities and oversell drops.
  • 02 Two-way sync Companies (retail accounts) between NuORDER and a CRM so buyers created in either system stay aligned on customer master data.
  • 03 Write purchase orders created in a planning tool back into Cin7 for receiving.
  • 04 Consolidate stock movements from multiple branches into one reporting database.

Common sync patterns

One product catalog

Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Cin7, tracking and status flow back to Nuorder so buyers see accurate updates.

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

What you can sync between Cin7 and Nuorder

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.

Cin7 objects Nuorder objects How this pairing syncs
Products SKU records with options and pricing, synced with storefront and marketplace catalogs. Products Fluent-schema catalog records (style, SKU, images, custom fields); brands push them in via /api/product/new (POST) and update via /api/product/{id} (PUT), typically mastered in a PIM or ERP. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Contacts Customers and suppliers, matched to CRM records to keep account data consistent. Payments Payment status and detail returned alongside Orders (the modified-orders date-range query returns the order plus its payment information); read-oriented in most syncs. Contacts is specific to Cin7 and Payments to Nuorder — each maps to any object or custom field on the other side.
Branches / locations Warehouse entities that scope every stock movement and order allocation. Orders Wholesale sales orders with nested line items and payment info; read via /api/orders/{status}/detail, created via /api/order/new (PUT), and advanced via /api/order/{id}/process and /cancel. Branches / locations is specific to Cin7 and Orders to Nuorder — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Companies Retailer and customer accounts (buyers, doors); enumerated via /api/companies/codes/list and created through the customer-creation API, commonly synced with a CRM or ERP. Stock adjustments and transfers is specific to Cin7 and Companies to Nuorder — each maps to any object or custom field on the other side.
Credit notes / returns Return documents synced so finance and support see the same refund state. Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. Credit notes / returns is specific to Cin7 and Line Items to Nuorder — each maps to any object or custom field on the other side.
Inventory levels Stock on hand by branch or location, published outward for availability. Inventory (ATS) Available-to-sell stock levels updated via /api/inventory/{id} (PUT); usually written from a warehouse or ERP into NuORDER so buyers see accurate availability. Inventory levels is specific to Cin7 and Inventory (ATS) to Nuorder — each maps to any object or custom field on the other side.

How changes propagate between Cin7 and Nuorder

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.

Cin7 Nuorder Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

DeliveryEach detected change is written to Nuorder through its API, with automatic retries and rate-limit backoff.

Nuorder Cin7 Interval-based propagation

DetectionStacksync polls Nuorder for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window.

DeliveryEach detected change is written to Cin7 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
  • Nuorder: Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
What ships with Cin7 ⇄ Nuorder

Connect Cin7 and Nuorder for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Nuorder connection.

Real-time

Two-way sync

Changes in Cin7 or Nuorder instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Cin7 or Nuorder 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 Cin7 or Nuorder record.

Observability

Monitoring

Track your Cin7 ⇄ Nuorder sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Cin7 and Nuorder.

How the Cin7 and Nuorder connectors work

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core

Nuorder

Integration surface
REST API (JSON), with optional SFTP flat-file data feeds
Authentication
OAuth 1.0 — consumer key/secret plus an access token/secret issued per approved application in the NuORDER Portal (Admin > Settings > API Management > Approved Applications)
Change detection
Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window; products and customers are pulled by last-modified date. No native webhooks.
Capabilities
read · write
Rate limits
Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
How it works

How to connect Cin7 to Nuorder — 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.

  1. 01

    Connect your apps

    Authenticate Cin7 and Nuorder with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Cin7 connected
    Nuorder connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Cin7 and Nuorder 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Cin7 ⇄ Nuorder
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Cin7 Nuorder
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Cin7 and Nuorder integration FAQ

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 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 363 integrations available for Cin7 and Nuorder.

Popular · 5 of 363
All Cin7 integrations All Nuorder integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own