Several shops, one queue.
Each WooCommerce store keeps its own orders and rules. Every write names its shop, so an order number on one can never touch another.
- Multi-shop configuration
- One status page
- Audit trail on every write
CONNET sits between your WooCommerce shops and Odoo. A paid order becomes an ERP sale, a carrier label and a tracking message, and closes when the invoice is posted.
What it does
Six jobs CONNET does so nobody copies an order by hand.
Each WooCommerce store keeps its own orders and rules. Every write names its shop, so an order number on one can never touch another.
A shop sells cartons; Odoo counts pieces. Per-shop rules rewrite SKU, quantity and price before the order enters the ERP.
Partita IVA and codice fiscale checked by their check digit before a customer is matched to an Odoo partner. SDI code and PEC captured for e-invoicing.
Rates, ZPL labels through CUPS, pickups booked and tracking sent to the shop order and the buyer.
CONNET polls Odoo. When the invoice posts, the shop order completes on its own. Tracking refreshes until delivery.
06 · Headless
Every action is a command. An MCP server exposes the same operations to the AI assistant you already use. Web, CLI and MCP run the same code.
What ships today?
Three orders are ready: #10482 and #10481 from prodottipulizia.eu, #2093 from global-clean.it. Labels printed, pickup booked for 16:00.
$ connet preflight 10482 customer P.IVA check digit ok → Odoo partner matched lines 3 mapped · 1 rule (carton → pieces ×12) $ connet fulfill 10482 label FedEx 7900 0000 4821 · printed vretti-420b pickup booked 16:00 · invoice draft created $ connet invoice-poll #10482 completed (invoice posted) $
Integrations
Shops, ERP, carrier, printer and assistant, each talking to one place. No middleware of your own.
We set the first shop, printer and rules up with you.