Odoo + WooCommerce documentation
When something needs attention
How the Odoo + WooCommerce connector reports problems, what common review reasons mean, and what to include when you ask for help.
Last updated
Pre-release documentation.
How problems are reported
The connector does not guess. When it cannot safely finish something, it puts the record in a review list with a plain reason, and carries on with everything else. Temporary problems, such as a system being briefly unreachable, are retried automatically with increasing waits.
If a connection drops part-way through, the connector checks what actually happened before trying again. It never creates a second order, invoice or payment just to find out.
Alerts are raised once per problem and cleared when it is resolved. They currently appear inside the connector’s own pages.
Common review reasons
| What you see | What it means | What to do |
|---|---|---|
| Tax total does not match | The order was written to Odoo, but a tax amount came out differently from WooCommerce. | Check that each WooCommerce tax rate is matched to the right Odoo tax, then retry. |
| Unsupported order line | The order has a shipping method or fee with no matching Odoo product. | Choose a service product for that method or fee, then retry. |
| Tax not matched | A WooCommerce tax rate has no matching Odoo tax. | Add the matching tax in the financial setup. |
| Order could belong to more than one shop | An Odoo order matches several shops, or none. | Check the company and sales team on the order. |
| Refund exceeds invoice balance | The refund is larger than what remains on the invoice. | Check the invoice and the refund in both systems. |
| Payment evidence missing | The order has not reached a status you accept as proof of payment. | No action needed if payment is still pending. |
| Configuration changed | An order was edited after confirmation, or a setting changed after a plan was approved. | Review the difference, or rebuild and approve the plan. |
Asking for help
When you contact us, include:
- the shop address and roughly when the problem happened;
- the reason shown in the review list, and the order or product number;
- what you expected to happen.
Never send passwords, API keys, pairing codes or full customer records. We will never ask for them by email or through the form.
Ask the product team — and please never include passwords, API keys or customer records.