Automatic vs manual refunds
Which refunds a person raises, and which ones the app records by itself.
User guide
Which refunds a person raises, and which ones the app records by itself.
Almost every refund is raised by a person. A few are recorded by the app as part of another step. Knowing which is which explains any refund row you do not remember creating.
Who can do this: the roles that handle refunds: the Administrator, Admin, Store Admin and Cashier. The steps below all work on every plan.
A return never pays out by itself. Approving a return lets you click Process refund, where a person chooses the method and amount, up to the return's value. Money moves only when someone moves it.
When an edit lowers an order's total below what the customer paid, the order shows Refund due. A person clicks Refund excess in the order's Payments section to pay it back. See Refunds.
An order can have a negative total, for example an exchange where the store credit is worth more than the new goods. When you complete such an order at checkout, the summary offers Create refund of the amount for negative balance.
The app then creates the refund in the same step, already completed, with the source Manual. You decided to create it, but no separate refund form was involved.
A store credit's status follows the order that spends it. Adding it to an order holds it. The order's payment completing marks it Completed. Cancelling the order puts it back to Pending. Only the app makes these moves. See Store credit refunds.
Every refund row shows its Source and its method:
| Symptom | Cause | Fix |
|---|---|---|
| A completed refund with no return appears after a checkout. | The order had a negative total and the refund box was ticked. | Open the refund. Its page shows the order it came from. |
| A store credit changed status by itself. | An order spent it, completed, or was cancelled. | Open the refund and check Used in order. |