FOR SELLERS
Price list requirements
Send your file as it is — no need to rework it. The platform reads the columns itself and shows you what it understood before anything is saved. Below is what it can read and where files most often trip it up.
File format
- CSV, XLSX or XLS. Other formats are not read yet.
- One product per row.
- A company header above the table, group separator rows and a footer are fine: the parser recognises and skips them.
- Columns may be named anything, in any language — no need to translate the headers.
- Numbers in any style: “8,10”, “8.10” and “1 234,56” are all read correctly.
What a row should contain
- Product name.
- Price — or a dash: an empty price means “price on request”, not an error.
- Stock, unit, weight and currency. Whatever is missing we will ask about or take from your settings.
- Description, category and HS code are optional: we will write the description and pick the category and code.
Volume tiers
- Several price columns — “1–9”, “from 100 pcs”, “≥1000” — are fine.
- One of them becomes the regular price, the rest become tiers.
- If the header does not say from what quantity a price applies, you will be asked.
Variants of one product
- Pack sizes and sizes go as separate rows with the same name.
- The platform will offer to merge them into one product with variants; accepting or leaving them apart is your call.
- The card shows the price of the cheapest variant.
Price, unit and VAT
- Once for the whole file you say: which currency the prices are in, what they are per — per piece, per kilogram or on request — and whether VAT is included.
- A price per kilogram needs a weight: without it there is nothing to convert from.
- If the file has a VAT rate column, it is picked up automatically.
Photos
- A column with a link to an image (http or https). There may be several such columns.
- The link must open without a password and from outside your network — internal company addresses will not work.
Weight and delivery
- A physical product needs a weight — without it delivery cannot be calculated.
- Delivery terms — EXW, FCA, FOB, CIF, DAP or DDP.
- Anything about delivery that is missing from the file is taken from your logistics settings.
What happens after the upload
- Mario maps the columns to product fields and shows you the mapping — you check and correct it.
- It flags the doubtful parts itself: an unrecognised delivery term, a link that does not look like a photo, a price per kilogram with no weight.
- How many products are visible on the storefront depends on your plan. The rest stay in your cabinet and come back as soon as the plan allows.
Common mistakes
- Merged cells in the headers — a column cannot be built from them.
- Two prices in one cell: “10/12” is read as a single number.
- Weight only in the product name and not in a column of its own.
- A photo link that only opens from inside your network.
Columns the platform recognises by itself
You do not have to name them this way — they are recognised by meaning, in any language.
NamePriceCurrencyStockUnitPack sizeDescriptionCategoryMinimum orderOrder stepManufacturerCountry of originBest beforePackagingBarcodeWeightConditionSKUHS codePhoto linkStorage temperatureVAT rateIncotermsCertificatesVolume tiers
Still unsure about your own file? Write to support straight from your cabinet and attach it — we will look through it.
Upload a price list