Nafy · 28 April 2026 · 7 min read

I built a tool because Sellbrite was EUR 49 and I just wanted a spreadsheet that did math

The story behind WardaOS, written 7 days into the build.

My brother sells on eBay. His Excel was a disaster.

Not "cute little spreadsheet with a few rough edges" disaster.

I mean the kind of spreadsheet where one tab is called real final, another tab is called use this one, and a third tab somehow contains the truth but only if you remember that shipping is in column J unless the item came from Vinted, in which case shipping is in a note field because "I'll fix it later".

He sells normal reseller stuff. Some eBay, some other marketplaces, some in-person bits, the occasional weird product that sells faster than expected. Nothing that should require enterprise software. But the admin had become a second job.

The big problem was not that Excel could not store the data. Excel can store anything. That is both its superpower and the reason it quietly ruins your evening.

The problem was that it did not answer the only question that matters:

Did this item actually make money?

Not revenue. Not "it sold for EUR 35 so nice one". Actual profit after cost of goods, platform fees, shipping, packaging, random expenses, and all the little cuts that make marketplace selling feel like being slowly nibbled by percentages.

He had the data. It was just spread across exports, notes, old tabs, and memory.

The Sellbrite incident

At one point he was about to pay for Sellbrite.

Sellbrite looks solid. This is not a hit piece. If you run a serious multi-channel operation and need live inventory sync, listing tools, and proper channel management, Sellbrite can make sense.

But he is not a warehouse. He is one person selling a few hundred SKUs. He did not need a command center. He needed a spreadsheet that stopped lying.

The plan he was looking at was about EUR 49/month.

EUR 49/month is not insane for a business tool. But it is very insane when your actual need is:

  • import this CSV
  • match it to my products
  • tell me what sold
  • decrement stock
  • show me profit
  • keep receipts somewhere less chaotic than my camera roll
  • give me something my accountant won't hate

That should not cost more than your phone bill.

So I went looking for the obvious product. Surely someone had built it.

They had not. Or at least not in the shape I wanted.

There are spreadsheets. There are accounting tools. There are inventory platforms. There are massive systems for people with warehouses, barcode scanners, purchase orders, and a deep emotional relationship with SKU architecture.

But the middle was weirdly empty.

Where is the tool for the solo seller who already has CSV exports, wants real profit, and does not want to wire their whole business into five APIs before breakfast?

That became WardaOS.

The obvious thing nobody had built

The idea was boring in the best way:

Take the seller spreadsheet and automate the bits that create errors.

CSV import. Auto-detect common platform exports. Preview the rows before they go in. Skip duplicates. Track products and sales. Calculate profit per item. Store expenses and receipts. Export clean data when tax season arrives.

That is it.

No "AI-powered commerce operating system". No "next-generation omnichannel growth engine". No dashboard pretending to be a spaceship.

Just clean numbers, fast.

The more I thought about it, the more convinced I became that CSV is not a compromise. For this market, CSV is the wedge.

Every marketplace exports something. eBay exports CSV. Shopify exports CSV. Etsy exports CSV. Sellers already have spreadsheets. Even if a platform does not have a nice export, the seller can make a generic sheet.

APIs sound fancy until they become the reason the product is expensive, brittle, and only supports the platforms with good developer programs.

CSV is boring. Boring is good. Boring works.

Seven days of building

I gave myself a week to make the first real version.

Day one was the foundation: Next.js, Supabase, auth, database schema, legal pages, the basic shell. The not-glamorous stuff that decides whether the rest of the product can stand up without wobbling.

Then products and stores. A seller needs somewhere to put inventory, categories, stock levels, prices, and the platform context. Nothing clever. Just the bones.

Then CSV import, which was the real heart of it. I wanted the import flow to feel less like uploading a tax document and more like dropping a messy file on the table and saying, "Here, make sense of this." Detect the platform. Show the preview. Highlight bad rows. Skip duplicates. Let the seller fix the mess before it becomes database mess.

Then sales and expenses. Sales need fees, shipping, quantities, source platform, and calculated profit. Expenses need receipts, recurring costs, product allocation, and enough structure that "packaging from last Thursday" does not disappear into a shoebox.

Then dashboard and reports. Revenue is nice. Profit is better. Low stock matters. Top sellers matter. A decent export matters a lot when the accountant asks for numbers and you would prefer not to send them a cursed spreadsheet from 2023.

Then billing and polish. Free, Solo, Pro. Founder Lifetime for the first 100 sellers. Trial emails. Plan limits. The slightly boring machinery that makes the product real.

And now this marketing layer, which is basically me admitting that if you build a useful thing in a dark room and never explain it, that is not charming. That is just bad distribution.

No API integrations is a feature, not a bug

This is the bit that will annoy some people.

WardaOS does not connect to your eBay account. It does not connect to Shopify. It does not ask for marketplace permissions. It does not promise magical live sync.

That is deliberate.

APIs are great when you need real-time operations. If you sell across six channels and stock must update everywhere instantly, use a proper multi-channel tool. Seriously. WardaOS is not trying to replace that.

But most solo sellers are not there.

They are doing batch admin. They export orders. They update stock. They want to understand margin. They want to know which products are secretly rubbish. They want clean records. They want software that does not punish them for being small.

CSV means WardaOS can support eBay, Shopify, Etsy, Vinted, Depop, Facebook Marketplace, in-person sales, and your weird custom spreadsheet without waiting for platform APIs or charging you for integration complexity you did not ask for.

It also means your data is yours. You can export it. You can leave. No hostage situation dressed up as "ecosystem".

Founder Lifetime

The first 100 customers can buy lifetime access.

EUR 69 once for Solo. EUR 129 once for Pro.

Why? Because early users are not just customers. They are the people who tell you where the product is wrong. They find the import edge cases. They send the cursed CSV that breaks your assumptions. They say "this button should be there" and, annoyingly, they are right.

I want those people close. I want the first 100 sellers to feel like they got in early because they did.

After 100 spots, it is gone. Not "gone until the next launch campaign". Gone.

Try it free

If your spreadsheet is working, keep it. I mean that. You do not need software for the sake of software.

But if you have 50+ products, 50+ sales a month, or a file that only makes sense after three coffees and a small act of faith, WardaOS is probably worth trying.

Start free. No card. Drop in a CSV. See if the numbers tell you something your spreadsheet has been hiding.

And if they do, welcome. The boring bits are now somebody else's problem.