Skip to content
E-commerce ⇄ ERP

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

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

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

Nuorder runs the storefront and takes the orders; Odoo 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 Pricing / Price Lists, Payments, Products, Orders in Nuorder with CRM Leads (crm.lead), Purchase Orders (purchase.order), Inventory Transfers (stock.picking), Employees (hr.employee) in Odoo field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Odoo, 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 Sync Odoo contacts and CRM leads with an external CRM when sales runs outside Odoo but invoicing stays in it.
  • 04 Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.

Common sync patterns

Where Odoo is the inventory system of record: stock stays accurate

Available quantities from Odoo publish to Nuorder, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Nuorder creates the matching record in Odoo with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

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.

What you can sync between Nuorder and Odoo

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.

Nuorder objects Odoo objects How this pairing syncs
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. Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. Payments is specific to Nuorder and Purchase Orders (purchase.order) to Odoo — each maps to any object or custom field on the other side.
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. Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Products is specific to Nuorder and Inventory Transfers (stock.picking) to Odoo — each maps to any object or custom field on the other side.
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. Employees (hr.employee) HR records read for directory and provisioning syncs. Orders is specific to Nuorder and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side.
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. Projects and Tasks (project.project / project.task) Work items synced with external project tools. Companies is specific to Nuorder and Projects and Tasks (project.project / project.task) to Odoo — each maps to any object or custom field on the other side.
Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. Line Items is specific to Nuorder and Contacts (res.partner) to Odoo — each maps to any object or custom field on the other side.
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. Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. Inventory (ATS) is specific to Nuorder and Sales Orders (sale.order) to Odoo — each maps to any object or custom field on the other side.

How changes propagate between Nuorder and Odoo

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.

Nuorder Odoo 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 Odoo through its API, with automatic retries and rate-limit backoff.

Odoo Nuorder Sub-second propagation

DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.

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

Rate-limit considerations

  • 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.
  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Nuorder ⇄ Odoo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Nuorder and Odoo connectors work

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.

Odoo

Integration surface
XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
Authentication
Database user credentials or per-user API keys
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

How to connect Nuorder to Odoo — 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 Nuorder and Odoo 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
    Nuorder connected
    Odoo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Nuorder and Odoo 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 · Nuorder ⇄ Odoo
    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
    Nuorder Odoo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Nuorder and Odoo 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 383 integrations available for Nuorder and Odoo.

Popular · 7 of 383
All Nuorder integrations All Odoo 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