🔗 Import a product file from anywhere, not just Erpilo's own export
Upload a supplier price list or an export from another system and tell Erpilo what each column means. Name the matching once and it is offered again next time.
Importing products used to mean one thing: a file Erpilo had exported itself. Anything else - a supplier's price list, a spreadsheet you keep by hand, an export from the system you're moving off - was rejected with "No recognised columns were found", and the only way through was renaming twenty headings by hand.
Now you upload the file as it is, and Erpilo asks you what its columns mean.
One row per column in your file
The matching screen lists the columns your file actually has, side by side with the first few real values from each one, so you can see what you're looking at before you decide. Next to each is the Erpilo field it should feed.
That preview is the important part. A column headed Price that turns out to hold 12,90 EUR is obvious at a glance, and so is one you've matched to the wrong field.
Most of it is filled in for you
Obvious headings are matched before you arrive: Title and Product name to your product's name, Cost to purchase price, Qty to stock, EAN and UPC to barcode - and the same list in Estonian, since a supplier file is far more likely to say Nimetus, Ostuhind and Ribakood. A heading that names a language, like Name EN or Kirjeldus (et), goes to that language.
They are guesses, and the values beside them are there so you can check.
Two things the screen won't guess at:
- A column with nothing in it. An empty cell clears a field, so a pre-matched empty
Costcolumn would quietly offer to wipe every purchase price. You can still match it by hand if clearing is what you want. - Columns it doesn't recognise. Anything left unmatched is highlighted and tagged ignored, so a heading you meant to match and missed stands out instead of blending in with the ones you skipped on purpose.
Remember a matching and reuse it
Give a matching a name - Supplier price list, say - and it's offered the next time you import from the same source. When the new file has every heading the saved one needs, it's applied for you as soon as the screen opens, with a note saying so and a button to undo it.
It's remembered by the column headings, not by their order. If your supplier re-exports with the columns shuffled around, the saved matching still works.
Your own export is unaffected
A file Erpilo exported goes straight to the validation report as before. The matching screen only appears when a heading isn't one Erpilo knows, when two headings claim the same field, or when there's no id or sku column to match rows on. A round trip still costs one click.
And after that, everything is the import you already know: the same report, the same per-row errors with line numbers, the same downloadable list of failed rows, and nothing written until you press Apply import. If the matching turns out to be wrong, Change the column matching on the report takes you back until you apply.
Worth knowing
Only id or sku is genuinely required. Without one, no row can be matched to a product at all.
A missing name column is fine if you're only updating. A product can't be created without a name, but a row that matches something you already have is an update and needs nothing of the sort. Rows that would have created a nameless product are reported individually, with their line numbers, alongside every other row error.
Commas, semicolons and tabs are all handled, as are files saved by Excel on Windows - õäöü survive the trip. Foreign files are far likelier to be comma-separated than your own exports, so this matters more here than it used to.
Excel files aren't supported: save as CSV first.