Sync Odoo ERP with WooCommerce Store

Odoo WooCommerce Bridge guides the design of a synchronization bridge between a WooCommerce storefront and Odoo for back-office inventory and fulfillment. It covers product catalogs, order imports, customer records and stock updates. Mention @odoo-woocommerce-bridge with sync requirements to obtain field mappings and Python integration scripts using the WooCommerce REST API.

The mappings connect products to product.template and product.product, orders to sale.order and sale.order.line, and customers to res.partner. SKU links to product.product.default_code. Stock quantities relate to stock.quant conceptually; changes must follow authorized inventory workflows rather than direct state writes.

Use it when pulling store orders into Odoo or publishing warehouse stock to WooCommerce. Define the warehouse and company, variant/SKU uniqueness, available-to-sell policy and mappings for tax, currency, shipping, discounts and refunds before enabling writes. WooCommerce payment completion does not prove that Odoo delivery is complete.

The examples require environment-specific validation and expert review. Stop for clarification when inputs, permissions, safety boundaries or success criteria are missing. They are not complete production integrations: the order-import function deliberately stops until atomic idempotency and reviewed mappings are implemented.

Provide sync direction, object mappings, account identity and inventory policy. Outputs include a field mapping table and Python examples using WooCommerce's client and Odoo XML-RPC. The explicit import guard is:

def sync_orders():
    raise NotImplementedError("Add atomic shop+order-ID idempotency and reviewed mappings before enabling writes")

Both API examples need authentication, pagination, HTTP error handling, timeout handling and dry-run review. Never silently choose the first ambiguous customer or SKU. A missing or ambiguous SKU should quarantine the whole order rather than drop a line.

Use a server-side unique external shop-plus-order ID and reconcile uncertain timeouts. A display order number or client_order_ref alone does not establish atomic idempotency. Persist the mapping with the Odoo order; do not change customer-facing payment or fulfillment status merely to mark an import.

The Python examples use the WooCommerce REST API and xmlrpc.client for Odoo model calls. The stock example reads default_code and qty_available and updates WooCommerce stock_quantity with manage_stock enabled. Adapt it to a confirmed warehouse/reservation policy and fractional units rather than blindly truncating quantities.

Schedule inventory synchronization, with 15-30 minutes given as an example, to reduce rate-limit pressure. Filter eligible order states such as processing or completed and avoid draft or cancelled orders. Log redacted operation IDs, statuses and errors while excluding customer addresses, credentials and full request/response bodies.