Importing your CSV
Step-by-step for Products, Sales, Expenses, and marketplace exports.
Visual walkthroughs are coming soon. The text steps below are the fastest path.
What we support
- ebay-uk.csv
- ebay-de.csv
- ebay-fr.csv
- ebay-it.csv
- shopify-orders.csv
- etsy-sold-orders.csv
- vinted.csv
- depop.csv
- generic.csv
Getting your CSV from eBay
- Open eBay Seller Hub.
- Go to Orders -> Paid and shipped.
- Pick the date range you want to import.
- Click "Export" -> choose CSV format -> download.
- Upload that file to WardaOS's Import page. We auto-detect UK, Germany, France, and Italy regional formats.
eBay's monthly invoices export is different from the orders export. Use the orders one - that's what has your sales data.
Getting your CSV from Shopify
- Open your Shopify admin.
- Go to Orders.
- Apply the date range filter you want.
- Click "Export" -> "CSV for Excel, Numbers, or other spreadsheet programs" -> "Export orders".
- Upload the downloaded file to WardaOS.
Getting your CSV from Etsy
- Open Shop Manager.
- Go to Settings -> Options -> Download Data.
- Pick the year you want under "Orders".
- Click "Download CSV".
- Upload that file to WardaOS.
Getting your CSV from Vinted
Vinted doesn't currently offer a built-in CSV export. For now you have two options:
- Manually log sales as they happen via WardaOS's "Log sale" button.
- If you've kept a spreadsheet of your Vinted sales, upload it via the Generic template - WardaOS will walk you through column mapping.
Getting your CSV from Depop
Same situation as Vinted - no native CSV export. Use manual entry or the Generic template.
Generic / messy spreadsheets
Before import, choose the right mode. Products CSV is for current stock, Sales CSV is for completed transactions, and Expenses CSV is for business costs. Do not mix unsold inventory rows with sales rows in one file.
I have a messy sales/order spreadsheet that I want to import into WardaOS. Please clean and convert my data into this exact CSV format: sale_date,store,product_name,sku,quantity,sale_price,purchase_cost,shipping_charged,platform_fee,shipping_cost,other_costs,buyer_country,notes Rules: - Keep one row per completed sale transaction. - Use YYYY-MM-DD for sale_date. - quantity means the number sold in that transaction. - Use numbers only for money fields. Do not include currency symbols. - If a value is missing, use 0.00 for cost fields and leave text fields blank. - Match repeated products using sku if available. - If sku is missing, create a clean stable sku from the product name. - Do not invent sales. - Do not include unsold inventory rows here. Unsold inventory belongs in the Products CSV. - Return only the final CSV content, no explanation.
Common issues
- Encoding: export as UTF-8 CSV where possible.
- Dates: use day/month/year or ISO dates consistently.
- Decimals: keep prices as 12.34, not EUR 12,34 unless your export uses regional formatting throughout.
- Quantity: in Sales mode it means sold quantity; in Products mode stock must use current_stock or another explicit stock column.
- Fees: put platform fee, payment fee, shipping charged, and shipping actual in separate columns if you can.
What gets imported vs not
| Imported | Not imported |
|---|---|
| Products, SKUs, sale dates, quantities | Live platform account connections |
| Sale prices, fees, shipping, profit fields | Listing creation or channel sync |
| Stores, source platform, external order IDs | Messages, disputes, or platform inbox data |
| Duplicate checks using order IDs and row data | Tax filing itself |