Customers
Save customer details, understand customer activity, and reuse recipients across invoices and payment links.
The Customers page brings together people and businesses associated with the active organization. It helps you reuse contact details and understand where paying customers came from.
Two customer groups
Seev keeps manually saved contacts and paying customers conceptually separate:
| Group | Meaning |
|---|---|
| Saved customer | Added manually for an invoice or payment link. They may never have paid. |
| Paying customer | Appears after a storefront, invoice, payment-link, POS, or API payment can be associated with real customer details. |
This prevents a contact you added while preparing a quote from being mistaken for a paying customer.
Add a reusable customer
- Open Customers.
- Select Add customer.
- Choose Company or Individual.
- Enter the name and any available email, phone, address, and city.
- Create the customer.
The saved customer becomes available when you create an invoice or payment link.
You can also add a customer from those creation forms without leaving your work.
What appears in the customer snapshot
The snapshot helps you see total and recent customers and supported sources such as storefronts, invoices, and payment links. It is a business overview, not a wallet balance or transaction total.
Customer list
The customer table keeps the avatar and customer identity easy to scan. Open a row to inspect available contact information and associated payment activity.
When a name is not available, Seev uses the best identifier it has, such as email, phone, customer ID, or recipient ID.
POS customers
POS orders begin with generic customer details because a walk-in merchant should not need to collect a full profile before creating the order. On the checkout screen, the payer can provide a receipt email.
Generic placeholder details are excluded from customer analytics. If the payer supplies an email already associated with previous activity, Seev can group the payment with that customer.
API customers
Customers derived from Seev API transactions appear in the Developer overview. They are separated by sandbox and production and are currently read-only. See API Customers.
Avoid duplicate customers
- Search before adding another record.
- Reuse an existing customer from invoice and payment-link forms.
- Enter the email consistently; it is often the strongest matching field.
- Do not use a generic team email for unrelated customers.
- Do not add POS placeholder details manually.
Organization boundaries
Customers are not automatically shared between organizations. If a customer appears missing, confirm the active organization before recreating them.
Common questions
Why is a saved customer not in paying-customer totals?
They have not yet completed a payment that can be associated with the record.
Why is a POS customer missing?
The payer may not have provided a real receipt email. Placeholder POS identities are intentionally excluded.
Can I edit API customers here?
Not currently. API Customers is derived from transaction data and is read-only.