What WardaOS is
A CSV-first seller dashboard for small and solo sellers in Europe. No marketplace API is required: import sales, products, and expenses from files you already have.
CSV-first seller workflow
How WardaOS turns seller spreadsheets into clean tracking
Built for small European sellers who need profit, stock, expenses, and reports without connecting marketplace accounts.
1. Prepare CSV
Export marketplace sales or clean your own spreadsheet.
2. Import or log
Preview rows, match products, and log repeat sales quickly.
3. Review numbers
Dashboard and reports update from the same sales and expenses.
Basic workflow
Import Products CSV for current stock, Sales CSV for completed transactions, and Expenses CSV for business costs. Going forward, log new sales in WardaOS so stock updates automatically.
CSV import explained
Products, Sales, and Expenses have separate templates. Unsold inventory belongs in Products CSV. Sold transactions belong in Sales CSV. Business costs belong in Expenses CSV.
Product matching
WardaOS matches SKU first. If SKU is missing, it falls back to a stable SKU made from the product name, so repeated products stay together. Avoid duplicate product names when possible.
Inventory behavior
Manual sales reduce stock automatically. Historical Sales CSV imports do not reduce stock by default, because marketplace exports usually describe transactions already reflected in current inventory.
Expenses and profit
Profit uses sale price minus purchase cost, platform fee, shipping cost, and other costs. Dashboard net profit also subtracts expenses such as packaging, postage, subscriptions, or recurring costs.
Using AI to clean CSVs
You can use the prompt below with ChatGPT, Claude, Gemini, or another LLM. Always verify the cleaned file before importing.
Cleanup prompt
Attach your messy CSV and the WardaOS sample file, then paste this prompt.
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.
Simple example
Quantity 5
Start with five units of one product.
Sell 1 now
Inventory becomes 4.
Sell another later
Inventory becomes 3.
Dashboard updates
Profit and stock reflect both sales.