Marketplace e-commerce · Sales analytics
One profit per SKU across three marketplaces, reconciled to 0.00%
Five seller accounts on WB, Ozon and Yandex Market merged into one SKU-level P&L: 0.00% variance vs the client's manual benchmark, forecast 2.7× more accurate than naive.
- Status
- In production
- Timeline
- ~2.5 months (two phases)
- Stack
- Python / FastAPI
- ClickHouse + PostgreSQL
- LightGBM / XGBoost / scikit-learn
- API Wildberries, Ozon, Яндекс Маркет
- OpenAI API (function calling)
- Docker / Traefik / GitHub Actions
The task
A home-goods manufacturer sells through five seller accounts on three marketplaces and had no reliable profit per SKU: statements differ by platform, some operations settle in another month, ad spend and account fees never reached products. Excel reconciliation took days and still drifted. They needed one source of truth for profit, a demand forecast for purchasing, and a check on marketplace overcharges.
What we built
- One pipeline for all five accounts: 12 months of history, daily refresh, restart-safe jobs. Marketplace access is read-only — nothing in the seller accounts is ever changed.
- We reverse-engineered the platform's monthly statement logic and verified it against the client's own numbers, day by day and SKU by SKU. COGS comes in as a file from the client's ERP, as agreed.
- 7–30 day demand forecast: several models compete on a held-out period and the winner ships. Daily retraining, degradation monitoring, the acceptance metric computed automatically.
- Stock-out signals and a trend detector, shipped with backtests on history. Commission, logistics and storage are checked against the platform's tariff — a ready basis for claims.
- Role-based dashboard, an AI assistant over account data, alerts to Telegram and email, a weekly P&L. Acceptance on measurable KPIs, weekly demos, automated tests in CI.
Outcome
- 0.00%
- variance vs the client's manual benchmark across units, revenue, COGS, profit and margin for a control SKU over a month; threshold was 1%
- 2.7×
- more accurate than naive: weekly WAPE on SKUs driving 80% of revenue, 29.6% vs 81.4%. The 25% goal is open: history covers 66.9% of SKUs
- 1.18M rows
- of sales across 5 accounts and 12 months processed; 10.7% were ordered and settled in different months
- ~7.5% of spend
- in one account's monthly statement never reached the SKU report (no SKU attached). Found and included in total spend; reconciled down to one control line
More cases
Music tech · SaaS
MVP in operation (closed launch)Music releases without missed deadlines
Release ops for independent labels: 9-stage lifecycle, pitching deadlines for 12 stores, AI drafts with human approval. Zero to production-grade in 7 weeks.
- 7 weeks
- from first commit to a production-grade stack with Vault, encrypted backups, SLOs and a move to a Russian data centre (265 commits)
- 16 days
- from project start to an investor presentation with a live product demo
IT consulting · Lead qualification
In-house productA pilot plan for the visitor, a qualified lead for sales
We replaced the contact form with an AI consultant: it interviews the visitor, returns a pilot plan with KPIs and risks, and sales gets a lead with budget and timeline.
- 1 day
- Working MVP — frontend, backend and deploy configs — built in a single day
- 16 days
- From first commit to production with HTTPS and an issued certificate on its own domain
Aviation — aircraft components trading and MRO
PilotAircraft parts procurement: from inbox chaos to a managed pipeline
An AI agent reads incoming RFQs, compares supplier quotes and checks trace documents; an operations system moves each deal through mandatory stages.
- Full loop
- full AI loop on a live procurement process — from incoming RFQ to team notification; confirmed by the owner
- 3
- types of trace documents checked by the agent: FAA 8130-3, EASA Form 1, COC; counted from the owner's brief
Estimate the impact on your own figures
AVA is a process-economics calculator. In a couple of minutes it shows whether a similar task pays off in your case — before any call and with no commitment.
Estimate the impact with AVAHave a similar task?
Describe the process and the data you have. We will tell you what can be measured in money and what cannot — before any work starts.
or email us directly: hello@xteam.pro