Skip to content

Customers, Returns, Subscriptions and Alerts

Customers

Customers lists everyone the shop knows about: people who have visited, signed up or ordered, and your team.

  • Customers in the menu opens the list on the Customers chip: everyone who has placed an order (free orders count), donated or subscribed, whether or not they have an account. Each of them has a green Customer badge wherever they appear in the list. Someone who orders by checkout shows up straight away. People from before this, and orders taken another way (such as on the till), donations and subscriptions are picked up within the hour. Baskets, failed payments and cancelled orders don't make someone a customer.
  • The other chips narrow it to All, Registered (has an account, whether or not they've ordered), Guests (gave their details, usually at checkout, but has no account), Visitors (never gave their details), Staff (anyone with an admin role) and Banned.
  • Search matches a name or email address. Sort by Last seen or by when someone Joined.
  • Roles show as names ("Content editor", "POS agent"), not codes.
  • Download email list opens Contacts' Export subscribers panel: a CSV of everyone subscribed to one list, for your mailing tool, with each person's unsubscribe link (admins only; the file is deleted after 7 days). See Customer Messaging and Consent.
  • Messages from customers (the contact form, help with an order, email replies) are under Customers › Contact requests; see Customer service inbox.
  • Tick people and use Mark selected for deletion to queue them for deletion. You are asked to confirm first.
  • List and Map at the top switch how they're shown. The map keeps the chip and search you chose and shows everyone in it who can be placed: at their latest order's address (by postcode), or else where they last browsed from (roughly the town, from their internet connection). People in the same place share one circle, bigger the more there are; click it for their names and links to their pages. The tick boxes under the map show or hide each kind of place, so you can see only order addresses or only where people browsed from. An order's address is placed by postcode shortly after the order is submitted; orders from before this were not looked up, and are placed when you open that customer's page. Until then those customers show where they browsed from.

Old links such as /admin/users/list/registered still work and land on the matching chip.

Visitors are tidied up. A visitor who hasn't been seen for 30 days and never gave their details is marked for deletion and removed within the hour. Anyone with a placed order is kept. A shopper's name and email reach their account when they type them at checkout. Some older customers have them on their orders only, so they show as anonymous visitors; the hourly tidy-up gives each of them the details from their latest order, after which they show as a guest (and may appear as a duplicate account to merge).

A customer's page

The title is the person's name (their email if they have no name, "Anonymous visitor" if neither), with a badge for what they are. The top shows their orders and total spent (cancelled orders and failed payments left out, refunds taken off), plus donations and subscriptions when they have any, and a warning if they have a basket in progress.

Below that, Recent orders lists their last three placed orders with status and total (See all for every order and basket). Gift Aid (only when they have Gift Aid declarations or Gift Aid donations) counts their declarations and Gift Aid donations and what can be reclaimed from HMRC. Then three short timelines: Recently viewed products on one side, and Activity (the last few things they did, newest first: pages viewed, items added, checkouts and orders; the same thing done several times in a row is one line, such as "Viewed account/donations ×5") and Likes on the other. Each has See all in its header for the full list, where the Activity list also names the browser used for each event.

Recently viewed products and likes show each item's picture and name; a liked product or collection links to its editor, and See all on Likes also links to the item in the shop.

Signed-in devices (for customers with an account) lists the browsers they're kept signed in on with "Remember me", and when each was last used. Sign out everywhere signs them out on every browser and phone straight away, including ones signed in without "Remember me": those sessions end on their next page. Nothing else on the account changes; they just have to sign in again. A "Remember me" login unused for 30 days (3 days for staff with any admin role) no longer signs anyone in and is removed. Shops using central sign-in also keep a session on the sign-in server, which this doesn't end.

Marketing shows the email lists the customer is on and links to their contact, which has every consent decision they made; the subject access request has them all. See Customer Messaging and Consent.

Also on file (only when there is something) lists their fundraisers with their status, their newest reviews with the rating, product and status, their restaurant guest profile (visits and no-shows) and how many event tickets their orders issued.

Marketing (when the customer has a contact record) shows which of your mailing lists they are on, with a link to their contact. Marking a customer for deletion offers Also erase their marketing contact and enquiries, ticked by default. Everyone you can email, including people without an account, is under Customers > Contacts: see Customer messaging.

Contact details shows what they gave you, then the browser they last used (an icon and, for example, "Chrome on macOS"; hover for the full browser string), where they last browsed from and its time zone. Edit corrects their title, name, email, phone numbers and date of birth; leave a box empty to remove that detail. A customer can have several phone numbers: the first is their main number (used where only one fits, such as kitchen tickets), Make main moves another to the top, and Add a number adds one. A number entered twice is kept once. The email is where you contact them: if they have an account they still sign in with the same login. Orders they have already placed keep the details they were placed with. A map marks their latest order's delivery and billing addresses (one pin when they're the same place) and where they browsed from: the latest place solid, earlier ones fainter. Hover over a pin to see what it is.

