Customers

Everything the store knows about one customer on one screen: the five summary tiles including the RFM group, recent and draft orders, the Customer panel with its three separate marketing consents, store credit that can hold a balance per currency, the More actions menu where merging, privacy requests and deletion live, and a timeline you can resend an email from.

A segment is a saved question about your customers rather than a saved list, so its members change as they do. Tanqory gives you two ways to write that question, a query builder and a form of Field, Operator and Value filters, and this article covers both, plus the panel that starts closed, the AI Refine field and what to do when it answers with nothing, the forty-nine fields you can filter on, and everything the row menu lets you do to a segment afterwards.

Creating a customer record by hand, from the Add Customer button to the saved record. Three fields are required and everything else can wait, the three marketing consents start unticked and are a record of what the customer agreed to rather than a way to opt them in, and the Save bar is on the form from the moment it opens.

Finding one customer and finding a group are different jobs with different tools. The search box matches name, email and phone and nothing else, it searches inside the tab you are standing on rather than the whole store, and the thing people most often type into it, a tag, comes back as No customers found rather than as an error.

A tag gives a group of customers a name so it is already assembled when you need it. This article covers where tags are set, one record at a time or in bulk from the list, what a tag is actually good for once it exists, and the one thing it will not do, which is answer the search box.

The Edit control on the Customer panel opens five things, not four: contact information, addresses, marketing consent across three channels, tax details, and adding the customer to a company. This walks each dialog, what it asks for, which fields are required, and which of them the store acts on without asking you again.

The Customers page is where most customer work starts, and four bands sit above the table before you reach a single row. This article covers what each band is for, the segment bar and its templates, saving a tab of your own, and the ways out of the page to one record or to a file. It also takes the two controls that are easy to miss entirely: the selection bar, which does not exist until you tick a row, and the counter at the foot that tells a short list apart from the first page of a long one.

Customer privacy is spread across three places in the admin: a settings page for what applies to everybody, the actions on one customer for what one person has asked, and a queue of requests waiting to be approved or rejected. This article maps the settings page row by row and says which of the three you want.

A map of the Customers area and which article covers each part of it, from the list page and its table to a single record, tags, segments, merging duplicates, store credit, export and privacy requests. The list is covered by two articles rather than one, and this says which takes which half. It also separates the two pairs people most often confuse, views against segments and tags against notes.

Bulk Edit opens the customers you ticked as a spreadsheet, one row each, so the same field can be changed across all of them without opening a single record. Five columns show by default and three more can be added, including the marketing consents. Nothing is stored until you select Save, and leaving by any other route discards the lot.

A balance a customer can spend with you instead of paying in full. It is held per currency rather than as one figure, so one customer can carry two balances at once, it can be taken back as easily as it is given, and the Enable store credit toggle in Settings is a different thing from the balance on a record.

The Customer accounts page has no Save button, so nothing tells you when you are finished with it. This walks its three parts in the order that avoids setting anything twice, starting with the account type, which the switches below it depend on.

Customer accounts turn a one-off buyer into someone who can sign in, see what they have ordered, start their own return, and spend a store credit balance. One settings page decides how much of that your store offers, and this explains what each part of it decides and which article covers it.

What belongs in a customer note and what does not, with examples of four kinds of context worth saving. It also sets the Notes card, which holds one standing description of the customer, against the Timeline below it, which is a dated feed of comments and activity, and walks through writing a note from the record.

Deleting a customer removes the record and everything personal on it, and keeps their orders with the personal information stripped out. The dialog will not let you through until you tick a box confirming you understand, and there is no undo afterwards. This covers what survives the delete, why Erase personal data is usually the right tool instead, and the one thing to do before you confirm.

When the same person has two customer records, merging moves one onto the other. The record you start from is the primary and keeps its customer ID and its email, so open the merge page from the record you want to keep. Tanqory refuses the merge outright if either record has an open order, an open draft order or a gift card with a balance, and the record you merge in is emptied rather than deleted.

