Stock and Supply Dashboard for Ozon and Wildberries
A seller dashboard for a home textile brand with 140 SKU on Ozon and Wildberries: stock in 13 marketplace warehouses and at the factory in one table, days until zero for every SKU, an FBO supply plan with a one-click supply sheet, FBS orders, returns and a Telegram bot with a morning digest.
Problem :
A textile factory in Ivanovo sells 140 SKU (bed linen, sheets, pillowcases, towels, blankets and curtains) through 13 Ozon and Wildberries warehouses and keeps its own stock at the factory. Each marketplace shows stock in its own seller account and in its own format, so “what runs out where, and what do we sew and ship this week” gets answered by hand in spreadsheets. When a warehouse hits zero, the product stops selling there, and sewing plus delivery takes days, so the decision has to be made before the zero, not after it.
Solution :
One dashboard for the whole chain. Stocks: all 140 SKU in one table with the factory, Ozon and WB, sales per day and days until zero, sorted by urgency; a row opens into every warehouse, and the “Time to ship” rail groups the 49 SKU that need to go by warehouse. Supplies: an FBO plan per warehouse that counts sewing time, delivery, coverage and safety stock, a budget per warehouse and a supply sheet built with one button. FBS orders with shipping deadlines on a timeline, returns with reasons and claims to the carrier, and products with price, cost, margin and sewing time. A Telegram bot sends a morning digest and urgent messages during the day. Connections cover the Ozon Seller API, the Wildberries API, MoySklad and Telegram, and the settings hold the profile, the team with roles, warehouse shares and the calculation parameters.
My Role :
Product, design and build: the structure of eight sections, the stock and supply calculations, the interface in light and dark themes, a separate phone layout, SVG charts and all the copy, including tap tooltips for every marketplace term.
Process :
I started from the question a seller asks every morning (what do we ship today and what will it cost) and built the supply formula first: sewing time, plus 4 days of delivery, plus 21 days of coverage, plus 5 days of safety stock. Every number on the screen reads from it: the cards at the top, the “Time to ship” rail, the plan per warehouse and the bot digest. Then I went through stock reports in the marketplace accounts and in seller tools, ordered the columns by priority (product, days until zero, what to ship, stock) and checked every section at eight screen widths, from a 360 px phone to a 1920 px monitor. On the phone, tables turn into lists and edits open in a bottom sheet, the way the Ozon Seller and WB Partners apps do it.
Outcome :
The morning starts on one screen: 9,421 units in marketplace warehouses, 10.8 million rubles frozen in stock at cost, 49 SKU due for shipping, about 176 sales and 500 thousand rubles of revenue a day. The plan says what to sew and where to send it, the supply sheet is ready in one click, and the bot repeats the urgent part in Telegram for whoever is away from the dashboard. Marketplace terms (FBO, FBS, coverage, safety stock) explain themselves on tap.
Tech Stack :
Next.js (App Router) + TypeScript, hand-written CSS with no UI kit. The charts are plain SVG with no chart library (orders over 30 days by marketplace, the supply budget by warehouse, the FBS deadline timeline, the shares of return reasons), each one sized to its container. Light and dark themes run on CSS variables, the phone gets its own layout with lists and bottom sheets, and term tooltips render through a portal so they stay next to their button while the page scrolls. The connections section is built around the Ozon Seller API, the Wildberries API, the MoySklad JSON API and the Telegram Bot API. Hosted on Vercel.
