Enterprise Hardware Bundle and Cross-Sell Merchandising Spec
Architect an e-commerce bundling and accessory cross-sell specification for enterprise IT hardware.
Use this template when configuring digital commerce checkout paths and configuration pages for technology hardware. It standardizes bundle discounts, compatibility rules, and dynamic recommendation logic.
Role: Senior E-Commerce Hardware Merchandising Lead specializing in enterprise IT configuration and accessory bundle architectures.
Context
- Core Hardware SKU: {{core_hardware_sku}}
- Compatible Accessory List: {{compatible_accessory_list}}
- Target Buyer Segment: {{target_buyer_segment}}
- Target Margin Threshold: {{margin_target_percentage}}
- Cart Value Incentive: {{cart_threshold_incentive}}
- Active Campaign Period: {{promotional_season}}
Task
Author a dynamic bundling and cross-sell merchandising specification for {{core_hardware_sku}} to maximize attachment rates of {{compatible_accessory_list}} while safeguarding {{margin_target_percentage}} during {{promotional_season}}.
Method
- Map {{core_hardware_sku}} technical dependencies against items in {{compatible_accessory_list}}.
- Establish bundle qualification rules, tiers (Essential, Pro, Enterprise), and discount curves.
- Define real-time compatibility checks to prevent incompatible accessory pairings in the cart.
- Design PDP bundle selector UI logic, pre-checked accessory defaults, and tier visual styling.
- Specify cart-drawer interstitial cross-sell triggers anchored on {{cart_threshold_incentive}}.
- Formulate margin-protection guardrails ensuring total bundle margin never drops below {{margin_target_percentage}}.
- Define fallback SKU logic when individual bundle accessories experience inventory stockouts.
Constraints
- Must maintain explicit inventory compatibility rules between all hardware components.
- Must provide exact mathematical discount thresholds matching {{margin_target_percentage}}.
- MUST NOT suggest accessories that require unlisted third-party adapters or licensing.
- MUST clearly differentiate self-serve buyer options from enterprise quote-request triggers for {{target_buyer_segment}}.
Output format
- Bundle Configuration Architecture (table: Bundle Tier, Included SKUs, Base Price, Discounted Price, Net Margin)
- Dynamic PDP Merchandising Rules (bulleted logic for pre-selection, error messaging, and tooltips)
- Cart Threshold & Cross-Sell Logic (trigger condition, recommended SKU, {{cart_threshold_incentive}} messaging)
- Out-of-Stock Fallback Matrix (table: Primary SKU, Substitute SKU, Fallback UI behavior)
Self-review
- Does the bundle pricing maintain the {{margin_target_percentage}} threshold across all variations?
- Are compatibility conditions between {{core_hardware_sku}} and {{compatible_accessory_list}} explicit?
- Is the specification ready for immediate implementation in an e-commerce catalog rule engine?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.