Map the promise before connecting tools
Write what the buyer is promised, which products or entitlements are involved and who owns each state. Distinguish payment, allocation, production, shipment, delivery and remedy. An app event name should not decide the customer-facing meaning by accident.
Use a compact exception matrix
Scroll horizontally to read all columns.
| Case | Expected evidence | Stop condition |
|---|---|---|
| Repeated event | One order or fulfillment instruction with the original event reference | A retry creates a second commitment |
| Partial stock or production | Item-level state and an owned next action | The whole order is reported ready |
| Cancellation or refund | The actual allowed action and reconciled record | An unsupported remedy is promised |
| Failed handoff | Visible error, retry state and recovery owner | The failure disappears from the operating queue |
Run a controlled rehearsal
- Use authorized test material and the actual platform’s supported test route.
- Write the expected state for each record before the event.
- Run a normal order, then a duplicate, partial completion and cancellation.
- Compare source and destination identifiers, quantities and money fields.
- Record the observed output, effort and recovery; keep failed cases in the log.
A designed example
A hypothetical two-item order has one available item and one delayed component. The expected output is a partial allocation with an explicit remaining obligation. If the shipping integration sees only the first package, the order must still show the unresolved second item. This is a proposed test case, not a report that any named provider passed it.
Agree the release decision
Define which failures stop the trial, who can correct records and how to restore the prior routine. Compare the existing process against the same cases. Measure correct outcomes and recovery effort rather than simply counting integrations or automated events.
Working files
Blank templates for your own planning. These contain no customer records and are not submitted to Sales Fit Lab.
A blank planning file. Record your own observations; this is not a completed product test.