Promotions
AuraScore 81/100

Seasonal Clearance Markdown Execution Audit Checklist

Comprehensive markdown compliance checklist to audit seasonal retail inventory clearance cycles.

Use this prompt when transitioning retail inventory from full price to clearance and terminal liquidation. It ensures store and digital channels follow scheduled markdown cadences without unauthorized price overrides.

Template

Role: Omnichannel Inventory Operations Director managing retail lifecycle clearance and margin recovery.

Context

  • Store banner: {{store_banner_name}}
  • Clearance cycle: {{clearance_season}}
  • Inventory aging criteria: {{aging_inventory_threshold_days}}
  • Price drop schedule: {{markdown_cadence_schedule}}
  • Liquidation/Salvage vendor terms: {{salvage_vendor_rules}}
  • Regional footprint: {{regional_market_scope}}

Task

Produce an operational markdown execution audit checklist for {{store_banner_name}} to systematically clear seasonal stock past {{aging_inventory_threshold_days}} during {{clearance_season}} across {{regional_market_scope}} in accordance with {{markdown_cadence_schedule}}.

Method

  1. Outline physical and digital inventory tagging checks for SKUs meeting {{aging_inventory_threshold_days}}.
  2. Detail pricing ladder validation checks aligned with {{markdown_cadence_schedule}} across online storefronts and store registers.
  3. Create in-store merchandising compliance checks (clearance signage, red-tagging, aisle placement) for {{regional_market_scope}}.
  4. Define system permission checks to restrict unauthorized local manager price overrides beyond allowed thresholds.
  5. Establish digital catalog filtering rules to suppress clearance items from primary paid acquisition ad feeds.
  6. Formulate salvage transfer criteria adhering to {{salvage_vendor_rules}} for terminal non-moving units.
  7. Structure weekly sell-through audit checkpoints to trigger planned secondary markdown steps.

Constraints

  • MUST include dedicated sections for both physical retail operations and digital catalog sync.
  • MUST NOT allow manual price deviations outside of the authorized cadence schedule.
  • Every item must specify the verification method (system audit, visual check, report query).
  • Checklist must follow chronological markdown operational phases.

Output format

  • Phase 1: Pre-Markdown Inventory Identification & Tagging (4 items)
  • Phase 2: Pricing Engine & POS System Sync (4 items)
  • Phase 3: Merchandising & Digital Catalog Curation (4 items)
  • Phase 4: Sell-Through Cadence & Secondary Markdowns (3 items)
  • Phase 5: Terminal Liquidation & Salvage Handover (3 items)

Self-review

  • Check that {{store_banner_name}}, {{clearance_season}}, {{aging_inventory_threshold_days}}, {{markdown_cadence_schedule}}, {{salvage_vendor_rules}}, and {{regional_market_scope}} are used.
  • Ensure each checklist item includes verification method and owner role.
  • Confirm clarity and conciseness across all markdown phases.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ecommerce-retail
ecom-promotions
retail-consumer-goods
clearance
markdown-management
inventory-recovery