Customer journey: map discovery to returns

Map the customer journey from discovery to returns. Improve ecommerce customer experience with a reusable journey map and clearer channel handoffs.

A customer journey is the sequence of interactions a customer has with your store, from discovering a product to buying it and getting help after the sale. A customer journey map makes the gaps between those interactions visible, so you can assign a specific fix to the team that controls it.

Start with one purchase scenario. Map the information a customer needs at each stage, then compare that need with what your store actually provides.

Map the ecommerce customer journey

Record the customer’s goal, actions and expectations alongside the evidence for each touchpoint in your ecommerce customer journey map. Customer experience is how the customer experiences those interactions: whether they can find a suitable product, understand the total cost and get a promised remedy.

Customer journey mapping covers the relationship across channels and after purchase. A user journey usually follows one task through an interface, such as changing a delivery address. A successful address form doesn’t establish that the parcel reaches the right place.

Shopify’s guide to mapping the customer journey distinguishes the broader customer journey from a user’s task within a digital interface. Keep that distinction when a website team and a support team map the same purchase.

Reusable customer journey map template

Copy this table into a spreadsheet and add one row for each stage. Split the combined fields into separate columns if your workshop needs more room.

Stage and customer goalCustomer action and touchpointInformation needed and expectationFriction and failure signalEvidence and emotionAccountable team and success measure
Initial need: define the jobRecord the trigger and first contactRecord the intended use and constraintsRecord what prevents a useful next stepAdd an observation reference. Record an emotion only from customer researchName one owner and the observable outcome
Product discovery: find candidatesRecord the search or category visitRecord the attributes needed to find productsRecord failed searches or missing categoriesCite the search record or customer statementName the catalogue owner and discovery measure
Comparison: choose a productRecord a product question or store visitRecord specifications, availability and policy needsRecord unanswered questions or inconsistent adviceCite the enquiry. Keep inferred feelings labelled as assumptionsName the merchandising owner and choice measure
Checkout: place the orderRecord basket, payment and confirmation stepsRecord total cost and delivery promiseRecord payment errors or unexpected chargesCite checkout records without retaining payment credentialsName the ecommerce owner and completion measure
Delivery: receive the purchaseRecord tracking and receiptRecord status, arrival expectations and next actionRecord status gaps and delivery contactsCite order and carrier recordsName the fulfilment owner and delivery measure
Returns: resolve the problemRecord return request and resolutionRecord eligibility, instructions and remedyRecord repeated requests or an unresolved returnCite the service case and customer statementName the support owner and resolution measure
Repeat purchase: buy againRecord the next need or reorderRecord changed stock, price and preferencesRecord a failed reorderCite the later order or enquiryName the ecommerce owner and repeat-order measure

Fictional retail purchase example

Consider a fictional customer, Sam, buying a desk lamp from Harbour Home. Every observation below is invented to demonstrate the template. These are sample records, not retailer results.

Stage and goalAction and touchpointNeed and expectationFriction and signalIllustrative evidence and emotionOwner and success measure
Initial need: light a small deskSam notices glare while workingA lamp that fits the deskUnclear dimensions prevent a shortlistScenario note F1. No emotional evidence recordedMerchandising: dimensions present for eligible lamps
Product discovery: find lampsSearches the website for a narrow baseSearch results include base widthSearch returns lamps without dimensionsSample search F2. Emotion unrecordedCatalogue team: searches reaching a suitable product
Comparison: choose between two lampsAsks online, then visits the shopSame dimensions and bulb advice in both channelsStaff cannot find the earlier questionSample enquiry F3. Fictional statement: “I’m unsure which one fits”Store team: question resolved without repeating measurements
Checkout: order the chosen lampPays on the website after the visitDelivery cost and dispatch timing before paymentTiming appears only after purchaseSample order F4. Emotion unrecordedEcommerce: delivery answer visible before payment
Delivery: receive the lampOpens tracking, then contacts supportA status explanation and next stepTracking shows no explanation for a delaySample case F5. Emotion unrecordedFulfilment: delivery contacts per dispatched order
Returns: resolve damageReports a damaged shadeClear return instructions and a remedyPhotos are requested twiceSample case F6. Fictional statement: “Repeating this is frustrating”Support: returns resolved within the agreed service window
Repeat purchase: buy another lampReopens the product page laterCurrent availability and product detailsThe earlier variant is unavailableSample visit F7. Emotion unrecordedEcommerce: repeat orders completed after starting a reorder

Use a stage-based customer journey framework when you need a readable view of the purchase and its handoffs. Add a service blueprint when the problem depends on work behind the touchpoint, such as warehouse and support responsibilities for damaged goods.

