E-commerce
One operations dashboard for every marketplace you sell on
A single operational view for brands and sellers: stock, prices, orders, margins, alerts and SKU analytics in one place.
Stack and integrations
Marketplace APIs ClickHouse PostgreSQL FastAPI Bots
In short
- What we build
- A single operations dashboard across marketplaces: stock, prices, margins, alerts.
- Who for
- Brands and sellers with 200 SKUs or more on three or more platforms, where manual synchronisation causes oversells and penalties.
- Stack
- FastAPI with PostgreSQL and ClickHouse, marketplace APIs, accounting and inventory integrations.
- Timeline
- Synchronisation MVP in six to ten weeks, a full dashboard with BI in three to four months.
A good fit when
- → You sell on several platforms at once
- → Stock and prices are synchronised by hand
- → You need margin per SKU including commissions and logistics
- → Penalties, oversells or loss of control over promotions are a real cost
What you get
- → Integrations with each marketplace and your own warehouse
- → Automated repricing rules with margin guardrails
- → Dashboards for sales, stock, returns and unit economics
- → Alerts on anomalies and critical stock levels
Process
- 01 An audit of the APIs, the SKUs and the current operating model
- 02 MVP: stock synchronisation and basic analytics
- 03 Expansion: prices, promotions, forecasts, BI and alerts
Why not an off-the-shelf product
Custom development earns its place where your processes matter.
Ready-made SaaS is good for standard scenarios. But once the business logic depends on specific roles, documents, integrations, security or data, the cost of the workarounds quickly exceeds the cost of a proper architecture.
We start with discovery, separating what genuinely has to be built from what is cheaper to cover with an existing service. That is why the project ends up smaller, clearer and easier to run.
Related cases
Similar problems from the portfolio.
FAQ
Common questions
Can our own warehouse be connected?
Yes. We integrate with accounting systems, inventory tools, a WMS or a custom database over an API or exports.
Can prices change automatically?
Yes, but we start with safe rules and manual confirmation, so margins do not break while the rules are being tuned.
How many SKUs will it handle?
The architecture is chosen for the volume; large catalogues run on ClickHouse with background queues.
What does it cost?
An MVP with stock synchronisation and basic analytics is the entry point; a full dashboard with automated repricing, unit economics and BI costs more. Both are quoted after the API audit.
How long does it take?
MVP in six to ten weeks. A complete dashboard with BI, alerts and automated rules in three to four months.
Is there an example?
A marketplace manager for a cosmetics brand: one dashboard across two platforms, automated repricing, ClickHouse analytics, and a 12-point gain in margin. The write-up is on the case page.
Are there off-the-shelf aggregators?
Several, and they cover competitor analytics and part of the operational work well. Your own dashboard is warranted when integration with your accounting or WMS matters and the rules follow your specific logic.
How do we measure the effect?
Three metrics: margin per SKU (usually up 5–15 points through repricing), the share of oversells and penalties (down towards zero), and time spent on operations (down 60–80%).
Written up in more detail
Next step
Let us go through your problem.
We will show you a possible architecture, the risks, the order of the budget and what an MVP could prove.
Discuss a project