Master hub

• Connections to each client (bot user and API key)
• Install product catalogue rules in one click
• Push Now, dry run, or scheduled cron
• Templates, variants and images - not prices

Client site

• Same module, deployment mode Client site
• Local product creates a sync proposal
• Client Approvers choose fields and send to HQ
• Prices never go upstream

• Transport: POST /json/2/<model>/<method> with bearer API key only
• No XML-RPC / JSON-RPC - External JSON-2 API only
• Resumable, idempotent runs with per-record audit
• Units matched by xml id, then English name
• Works on Odoo.sh and on-premise

From master to clients

• Product categories
• Attributes and attribute values
• Product templates and images
• Attribute lines and variants

Kept on each client

• List price and cost
• Pricelists
• Supplier info
• Local commercial settings

Before Push Now, every client database needs the following. Missing items are a common cause of remote HTTP 422 errors (for example an empty Unit / uom_id).

• App Product (and the same optional apps as master)
• This module installed with Deployment = Client site
• Language English (en_US) activated
• Standard Units of Measure kept (matched by xml id)
• Bot user and API key with product create/write rights
• Optional: HQ connection and group O2O / Client Approver for upstream proposals

Catalogue rules identify products by Internal Reference (default_code and/or barcode when set. If both are empty, a unique product name is used. Prefer Internal Reference on the master whenever possible.

• No inter-company document flow between databases
• No multi-company replacement inside one database
• No cross-instance consolidated reporting

Scope is product master data between Odoo 19 databases.

• Odoo 19.0 on master and each client
• Python package requests on the connector host
• Bot users with API keys on both sides