How Runit Handles Markdowns & Timed Sales - Cloud Retail Management System

Runit runs markdowns and timed sales from a rule-based engine: instead of hand-picking styles, you set criteria — sell-through %, days on the floor, units on hand, style status, markdown and price ranges — and Runit builds a markdown batch of exactly the merchandise that qualifies, by store, for your team to review and commit. The same engine schedules timed sales that, once committed, start and revert on their own. It turns markdown strategy into a repeatable rule — the system does the setup and selection; you make the final call.

Batch markdowns, driven by rules

A Runit markdown batch starts with what to mark down and by how much — then narrows to the styles that actually meet your criteria. You choose the basis (mark down from current, suggested retail, store-suggested, or original price), the amount ($ off, % off, or +/- % off), how to round (e.g., to $.99), and which store(s) it applies to, then commit it on a date.

The engine’s power is the exception criteria — work only with styles that meet conditions such as:

Sell-through — at least / no more than X% over the past N days.
Days on the floor — aged beyond (or under) a threshold.
Units sold / units on hand / on order — over a chosen period, optionally in any one store.
Retail sales & on-hand-at-retail $ — target by dollar performance, not just units.
Style status — new, reorder, markdown, transfer, or finished.
Markdown % range & price range — only touch items already within (or outside) set bands.

Criteria per Runit’s Batch Markdown tool. The batch previews the qualifying styles before you commit, so you see exactly what will change.

Timed sales that start and revert on schedule

Runit’s Batch Timed Sales use the same criteria engine, with start and end dates. Set a weekend event, a clearance window, or a store-specific promotion; once committed it activates and reverts to regular pricing on schedule — no need to remember to change prices back. Because timed sales share the exception logic, a scheduled event can target exactly the aged or slow-selling styles you want to move, rather than a blanket discount.

Why rule-based markdowns matter

Manual markdowns are slow and blunt: someone scrolls a report and edits prices, so timing slips and the wrong items get discounted. Rule-based markdowns let you encode a real strategy — “mark down anything under 40% sell-through after 60 days on the floor, by 25%, in these stores” — and Runit builds that markdown for you to approve, applied consistently across the whole assortment. You clear aged stock on time, protect margin on what’s still selling, and free your buyers from spreadsheet triage.

How this compares

Bulk and scheduled markdowns are common; a criteria-based markdown engine that selects the items for you is not. In our research of major specialty-retail POS systems, markdown tools were manual, bulk, or date-scheduled — we did not find a documented engine that selects items to mark down by performance rules like sell-through, days on floor, or units on hand; the user identifies the items.

Markdown capability	Typical POS	Runit
Bulk / batch price changes	Yes	Yes
Scheduled (timed) sales that auto-revert	Often yes	Yes
Criteria-based markdown selection	Not typically documented	Yes — select by sell-through, days on floor, units, status, price bands (you commit)

Comparison reflects public vendor documentation reviewed in 2026 and may change; see our Runit vs Lightspeed and Runit vs RICS vs Teamwork pages for system-by-system detail.

Frequently asked questions

Can Runit select markdowns by performance rules?

Yes. Runit’s batch markdown engine works only with styles that meet criteria you set — such as sell-through % over a period, days on the floor, units on hand or sold, style status, and markdown or price ranges — then builds a markdown batch of exactly those items, by store, which you review and commit. It previews the qualifying styles before anything changes, so the system does the selection and setup while you make the final decision.

What criteria can trigger a markdown in Runit?

Criteria include sell-through percentage over a chosen number of days, days on the floor, units sold, units on hand, units on order, retail sales and on-hand-at-retail dollars, style status (new, reorder, markdown, transfer, finished), days from last received, and markdown-% or price ranges — optionally scoped to any one store.

Do timed sales revert to regular price automatically?

Yes. Runit’s batch timed sales run with start and end dates and, once committed, revert to regular pricing on schedule, so staff don’t have to change prices back manually. Timed sales use the same criteria engine, so an event can target specific aged or slow-selling styles.

Can markdowns and sales be set per store?

Yes. Markdown and timed-sale batches can be scoped to specific stores, and criteria such as sell-through and units can be evaluated in any one store, so you can clear stock where it’s actually sitting.

How is this different from a normal POS discount?

A normal POS discount or bulk price change applies to items you pick manually. Runit’s engine selects the qualifying items for you based on performance rules and can schedule the change, so markdown strategy runs consistently across the whole assortment instead of one report and edit at a time — you still review and commit.

Related guides & features

See rule-based markdowns in action

Book a demo and we’ll build a markdown and a timed sale against your own criteria and stores.

Book a Demo