Every Amazon unit, accounted for.

SellerERP follows each unit from purchase to payout, so your margins, stock and claims finally add up.

Laptop on a desk showing a sales analytics dashboard with area charts and a donut chart

One unit. Every stop on its journey.

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.

The clarity Seller Central never gave you.

Monitor showing analytics charts with histograms and trend lines

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.

Know what Amazon owes you

Removals, vendor receipts, cases and reimbursements are chained per unit, so unclaimed money has a name and a number.

Every unit has an ID

Assigned at purchase, then followed through every receipt, transfer and return.

A real COGS engine

FIFO per fulfillment center or weighted average. Cost travels with the unit.

Reconciliation, not estimation

Unlogged shipments, wrong MSKUs, over-receipts and vanished units show up as exceptions you can act on, never averaged away.

Purchase planning

Reorders from sell-through, lead times and inbound delays. Fewer stockouts, less cash stuck on shelves.

Two people working at desks with laptops and monitors in a bright office
Optional private hosting

Prefer to keep it in-house? You can.

For sellers who want full control of their margins and supplier prices, SellerERP can also run as a private install on infrastructure you choose.

  • Your servers or your cloud

    Kubernetes on your own hardware or a cloud account you choose.

  • Your own Amazon connection

    The API client and credentials are registered to you. No aggregator in between.

  • One customer, one install

    Raw reports in your PostgreSQL, insights in your DuckDB store.

  • A developer you can call

    The person who built it sets it up with you and adapts it to your files.

How a private install works

Close to real time, paced to Amazon's rate limits.

AmazonReports, history and live notifications
Inside your walls
API gatewayYour client, on Kubernetes
PostgreSQLRaw reports, kept as received
ETL workersMatch, reconcile and cost
DuckDBInsights beside the app
SellerERPOpened in your browser
Single-tenant install No data aggregators Data stays in your network

Sound familiar?

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.

SellerERP fixes all of this.

Built for Amazon FBA brands with large SKU ranges, fast-moving goods, complex landed costs and tight cash cycles.

Try the demo

Private install, step by step.

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.

  1. Register privately

    A developer registration and Selling Partner API client are created under your account.

  2. Deploy the gateway

    It runs in your cluster and paces every call to Amazon's rate limits.

  3. Fetch your history

    Past reports load in the background, so dashboards start full, not empty.

  4. Subscribe to live updates

    Notifications start arriving while the backfill is still running.

  5. Store raw reports

    Everything Amazon sends is kept as received in your PostgreSQL.

  6. Turn data into insight

    ETL workers match, reconcile and cost it, then write to DuckDB.

  7. Open it in your browser

    Your team signs in and the first dashboards are ready.

The whole back office in one tab.

Hover a module to see what it does, or click through all of them in the demo.

Inventory and costing

Product Catalog Stock Replenishment Warehouse and Purchasing FBA Inventory Virtual Shelves Vendor Returns Claims and Reimbursements

Seven modules for stock, purchasing and claims.

Finance

Financials Settlement and Cash VAT Reporting

P&L, cash and VAT from the same ledger.

Sales

Sales Product Performance Marketing

What sells, where, and what it cost to sell it.

Operations

FC Performance Carrier Performance

How your warehouses and carriers really perform.

Audit and system

Exceptions and Audit Settings and Users

Every mismatch explained, every user managed.

Sellers who sleep better.

We work closely with Amazon brands across Europe and adapt SellerERP to how each of them runs.

Questions

Before you ask.

Where does my data live?

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.

What data does it need?

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.

Will it fit my setup?

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.

What do I need to host it myself?

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.

Who builds and maintains it?

The developer who built it. You work with that person directly on setup, custom reports, and changes as your business changes.

What does it cost?

Start with the demo and click through the modules. Add the pricing model, or say pricing is scoped per deployment.

Let's get your numbers in order.

Tell us your marketplaces and fulfillment model. You'll talk directly to the developer who builds SellerERP.

Add a contact email or booking link here. Not ready yet? Try the demo first.