A circular repeat-purchase model suits consumables and regular ordering because the next need follows the previous purchase. Customers can revisit comparison, abandon a basket or return an item. Draw those branches instead of forcing every interaction into a one-way funnel.

Carry context across an omnichannel journey

An omnichannel journey connects interactions through relevant context, even when the customer switches between the website and a physical shop. In Sam’s fictional journey, the online enquiry records the lamp models and desk measurements. With Sam’s agreement, shop staff retrieve that question when Sam presents its reference.

Later, support needs the purchased variant and the delivery issue. A product-question reference can help staff understand the request, but it mustn’t authorise access to a private order.

End-to-end customer journey diagram

This diagram explains the fictional sequence. The sample references F1 to F7 match the example map. They show how to organise evidence, not observed customer behaviour.

Fictional customer journey from initial need to repeat purchase Initial need F1 leads to product discovery F2, comparison F3, checkout F4, delivery F5, returns F6 and repeat purchase F7. Comparison spans an online enquiry and a shop visit. Private order access requires an identity check. Repeat purchase returns to product discovery. Initial need · F1Desk lamp requirements Product discovery · F2Website search Comparison · F3Online enquiry and shop visit Checkout · F4Payment and order reference Delivery · F5Identity check for private order Returns · F6Identity check and service case Repeat purchase · F7Back to product discovery

The sequence also works as a compact infographic in text: Initial need (F1), then Product discovery (F2), Comparison (F3), Checkout (F4), Delivery (F5), Returns (F6) and Repeat purchase (F7). Repeat purchase leads back to Product discovery. A customer can also return from Comparison to Product discovery without ordering.

Carry product identifiers, variant choices and the customer’s stated requirements between channels when the customer expects that handoff. Recheck stock and price at the next decision because an earlier answer can become stale.

Keep personal details and order history within authorised staff access. Verify identity again through the retailer’s approved process before disclosing private order information or changing an address. A shared device or an enquiry reference alone doesn’t prove who is asking. Share only the issue summary and records needed for the next team’s task.

Remove uncertainty during product selection

Remove product-selection uncertainty by fixing the missing fact at its source. Add base dimensions to the lamp catalogue, expose stock by variant and compare compatible bulb types consistently. A general reassurance about quality won’t answer whether a lamp fits a narrow desk.

For unavailable variants, show the stock state before the customer reaches payment. Explain a suitable alternative through the attribute the customer needs, such as a smaller base, rather than suggesting any product that happens to be available.

Shopping assistance can use those same catalogue facts and delivery policies in the conversation. Retailers use shoppa, an AI shopping agent, to help customers find, compare and buy products on their site. Its answers use the retailer’s catalogue and documents. Customers can compare lamp dimensions, ask about delivery and pay in the chat. Order support and returns continue there after the sale.

For example, a customer asks for a lamp with a base under 18 cm wide. The agent can narrow the catalogue, compare matching lamps and answer a delivery question from the store’s policy. The example describes the workflow, not a measured improvement in sales.

Join checkout with delivery and returns

Keep the promise made before payment available to the teams handling delivery and returns. Record what dispatch timing the customer saw, which shipping service they selected and what the confirmation says. A dispatch estimate and a delivery estimate describe different events.

When a parcel is delayed, show its latest known status and the next action your team can take. If the carrier has supplied no update, avoid inventing an arrival time. Explain the retailer’s actual escalation route and the remedies that apply to the customer’s issue.

A handover needs the problem, relevant order reference, checks already completed and the promised follow-up. Staff must be able to see that the customer already supplied a damage photo. Transfer that record through approved access instead of asking for it again.

Use checkout optimisation for the payment-stage checks. Decisions about queues and staff escalation belong in the guide to ecommerce customer service.

Prioritise changes by customer outcomes

Customer journey analytics analyses connected events and outcomes across customer stages. A journey map organises the customer’s needs and handoffs. Analytics tests where progress stalls and whether an assigned change improves the outcome.

Choose the measurement unit before calculating a rate. A browser session, a person and an order are different units. Anonymous sessions cannot establish a person’s full cross-device journey. Report unmatched records separately instead of joining them through guessed identities.

Customer journey metrics and KPIs

Use the following operational definitions as a starting point for your key performance indicators (KPIs). These are suggested reporting contracts, not universal platform defaults. Segment each measure by device and channel, then by relevant product category or delivery service where volumes permit.

