Two-way sync
Changes in Odoo or Shipwire instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
As orders are picked, shipped, or invoiced in Odoo, tracking and status flow back to Shipwire so buyers see accurate updates.
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–Shipwire connection.
Changes in Odoo or Shipwire instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Odoo or Shipwire data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Odoo or Shipwire record.
Track your Odoo ⇄ Shipwire sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Odoo and Shipwire.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Odoo and Shipwire: authenticate both systems, choose the objects to sync (such as Odoo's Inventory Transfers (stock.picking) and Employees (hr.employee)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Odoo and Shipwire records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Odoo and Shipwire connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Odoo–Shipwire integration in-house.
Yes — Stacksync ships production-grade connectors for both Odoo and Shipwire. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. On Shipwire: 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). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Shipwire side: Trackings, Rates, Orders, Products, plus custom fields where Shipwire exposes them. On the Odoo side: Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order). Stacksync auto-detects both schemas and converts types between the two systems.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 478 integrations available for Odoo and Shipwire.