Markdown optimisation software that only cuts what’s truly slow.
Zyntel is markdown optimisation software that separates a price problem from a visibility or wrong-store problem first. When a discount is the right lever, it sets the depth, the place and the timing, steps down a ladder with rest periods, and never goes below the margin floor.
| Product | Sell-through | Lever | Engine says |
|---|---|---|---|
| Graphic tee, summer drop FF-TEE-5510 | 41% | Discount | Step 1 · 20% for 10 days |
| Linen shirt, sand FF-SHT-3104 | 58% | Wait | Holiday peak in 6 days |
| Satin midi dress, coral FF-DRS-1150 | 22% | Get seen | Low views, healthy margin |
| Puffer vest, olive FF-JKT-4410 | 19% | Exit | 3 steps tried · outlet route |
01The problem
Why blanket markdowns cost margin.
Slow lines surface at the end-of-season review, when the only lever left is a deep cut.
Every slow product gets the same discount, whether the problem is price, visibility or the wrong store.
Markdowns land days before an event that would have cleared the stock at full price.
Repeated cuts chase stock that was never going to sell, instead of moving it to an exit route.
02How it works
How Zyntel sets every markdown.
Four checks, in the same order, for every product on every run.
Find the real cause
Every product is scored on sell-through, age, days of cover and margin against its segment’s selling life. Lines that are unseen or sitting in the wrong store go to other levers first.
Check what’s coming
If an event that clears this category is days away, the engine recommends waiting. Discounting into demand you would have had anyway only gives margin away.
Pick the ladder and the depth
Fast fashion, premium and luxury each step down their own ladder, for example 20, 40, 60% or 15, 25, 40%. Every depth is checked against break-even, category, segment, brand and product rules, and the tightest one wins.
Rest, measure, then step
Each step gets time to work before the next. After three attempts the engine recommends an exit route instead of a fourth cut.
03Outcomes
What your team gets.
- A daily list of which SKUs to discount, by how much and from when
- The reason, the second-best option and doing nothing, side by side
- Depths that never break the margin floor or a brand agreement
- Approval levels by lever and value
- Results measured: did it add sales, and was the engine right
04Questions
About markdown optimisation
How is this different from a markdown rule in our ERP?
A rule applies the same cut to everything that crosses a threshold. Zyntel first checks why a product is slow, whether an event is coming, and whether moving or promoting it would cost less, then sets a depth that respects every rule layer.
Can we approve markdowns before they go live?
Yes. For each decision type you choose approve first, run and tell, or run within limits, with approval levels set by value and depth.
Does it work without changing our checkout?
Yes. In recommendations-only mode the engine sends approved markdowns daily as Excel, CSV or a feed, and your own systems apply them.
05Walkthrough on your data
Bring one category. See tomorrow’s worklist.
We load a sample of your catalogue, sales and stock, run the engine on it, and walk you through every recommendation, the reason behind it and what it would have earned.