Customers
Save reusable customer records and find the people who have paid the active organization.
The Customers page holds the people and businesses attached to the active organization. Use it to reuse contact details when billing someone, and to look up what a paying customer has bought.
The page splits into two tabs, because a contact you typed in while preparing a quote is not the same thing as someone who has actually paid you.
| Tab | What it lists |
|---|---|
| Activity customers | People who have paid through your store, through an invoice, or through a payment link. Seev builds these records from payment activity, so you cannot create or edit them here. |
| Saved customers | Records you added by hand, available to reuse when you create an invoice or a payment link. A saved customer may never have paid you. |
Add a reusable customer
Open Customers, select Add customer, fill in the form, and select Add customer again to save. Seev switches you to the Saved customers tab and confirms with "Customer created successfully".
Every field is required, including the ones you might expect to be optional.
| Field | Type | Required | Description |
|---|---|---|---|
| Full name | Text | Yes | The name that appears on invoices and payment links built from this record. |
| Yes | Also the strongest field Seev has for matching this person to later payment activity, so enter it the same way every time. | ||
| Phone | Text | Yes | Accepts an international format such as +233 24 000 0000. |
| Address | Text | Yes | Street address of the customer. |
| City | Text | Yes | City of the customer. |
| Type | Choice of Company or Individual | Yes | Defaults to Company. Choose Company when invoices should carry a company name, Individual when the buyer is a person buying for themselves. |
Leaving any field blank stops the save and shows "Please fill in all customer details." Nothing is submitted, so correct the empty field and select Add customer again.
If the save reaches Seev but fails, you get "Could not create customer. Please try again." and the modal stays open with your input intact. Retry once before assuming the record was created, then check the Saved customers tab so you do not save the same person twice.
You can also add a customer directly from the invoice and payment-link creation forms, which saves the same record without leaving the work in progress.
Find a customer who has paid you
Open the Activity customers tab. Narrow the list with the source filter, which offers All, Store, Invoices, and API, then search by name, email, or phone in the search box.
When a customer has no name attached to their payment, Seev falls back to the best identifier it holds, usually the email address, and shows the word "Customer" when it has nothing else. Search by email or phone in that case rather than by name.
Read the customer totals
Four tiles sit above the list: Total customers, Store, Invoices, and Payment links. These count activity customers by the source that produced them. They are hidden entirely until the organization has at least one activity customer, so an empty space here means no payments have been attributed yet rather than a loading failure.
These are counts of people, not money. For balances, open Accounts and Wallets.
Open a customer record
Select any row to open the customer. The record shows Lifetime spend alongside counts of orders, invoices, and API payments, then lets you filter the history through the Activity, Orders, Invoices, and API payments tabs.
Lifetime spend is a dashboard figure in major currency units, so GHS 100.00 displays as such rather than as a smallest-unit integer. It adds up paid invoices, orders that were not cancelled, and API payments in a successful state.
Lifetime spend is labelled with a single currency, taken from the customer's first invoice, order, or API payment. If one customer has paid you in more than one currency, the tile adds those amounts together and labels the result with only one of them. Open the tabs and read the individual amounts instead of trusting the total.
If the row opens on "Invalid customer", the link or URL you followed is malformed; return to Customers and select the row again. "Customer not found" means the record does not exist in the active organization, which most often means you are in the wrong workspace. See Organizations for switching.
Take payment from a walk-in customer
Point of sale, under Store, builds a cart and creates an order that produces a checkout link and QR payment options for a walk-in buyer. The POS order carries the store currency and the cart items; it does not ask you for the buyer's name or contact details, so nothing is written to Saved customers when you create one.
A payer who supplies a receipt email at POS checkout is attached to an existing customer record when that email already matches one.
If POS order creation fails you get "Could not create POS order." and the cart is preserved. Check that the store has at least one active product with stock before retrying, and see Troubleshooting for products that cannot be enabled.
Find customers created by API payments
Customers derived from Seev API transactions appear in the Developer overview, kept separate by sandbox and production, and are read-only. See API Customers.
Avoid duplicate customer records
Duplicates come from small inconsistencies rather than from anything the product does wrong, so a few habits prevent almost all of them.
- Search the Saved customers tab before adding a record.
- Reuse an existing customer from the invoice and payment-link forms rather than retyping the details.
- Enter the email address consistently, since it is the field most likely to link a payment to the right person.
- Avoid a shared team email address on records for unrelated customers, which merges people who should stay separate.
Customers are not shared between organizations. If a customer looks missing, confirm the active organization before you recreate them.
Troubleshooting
Why is a saved customer missing from the activity totals?
The tiles and the Activity customers tab count payment activity. A saved customer who has not completed a payment Seev can attribute to them will not appear there, which is expected rather than a failure.
Why can I not edit a customer in the activity list?
Activity customers are derived from payment records, so there is no edit control on them. Add a saved customer with the corrected details if you need a record you can reuse and change.
Why can I not edit API customers?
The Developer customers view is derived from transaction data and is read-only.
Why does a customer show only an email address?
The payment carried no name. Seev shows the best identifier it has rather than leaving the row blank.