Drop performance tracking for fashion brands: launch sales, drop comparison and sell-through in KNKTD OS
A drop is a launched board: KNKTD OS measures what its own products sold from launch day, compares it with every earlier drop, and ranks what is selling fast and what is sitting in stock.
· 7 min read
In short: KNKTD OS treats a drop as a launched board. The Drop Performance report measures what that drop's own products sold from launch day — over the first day, 7 days, 30 days, until the next drop, or a custom range — and sets it against earlier drops and the rest of the catalogue. A Compare drops view ranks every drop over the same window, the dashboard shows the latest drop live for its first week, and the Product Performance report ranks best sellers, fast movers and slow movers by sell-through.
A brand that sells in drops lives by launch week, and most answer "did it work?" from Shopify's sales page. That page shows the whole store — the new capsule, last season's carryovers and the basics, added together — so a strong week for the basics looks like a strong drop.
Drop performance tracking needs two things a store total lacks: which products belong to the drop, and a launch date to measure from. KNKTD OS holds both, because the drop was planned in it.
What counts as a drop
A drop is a board in product development that has launched. A product belongs to the drop when the style it was created from is on that board, so membership is decided by the plan, not by whichever Shopify collections a product happens to sit in.
The launch date comes from one of two places. A board can be marked by hand — Mark as launched, with the day the drop went out — or, if it is not, it takes the earliest publish date of a Shopify collection linked to it. The manual date wins, because a collection often goes live the night before the announced launch. A drop dated in the future does not appear until its day arrives.
Two edge cases are settled by rule rather than judgement:
- Carryovers. A product on several boards belongs to the earliest launched one. A style that returns in a later capsule still counts towards the drop that introduced it.
- Unplanned products. A product on no board is No drop — the core range. A product on a board that has not launched yet is counted under Later / upcoming drops.
Reading a single drop
The report opens on the latest drop with the First 7 days window. The window options are Launch day, First 7 days, First 30 days, Until next drop and Custom range. Every window except a custom range starts on the launch day, and a window that has not finished yet says so — three days into a 7-day window, the report reads "day 3 of 7" rather than pretending the week is over.
Four cards sit at the top: Net sales, Units sold, Discounts and Returns, each split by drop. Net sales is after discounts and returns, before shipping and tax. Below them, Sales by drop answers the question the store total cannot:
| Row | What it holds |
|---|---|
| This drop | The selected drop's own products |
| Each previous drop | Listed separately, newest first, so carryovers stay visible |
| Later / upcoming drops | Products on boards that launched later or have not launched |
| No drop | Products on no board — the core range |
Each row shows gross, discounts, returns, units sold, units returned and Share of gross. The share is the useful number on launch day: if the new drop took a small share of a busy week, the week was busy for some other reason.
The Products table lists every product sold in the window with the drop it belongs to, filterable by group, and the list exports to CSV.
Returns follow the order, not the calendar: they are the refunded, removed and cancelled items so far on orders placed inside the window, so a launch-week figure can keep rising after the week ends.
Comparing drops
The Compare drops tab puts every launched drop in one table, each measured over its own window using the same rule — the first 7 days of each, or the first 30, or each drop until the next one — so the comparison is like with like. For every drop it shows what its own products grossed, their discounts, returns and units, Gross / day, the Store gross over the same days and the Drop share of it.
The top three drops carry medals, ranked by gross per day rather than total gross, so a drop on day two of seven is judged on the days it has had instead of losing to finished drops on length alone. Archived boards still appear, marked Archived — a drop that happened is history.
The live drop on the dashboard
For the first seven days after the latest drop launches, the dashboard carries a live card for it: the drop's name and cover, Day 3 of 7 with a pip for each day, and three figures — Drop net sales since launch, Units since launch, and Today's product sales from the drop as a share of everything the store sold today. A sparkline tracks cumulative drop sales hour by hour from launch, with the time of the last sale beneath it, and the five Top sellers by units are listed with their images.
The card refreshes every minute while the tab is open, and sooner when a new order arrives. After day seven it disappears; Open drop report opens the full report on the same 7-day window.
Clean numbers: gifts out, currencies converted
Two things quietly inflate drop numbers in most tools, and both are handled before anything is summed.
Influencer gifts and paid collaborations are excluded. Seeding a new drop to thirty creators is marketing, not demand. An influencer's own purchase still counts, because that is a sale. The rule comes from the influencers module, where every gift is linked to its order. Gift cards and service items are left out too.
Order currencies are converted, never added together. A brand selling in several markets takes orders in several currencies. Each currency's sales are converted into the workspace currency at the latest daily exchange rate before they are totalled. If a currency has no rate, its amounts are left out rather than added in the wrong unit, the units still count, and the page names the currency under Some sales could not be converted.
Best sellers, fast movers and slow movers
The drop report measures sales. The Product Performance report measures how products sell against the stock they had, and it is where sell-through lives. It splits the question into three tables, each with a 0–100 score ranked against the products competing for that table:
- Best sellers — what brought in the most sales in the range: 60% net sales, 40% units sold. A new product is not held back for being new.
- Fast movers — what is selling fastest for the chance it had: 60% sell-through (units sold ÷ the stock there was to sell), 40% units per in-stock day. Days before launch or while sold out do not count against a product, and one with fewer than seven in-stock days is marked New as an early read.
- Slow movers — products that had a fair chance and are tying up stock: slow units per in-stock day, low sell-through and stock on hand now. A higher score is a bigger problem. These are the markdown candidates, and they feed straight into demand planning and markdowns.
A product needs a real opportunity before it is judged. Fast movers need sales, at least three in-stock days and at least five units to sell; slow movers need fourteen in-stock days and five units on hand, and a product under thirty days scores lower as an early read. Days before stock tracking began are treated as unknown, never as sold out, and the report notes which products were measured from that point.
Above the tables, Units sold splits by size, Products sold separates products whose first-ever sale fell in the range from established ones, and Net sales by category shows how concentrated sales are across Shopify product categories. Set the range to a drop's first weeks and the new-product split shows how much the new styles carried. The workspace assistant, connected to Claude or ChatGPT, reads the same report — "what were our slowest movers last month?".
Both reports sit alongside sales velocity, margin and returns in the analytics module.
Pricing
Drop Performance and Product Performance are part of the analytics module, included on every plan. Plans start at $100 USD per month for two team members, with a 14-day free trial. See current pricing.
Bottom line
A drop can only be measured against a plan. Because KNKTD OS knows which styles were on the board and the day it launched, it can say what the drop sold, not what the store sold that week — with gifts taken out, currencies converted, and the next drop's numbers ready to be compared on the same terms.
Frequently asked questions
How does KNKTD OS decide which products belong to a drop?
A drop is a product development board that has launched. A product belongs to it when the style it was created from is on that board, so Shopify collection membership does not decide it. A product on several boards belongs to the earliest launched one, so a carryover still counts towards the drop that introduced it.
Where does the launch date come from?
A board can be marked as launched by hand with the day the drop went out. If it is not, the launch date is the earliest publish date of a Shopify collection linked to the board. The manual date wins, because a collection often goes live the night before the announced launch.
Are influencer gifts counted in drop sales?
No. Influencer gift orders and paid collaborations are excluded, because seeding a drop is marketing rather than demand. An influencer buying something themselves still counts as a sale. Gift cards and service items are also left out, so only physical products are measured.
How are orders in different currencies handled?
Each order currency is converted into the workspace currency at the latest daily exchange rate before anything is totalled, never added together in mixed units. If a currency has no rate, its amounts are left out, its units still count, and the report names the currency so the gap is visible.