Customers

Manage → Customers. Search by name, email or phone. The columns are Name, Email, Phone, Orders, Spent, Tags.

Where customer records come from

Three ways:

• Automatically, after a first order. A shopper who ordered without signing in still gets a record — it wears a Guest badge until they create an account with that same email.
• The shopper registers on the storefront — see Customer accounts.
• You add them, with New customer — when importing from an older system, or taking 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 valid and unique within this store — a clash gives "A customer with this email already exists in this store." Two stores can hold the same email, because they are two separate customer lists.

Phone, Tags (type and press Enter or comma), a Note, and Addresses — as many as you like, one of them the Default.

Accepts marketing emails — only with real consent

The Accepts marketing emails switch decides whether the customer receives invitations to come back — the "back in stock" and "price drop" emails of Saved for later, for instance. The hint under it is the one thing to remember: "Turn on only with real consent — the consent timestamp is recorded by the system." That timestamp shows on the record (Subscribed at …) and is what you need when a marketing email is disputed. A record created by an order has it off — a purchase is not treated as consent.

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 a partner integration to display back to the customer. For something an outside system can read, use Tags.

The detail page

Click a customer to open their page: Contact, Stats (orders, spent), Default address, Tags & note, and that customer's Orders — with a way straight into the order list filtered to them. With the Loyalty app installed there is also a Loyalty points block, with the points history and an adjustment control.

Orders and Spent are computed at read time from real orders. You neither enter nor edit them, so they always agree with the order list — there is no stored number to drift.

Deleting a customer

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

Their orders keep a snapshot of the buyer's details as of the purchase, so old orders still read correctly afterwards. 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, totalSpentCents and marketingOptInAt come back in the response, so a loyalty integration does not have to pull every order per customer. See The public API.