Network Store Orders
Amendments: the change history behind every subscription
The record of what changed, when and who did it — and how to use it to answer "why has my bill gone up?".
Last updated September 2, 2026
Every change to an order or a subscription is recorded as an amendment. It is a plain audit trail, and it is the fastest way to answer a billing query without guessing.
What gets recorded
| Amendment | Recorded when |
|---|---|
| Order placed | A new order is created, whether bought or assigned. |
| Unit added | A seat is added to a subscription. |
| Unit updated | A seat's details are changed. |
| Unit removed | A seat is removed. |
Each carries what changed, when, and who did it — including whether it was the tribe acting for themselves or someone in your team acting on their behalf.
Answering "why has my bill gone up?"
This is what amendments are for. A renewal is priced against the seats in use at that moment, so a bill that moved means the seats moved. The amendment list between the two renewal dates shows exactly what.
- Open the subscription and find the two renewal dates either side of the change.
- Read the amendments between them — added seats are the usual answer.
- Check whether the seats crossed the included allowance. Seats inside it change nothing; seats beyond it each add the overage price.
- Reply with the dates, the seats and who added them.
Changes waiting to be actioned
Some amendments need your team to do something — a seat added that needs provisioning, details changed that need applying somewhere else. The dashboard's Changes to action tile counts these, and it is the queue to keep at zero.
What it is not
Amendments are a record, not a workflow. Recording one does not bill anything, undo anything, or notify anyone by itself — the billing follows the seats at renewal, and the amendment simply explains it afterwards.