E-commerce
July 1, 2026
"I have been wearing these shoes for three days and they hurt." "This serum causes tingling: is that normal?" "I don't see any effect after a week." These inquiries arise when the customer does not know how much time to give the product, how to use it progressively, or what signs should lead them to stop.
The support for products with an adaptation period must explain the expected timeline without downplaying a concerning symptom. It covers breaking-in, gradual use, anticipated sensations, abnormal signals, and return requests made before the end of the period. It is distinct from the satisfaction guarantee #731, which takes place after the period and under specific commercial conditions.
The guide #733 presents the ADPTPER-SUP policy, the flow ADP-1 to ADP-8, and the ADPTPER-MAP matrix. It complements the future ADPTPER bot (#734), designed to answer simple questions about timeline and usage.
Summary
Why does a poorly explained trial period generate returns?
Some products require a breaking-in period or progressive use: shoes, orthotics, mattresses, dietary supplements, or active cosmetic ingredients. Without clear information, the customer may interpret initial discomfort or the lack of an immediate effect as a defect, or even as a misleading promise.
The five main sources of misunderstanding
An imprecise timeframe: the customer does not know when they can reasonably assess the comfort or effect.
Unexplained progressive use: the frequency, duration, or dosage are not detailed.
A blurry boundary between normal and abnormal: the customer does not know when to continue or stop.
A very early return request: the product is judged before the end of the documented period.
Confusion with a guaranteed result: the customer thinks that a normal adaptation period immediately entitles them to a refund.
User Intuition points out that a portion of returns related to a product that "does not suit" stems from a gap between expectations and the actual experience, a gap that can sometimes be reduced through better post-purchase education (User Intuition, post-purchase expectations 2026). ADPTPER-MAP ensures that support and marketing communicate the same timeline.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How do you distinguish ADPTPER from other post-purchase customer journeys?
The customer can request instructions for use, report a reaction, claim a return, or invoke a warranty. Each situation corresponds to a different pathway.
Which guide to use?
#733 ADPTPER: explains the adaptation period, gradual use, and the difference between expected and abnormal signs.
Satisfaction Guarantee #731: handles the commercial solution when the promise is not met after the scheduled timeframe and conditions.
Post-purchase User Guide: explains the assembly, dosage, and general use of the product.
Onboarding #179: supports the new customer over a broader period.
Training #729: applies to products that require structured training.
Bot #734: answers simple scheduling and usage questions before a potential escalation.
Guide #733 describes a normal phase prior to comfort or the expected effect. Guide #731 applies when a commercial promise remains unfulfilled after compliance with the scheduled conditions and timeframe.
Which adaptper_* typologies should be used?
The classification must describe the customer's actual question and allow for a response based on the correct field of the matrix.
The eight ADPTPER typologies
adaptper_timeline: the customer is asking how many days to wait before evaluating the product.
adaptper_progressive_use: they need a break-in, dosage, or frequency plan.
adaptper_normal_symptoms: they want to know if a specific sensation is expected.
adaptper_abnormal_symptoms: they describe a signal that may require stopping use and escalating.
adaptper_early_return: they are requesting a return before the end of the adaptation period.
adaptper_no_effect_yet: no effect is visible yet, but the expected timeframe has not passed.
adaptper_vs_perf_guar: they confuse the adaptation period with a performance guarantee.
adaptper_checkin: they are responding to a proactive follow-up sent at Day 7 or Day 14.
Use the tags adaptper, adaptation_period, break_in and progressive_use. The TIMELINE-CITE rule requires using the validated text in adaptation_timeline_copy.
How to build a reliable ADPTPER-MAP matrix?
ADPTPER-MAP centralizes, for each product concerned, the information that agents and the future bot #734 can communicate. It avoids inventing a timeframe or downplaying a symptom.
Fields to complete
adaptper_program_id: identifies the adaptation program.
eligible_skus: lists the products subject to an adaptation period.
adaptation_period_days: indicates the minimum timeframe before a reasonable assessment.
adaptation_timeline_copy: describes step-by-step expectations in customer-facing language.
progressive_usage_steps: specifies the break-in period, frequency, or dosage over the days.
expected_symptoms_copy: lists the sensations considered expected according to the validated documentation.
abnormal_symptoms_copy: indicates the signs that warrant discontinuation and appropriate referral.
early_return_policy_copy: explains the conditions for a return requested before the end of the timeframe.
checkin_touchpoints: defines the messages sent at D+3, D+7, and D+14.
perf_guar_link_flag: indicates whether the guarantee program #731 applies afterwards.
customer_communication_copy: provides the texts used on the product page, the packaging, and in macros.
bot_intent_map: associates the adaptper_* typologies with the intents of bot #734.
Synchronize the matrix with the product page, packaging, the email sent after delivery, and helpdesk macros so that the customer receives the same information at every stage.
What ADPTPER-SUP rules should govern the responses?
The six ADPTPER-SUP rules protect both the customer and the brand by requiring documented responses.
ADPTPER-MAP-GROUNDED: only use the timelines, steps, and symptoms validated in the matrix.
TIMELINE-CITE: faithfully reproduce adaptation_timeline_copy when explaining the duration.
STEPS-CITE: use progressive_usage_steps for any progressive usage recommendation.
SYMPTOM-CITE: clearly distinguish between expected_symptoms_copy and abnormal_symptoms_copy.
NO-EARLY-RETURN-PROMISE: do not promise the acceptance of a return before consulting early_return_policy_copy.
PERFGUAR731-REROUTE: when a customer requests the application of a performance guarantee, direct them to guide #731.
Which process should be followed to handle an ADPTPER ticket?
The ADP-1 to ADP-8 flow helps the agent check the product, elapsed time, and risk level before responding.
ADP-1 — Gather: identify the question, order, SKU, and number of days since delivery.
ADP-2 — Consult ADPTPER-MAP: check the timeline, steps, symptoms, and return policy.
ADP-3 — Verify Order: confirm the product, delivery date, and already elapsed time.
ADP-4 — Classify: select timeline, progressive_use, normal_symptoms, abnormal_symptoms, early_return, or no_effect_yet.
ADP-5 — Choose Path: apply TIMELINE, STEPS, SYMPTOM, NO-EARLY-RETURN, or redirect to PERFGUAR731 or REG119.
ADP-6 — Respond: use an ADPTPER macro based on customer_communication_copy.
ADP-7 — Execute: create a return exception or quality escalation when conditions warrant.
ADP-8 — Close: apply adaptper_resolved and record if the timeline was cited and how many days remained.
An adaptper_timeline request should ideally be resolved in a single interaction with adaptation_timeline_copy and, where relevant, the terms of progressive use.
Which ADPTPER macros should be used?
Macros provide a consistent foundation, but the agent must always replace the fields with the validated information of the concerned SKU.
ADPTPER-TIMELINE-01
"For [SKU], the planned adaptation period is [adaptation_period_days] days. Here is what is expected over time: [adaptation_timeline_copy]. When applicable, also follow these steps: [progressive_usage_steps]."
ADPTPER-SYMPTOM-01
"During the adaptation period, the following sensations/symptoms can be expected according to the documentation: [expected_symptoms_copy]. Discontinue use and contact us if you observe: [abnormal_symptoms_copy]. Our support does not replace the advice of a healthcare professional."
ADPTPER-EARLY-RETURN-01
"Your order [order_ref] was delivered [days_elapsed] days ago. The planned adaptation period for this product is [adaptation_period_days] days. Here are the conditions applicable to your request: [early_return_policy_copy]."
ADPTPER-NO-EFFECT-01
"According to the instructions, the expected progress is as follows: [adaptation_timeline_copy]. There are [days_remaining] days remaining before the end of the evaluation period. If a result guarantee is provided, then consult guide #731."
Which cases must be removed from the standard flow?
An adaptation period must never be used to minimize a severe reaction or to delay a necessary referral.
Severe reaction or suspected allergy: apply abnormal_symptoms_copy, request cessation of use according to documentation, and follow regulated pathway #119.
Product-specific warning: refer to the PRODWARN guide rather than treating the issue as a simple delay.
Active satisfaction guarantee: after the end of the period, apply PERFGUAR731-REROUTE.
Return for change of mind: follow the standard return policy when it is not an adaptation issue.
Very early chargeback threat: acknowledge the concern, explain the timeline and the return policy, without promising an unapproved refund.
Adaptation is a documented phase. A concerning reaction or a claim based on a guarantee falls under a different playbook.
Which ADPTPER KPIs should be tracked?
KPIs make it possible to verify that agents cite the correct information and that post-purchase education reduces premature returns without masking necessary escalations.
adaptper_timeline_cite_rate: share of timeline and no_effect tickets in which the validated schedule was cited.
adaptper_early_return_save_rate: share of premature returns avoided after an appropriate explanation.
adaptper_days_to_return_median: median number of days between delivery and return of a concerned SKU.
adaptper_abnormal_escalation_rate: share of abnormal signals transmitted to quality or the regulated path.
adaptper_checkin_response_rate: response rate to follow-ups sent at D+7 and D+14.
An initial target can be set at over 95% for adaptper_timeline_cite_rate. The median time before return must be compared to adaptation_period_days without artificially trying to retain a customer reporting an abnormal problem.
Which mistakes must absolutely be avoided?
The following five practices expose the customer to misinformation and make support inconsistent.
Automatically accepting or refusing a return at D+2: always consult early_return_policy_copy.
Minimizing an abnormal sign: use abnormal_symptoms_copy and trigger the planned escalation.
Inventing a timeframe: refer only to adaptation_timeline_copy.
Confusing adaptation and warranty: use PERFGUAR731-REROUTE when the customer requests a remedy after the period.
Forgetting progressive use: cite progressive_usage_steps when it is part of the validated protocol.
How does Qstomy support ADPTPER questions?
On Shopify, Qstomy can detect an adaptper intent, find the SKU, and reply using ADPTPER-MAP. The bot quotes the schedule and usage steps without making up advice.
Bot #734 handles simple first-level questions. Exceptional return requests, abnormal signals, and quality escalations are then forwarded to agents who apply guide #733.
Discover AI customer support or request a demo.
Checklist, FAQ, and additional resources
Eight-step ADPTPER checklist
Create the ADPTPER-MAP for each SKU, including the timeline, stages, symptoms, and return policy.
Validate the six ADPTPER-SUP rules.
Configure the eight adaptper_* typologies in the helpdesk.
Create the four macros: TIMELINE, SYMPTOM, EARLY-RETURN, and NO-EFFECT.
Display the adaptation period on the product sheet before purchase.
Synchronize post-delivery follow-ups at D+0, D+7, and D+14.
Train agents to distinguish between adaptation, warranty, standard return, and abnormal signal.
Create the KPI dashboard for Section 9.
FAQ
What is the difference with the #731 result warranty?
Guide #733 explains the normal phase leading up to comfort or effect. Guide #731 addresses the commercial solution once the warranty conditions are met.
What is the difference with a user guide?
The user guide explains how to use the product. ADPTPER specifies how long the adaptation lasts and which signs are expected or abnormal.
How to respond to a return request at D+3?
Check the delivery date, the SKU delay time, and early_return_policy_copy before confirming a solution.
What is the role of bot #734?
It answers simple schedule-related questions. Exceptions, abnormal signals, and complex returns remain handled by agents.
Going further
Start by identifying the SKUs subject to an adaptation period, synchronize the follow-up email at D+7, and test the ADPTPER-TIMELINE-01 macro on a premature return request.
Enzo
July 1, 2026
