How a product is matched
The order the connector tries in order to know that this Salla product is that Odoo item.
No match, no order
An order containing even one unmapped product will not reach Odoo at all, and no sales order is created for it. It shows up on the Product Error screen. This is the single most common problem in a merchant's first week.
The order of attempts
The connector tries, in order:
- The custom mapping table — if you mapped a Salla SKU to an Odoo barcode by hand, that wins over everything.
- SKU — the Salla item code against the Odoo barcode or internal reference.
- Barcode.
- Internal reference.
- Single-variant matching — if you enabled the option and not every variant matched.
Variants are the hard part
A simple product has one SKU and is easy to map. A product with options (colour and size, say) has a SKU per combination in Salla and a variant per combination in Odoo. Every combination must match, or an order containing just the unmatched one fails.
Match only one variant
An Inventory-tab option that lets the connector accept a match on a single variant when not all of them match. It clears a lot of problems quickly, but it can link the wrong combination if your codes are inconsistent. Turn it on carefully and check the result.
The practical rule
Make the Salla SKU exactly equal to the Odoo barcode for every combination. The automatic mapping then handles nearly everything with no intervention. The "Updating barcodes in Salla" page helps you enforce this across a whole catalogue.
Open Products Mapping
The link opens the screen directly in the Integration Dashboard.