A customer record holds a separate marketing consent for each of three channels: email, SMS, and WhatsApp. You read all three on the Customer card and change them in Edit marketing status, and because they record the customer's agreement rather than your preference, you change them only when the customer asks.

The Export dialog, control by control: the scope that decides who goes in the file, the two CSV formats, the twenty columns that all start ticked, and the summary that counts what you have chosen. The file is emailed to the address you signed in with rather than downloaded, and the dialog closes the same way whether it worked or not.

The Authentication panel is the only place that shows which sign-in methods your store offers, which makes it worth opening even when you are not changing anything. This covers reading it, what Shop and the social providers each need, and what it means when a switch cannot be moved.

A customer record is edited in several places, and this is the map of which is which. The Edit menu on the Customer panel holds the five forms for what the customer told you; tags, notes, store credit, metafields, merging and deletion each have their own control elsewhere on the page; and the figures at the top are worked out from the orders and cannot be edited at all.

A customer can ask to see the personal data your store holds about them, or ask you to remove it. Both are handled from the More actions menu on their record, and the requests that arrive from your storefront queue up under Customers > Data requests with a due date and Approve and Reject on each one. An erasure is scheduled rather than immediate, which is the window you have to call it off.

The table on the Customers page shows five columns out of twenty. Manage columns turns the other fifteen on, and the same panel reorders them by dragging. Each column header carries a menu holding two sorts, Copy column and Hide column. This covers which columns are worth adding for which job, what the note icon beside a row means, and why the layout you build here is worth building once.

Account features looks like five settings and is really three different kinds of thing: two shortcuts to other pages, one panel, and two switches that change something here. None of it is required, so this covers what each row is for and what turning it on gives your customers.

A catalogue of what the store writes into a customer's Timeline: orders, returns, sent emails, tags, addresses, store credit and privacy requests, in the wording each entry actually uses. Some name the thing they changed and some only say that something changed, which decides how far the timeline can answer a question on its own.

Email marketing consent records that a customer agreed to receive your marketing emails. It is what the Accepts Marketing tab and any segment built on that consent read, and you can set it on the Add Customer form, in Edit marketing status on an existing record, or for a batch of customers in Bulk Edit.

A company's page is where you work on it after it is created: the customers who may order for it and which of them is the main contact, the ordering status that follows from those customers, the actions menu behind the three dots, the company-wide markets, catalogs, payment terms and checkout, the staff assigned to it, its notes and locations, and placing an order on its behalf. This article maps the page and gives the steps for the parts that have them.

A duplicate is one person holding two customer records, so their orders and spend are split between them. Tanqory has no duplicate finder, so you spot the pair yourself in the Customers list and merge one into the other. The record you merge in is emptied but stays on the list, so expect two rows afterwards, not one.

Show sign-in links is the single toggle that decides whether your storefront offers shoppers a way into their account. It changes what shoppers see and nothing else: no account is created or closed, staff access is untouched, and the account area stays reachable through the Customer account URL even with the links hidden. This covers where the toggle sits, what turning it off really does, and why checking your own storefront is the only way to see the result.

You create a B2B company from Add company on the Companies page. The form takes the company name, an optional main contact, a first location with its shipping address, and the ordering, payment terms, checkout, and tax rules that location uses. Only the name is required, so you can save early and fill in the rest later.

Companies is where you sell to businesses rather than to individual shoppers. A company groups the buyers who order for it, one or more locations that each carry their own addresses, payment terms and checkout rules, and an ordering status that decides whether it can place orders yet. This overview explains the Companies list, what the Ordering column is telling you, and which article takes each task from here.

A company location is more than an address. Each one carries its own shipping and billing addresses, assigned customers, markets, catalogs, payment terms, checkout rule, and tax settings. You manage a company's locations from the Locations panel on its page, where you can add a location, copy an existing one, and see each location's terms at a glance.