Addresses lists the customer's saved address book on this shop, the addresses checkout offers them again: a name they gave it, the address, "Default delivery" and "Default billing" badges, and when it was last used in an order. With no saved addresses it says "No saved addresses". Staff can correct a customer's book:

  • Add saves a new address; Edit changes one. The shop's required address fields apply as they do at checkout, and if any are missing nothing is saved and the page names them.
  • Make default delivery and Make default billing choose the address checkout fills in first.
  • Remove asks you to confirm, then takes the address out of their book. A removed default passes to their most recently used address. Orders already placed keep the addresses they were placed with.

An address staff have added or changed shows "Changed by staff on" with the date, so the customer's own book can be told apart from a correction. The note goes when the customer next saves that address themselves. Anyone who can edit contact details can manage addresses.

  • Addresses are placed by postcode, at the middle of the postcode, using postcodes.io. Only UK postcodes are looked up; an address in another country gets no pin. Each address is looked up the first time someone opens the customer's page, and the position is saved on the order, so it isn't looked up again.
  • Where they browsed from comes from their internet connection, so it is approximate (usually the nearest town) and only recorded on live sites.

The ... menu holds the less common actions:

Action What it does
Subject access request Opens the printable data pack. See Subject Access Requests
Review duplicate accounts Appears when other accounts share the same email, and leads to the merge screens
Ban customer / Remove ban Blocks or restores access. You are asked to confirm
Mark for deletion Queues the account for deletion in the next clean-up

Duplicate accounts

When accounts share an email address, Review duplicate accounts compares their names and main phone numbers. If they agree, Merge automatically folds them into one account (a registered one if there is one). If they don't, Merge by hand asks you to pick the account to keep and the right name and number. Every other phone number is kept on the merged account.

What moves. Everything the duplicates have on this shop goes to the kept account: orders, subscriptions and invoices, donations and Gift Aid declarations, likes, reviews, fundraiser requests, uploads, restaurant guest records, POS staff profiles and devices, fulfiller links, promotions assigned to them and the promotions they've used (so a once-per-customer offer stays used), and page views. Where an account can only have one of something, the two are combined rather than one being dropped:

  • Baskets: every open basket, the kept account's own included, is combined into the one it's using, as when a shopper signs in with items in their basket: the same product adds to the quantity. Anything out of stock or no longer sold goes to saved-for-later instead. The basket is repriced the next time the customer opens it. A basket mid-payment is left alone.
  • Saved-for-later basket: the items are combined, each product once.
  • Recently viewed: both lists are woven together, newest first.
  • POS profile: the person keeps every permission and location either profile had, and the higher sale limit.
  • Roles: the kept account gets every role the others had, so a merged staff account keeps its access. Superadmin is never carried, and a superadmin account can't be merged into another. A ban goes with the person and, as banning does, replaces every other role, so you're asked to merge by hand when only some of the accounts are banned. Only accounts with the same email can be merged.
  • Customer details: anything the kept account has blank (name, phone number, date of birth, default addresses) is filled in from the duplicates. Every other phone number is kept.

