Master data is the foundation of any implementation. If the catalog goes in wrong, everything downstream suffers: stock, purchasing, marketplace listings, labels, invoices and reporting.
Key idea: a profitable integration isn't measured just by connecting an API. It's measured by how much manual work it removes, how many errors it prevents, and how much traceability it leaves inside the operational flow.
Product and variant
Every product needs a clear SKU and a consistent variant logic.
Keep trade name, internal reference, EAN or GTIN, brand, category and attributes as separate fields.
Logistics data
Weight, dimensions, packaging type and units per package look like secondary fields, until you actually need to print labels.
If they're missing, the warehouse falls back to manual work.
Initial stock and locations
A single total quantity isn't enough. You need to know where the stock actually sits, and how much of it is available, reserved or on order.
In a multichannel setup, this is critical to avoid selling more than you actually have.
Minimum template
- SKU
- Name
- Variant
- EAN or GTIN
- Cost
- RRP
- Tax
- Weight
- Dimensions
- Supplier
- Lead time
- Initial stock
Useful links within FlexigoTech
Frequently asked questions
Can I import products without an EAN?
Yes, but some marketplaces or logistics processes may require external identifiers.
What about duplicate SKUs?
They need to be resolved before migrating, since duplicates break mappings and syncs.
Should I import historical data?
It depends. In most cases you import the master data and current balances, and keep the historical records available for reference elsewhere.
Who should review the template?
Warehouse, sales, admin and the technical team, because each area catches different kinds of errors.
Want us to review your case?
We'll look at your channels, stock, carriers and Odoo version to propose the cleanest path forward.