Schedule the sale. Walk away.
Sale Scheduler is the promotion-automation engine multi-store Shopify operators trust for Black Friday and every promo cycle after. Set the start, set the end, set the scope. Prices flip across every connected store at the scheduled moment. They revert at the scheduled moment. The midnight ritual ends. The forgotten revert becomes structurally impossible. Finance gets an audit log of every flip — who, when, what changed.
The Sale Scheduler footprint
Numbers from real Black Friday and seasonal-promo runs across multi-store Shopify operations on Apimio.
The promo-ops failure pattern
Promotions break in the same four ways every cycle: manual midnight flips, forgotten reverts, partial multi-store fan-outs, and no audit when finance asks. Sale Scheduler is the operational answer to each.
How promotions fail today
What Sale Scheduler does about it
Someone stays up at midnight to flip prices
A team member loses Black Friday night flipping 150 products from $99 to $79 across two stores, one store at a time. Tired, error-prone, repeated next month for Cyber Monday, repeated again at Christmas. The ritual is unsustainable and the team resents it.
Schedule the start. Schedule the end. Walk away.
Set the start time, set the end time, set the scope (per-store / collection / sitewide), set the discount. Prices flip at the scheduled moment automatically. The team goes home at 5pm before Black Friday and watches the metrics roll in.
Forgotten reverts cost margin for days
Monday morning after the sale, 14 products are still at the discounted price because nobody remembered to revert them. Margin lost for three more days at full sales velocity. Finance notices a week later. The conversation is awkward.
Auto-revert is built in, not a separate step
The revert is part of the same schedule. There is no separate action to remember. The discount lifts at the scheduled end-time, the compare-at-price restores, the strike-through disappears. Forgotten reverts are eliminated by construction.
Multi-store fan-out drifts
Sale starts on Store A at midnight, but the sync app misses the webhook for Store B. Customers see different prices for the same SKU on the same brand's sites. Trust erosion compounds. The team scrambles.
One schedule, every store, fault-tolerant fan-out
One schedule writes to every connected store via the same queue Catalogue Hub uses for sync. If Shopify hiccups, the queue retries until the write succeeds. Multi-store drift becomes operationally impossible.
No audit log when finance asks "who changed this?"
Finance flags a 30% discount that ran on Store B for a week longer than planned. Who scheduled it? Who forgot to revert it? In Shopify admin alone, the answer is "we don't know." Reconciliation takes days.
Audit log every flip
Every price flip — start, revert, manual override, schedule edit — is captured in the audit log with actor, source, before/after, and target store. Finance reconciliation moves from days to minutes.
The six capabilities, in operational detail
These are the surfaces your promo + finance + ops teams will actually use. Each behavior described here is what production looks like, not the marketing version.
Schedule start + end with auto-revert
A schedule is a triplet — start, end, discount. The revert lives in the same object as the start. Editing the end-time edits the revert. There is no separate revert task to lose.
- Start/end at minute granularity, in your team's timezone
- Pre-flight preview: see the new prices before activation
- Schedule edit captures audit trail (who changed end-time, when)
- Cancel a schedule mid-sale and the prices revert immediately
- Stacked schedules: Black Friday + Cyber Monday + Christmas all queued
- Holiday templates: pre-built schedules for major promo periods
Multi-store fan-out from one schedule
One schedule writes to every connected Shopify store via the same fault-tolerant queue Catalogue Hub uses. Per-store overrides apply if you need different discounts per market.
- One schedule, N stores — one operation per scope rule
- Per-store discount overrides where you need them (regional pricing)
- Per-locale scheduling via Shopify Markets
- Plus Org Admin recognized natively (no per-store reauth)
- Progress tracking per store in the Activity Log
- Failed-store retry without restarting the whole fan-out
Scope rules per store / collection / vendor
Scope a schedule to a collection, a vendor, a tag, a custom product set, or a sitewide push. Mix-and-match — the schedule editor builds the target set from any combination of filters.
- Per-store: D2C store on sale, wholesale store not
- Per-collection: "Summer 2026" only
- Per-vendor: clearance on Vendor X products only
- Per-tag: products tagged "clearance" sitewide
- Custom product set: explicit SKU list
- Saved scope templates for repeating promos
Fault-tolerant queue (Shopify-outage proof)
When Shopify's API hiccups during a fan-out, the queue persists. Failed writes are retried with exponential backoff. If Shopify is unreachable for an extended window, the queue catches up in the original order when it returns.
- Durable queue with exponential backoff + dead-letter handling
- Order-preserving writes (no out-of-order price drops)
- Catch-up mode when Shopify returns from outage
- "Queued — waiting on Shopify" surfaced in the dashboard
- No silent failures — every queued operation is visible
- Activity Log shows the exact retry trail per failed write
Audit log of every price flip
Every start, every revert, every cancel, every override is captured in the audit log with actor, source (manual / scheduled / API / Apimio AI), before/after value, and target store. Finance reconciliation in minutes.
- Per-attribute write trail (price + compare-at-price)
- Source attribution: scheduled, manual, integration, API
- Before/after diff, with one-click rollback per attribute
- CSV export for finance reconciliation
- Filter by date range, store, actor, source
- SOC-grade audit trail for compliance teams
Compare-at-price + strike-through done right
Sale Scheduler manages both sale-price and compare-at-price together so the storefront shows proper strike-through pricing — not just a lower number with no context. The original price is preserved on revert.
- Compare-at-price = original price during sale (proper strike-through)
- Sale-price = the discounted number customers see
- Revert restores original price and clears compare-at-price
- Discount % auto-computed and shown in the dashboard
- Markdown stacking on already-discounted items handled correctly
- Markets-aware: per-locale strike-through pricing
Five steps from promo plan to audit
From Black Friday planning to the Monday-after finance review. Most teams plan a promo in step 1–2, then the rest happens without manual intervention.
Define the scope
Pick the product set: a collection, a vendor, a tag, a custom SKU list, or a sitewide push. Layer per-store rules if regional pricing differs. The scope preview shows exactly which SKUs in which stores are about to be discounted.
Schedule start + end
Set the start time, set the end time, set the discount (percentage or flat amount). The revert is part of the schedule — you do not set it separately. Pre-flight preview shows the new prices before activation.
Prices flip — automatically
At the scheduled start time, the fan-out queue writes the new prices to every targeted store. Compare-at-price restores the original. Strike-through appears on the storefront. The team is sleeping or working on the rest of the business.
Auto-revert at sale end
At the scheduled end time, the prices revert automatically. Compare-at-price clears. Strike-through disappears. No manual reset task. No 14-products-still-discounted Monday morning.
Finance reads the audit log
Monday-after review: finance reads the audit log — every flip, every store, every actor. Reconciliation that used to take days takes minutes. The pattern repeats for every promo cycle without team burnout.
Outcomes from automating multi-store promotions
The operational changes teams report after one full promo cycle running on Sale Scheduler. Margin saved is measurable; sleep saved is harder to quantify but reported every quarter.
Midnight ritual ends
The team stops losing nights to manual price flips. Black Friday becomes a metrics-watching exercise, not an operational sprint. Cyber Monday is the same workflow with different inputs.
Margin recovered from forgotten reverts
The 14 products at 30% off for three extra days were costing margin that nobody could quantify. Auto-revert recovers it. Most teams see the recovery in their first month-end close after switching.
Multi-store drift eliminated
Pricing inconsistencies across stores during promos disappear — the fan-out fault-tolerantly writes to every connected store from one schedule. Customer trust holds up under heavy promotional traffic.
Finance gets the audit trail it wanted
Reconciliation conversations stop being "we don't know." Every price flip is attributable to a schedule, an actor, a source. SOC and finance teams stop hassling marketing about pricing history.
New promo formats become tryable
A 4-hour flash sale on one collection across two stores used to require dedicated team coverage. With Sale Scheduler, it's a 5-minute setup. Operational cost of trying new promo formats drops to near-zero.
Plus operators get organization-wide promos
Shopify Plus orgs running 8+ stores can schedule one promo across the entire organization without per-store reauthorization. The Markets translation overhead also disappears (Sale Scheduler is locale-aware).
Sale Scheduler vs Shopify Discounts and sale apps
Three ways teams try to handle multi-store promotions on Shopify. Sale Scheduler is the only one with auto-revert + fault-tolerant fan-out + finance audit log together.
Shopify Discounts | Sale apps (single-store) | Multi-store + audit Sale Scheduler | |
|---|---|---|---|
| Schedule start + end time | |||
| Auto-revert at end (no manual reset) | |||
| Multi-store fan-out from one schedule | |||
| Fault-tolerant queue for Shopify outages | |||
| Compare-at-price (proper strike-through) | |||
| Per-store / collection / vendor scope rules | |||
| Finance audit log + CSV export | |||
| Markets-aware (per-locale pricing) | |||
Questions about running multi-store promotions
The questions we get most often from teams evaluating Sale Scheduler — especially around the auto-revert, multi-store fan-out, and audit log.
Auto-revert is part of the schedule object, not a separate task. To extend a sale, edit the schedule's end-time — the revert moves with it automatically. The audit log captures the extension (who changed the end-time, when, from when to when). To end early, edit the end-time to now or cancel the schedule — the revert fires immediately. There is no scenario where the revert "gets forgotten" because it isn't a separate to-do.
The fan-out queue persists. Failed writes are retried with exponential backoff. If Shopify is unreachable for an extended window, the queue catches up in the original order when the API returns — usually within minutes. The Activity Log surfaces "Queued — waiting on Shopify" so the team knows the schedule fired but is held up. We have not lost a scheduled price flip yet.
Yes — that's exactly what per-store override scope rules are for. One schedule with a per-store override panel: 20% in Store A, 15% in Store B, no discount in Store C (wholesale). The fan-out applies the right discount to the right store. Markets-aware locales handle multi-currency on the same schedule.
Sale Scheduler manages product-level pricing (price + compare-at-price) — the strike-through customers see on the product page. Shopify Discounts (codes, automatic-tier, BOGO) is a separate mechanism for cart-level discounts. The two stack: a Sale Scheduler promotion can run alongside a 10% code, and Apimio tracks the interactions in the audit log.
Yes — stacked schedules are fully supported. Each schedule has its own start/end/scope, and Sale Scheduler resolves overlapping schedules using the most recent (last-write-wins) at every flip moment. The Activity Log shows the entire schedule queue for the next 12 months. Holiday templates (BFCM, MLK, Memorial Day, July 4th, etc.) ship with the product as starting points.
Yes. Scope can be: a single SKU, a custom SKU list, a vendor, a tag, a collection, a category, or sitewide. Per-store scope layers on top. The schedule editor builds the target set from any combination of those filters with a pre-flight preview before activation.
Per-flip records: timestamp, target store, target SKU, before/after price, before/after compare-at-price, source (which schedule fired it, or which actor edited it), schedule ID for traceability, and the schedule's configured end-time so you can verify the revert. Export to CSV for finance reconciliation. Filter by date, store, actor, source.
Yes. Sale Scheduler is Markets-aware — schedules can be scoped per locale, with proper currency conversion at write-time. A €-priced Spain market and a $-priced US market on the same schedule each get correctly localized discounted + compare-at prices. Plus Organization Admin is recognized so you do not reauthorize per store.
Sale Scheduler reads canonical pricing from Catalogue Hub and applies the discount via the per-store override layer. Quality Guard does NOT block scheduled price flips (the gate is for missing-data quality, not pricing). When a schedule fires, the audit trail captures the source as "Sale Scheduler" — so a finance reviewer can distinguish a scheduled flip from a manual override.
Sleep through your next Black Friday
Install Apimio, define your first promo schedule, watch it flip and revert without you. The 14-day trial includes the full Sale Scheduler — multi-store fan-out, fault-tolerant queue, audit log, holiday templates. No credit card required.