Price lists and exports
We find the separator ourselves, handle the encoding and put a broken row back together instead of shifting every value into the wrong column.
Upload the file you got from your supplier in CSV, XML or Excel. Pobo pulls the products out of it, looks up what the file is missing and fills in parameters and descriptions.
From the file your supplier sent to product data you can use, without retyping a single row.
CSV, XML or Excel. We recognise the format by its content, so a feed saved as .txt works too.
Pobo suggests which column holds the name, the price or the EAN. You only check it and fix what you want.
Brand, category and parameters get searched across several AI models and compared against each other.
In the same format you uploaded, or straight into your product pages in Pobo.
Supplier feeds arrive in whatever shape the supplier likes. Pobo reads all three common formats and treats every row of the file as one product.
We find the separator ourselves, handle the encoding and put a broken row back together instead of shifting every value into the wrong column.
Heureka structure or a supplier's own. We locate the products in the tree without you describing it to us.
XLSX, XLS and ODS. Prices stay numbers, delivery dates stay dates, and a header on the second row is recognised.
Anything that does not match a known field becomes a product parameter named after its own heading. Supplier files are built exactly like that: a handful of commercial fields and a long tail of Colour, Material and Size.
The whole process runs in the Pobo administration and the batch waits for your approval before anything is created.
Drag in what you got from the supplier. Nothing needs to be renamed or converted first, and you do not have to know which format it is.
Before anything is created, Pobo shows you what it read: how many rows the file has, how many products that really means and which columns it recognised.
Every column gets a proposal: this one is the name, this one the price without VAT, this one the EAN. Change any of them with one click.
A column Pobo does not recognise is not a problem. It becomes a product parameter named after its own heading, which is exactly how supplier files look: a few known fields and a long tail of Colour, Material and Size.
First the whole file is checked and only then are you asked. You see how many rows will go through, which ones have a problem and what the batch will cost.
Fixing something at this point is free. That is the entire reason the approval step exists.
You can see how far the batch has got, how fast it is going and when it should finish. Nothing hides behind a spinner.
Every row of the file keeps its place in the batch. A row that cannot be used says why, so a file of five hundred products never quietly turns into four hundred and eighty.
Download the filled file in the shape you uploaded it, or let the products stay in Pobo and go straight to writing descriptions.
Values that were looked up are marked as such, so you always know what came from the supplier and what Pobo found.
Real supplier files are messy in predictable ways. These are the ones that would otherwise cost you an afternoon in a spreadsheet.
A row with no name or a duplicate code is written down with its state, never dropped. The count in the batch always matches the file.
The next file from the same supplier maps itself. Feeds are stable per supplier, so guessing again would only add noise.
What several models agree on is treated as reliable. What only one of them claims stays marked, so an invented parameter does not end up in your catalogue.
A missing protocol gets fixed, duplicates in one row are merged and a value that is not an address at all is thrown away instead of saved as a broken photo.
A file with Parameter name 1 and Parameter value 1 is read as pairs, not as two useless columns.
The batch validates first and stops. Until you approve it, nothing is created and nothing is charged.
CSV, XML or Excel. We recognise the format by its content, so a feed with a wrong or missing extension works as well. The file does not have to have a prescribed structure, that is what the mapping step is for.
They become product parameters named after their own heading. Nothing from the file is lost, which matters for supplier feeds where most of the value sits in columns like Colour, Material or Waterproofing.
It still goes through. Larger wholesalers synchronise prices from their own warehouse, so a price list without prices is a normal state. A product we do not know the price of is simply never made visible on its own.
Several models search independently and the results are compared. Agreement across sources counts as confidence, a single source stays marked as unverified. We would rather leave a field empty than fill it with something invented.
Only if you want. Products are created in Pobo and you decide what happens next: take the data as a file, or publish the descriptions to your e-shop the same way you do today.
In thirty minutes Lenka goes through your catalogue with you and shows you what the descriptions would look like. If you would rather look around on your own, you can start right away.
