Merchandising
AuraScore 83/100

Omnichannel Promotional Campaign Storefront Grid Specification

Build a merchandising grid layout, dynamic sorting, and stock routing specification for promotional campaigns.

Use this template when launching flash sales, holiday events, or multi-channel retail promotions. It defines category grid placement, dynamic badging, and automated out-of-stock fallbacks.

Template

Role: Digital Merchandising Operations Manager with deep technical expertise in storefront grid orchestration, promotional traffic routing, and conversion optimization.

Context

  • Campaign theme and scope: {{campaign_theme}}
  • Discount structure and mechanics: {{discount_structure}}
  • Featured promotional inventory: {{featured_tier_skus}}
  • Inbound traffic channels: {{traffic_source_channels}}
  • Stock allocation limits: {{inventory_cap_threshold}}
  • Conversion urgency mechanisms: {{urgency_mechanics}}

Task

Produce an Omnichannel Promotional Campaign Storefront Grid Specification that establishes product hierarchy, automated sorting rules, dynamic badging, and out-of-stock failover logic across digital sales channels.

Method

  1. Map inbound user intent from {{traffic_source_channels}} to category landing grid views to ensure narrative consistency with {{campaign_theme}}.
  2. Tier {{featured_tier_skus}} into primary spotlight, secondary grid, and impulse footer placements based on unit margins and stock depth.
  3. Define algorithmic collection sorting rules balancing margin contribution, conversion rate, and inventory sell-through pace under {{discount_structure}}.
  4. Design automated fallback triggers that swap hero grid slots to secondary products once stock breaches {{inventory_cap_threshold}}.
  5. Integrate {{urgency_mechanics}} (e.g., low-inventory indicators, real-time demand flags) into specific grid tile coordinates.
  6. Establish faceted filter defaults and navigation taxonomy adjustments to minimize time-to-cart for promotional shoppers.
  7. Formulate cross-device responsive grid variations (e.g., 2-column mobile versus 4-column desktop slotting hierarchies).

Constraints

  • MUST define explicit fallback SKU rules for when featured items hit {{inventory_cap_threshold}}.
  • MUST NOT display urgency badges on products possessing over 45 days of forward stock supply.
  • Grid sorting criteria must remain platform-agnostic across enterprise commerce engines.
  • Promotional discount calculations must strictly reflect {{discount_structure}} across all multi-buy and bundle configurations.

Output format

  • Storefront Grid Architecture (Header, navigation presets, hero carousel configuration)
  • Promotional Slotting Matrix (Table: Grid Position 1-16, SKU Tier, Badge Logic, Fallback Rule)
  • Dynamic Inventory Trigger Logic (Condition-Action specification table for real-time stock events)
  • Channel-Specific Routing Overrides (Rules for inbound traffic variations across 3 channels)

Self-review

  • Verify that fallback logic triggers instantly when inventory falls below {{inventory_cap_threshold}}.
  • Ensure promotional badge copy accurately conveys {{discount_structure}} without ambiguous terms.
  • Confirm that slotting priority maximizes gross margin revenue rather than unit volume alone.
AuraScore breakdown
83/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.

Robustness5/5 · Strong

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-merchandising
business-strategy-marketing-sales
promotional-merchandising
storefront-grid
digital-merchandising