Customers

Manage → Customers. Search by name, email or phone.

The columns are Name, Email, Phone, Orders, Spent, Tags.

Where customer records come from

Two ways:

• Automatically, after their first order. You do nothing.
• You add them, with New customer — useful when importing from an older system, or when you take orders over the phone.

The empty state says exactly this: "Add your first customer or they'll appear here after their first order."

What a record holds

Name and Email are required. The email must be a valid address and unique within this store — a clash gives you "A customer with this email already exists in this store." Two different stores can hold the same email, because they are two separate customer lists.

Phone, Tags (type and press Enter or comma), and a Note.

Addresses — as many as you like; one of them is the Default. Each holds a full name, phone, two address lines, city, province/state, postal code and country.

The note is internal, and it stays here

The Note field is for your colleagues: "Internal note about this customer…".

It is not exposed through the public API. Support notes are written for people in the building, not for whatever a partner integration might display back to the customer. If you need something an outside system can read, use Tags rather than the Note.

Orders and Spent

Both columns are computed at read time, from that customer's actual orders. You do not enter them and you cannot edit them.

Which means they always agree with the order list — there is no stored number that can drift away from reality over time.

Deleting a customer

Delete customer permanently removes the record and its data, and cannot be undone.

Think first: their orders keep a snapshot of the buyer's details as of the moment of purchase, so old orders still read correctly after the record is gone. But the link between those orders and a customer record is lost, and cannot be rebuilt.

Through the API

GET, POST, PUT, DELETE /api/v1/customers under the customers.read / customers.write scopes. ordersCount and totalSpentCents come back in the response, so a loyalty integration does not have to pull every order per customer. See The public API.