01
Specify required order context
Document the identifiers, timestamps, currency context, customer reference, product or collection facts, discount context, payment or fulfillment state, and campaign markers actually needed by the policy.
Collect only what the program needs and define retention and access boundaries for that data.
02
Handle delivery realities
Events can arrive more than once, out of order, or after temporary failures. Intake should identify duplicates, preserve relevant source timing, retry safely, and avoid turning transport behavior into multiple customer outcomes.
03
Separate intake from decision
Receiving an order event should not automatically mean the customer qualifies. Store the source evidence, then apply the current approved policy in a distinct decision step.