The tabs above the customer list are views, and the plus at the end saves one of your own from whatever filters you have on. This covers what each built-in tab actually returns, why New Customers is worth checking rather than trusting, and the difference between a view and a segment.

What a shopper actually finds on your storefront when they go looking for their account: a person icon in the header, and the panel behind it offering Sign in, Orders and Addresses. This covers where each of those leads, what the sign-in page asks for, and what a shopper sees when the links are switched off.

Whether a customer's orders are taxed is set in two places, and the two do not offer the same choices. The Add Customer form has it while you are creating the record, and Edit tax details has it afterwards, where the middle setting will not save until you pick an exemption. This covers both, what each setting means, and why the paperwork behind an exemption is your responsibility rather than Tanqory's.

Why you would take a customer export, what the file holds and what you owe the people in it. Every column is ticked when the dialog opens, so the default file is close to everything you hold about everyone, and it arrives by email rather than as a download, which means a refused export looks exactly like a successful one.

SMS marketing consent records that a customer agreed to receive marketing text messages. It runs on the phone number rather than the email address, so a customer with no phone on file cannot be subscribed at all, and its switch is greyed out until you add one.

A customer can hold more than one address, but their record only ever shows one of them, and it is not on the card until you expand it. The Customer card hides the default address behind Show more, and the rest of the addresses live behind Manage addresses. This covers reading the card, working the dialog, and why the Default badge decides what your team sees.

The field-by-field reference for the Add Customer form: the three required fields, the three marketing consents and the notice above them, where Save hides until you change something, and the four sections that are on this form but not in the Edit menu afterwards.

The Timeline at the foot of a customer page records what happened and who did it, newest first under date headings. Entries begin You or Staff, an order number inside one is a link that carries a way back, every sent email offers Resend, and the note box takes 2000 characters that only staff can see.

The Notes card holds one internal note per customer, opened with the pencil on the card. The dialog is headed Add note or Edit note depending on whether there is one already, the box counts to 5000 characters, and saving replaces whatever was there rather than adding to it.

Fifty ready-made segments you can start from instead of writing a query. Taking one replaces whatever is in the builder and runs it at once, so you see who matches immediately. This article covers the window, the seven groups, what the filter count on each card tells you, and why a template showing zero filters matches everybody.

Duplicate copies a segment you already have, and it saves the copy immediately rather than handing you a draft. This article covers the dialog, what comes across with the copy, and the order the work has to happen in.

One dialog both gives credit and takes it back, through an Adjustment field set to Credit or Debit. The currency is a full list rather than your store's own, so the wrong choice quietly starts a second balance instead of changing the one the customer has, and the Notify customer box is ticked while the emails behind it are not available yet.

The controls for tagging, one record at a time and in bulk. It covers the Tags card low on a customer record, the selector that searches and creates in the same field, the chip that takes a tag off again, and the bar above the customer list that tags every row you ticked in one action. Tags are written the moment you tick them, with no save step anywhere.

There is more than one way a customer record appears. You can create one by hand with Add Customer, bring a batch in from a CSV file with Import, or let shoppers create their own accounts on your storefront. This says which route fits which situation, and how to tell afterwards which way a record arrived.

A customer detail page answers what someone has bought at two depths: a statistics strip with their spend, order count and RFM group, and View all orders, which opens the Orders overview filtered to that person. This covers reading both, why the count and the list can disagree, and which figures on that page ignore the filter.

A customer detail page carries two order cards. The one headed Last order lists their recent orders in full, with the line items, both status badges, and the buttons that open the whole history or start a new sale. Below it, Draft orders lists the drafts made for that customer, which are not sales until they are completed.

Account type decides which account system your store runs on, and the page states that only the recommended one enables store credit in full. This covers what each option says on screen, how to tell which you are on, and why leaving it alone is usually the right answer.

The Customers page carries two subjects that people come looking for separately, the page around the table and the table itself, and each has a detailed article of its own. This page is the signpost between them: one table that matches what you came to do against the article that covers it.