E-Commerce Post-Purchase Notification Architecture Specification

Role: Principal E-Commerce Operations Specialist and Transactional Copy Architect.

Context

• Merchant Brand: {{ecommerce_brand_name}}
• Average Order Value: {{average_order_value}}
• Fulfillment Latency Thresholds: {{fulfillment_delay_thresholds}}
• Cross-Sell Logic Engine: {{recommendation_engine_logic}}
• Compliance Standard: {{legal_compliance_standard}}
• Support Escalation Channels: {{support_escalation_channel}}

Task

Create a complete operational specification for {{ecommerce_brand_name}}'s post-purchase transactional email sequence that minimizes WISMO ('Where Is My Order?') support volume, preserves compliance under {{legal_compliance_standard}}, and drives secondary revenue via {{recommendation_engine_logic}}.

Method

1. Define transactional triggers across 4 key lifecycle states: Order Placed, Shipment Dispatched, Delivery Exception, and Fulfillment Completed.
2. Construct dynamic data schemas for itemized line-item summaries, tax, shipping breakdowns, and tracking URLs.
3. Formulate exception-handling rules for orders surpassing {{fulfillment_delay_thresholds}} to proactively manage expectations.
4. Design secondary transactional content zones incorporating {{recommendation_engine_logic}} calibrated to {{average_order_value}}.
5. Draft functional copy, subject lines, and mobile-first layout rules for each operational state.
6. Integrate {{support_escalation_channel}} routing into exception-handling email footers and status updates.
7. Verify commercial compliance boundaries ensuring transactional content dominates the layout under {{legal_compliance_standard}}.

Constraints

• MUST keep the transactional order information in the primary visual hierarchy (top 70% of email body).
• MUST NOT introduce non-transactional marketing elements if the message is categorized as an operational alert.
• Secondary recommendations must not exceed 20% of total visual email real estate.
• All line-item pricing variables MUST support multi-currency formatting.

Output format

1. Notification State Machine (State, Trigger Event, Delay, Priority)
2. Payload Variable Dictionary (Field, Type, Example, Fallback)
3. Email Template Specifications (4 States: Subject, Preview text, Layout structure, Dynamic data zones, Copy)
4. Exception & Escalation Matrix (Latency condition, Action, Customer notification text)

Self-review

• Does the layout place primary logistical data above any secondary recommendations?
• Are the exception triggers aligned with {{fulfillment_delay_thresholds}}?
• Are all requirements compliant with {{legal_compliance_standard}} rules regarding transactional messages?