A hundred at a time. A customer who checks out as a guest again and again gets an account per checkout, so one email can have hundreds. A merge takes up to 100 of them into the account you keep, and the duplicates page says how many are left: merge again for the rest. Accounts already merged aren't offered again.

All or nothing. A merge either completes or changes nothing: if something goes wrong part way, everything it had done is undone and you can simply try again. Only one merge runs on a shop at a time; a second one started meanwhile (a double click, or another admin) is turned away with "Another merge is running on this shop".

One login per email. An email can only be registered once, whatever its capitals: "[email protected]" signs in to the account made as "[email protected]". If two accounts can sign in with one email (made before this was enforced), they won't merge automatically: Merge by hand asks you which one to keep, and the other can no longer sign in.

One shop at a time. An account can be shared by every shop in its group, so a merge only moves this shop's records. A duplicate that still has orders or other records on another shop is kept for that shop; it is only marked for deletion when nothing is left anywhere.

Names are compared ignoring capitals and spaces, so "Kevin", "KEVIN" and "Kevin " (with a trailing space) count as the same name. Phone numbers are compared on their digits, so "07713 066473" and "+44 7713 066473" count as the same number.

Names, titles and phone numbers are tidied whenever a customer or an order is saved: at sign-up, at checkout, and when you edit them. Spaces at the start and end are removed (non-breaking spaces included), as are invisible characters; the spacing inside stays as the customer typed it, so "07700 900123" is kept as it is. Older accounts are tidied the next time they are saved.

Edit roles (admins only) opens a dialog. Everyone keeps customer access; tick what else the person can do in the admin. Before you can edit, you are asked to confirm it's you, with a passkey, your password or the account you sign in with (Google, Apple or Microsoft), whichever your account has. Confirming lasts a few minutes, so several edits in a row only ask once. A Superadmin role is never removed by editing someone's other roles.

Email campaigns, sending domain and the do-not-email list

Three entries under Customers run email campaigns:

  • Email campaigns lists your campaigns by status (draft, scheduled, sending, paused, sent, cancelled) with how many went out and arrived. A draft opens the editor; anything else opens its report. Admins only.
  • Sending domain is where you set up the address campaigns are sent from, and see whether it's ready.
  • Do-not-email list holds the addresses campaigns will never go to: people who unsubscribed or complained, addresses that bounced, and any you add.

Finance and other staff roles can't open them. See In the admin for how each screen works.

Returns

Orders > Returns lists return requests with their status, value and how long ago they were asked for. A return's page shows where it has got to (approval, items on their way, received, refunded), the items, the reason, the history, and a Next step card with the one action that applies:

State Next step
Awaiting approval Approve and send instructions (or Decline in the header)
Requested Mark as received, choosing whether the items go back into stock
Received Refund. You type the amount in pounds, and it defaults to the value of the returned items. Admins only

Reject is in the header while a return is still open.

When the shop emails return labels (Settings › Shipping and labels › Email return labels), approving a return also buys a prepaid return label and emails it to the customer. The return's Return label card lists the labels bought and has Send a return label (or Email the label again) while the items are on their way. See Parcel Labels.

Subscriptions

Subscriptions (when subscriptions are switched on) shows the customer's name, product, status, amount, how often it repeats and the next payment date. Filter by status or product above the list.

Sync from Stripe catches up recent changes. Full resync re-reads the whole of Stripe, so it asks you to confirm first and can take several minutes. The page shows when it last synced.

A subscription's page has the invoices, plan, billing dates, customer and Stripe references. Pause, Cancel at end of period and Resume are there, each with a confirmation.

Alerts

The bell in the top bar opens a short list; Alerts shows the full history. Filter to Unread, use Mark all as read, or remove an alert with the cross. Each alert links to the order, return or customer it is about.