Vinted and other channels without an API: importing orders from a CSV file and the customer API channel

What it is for

Not every platform provides a public API to sellers. Regular Vinted sellers do not have one, so Zaksio cannot fetch orders from there or send stock levels by itself. The Vinted connector is therefore file-based: instead of synchronisation, it has ready-made CSV templates for orders and listings. You can upload orders (or a list of listings) from a CSV file exported from the platform panel or prepared in a spreadsheet. Orders from the file go through the same flow as marketplace orders: reservations, picking, shipment.

Where to find it in the app

File handling is available for channels of the "Manual" and "Vinted" types (Sales and logistics, "Sales channels"). Once in the channel, open the "Import" tab: choose what you are importing (orders or listings), click "Download CSV template", select the file and review the preview before saving. For the "Vinted" channel the order and listing templates are ready; for "Manual" the columns described below apply. Import requires write permission for channels, and for orders also write permission for orders.

Step by step

1. Export orders from the platform panel to CSV or prepare a spreadsheet with the columns: order number, SKU (or EAN), quantity, gross price. Vinted has no export, so after each sale add a row from the sale notification (a number such as "VINTED-" plus the transaction number). The buyer usually does not share an address because Vinted Go delivers to a pickup point, so you can leave the address empty.
2. Optionally add: date, customer, email, phone, street, city, postcode, country, payment (cash on delivery, bank transfer), paid, delivery, delivery cost, notes.
3. Upload the file as "orders". By default a preview is run without saving: the number of orders and lines, duplicates, a sample of the first 10 orders and a list of row errors (up to 100).
4. Fix the errors in the file and upload it again. When the preview is clean, run the actual import.
5. After the import you will see how many orders were imported, how many were duplicates and how many need your decision (e.g. an unrecognised item).

File format

• Encoding: UTF-8 or Windows-1250 (a typical Excel export). Separator: semicolon, comma or tab, detected automatically.
• The first row contains headers. Polish and English names are recognised, regardless of letter case and Polish characters, e.g. "numer zamówienia" or "order id", "ilość" or "quantity", "cena brutto" or "price".
• Required: order number, quantity, and SKU, EAN or listing identifier.
• Multiple rows with the same order number create one order with multiple lines. We take the customer and delivery data from the order's first row.
• Prices in the form 12,34 or 12.34. VAT rates: 23, 8, 5, 0, zw, np. Dates e.g. 31.12.2026 or in ISO format.
• Limits: file up to 2 MB and up to 5000 rows.

Errors and idempotency

An invalid row (missing order number, wrong quantity or price) is skipped and described in the error list with its row number, and the rest of the file is imported normally. The order key is its number from the file within the channel, so uploading the same file again does not create duplicates: existing orders are counted as duplicates. The same applies to the listing list (columns: SKU, EAN or listing identifier, name, stock level, price), which goes to the "Listings" tab to be mapped.

The "Customer API" channel

A channel of the "API" type is an integration point for your own shop or system. Zaksio does not fetch anything from your system, so there are no keys to enter and no "Check connection" button. You create API keys under Settings, "API and integrations".