Metric and denominatorData source and identityReporting windowConsent and access boundaryInterpretation and assigned action
Stage completion: eligible sessions reaching the next stage divided by sessions entering the stageStorefront events joined by session identifierWeekly cohorts, allowing 7 days to progressInclude only events permitted for analytics. Keep anonymous sessions separateCheck event coverage first. Ecommerce investigates the largest confirmed break
Abandonment: entrants without recorded next-stage completion divided by entrantsSame event stream and session identifierSame 7-day progression windowSame analytics permission and access controlsA missing event isn’t proof of lost intent. Ecommerce inspects the affected device flow
Time to next step: median elapsed time among records completing both stepsLinked event timestamps and session identifierWeekly cohorts with 7-day follow-upPermitted analytics records onlyCompleters exclude unresolved journeys. Report their count separately. Ecommerce checks slow steps
Failed searches: zero-result searches divided by all submitted searchesSearch service result counts joined by search request identifierWeeklyApply the store’s analytics permissions. Redact personal data typed into searchA submitted-search event alone doesn’t show failure. Catalogue team repairs supported query gaps
Payment failure: failed attempts divided by all payment attemptsPayment outcome records joined by attempt identifierWeeklyRestricted transaction reporting. Exclude payment credentialsSeparate technical errors from declines. Payments owner diagnoses the relevant category
Delivery contacts: distinct dispatched orders with a delivery enquiry divided by dispatched ordersOrder and service records joined by order identifierDispatch cohorts followed for 14 daysStaff access for service reporting. Separate any optional marketing reuseRepeat contacts need a separate count. Fulfilment checks the status or promise gap
Repeat contacts: cases with another contact about the same issue divided by cases openedService records joined by case identifierWeekly case cohorts followed for 14 daysRestricted service reporting. Redact shared examplesDistinguish an agreed follow-up from a repeated unresolved question. Support repairs the failed handover
Unresolved returns: requests still open after 14 days divided by return requestsReturn and service records joined by return identifierWeekly request cohorts with 14-day follow-upRestricted service records used for the approved reporting purposeExclude immature cohorts. Support checks blocked remedies and assigns a case owner

Shopify’s standard customer events distinguish checkout starting from payment information submission and checkout completion. Payment information submission alone doesn’t prove a successful payment. Join payment outcomes to the transaction record when investigating failures.

For consent-aware collection, Shopify’s privacy permission states exposes analytics and marketing permission states separately. Your reporting must respect the permissions and purpose attached to each source. Service records don’t become marketing permission because they share an order identifier.

Worked delivery-information improvement

Suppose a fictional review finds 8 of 20 sampled lamp enquiries ask when an order will dispatch. In the sample, the product page omits dispatch timing. The customer journey map assigns that information gap to the ecommerce owner, with fulfilment responsible for the underlying promise.

The owner adds the approved dispatch answer beside the product’s delivery information and updates the shopping assistant’s policy source. The proposed change is small enough to test through one product category.

Before editing, record whether a customer can find the dispatch timing before payment without contacting support. After editing, repeat the same task on phone and desktop. Acceptance means the answer is visible, agrees with fulfilment’s policy and reaches the order confirmation without changing meaning.

Then compare the proportion of delivery-timing enquiries across comparable enquiry samples over two equal reporting periods. Keep product mix and channel visible. A lower rate would support fewer information gaps in that sample. It wouldn’t establish a revenue gain or prove the page change caused every difference.

Run a customer journey mapping workshop

Run the workshop around one bounded customer scenario and finish with a named improvement owner. Bring customer statements and operational records that participants are authorised to use. Remove personal details from shared workshop material.

  1. Choose the scenario and boundary. For the lamp example, start with product discovery and end when a delivery or return issue is resolved.
  2. Invite the teams that control those touchpoints, including merchandising, ecommerce and support. Include fulfilment when delivery promises are under review.
  3. Bring an evidence pack. Use redacted enquiries, search outcomes, checkout records and relevant service cases. Record the reporting window and selection method.
  4. Build the current-state map together. Write customer actions first, then attach the evidence. Mark an unsupported assumption explicitly in the working map.
  5. Resolve disputed stages through records. If staff disagree about where dispatch information appears, inspect the product page and confirmation from the same order scenario.
  6. Choose the friction with the clearest customer consequence. Assign the source correction and the handover to named owners, with an acceptance check.
  7. Draw a separate future state. Review the changed answer through the same customer task and preserve the original map beside the revised version.

If teams can’t reconcile two records, retain both observations with their source references. Assign someone to investigate the difference. Agreement around a tidy diagram doesn’t turn an assumption into customer research.

Map the B2B buying group and repeat order

A business-to-business (B2B) customer journey must show who can request, approve and pay for an order. One trade buyer’s successful search doesn’t establish that the buying organisation completes the purchase.

Consider a fictional café ordering replacement lamps. The buyer chooses products, the manager approves the quote and the accounts contact handles the invoice.

Fictional B2B customer journey map

