Discounts that clear the right stock at the right margin.
When a discount is the right lever, Zyntel sets the depth, the place and the timing, and holds every order above the margin floor.
Every offer has a reason, a limit and an end date.
Markdown recommendations
Which SKUs to discount, by how much and when, based on sell-through, age, cover and the margin floor.
ExampleFast fashion steps 20, 40, 60%. Premium 15, 25, 40%. Luxury usually none.
Ladders with rest periods
Each step gets time to work before the next. After three attempts, the engine moves to exit routes instead of cutting deeper.
ExampleNo endless discount spiral.
Event-based promotions
Offers timed to festivals, national days, payday, wedding season, weather and sport, in the regions they affect.
ExampleNever where there’s no stock to sell.
Bundles & thresholds
Multi-buy, spend-and-save and item offers, shown on the product page before checkout.
Combining offers
You decide which offers stack, which can’t, and which wins. Caps first, then the total discount limit, then the margin floor.
ExampleNo combination goes below break-even.
Budget & stock caps
Each offer stops when its budget or the stock behind it runs out, in every channel at once on the live cart.
Discount codes
A public code anyone can use, single-use codes created in bulk so they can’t leak to coupon sites, group codes for a chosen audience, and one code per creator per campaign so each partner’s sales count separately.
ExampleLimits per shopper, per day, per store, in total, and between set dates.
09Walkthrough 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.
Go live with as few as 100 SKUs and any length of sales history.
- Your catalogue and stock, loaded
- SKU health and risk scores
- Buy, move and markdown calls
- Festival effects for your regions
- Your brand and store rules
- Live cart or recommendations only
- What it would have saved
- A rollout plan by category