Mapping WooCommerce meta_data onto Odoo fields
No real store is stock WooCommerce. The delivery date, the PO number, the gift message — all of it lives in meta_data, and none of it syncs by default.
Where the data actually lives
Checkout plugins, B2B extensions and custom themes almost all write into meta_data rather than adding first-class fields. A connector that only maps documented WooCommerce fields will silently drop the parts of the order your operations team cares most about.
Start from real records
Do not map from a specification. Read the meta_data keys present on actual orders in the store, because plugin authors rename keys between versions and the documentation is often behind.
Line-level versus header-level
A delivery date belongs on the order header. A per-item engraving message belongs on the line. Map them separately — flattening line data onto the header is where connectors produce orders that look right and pick wrong.
Set direction per row
Some mappings should only ever travel one way. A warehouse note written in Odoo should not overwrite the customer's checkout note. Direction belongs on the individual mapping, not on the integration as a whole.
See how SyncO fits your WooCommerce and Odoo workflow.
Connect a store, map your fields, and watch the first orders land in Odoo.
Get started free