StageTrade buyerApprover or accounts contactHandoff and authoritative recordSuccess measure
Catalogue accessSigns into the authorised trade accountAccount administrator confirms accessCustomer account record sets the permitted catalogueBuyer reaches the correct trade range
Negotiated termsReviews the account’s agreed price and delivery termsAccounts confirms applicable termsApproved account terms, not a remembered quoteOrder uses the agreed terms
Quote or approvalSubmits quantities and delivery needsManager approves the quoteQuote identifier preserves the exact versionApproval delay measured from submission to decision
OrderingConverts the approved quote into an orderAccounts receives the payment obligationOrder links the approved quote and accountApproved orders complete without re-entry
DeliveryConfirms receipt at the caféAccounts reconciles the invoiceDelivery and invoice records link to the orderQuantity or invoice exceptions reach an owner
Repeat orderReorders the same products or approved replacementsManager reapproves changed cost where requiredNew order retains the earlier reference and current termsCompleted repeat orders divided by initiated reorders

Analyse person-level actions using authorised user identifiers and account-level outcomes using the business account identifier. Preserve each person’s role and permission. Two staff members at one café are two people within one account, not two acquired customers.

Measure approval delay for submitted quotes and repeat-order completion for initiated reorders over a stated window, such as 30 days. Separate quotes still awaiting a decision. Restrict reporting to approved account operations, and keep promotional reuse subject to its own permission.

A buyer who selects a lamp quickly can still wait several days for approval. That finding assigns an approval handoff to the account team. It doesn’t justify changing search rankings.

Connect journey strategy with marketing and service

A customer-centric journey strategy starts with the outcome the customer needs and the handoff preventing it. For Harbour Home, choose “understand dispatch timing before payment”. The ecommerce owner controls placement, fulfilment supplies the promise and the acceptance task tests whether a customer can find it.

Match digital marketing to the customer’s stage without treating every service interaction as a promotional opportunity.

Customer needMessage and triggerPermission and suppressionResponsible team
AwarenessA guide to lamp dimensions when someone visits the guideReading a page doesn’t itself authorise a promotional messageMarketing maintains accurate educational copy
ComparisonSend a requested product comparisonDeliver the requested information. Suppress promotional follow-ups without the required permissionMerchandising supplies the facts
Post-purchaseSend the requested order or return update when status changesLimit the message to the service purpose. Suppress duplicate or obsolete status messagesSupport and fulfilment own the update
Repeat purchaseSend a promotional reminder to an eligible opted-in audienceApply recorded permissions, withdrawal and frequency rules. Suppress reminders for customers with an open relevant complaintMarketing owns the audience and suppression checks

Keep the map focused on the purchase and its service handoffs. A full lifecycle automation programme needs a separate operating design.

Use AI without inventing customer insight

Use AI to summarise approved feedback or propose labels for an existing map, then trace each proposed finding to its source. AI can also help a customer compare catalogue products and complete a purchase. Those shopping actions and a generated summary are different kinds of evidence.

Suppose AI labels the fictional lamp case “customers distrust delivery promises”. Open the underlying enquiries. If they ask only when dispatch occurs, change the finding to “dispatch timing is missing from the product answer”. Keep a claim about distrust only when customer statements support that interpretation.

Remove inferred emotions and invented quotations from the map. Use redacted material in approved tools, with access and retention controls suitable for the data. Keep personal information out of unapproved tools. A generated label cannot supply an observation that your team never collected.

Give the journey a maintainable architecture

Customer journey architecture records how touchpoints connect through identity checks, authoritative records and team handoffs. It gives each map row a source that staff can maintain when the store changes.

Journey ownership register

Journey elementAuthoritative sourceConnection and checkAccountable owner
Product adviceCatalogue and approved policy documentsProduct and variant identifiers connect answers to current factsMerchandising
Purchase and delivery promiseOrder record and confirmationOrder identifier preserves the chosen variant and shipping serviceEcommerce and fulfilment, with one assigned handover owner
Private order accessCustomer authentication and staff permissionsVerify identity before disclosing or changing private detailsCustomer access owner
Service and return progressService case and return recordCase and return identifiers retain attempted remedies and next actionSupport
MeasurementDocumented event and reporting definitionsSession, order or account identifiers match the stated unitAnalytics owner
Map versionMaintained map and change recordEvidence references, assumptions and acceptance checks survive each revisionJourney owner

When the product range changes, check specifications and comparison answers. Checkout changes require a review of payment events and confirmation promises. After revising the returns process, check instructions, case handovers and unresolved-return reporting.

For each change, the journey owner versions the affected map rows and records who confirms the new answer. Retain unresolved assumptions until evidence resolves them. Start with the handoff that currently leaves a customer repeating a question, and keep its fix open until the same customer task succeeds.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup