E-commerce
July 1, 2026
"I received -20% by email but the code doesn't work." "Why did my neighbor get -30% and not me?" "The link to my personalized offer has expired, can you reactivate it?" Three tickets where a poorly documented segmented offer creates a perception of unfairness and checkout abandonment.
The e-commerce personalized offer support covers segment eligibility, code conditions, unique link expiration, and promo stacking. Performance is distinct from general promo (#111): here, it is a targeted CRM email 1-to-1 or micro-segment discount.
This guide #573 covers the POFF-SUP policy, flow PO-1 to PO-8, and the POFF-MAP matrix. First content on personalized offers for customer service. Future customer service pair bot POFF (#574).
Summary
Why do personalized offers generate tickets?
A personalized offer links a discount to client identity: LTV segment, abandoned cart, reactivation, VIP. The customer reads "just for you" and demands the same treatment as their peers. When the code fails or eligibility is unclear, the ticket becomes emotional.
Five typical frictions
Invalid checkout code: Shopify discount error
Disputed eligibility: why not me, why him
Expired offer: link or code TTL exceeded
Unclear conditions: minimum purchase SKU exclusions
Refused accumulation: stack with another promo requested
Klaviyo reiterates that segmented flows generate higher open rates but require unique profile-linked codes to limit sharing (Klaviyo, personalized email 2026). Without POFF-MAP, agents recreate codes or promise eligibility outside the segment.
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
POFF #573 vs promo #111, private sale #250, discount request and bot #574
Five contents, five distinct discount models.
Quick Matrix
#573 POFF: segmented email offer eligibility conditions
Promo #111: general promo offers cumulative conditions
Private sale #250: gated access third-party collection
Discount request: ad hoc agent discount request
#574 POFFbot: bot check eligibility conditions
#111 = open site promo. #573 = targeted CRM email profile offer. #250 = restricted access window.
Which poff_* typologies should be classified?
Eight personalized offer ticket scenarios.
Eight poff typologies
poff_code_invalid: code rejected by Shopify checkout
poff_eligibility: unsegmented customer requests the same offer
poff_expired: code or link TTL exceeded
poff_conditions: minimum purchase product exclusions
poff_stack_denied: stacking with another promo refused
poff_segment_unfair: comparison with neighbor's/friend's offer
poff_link_broken: email URL 404 or single-use used
poff_price_adjust: recent purchase before receiving the offer
Tags: poff, personalized_offer, segment_code, eligibility. POFF-MAP-GROUNDED: conditions from map only.
How should the POFF-MAP matrix be structured?
The POFF-MAP matrix documents each personalized offer campaign for agents and the future bot #574.
POFF-MAP Columns
offer_campaign_id: Klaviyo flow segment identifier
segment_rules: LTV tag behavior eligibility criteria
discount_type: percent fixed free ship BOGO map
code_type: unique per user static segment shared
min_spend: minimum cart conditions
exclusions: non-eligible SKU collections
stack_rules: stackable with other promos yes no
expiry_ttl: code link validity hours days
Sync Klaviyo flow, Shopify discount settings, CRM segment export, and helpdesk macros. Audit: each unique code = linked profile.
POFF-SUP policy in six rules
Six rules support personalized offers.
POFF-MAP-GROUNDED: eligibility conditions stack from map only
ELIG-VERIFY-FIRST: verify profile segment before extension
NO-CODE-INVENT: no new code outside policy map
EXPIRY-CITE: expiry_ttl cited without extension except map
STACK-RULES-CITE: accumulation according to stack_rules map only
SEGMENT-FAIRNESS: do not disclose third-party segment criteria
Flow POFF PO-1 to PO-8
Flow agent eight steps personalized offer.
PO-1 Intake: poff_* intent + email code offer_campaign
PO-2 Profile lookup: segment tag Klaviyo Shopify customer
PO-3 POFF-MAP: rules discount exclusions stack expiry
PO-4 Code verify: Shopify discount API status usage
PO-5 Classify: invalid eligibility expired conditions stack
PO-6 Respond: macro POFF grounded map
PO-7 Execute: reissue code extension map price adjust
PO-8 Close: tag poff_resolved offer_campaign_id
SLA: poff_code_invalid diagnosed with Shopify reason in one interaction.
Essential POFF macros
Four macro agents.
POFF-CODE-01
"Code [code]: [status: valid / expired / max usage / not product eligible]. Conditions: min [min_spend], exclusions [exclusions summary]. Stacking: [stack_rules map]. Valid until [expiry_ttl date]."
POFF-ELIG-01
"Offer [offer_campaign_id]: [If eligible: code [code] conditions map.] [If not eligible: segment [segment_rules summary public], no out-of-policy extension.] Third-party comparisons: undisclosed criteria SEGMENT-FAIRNESS."
POFF-EXPIRED-01
"Expired offer [expiry_ttl]. [If extension allowed map: new code within [delai].] [If refused: current site offers [lien promo #111].]"
POFF-ADJUST-01
"Order [order_ref] before offer [date]: [price_adjust_policy map]. [If eligible: credit / partial refund [montant].] [If refused: policy map cited.]"
Edge cases: abandoned recovery, VIP, BOGO, and expired cart
Five cases outside the standard macro code.
Abandon recovery email: flow abandon distinct POFF segment
VIP tier: policy VIP #207 recurring entitlements
BOGO stack: BOGO stack_rules map accumulation
Expired cart promo: EXPCART promo_grandfather #571
Ad hoc discount request: discount request outside POFF map
Generic site cart abandonment code: reroute promo #111 if no offer_campaign_id POFF-MAP.
Essential POFF KPIs
Five POFF steering metrics.
poff_ticket_rate: tickets / personalized offer emails sent
poff_code_success_rate: codes resolved without reissue
poff_eligibility_dispute_rate: segment_unfair tickets / campaigns
poff_expired_extension_rate: extensions granted / expired
poff_offer_to_order_rate: tickets → order code used
Target: poff_code_success_rate greater than 85% with POFF-MAP sync Klaviyo Shopify discount.
POFF anti-patterns
Five common mistakes.
Invented agent code: NO-CODE-INVENT map
Eligibility promised without verification: ELIG-VERIFY-FIRST
Disclosed segment criteria: SEGMENT-FAIRNESS
Systemated extension: EXPIRY-CITE map
Site promo confusion: reroute #111 promotional offers
POFF with Qstomy
Qstomy on Shopify: detect poff intent, POFF-MAP RAG eligibility cite, Klaviyo segment lookup, code verify workflow, handoff #574 bot tier 1 conditions.
Pipeline: #574 bot elig explain → #573 code reissue adjust execute.
Explore AI support and request a demo.
Checklist, FAQ and going further
POFF Checklist (8 steps)
POFF-MAP v1: segment discount exclusions stack expiry
Policy POFF-SUP: 6 ELIG-VERIFY-FIRST rules
8 poff_* typologies: helpdesk tags
4 POFF-* macros: CODE ELIG EXPIRED ADJUST
Klaviyo sync: offer_campaign_id segment export
Shopify discount audit: code_type usage limits
30 min agent training: eligibility vs promo #111 scenario
KPI Dashboard: poff_* section 9
FAQ
Difference with promo #111?
#111 = general site offers. #573 = segmented CRM email offer by profile.
Code not working?
POFF-CODE-01 Shopify verify + min_spend exclusions map.
Why not me?
POFF-ELIG-01 segment_rules verify. SEGMENT-FAIRNESS not third-party criteria.
Is Bot #574 enough?
Tier 1 eligibility conditions quote. Reissue adjust → agents #573.
Going further
This week: publish active campaigns POFF-MAP, test POFF-CODE-01 invalid scenario, measure poff_code_success_rate.
Enzo
July 1, 2026
