Built by people who run both WooCommerce and Odoo.

The problem we kept hitting

Every store that outgrows spreadsheets ends up running two systems: WooCommerce for selling and Odoo for everything after the sale. Neither was built with the other in mind.

What follows is predictable. Someone re-keys orders each morning. Stock is right in one system and wrong in the other. At month end, finance reconciles by hand and finds orders nobody knew had failed.

What we decided to build

A connector that treats sync as an operational system, not a nightly file transfer. Every sync is a job with a status, an error message and a retry — because the question that matters is not whether sync usually works, it is what happened to that one order.

• —Real-time webhooks, not polling on a timer.
• —Direction control per resource, so nothing moves that you did not ask to move.
• —Field and meta_data mapping, because no real store is stock WooCommerce.
• —Visible job history, so a failure is findable rather than silent.

What we will not do

We will not block a paying store's sync because it crossed a usage line mid-month — paid plans meter overage instead of stopping.

We will not hide failures behind a green tick. If an order did not reach Odoo, the Jobs screen says so, with the error Odoo returned.