Use explicit decision states
Define what approved, declined, pending, held, duplicate, changed, reversed, and errored mean for the program. Avoid one catch-all status that hides whether a case is waiting for data, policy review, or provider action.
PCXProgram operations / decisions
Decision workflows translate Shopify order facts into program outcomes. They should distinguish clear cases from exceptions and preserve enough context for support, finance, and governance review.
Define what approved, declined, pending, held, duplicate, changed, reversed, and errored mean for the program. Avoid one catch-all status that hides whether a case is waiting for data, policy review, or provider action.
Manual review should show the relevant evidence, permitted choices, reason categories, and escalation route. Record who made the decision, when it occurred, and which policy or exception authority applied.
Retries and reprocessing should not create duplicate customer communication or downstream requests. Link every action to a stable program record and define which transitions are reversible.