Network Store Reporting
Customer records
What a store customer is, what their record holds, and using it to answer questions about a tribe in one place.
Last updated September 2, 2026
A store customer is a buying tribe — the entity you invoice. Customers are created as tribes start buying, so you do not set them up in advance.
What the record holds
| Section | What it tells you |
|---|---|
| Orders | Everything they have bought, paid and unpaid. |
| Subscriptions | What renews, when, and for how much. |
| Payment methods | What is saved to charge. An empty list here is why renewals fail. |
| Balance | What they owe, and how overdue it is. |
| Credits | Any credit raised against the account and whether it has been applied. |
It is the screen to open when a tribe asks anything about their account, because it answers "what have they bought, what do they owe, and can we charge them?" in one place.
Payment methods on the record
A saved card is what renewals charge against. If a tribe is on a subscription with nothing saved, every renewal will produce an unpaid order that somebody has to chase.
You cannot add a card for them, and should never try — send a card request so they enter it themselves through a secure link.
Answering a query
- "What is this charge?" — find the order and read its items and answers.
- "Why has it gone up?" — open the subscription and read the amendments between the two renewals.
- "We already paid" — check whether the payment was recorded. Payments made outside the platform do not appear until someone enters them.
- "Cancel it" — cancel the subscription first, then deal with the orders.
- "Send me everything" — send a statement.
Before you chase
Open the customer first. Half of apparent non-payment is a card that expired, and the other half is a payment that arrived by transfer and was never recorded. Both are visible here, and neither is the tribe's fault.