> ## Documentation Index
> Fetch the complete documentation index at: https://www.twicecommerce.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Test your processes

> Run your own processes on your own data, unaided, and check what the customer receives.

Step 5 of [migrating from TWICE 1.0](/docs/guides/migration/overview). Run your own processes on your own data, **without help from TWICE**. If you need someone on a call to complete a case, your staff cannot do it on the day either.

Each case must produce **what the customer receives**, not only a correct record in the admin. A confirmation that renders correctly in the admin and never arrives in an inbox is a failure you will otherwise find on your busiest morning.

## The cases

| Run this                                  | It has passed when                                                                                                                |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| An order through your online store        | The confirmation email arrives with the correct dates, price and collection details.                                              |
| An order created in the admin             | You have assigned a customer, a listing and stock items to the order.                                                             |
| A handover                                | The units are marked out, and you know how to start an order.                                                                     |
| A return                                  | Items come back into stock, and you know how to close an order.                                                                   |
| A damaged return                          | The unit leaves availability and the cost is recorded. Internal reservations are created at **Inventory → Stock items → Events**. |
| A late return or no-show                  | You can see it, know how to charge for it, and can handle conflicts with other orders.                                            |
| An extension                              | Dates and price update without releasing the item, and you know how to process the unpaid balance.                                |
| A cancellation                            | The order closes and the customer receives the notice. You know how to process a refund.                                          |
| A refund                                  | The money moves and the customer receives the notice.                                                                             |
| A deposit taken and released              | Both work on a real card.                                                                                                         |
| A document — agreement, waiver or receipt | It renders correctly with your business and order details.                                                                        |

Cases below the handover row only apply if you take dated bookings — an extension or a late return has no meaning where the item never comes back. Skip the ones that do not describe anything you sell, and say in writing which you skipped, so nobody later assumes they passed.

Run each case as the person who will actually do it. A manager completing a return proves the software works; it does not prove the counter staff can do it.

## When something fails

A failed case is a normal outcome at this stage and a cheap one. Fix it, or write down the workaround and make sure the staff who need it know — an undocumented workaround is the same as an unfixed failure.

Archive the test orders before you go live, under **Settings → Archived assets**.

## Done when

* Every case above has been run by your own people.
* Each produced its customer-facing output in a real inbox.
* Anything that failed is fixed, or has a written workaround your staff know about.
* Your reports show the test orders correctly.

## Related articles

<CardGroup cols={2} className="doc-rows-condensed">
  <Card title="Take an order in admin" href="/docs/guides/orders/take-an-order-in-admin">
    Creating an order from the admin.
  </Card>

  <Card title="Handle a return" href="/docs/guides/orders/handle-a-return">
    Closing an order and bringing stock back.
  </Card>

  <Card title="Refund an order" href="/docs/guides/orders/refund-an-order">
    Moving money back to a customer.
  </Card>

  <Card title="Migrating from TWICE 1.0" href="/docs/guides/migration/overview">
    The full sequence this step belongs to.
  </Card>
</CardGroup>