How MarginOS flags High Velocity, Low Yield

High Velocity, Low Yield marks a product that sells well and earns thin. It is one of the few flags worth acting on immediately, because volume is actively working against you: every additional unit reproduces the same weak margin at scale, and the popularity of the item disguises the problem in your totals.

What the flag means

MarginOS raises it when a product clears two tests at once over the last 30 days:

1. It is a fast seller for your store — units sold reach the velocity level that qualifies a product as a hero in your catalogue.
2. Its margin percentage is thin — Gross Margin % falls below the low-yield level.

Both conditions are required, and that is the entire point of the flag. A slow-moving product with a thin margin is a pricing question you can get to next quarter. A best seller with a thin margin is money leaving the business every day, at a rate set by how well it sells.

Why the velocity gate exists

A catalogue of any size has plenty of thin-margin items. Flagging all of them produces a list nobody reads. The velocity gate restricts the flag to products where the margin problem is being multiplied by real volume — which is what makes it urgent rather than merely true.

The velocity level that counts as “hero” is not a fixed number of units. It scales with your store, so a brand shipping hundreds of units a month and one shipping tens of thousands both get a meaningful hero set rather than everything or nothing. You can adjust it in settings if your catalogue’s shape makes the default a poor fit.

What it is not

Two exclusions matter, because they separate this flag from problems that need a different response.

• Products losing money are not flagged here. A product whose margin is negative is a different and more serious condition, and it is reported separately. High Velocity, Low Yield describes profitable-but-thin, not unprofitable.
• It is a percentage test, not a dollar test. A product can pass this check and still be flagged Too Close to Cost, which asks a different question — whether the per-unit dollars are thin relative to what the item costs you.

What to do about it

1. Check the costs are real first. A thin margin caused by a wrong cost is a data problem, not a pricing problem. Look at Data Trust for the product before you change anything — if the margin is running on a store-wide default rather than the item’s own cost, fix that first.
2. Look at the whole cost stack, not just product cost. The margin includes fulfillment, payment fees and refund handling. A heavy or bulky item can be priced sensibly and still land here on fulfillment alone.
3. Check the return rate. Returns hit this flag twice — lost revenue and unrecovered handling cost.
4. Then decide: price, cost or position. Raise the price, renegotiate or re-source the cost, change how it ships — or accept it deliberately as a product that acquires customers you profit from later, which is a legitimate strategy as long as it is a choice rather than an accident.

Common questions

What exactly counts as “high velocity”?

A units-sold level over the last 30 days that scales with your store’s size rather than a universal number, so the hero set stays meaningful whatever your volume. It is adjustable in settings if the default does not suit your catalogue.

Why is a thin-margin product I sell a lot of not flagged?

The most common reasons are that its margin sits just above the low-yield level, that its units fall just under the hero velocity level, or that it is actually losing money and is therefore reported as a negative-margin product instead.

Can a product be both High Velocity, Low Yield and Too Close to Cost?

Yes. They share the velocity gate but test different things — one the margin percentage, the other the per-unit dollars against the item’s own cost. A cheap item can be dollar-thin while looking acceptable as a percentage, and an expensive item can be the reverse.

The flag appeared without anything changing on my side. Why?

Either the product crossed into hero velocity — the flag is only ever applied to fast sellers, so a rising product can acquire it purely by selling more — or its cost basis improved in accuracy, replacing an optimistic assumption with a real cost. The second case is the flag doing its job: the margin was always this thin, and MarginOS can now prove it.

Does this include wholesale or marketplace sales?

No. The flag looks at your direct-to-consumer business, so a product that is thin on DTC but healthy elsewhere is judged on the DTC economics alone.

Related

• Too Close to Cost — the per-unit dollar version of this question.
• How MarginOS calculates Gross Margin % — the percentage this flag tests.
• Data Trust levels — check this before acting on any margin flag.
• Store-wide cost defaults — where an assumed cost would be coming from.