Acceptance criteria say when a story is done. Written as scenarios in the Given / When / Then pattern, they are clear enough to test and can even be automated:
- Given the starting situation: "Given a customer has a delivered order from 10 days ago"
- When the action: "When she requests a return"
- Then the result you can check: "Then she receives a return label by email within 5 minutes"
Use And to add more of the same kind: "And the order shows the status Return requested".
One scenario is rarely enough. Write the happy path first, then the unhappy paths: what if the order is older than 30 days, the card has expired, the basket is empty, the item was a final-sale item? Edge cases found while writing criteria are found before anything is built, which is the cheapest time to find them.
Keep each Then observable: "Then the refund is shown as Paid", not "Then the system works correctly".
A happy-path scenario.