10. Customer Management
[← Order Processing SOP]/09-order-processing-sop/ · [Index]/00-index/
10. Customer Management
Verified against: Medusa admin dashboard 2.18.0 (customer-create, customer-edit,
customer-detail, customer-groups — source-read directly), plus .ai/features/customers.md.
Customer profile — what’s real
The customer record itself (customers module) is entirely Medusa’s default — inherited from
the Next.js starter theme, nothing custom-built (.ai/features/customers.md). Fields shown on
a customer’s detail page:
- Name (First/Last), Company, Phone, Email
- Guest or Registered status badge — a guest is someone who checked out without an account; a registered customer has a real login
- Order history (a list section on the same page)
- Customer Groups the customer belongs to
- Addresses
How to create a customer
Fields (via Customers → Create):
| Field | Required? |
|---|---|
| REQUIRED | |
| First Name | OPTIONAL |
| Last Name | OPTIONAL |
| Company | OPTIONAL |
| Phone | OPTIONAL |
INFO: There is no password field. Creating a customer here does not give them a way to log in — it just creates the record (e.g. for a phone/offline order). A real login only exists once the person registers themselves on the storefront with that same email, at which point their status badge flips from Guest to Registered.
How to edit a customer
Same fields as creation, with one real restriction:
IMPORTANT — verified, not assumed: the Email field is shown but disabled once a customer is registered — the exact tooltip text is “The email address cannot be changed for registered customers.” If a customer needs their email changed, this admin form cannot do it directly for a registered account.
How to view order history
The customer’s own detail page has an Orders section listing their past orders — click through to any of them for the full [Order Management]/08-order-management/ view.
How to handle duplicate customer records
There is no merge tool in this admin — Medusa doesn’t support combining two customer records into one. Real options, given what exists:
- Manually edit one record’s details and treat the other as stale (does not truly merge order history onto one profile)
- Delete the duplicate — a real, permanent action (confirmation requires typing the customer’s email to confirm; the dialog’s own words are “This action cannot be undone”)
TO BE CONFIRMED: what happens to a deleted customer’s past orders — whether they remain intact under the deleted customer’s ID or are otherwise affected — was not verified as part of this wiki. Do not delete a customer with real order history without confirming this first.
[PROPOSED] — a documented process for preventing duplicates in the first place (e.g. checking by email/phone before creating a new record for a phone order) doesn’t exist yet as a business policy.
Customer Groups
A separate, real feature — Customers → Customer Groups. Fields: just a Name at creation; customers are added to a group afterward via a separate “Add Customers” action.
INFO: No customer group has ever been created for this store. Groups only become useful once paired with [Price Lists]/02-admin-dashboard/#price-lists (e.g. a wholesale group with its own pricing) or customer-restricted [Promotions]/11-coupons-and-discounts/ — neither of which is used today either.
Privacy note
This is real personal data (name, email, phone, address, order/payment history). Only look up what’s needed for the task at hand — there is no access-restriction system in this admin beyond the single-admin-login limitation already noted in [Section 1]/01-getting-started/#admin-roles; treat this as a process discipline, not something the system enforces.
[← Order Processing SOP]/09-order-processing-sop/ · [Index]/00-index/ · [Next: Coupons & Discounts →]/11-coupons-and-discounts/