Margins you can trust
True profit per SKU after fees, returns and landed cost, built on each unit's actual cost. It feeds your monthly close.
SellerERP follows each unit from purchase to payout, so your margins, stock and claims finally add up.
Most tools count totals. SellerERP gives each unit an identity, so every number walks back to a real purchase.
Illustrative unit ITEM-3a101a3ba0-0005. Every stop is a row in the ledger, with its source and its cost.
True profit per SKU after fees, returns and landed cost, built on each unit's actual cost. It feeds your monthly close.
Removals, vendor receipts, cases and reimbursements are chained per unit, so unclaimed money has a name and a number.
Assigned at purchase, then followed through every receipt, transfer and return.
FIFO per fulfillment center or weighted average. Cost travels with the unit.
Unlogged shipments, wrong MSKUs, over-receipts and vanished units show up as exceptions you can act on, never averaged away.
Reorders from sell-through, lead times and inbound delays. Fewer stockouts, less cash stuck on shelves.
For sellers who want full control of their margins and supplier prices, SellerERP can also run as a private install on infrastructure you choose.
Kubernetes on your own hardware or a cloud account you choose.
The API client and credentials are registered to you. No aggregator in between.
Raw reports in your PostgreSQL, insights in your DuckDB store.
The person who built it sets it up with you and adapts it to your files.
Close to real time, paced to Amazon's rate limits.
The numbers you need are buried across Seller Central.
Customer returns quietly eat into your margin.
Units go missing and nobody can say where.
Reimbursements you were owed slip past the deadline.
Bestsellers run out right before the busy week.
Cash sits in slow stock instead of working.
Built for Amazon FBA brands with large SKU ranges, fast-moving goods, complex landed costs and tight cash cycles.
If you choose to host it yourself, this is how we set it up together. History loads in the background while live updates already flow in.
A developer registration and Selling Partner API client are created under your account.
It runs in your cluster and paces every call to Amazon's rate limits.
Past reports load in the background, so dashboards start full, not empty.
Notifications start arriving while the backfill is still running.
Everything Amazon sends is kept as received in your PostgreSQL.
ETL workers match, reconcile and cost it, then write to DuckDB.
Your team signs in and the first dashboards are ready.
Hover a module to see what it does, or click through all of them in the demo.
Seven modules for stock, purchasing and claims.
P&L, cash and VAT from the same ledger.
What sells, where, and what it cost to sell it.
How your warehouses and carriers really perform.
Every mismatch explained, every user managed.
We work closely with Amazon brands across Europe and adapt SellerERP to how each of them runs.
That is your choice. Describe the standard hosting setup here. If you prefer, SellerERP runs as a private install: the Amazon API client is registered in your name, raw reports sit in your PostgreSQL and insights in your DuckDB store.
Amazon data comes straight from Amazon through your own API client: history first, then live updates. You add your purchase register for costs. Anything that doesn't match becomes an exception, not a guess.
It is built for Amazon FBA brands selling across European marketplaces. The ETL is adapted to your purchase files and fulfillment model, and other setups can be scoped with the developer.
A Kubernetes cluster for the gateway and ETL workers, PostgreSQL for raw reports, and space for the DuckDB store, on your server or in a secure cloud account. Add sizing and network requirements.
The developer who built it. You work with that person directly on setup, custom reports, and changes as your business changes.
Start with the demo and click through the modules. Add the pricing model, or say pricing is scoped per deployment.
Tell us your marketplaces and fulfillment model. You'll talk directly to the developer who builds SellerERP.