Use Shopify customer accounts to give shoppers an identifiable route to their orders and profile, then test which actions the configured account actually permits. Separate signing in, finding an order and requesting a change. Build the acceptance sheet around those tasks so an account link is checked as a working customer journey.
Start with the journey a returning shopper needs. They may want to find an earlier purchase, correct their contact details or ask about an item they no longer need. Give each task a clear entry point and expected result. A useful account brief explains both what the customer can do and which decisions remain with the store team.
The examples below use Shopify’s own documentation checked on 24 October 2026, including the retained customer-account body and a distinct self-serve request guide. Use the broader customer portal guide for general portal planning. This worksheet stays with Shopify account identity and access to order actions.
Which identity should the account represent?
Shopify customer accounts let customers view and manage orders and edit profile information. Shopify documents passwordless sign-in using an emailed one-time code. These features are described in its customer accounts guide. In the proposed acceptance record, identify the account email used for each case and the order that should belong to it. Keep test identities distinct so the reviewer can explain why an order appears.
An existing customer profile in Shopify admin already gives that customer an account. Signing in with an email not associated with an existing profile creates a new profile. That distinction matters when investigating an apparently empty order history. First establish which address the customer used and which profile owns the expected order; a successful sign-in alone does not resolve that relationship.
Customers can update their name, email address and shipping addresses in their account. Changing the account email prompts email verification. Changing an email address cannot merge multiple customer profiles. Shopify admin provides a customer-profile merge route for requested account merges. Both points are documented in the customer accounts guide. Keep an identity correction separate from the decision to combine records.
Write a customer-facing route for an unresolved identity question. The proposed route should say what information support needs to investigate, who owns the review and where the outcome is recorded. Use synthetic data during the demonstration. An order reference supplied in a message should be treated as information to check against the approved process, rather than an instruction to expose the order to a different account.
For profile changes, compare the visible customer result with the relevant administrative record. Ask the tester to describe which value changed and which order they are examining. Keep historical order details and the current profile distinguishable in the observation sheet; establish the actual behaviour of the chosen configuration instead of assuming every earlier record will be rewritten.
What does an order action actually authorise?
Shopify requires activation of self-serve returns and cancellations before customers can submit those requests. Its setup guide treats the request journey as a configured feature. Record the selected request types, the account entry point and the person responsible for reviewing incoming requests before writing public instructions.
Self-serve returns and cancellations do not work with legacy customer accounts. The guide describes providing a customer-accounts URL as an access route, including where the storefront otherwise continues to use legacy accounts. Inspect the destination actually reached by the link. A familiar profile icon or old account template does not establish that it leads to the request experience being tested.
A cancellation request does not change the order state by itself. Exchanges cannot be requested through self-serve returns. These are separate documented boundaries. Explain a request as a request, and provide the store’s approved next step for a task outside the available account action. Avoid wording that turns submission into an automatic commercial decision.
Use the following original acceptance matrix to define the review. The expected results are proposed checks for your store, to be confirmed against its actual configuration and approved process.
| Customer task | Identity and record to establish | Observation to retain | Decision owner |
|---|---|---|---|
| Sign in | Synthetic email and intended profile | Account reached after verification | Account configuration owner |
| Find an order | Test order and owning profile | Expected order visible to its account | Store administrator |
| Change email | Original profile and new test address | Verification and resulting profile | Customer-record owner |
| Correct duplicate records | Separate profiles and evidence of relationship | Administrative review outcome | Authorised administrator |
| Request cancellation | Eligible sample item and signed-in account | Submitted request and order state | Order operations owner |
| Ask for an exchange | Customer’s intended change | Approved alternative route explained | Customer-service owner |
Place the matrix beside the store’s actual instructions. Ask a colleague to follow the account link from the footer or relevant policy page without being coached through the screen. Record unclear labels and unexpected destinations. The purpose is to determine whether the intended customer task is understandable, as well as whether the configuration permits it.
A worked identity-and-order exercise
Consider a hypothetical test store with two fictional shoppers, Account A and Account B. Account A has a sample order containing a notebook and a folder; Account B has a different sample order. Use harmless test contact details and the store’s authorised test arrangement. The following is a proposed exercise, not a report of an executed purchase or account-security test.
Begin with Account A signed out. Follow the intended account entry point, complete its documented sign-in route and locate the sample order. Record the account identifier, displayed order reference and available actions. Then repeat with Account B in a separate approved test session. Compare each observation with the expectation sheet prepared before the demonstration.
Next include a new synthetic email with no existing profile. Record the profile created and the information visible in that account. The point is to distinguish a new identity from an earlier shopper expecting their history. Keep the profile identifiers in the private test record; the public customer instructions should simply explain the appropriate support route for an unresolved history question.
For the cancellation case, prepare an eligible test item using the documented configuration and the authorised test procedure. Submit the request and record what the customer sees, what the reviewer receives and the order state before a decision. Give review ownership its own entry. A clear handover lets support explain whether a request is awaiting consideration or has a recorded outcome.
Finish with a duplicate-profile question. Ask the administrator to explain the evidence they would need before combining records, and record that decision without performing an unnecessary merge. This checks the escalation path while keeping the exercise focused on identity and permitted actions.
Retain the configuration date, account version, sample references, observations and unresolved cases together. Revisit the matrix when the account route or request settings change. For wider store constraints, see Shopify in Zambia; for the storefront scope, see online stores. To brief the account journey and its handover, get started with the tasks your customers need.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.