A store customer is a buying tribe or a team member making a personal purchase. 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 or verified bank account can be used for renewals. If a tribe is on a subscription with nothing saved, every renewal will produce an unpaid order that somebody has to chase.
Open Network Store → Customers → customer → Payment Methods to see saved cards and bank accounts. Bank accounts show their bank name, last four digits and verification status. When ACH is enabled, this section also offers Add Bank Account. Send Request Payment Method when the customer needs to provide their details remotely 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.