CONNET
CONNET sits between your WooCommerce shops and Odoo. A paid order becomes a sale, a label and a tracking message, and closes when the invoice is posted.
Labels, pickups and tracking go through CONNET. CONNET uses Odoo's external API, so the Odoo database needs the Custom plan: it pays off when you drop warehouse users.
Do the mathsEach 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.
Every action is a command. An MCP server exposes the same operations to the assistant you already use.
$ 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) $
What ships today?
Three orders: #10482, #10481 and #2093. Labels printed, pickup at 16:00.
Orders in, tracking back out.
Partners, sales, invoices, website orders.
Rates, labels, pickups, tracking.
Straight to the thermal printer.
The same operations for your assistant.