Skip to content
ERP ⇄ E-commerce

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

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

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

Shipwire 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 Trackings, Rates, Orders, Products in Shipwire with Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order) 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 Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Receivings (advance ship notices) and reconcile them against Purchase Orders so inbound supplier shipments are visible as they land.
  • 02 Pull Returns and tracking.delivered events into a support or analytics database for reverse-logistics and delivery-SLA reporting.
  • 03 Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.
  • 04 Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.

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 Odoo, tracking and status flow back to Shipwire 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 Odoo and Shipwire

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.

Odoo objects Shipwire objects How this pairing syncs
Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. Inventory Transfers (stock.picking) is specific to Odoo and Trackings to Shipwire — each maps to any object or custom field on the other side.
Employees (hr.employee) HR records read for directory and provisioning syncs. Rates Shipping cost quotes for a cart or order; read-only, called at checkout time to estimate carrier costs rather than synced as stored records. Employees (hr.employee) is specific to Odoo and Rates to Shipwire — each maps to any object or custom field on the other side.
Projects and Tasks (project.project / project.task) Work items synced with external project tools. Orders B2C fulfillment orders (create, update, cancel, get) with item, hold, routing, and tracking subresources; typically written from a storefront or ERP and synced back with status and trackings. Projects and Tasks (project.project / project.task) is specific to Odoo and Orders to Shipwire — each maps to any object or custom field on the other side.
Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. Products Catalog SKUs including kits, virtual kits, and marketplace products; created and edited via API, commonly mastered in a PIM or ERP and pushed into Shipwire with dimensions and pricing. Contacts (res.partner) is specific to Odoo and Products to Shipwire — each maps to any object or custom field on the other side.
Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. Sales Orders (sale.order) is specific to Odoo and Stock to Shipwire — each maps to any object or custom field on the other side.
Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. Invoices (account.move) is specific to Odoo and Receivings to Shipwire — each maps to any object or custom field on the other side.

How changes propagate between Odoo and Shipwire

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.

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

Shipwire Odoo Sub-second propagation

DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.

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

Rate-limit considerations

  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
  • Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Odoo ⇄ Shipwire

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Odoo and Shipwire connectors work

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

Shipwire

Integration surface
REST API (v3)
Authentication
Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
Change detection
Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
Capabilities
read · write · webhooks
Rate limits
No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works

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

    Choose tables

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

Odoo and Shipwire 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 478 integrations available for Odoo and Shipwire.

Popular · 7 of 478
Coworkers laughing in front of a laptop in a casual office setting

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