Supplier bulk upload
How to download your department's template in Excel, fill it in with your products and their variants, review it and send it for validation.
How do I send many products at once?
In Suppliers → Send products, the “Several products” section takes a file of up to 5,000 rows and 8 MB, in Excel (.xlsx) or as a UTF-8 CSV. Nothing you send goes into the catalog until the organization that invited you approves it. For a single product, use “One product”, the step-by-step form (guide “Supplier portal”).
Sending products takes the Editor role. In the menu it's shown to suppliers, who are limited to their brands.
How do I download my department's template?
In “Template by department”, choose the Department of your products and, in “Variants change by”, the attribute their variants change by (for example, shade or size), or “No variants”. Then click “Download Excel” or “Download CSV”.
A department is a category in the organization's tree with its own attribute family: the template has the columns the product form would ask you for that family. If the organization has no departments, “Download template” appears instead: a simple template with sku, name, brand and category.
How do I fill in the Excel template?
The Excel file has three sheets: “Products”, with one row per product (don't change the headers); “Instructions”, with each column's name in your language, its type, its unit and when it's required; and “Lists”, where the drop-downs come from. If a cell has several options, separate them with |. The CSV has only the headers.
- sku, name and brand: the SKU, the name and the brand. If you're limited to your brands, the list has only those.
- tipo: Individual (a product without variants), Padre (the parent that groups its variants, with its own SKU) or Variante (each shade or size, with its parent's SKU in parent_sku). These three values are written exactly like that, in any language.
- categoria_sitio: the subcategory within the department, from the list. If you leave it empty, the product stays in the department and the review warns you.
- categoria_sap: the code of the category in the organization's system (the code alone is enough). It only appears if the organization set up that root in its product form.
- Then, the attributes the family asks for and, if the organization asks for them, the texts for the product record. Columns whose note says “Goes on each variant, not on the parent” are filled in on the variant rows.
If you chose an axis, each Padre's SKU has to follow the SKU template the organization set up: the “Instructions” sheet shows it.
What does “Review” do and what do Go in, With a warning and With errors mean?
Choose the file and click “Review”. It doesn't send anything: it checks each product in the file with the same rules as the one-product form —an Individual, or a Padre with its variants— and says how many rows go in, how many go in with a warning and how many have errors, each problem with its row and column.
An error leaves the whole product out: if it's a Padre, together with all its variants, because a parent and its variants are never split. A warning doesn't stop anything; the row goes in, but it's worth checking.
Common errors: a tipo that isn't Individual, Padre or Variante; a variant without parent_sku, or whose parent isn't in the file nor among your products; a subcategory that isn't in the department; a SKU repeated in another row; a variant that doesn't match its parent.
Columns that aren't part of the template are ignored, and the review tells you which ones. If you change the file, review it again before sending.
How do I fix the rows with errors?
“Download rows with errors” downloads those rows in the same format you uploaded, Excel or CSV, with two columns at the start: the original row and the error, in your language. If a parent or one of its variants has an error, all of their rows come out; the ones without an error of their own say which row has it.
Fix them and upload that same file again: the two columns at the start are ignored when it's reviewed.
Can I send only the valid rows, or a pilot first?
Yes. If there are rows with errors, the button changes to “Send the N valid rows”: the products without errors go in, and you fix the rest and send it in another submission.
With “Send a pilot first” and “Pilot rows” you send only the first valid products, each parent with all its variants, until those rows are reached, so the organization can review a sample before the rest. The button says how many rows it actually carries.
Once sent, the file shows “Awaiting review” in My uploads.
What happens to my file after I send it?
The organization reviews it in Suppliers → Validation: it approves it or returns it with a reason, which you read in My uploads. On approval, the products go into their subcategory and category, inherit the department's family, each parent gets its axis and new axis options are created, like a new shade. A file with more than 500 rows is approved in the background.
How a submission is reviewed, how it's withdrawn and its journey are explained in the guide “Supplier portal”.