E-commerce
July 1, 2026
u201cMy cart disappeared when I switched from my phone to my computer.u201d u201cI had a promo code, everything is lost.u201d u201cSupport says to start all over again without even checking my account.u201d Three tickets where a poorly handled cross-device lost cart generates abandonment, a lost promo, and a frustrated customer.
The lost cart support after switching e-commerce devices covers account recovery, manual rebuilding, lost promos, and OOS variants. This complements saved cart (#437) and cross-device (#749): here, we focus on the concrete recovery of an empty cart post-device switch.
This guide #751 covers policy LOSTCART-SUP, flow LC-1 to LC-8, and matrix LOSTCART-MAP. Support service duo of the future: bot LOSTCART (#752).
Summary
Why do cross-device abandoned carts generate tickets?
The customer fills their cart on mobile, switches devices, finds the cart empty. Guest without saving, promo not reapplied, or agent proposes a rebuild without checking the account. Without SOP, support ignores login recovery or confuses it with passive abandonment #47.
Five typical frictions of cross-device lost carts
Guest local cart: not synced between device maps
Account not logged in: login would have restored the cart map
Promo lost: code not reapplied on rebuild map
OOS variant: SKU unavailable at rebuild map
Cleared cookie cache: guest session erased map
Shopify persists connected account carts cross-device; guest remains device-local (Shopify, cart persistence 2026). Without LOSTCART-MAP, agents suggest blind rebuilds without a recovery path.
LOSTCART #751 vs CROSSDEV #749, SCART #437, forfeit #47 and bot #752
Six contents, six distinct cart conversion journeys.
Quick Matrix
#751 LOSTCART: lost cart post-switch recovery rebuild promo variants
CROSSDEV #749: general mobile desktop continuity distinct empty cart recovery
SCART #437: cart save email distinct link loss without save
Abandon #47: distinct email follow-up lost active cart ticket
SCARTbot #438: bot restore save token distinct manual rebuild
#752 LOSTCARTbot: bot retrieve products variants promo tier 1
Cross-device = continuity prevention. #751 = operational recovery of already lost cart post-device switch.
Which lostcart_* typologies to classify?
Eight cross-device lost cart ticket scenarios.
Eight lostcart typologies
lostcart_device_switch: empty cart after device change map
lostcart_guest_no_save: guest without save cart disappeared map
lostcart_login_fix: account login restores cart map
lostcart_rebuild_manual: rebuild SKU manual list map
lostcart_promo_lost: promo code lost with cart map
lostcart_variant_oos: unavailable variant rebuild map
lostcart_cache_cleared: clear cache cookies cart gone map
lostcart_how_prevent: avoid future cross-device loss map
Tags: lostcart, cart_lost, cross_device, recovery. RECOVERY-CITE: recovery_steps_policy_copy map only.
How should the LOSTCART-MAP matrix be structured?
The LOSTCART-MAP matrix documents each lost shopping cart recovery journey for agents and future bot #752.
LOSTCART-MAP Columns
lostcart_program_id: recovery shopping cart map program identifier
recovery_steps_policy_copy: ordered recovery steps verbatim map
guest_recovery_policy_copy: guest save login rebuild map
account_recovery_policy_copy: account login lookup cart map
rebuild_policy_copy: manual rebuild SKU conditions map
promo_recovery_policy_copy: reapply promo code rebuild map
browse_history_fallback_copy: browsing history help rebuild map
oos_substitute_policy_copy: alternative OOS variant map
exclusions_copy: custom final sale rebuild limit map
customer_communication_copy: lost cart help page macro map
bot_intent_map: bot_lostcart_* #752 mapping
Sync lost cart help page, helpdesk macros, and agent login training before rebuild.
LOSTCART-SUP policy in six rules
Six cross-device abandoned cart support rules.
LOSTCART-MAP-GROUNDED : recovery rebuild promo from map only
RECOVERY-CITE : recovery_steps_policy_copy quotes map verbatim
LOGIN-FIRST-CITE : account_recovery_policy_copy before rebuild map
AUTH-VERIFY : account email verify before cart lookup map
CROSSDEV749-REROUTE : continuity prevention → CROSSDEV #749 distinct recovery
SCART437-REROUTE : save existing token → SCART #437 distinct loss without save
Flow LOSTCART LC-1 to LC-8
Eight-step agent flow for cross-device abandoned cart.
LC-1 Intake : lostcart_* intent + device_from device_to email skus promo_code
LC-2 LOSTCART-MAP : recovery guest account rebuild promo oos exclusions
LC-3 Auth lookup : customer logged_in cart saved_carts browse_history AUTH-VERIFY
LC-4 Classify : device guest login rebuild promo oos prevent
LC-5 Triage : RECOVERY LOGIN-FIRST AUTH REBUILD PROMO CROSSDEV749 SCART437
LC-6 Respond : macro LOSTCART grounded customer_communication_copy
LC-7 Execute : ops rebuild cart promo reapply oos substitute escalate
LC-8 Close : tag lostcart_resolved recovery_cited cart_rebuilt Y/N
SLA : lostcart_device_switch answered with LOGIN-FIRST-CITE account_recovery_policy_copy in one interaction.
Essential LOSTCART macros
Four macro agents for cross-device abandoned cart.
LOSTCART-RECOVERY-01
"Abandoned cart [device_from map] → [device_to map] : [recovery_steps_policy_copy map.] Step 1: [account_recovery_policy_copy map.] RECOVERY-CITE LOGIN-FIRST-CITE."
LOSTCART-LOGIN-01
"Log in with the same email [email map] on [device_to map]: account cart may reappear. AUTH-VERIFY. [If empty: rebuild step 2 map.]"
LOSTCART-REBUILD-01
"Manual rebuild: [rebuild_policy_copy map.] Requested SKUs: [list map.] [oos_substitute_policy_copy if OOS map.] [promo_recovery_policy_copy if code map.]"
LOSTCART-PREVENT-01
"Avoid future loss: log into account or save SCART cart #437 before changing device. CROSSDEV #749 continuity map."
Edge cases: expired promo, OOS, B2B, and save token
Five cases outside the standard lost macro basket.
Expired promo rebuild: promo_recovery_policy_copy alternative map
Total variant OOS: oos_substitute_policy_copy or notify back map
Existing save token: SCART437-REROUTE #437 restore link map
B2B draft basket: rebuild_policy_copy separate wholesale catalog map
Passive abandonment: #47 separate email follow-up active recovery ticket
Lost basket recovery = documented login rebuild. Save token or abandonment = separate reroute playbooks.
Essential lost cart KPIs
Five LOSTCART management metrics.
lostcart_recovery_rate: recovered or rebuilt cart / total lostcart device_switch
lostcart_login_first_rate: LOGIN-FIRST attempted before rebuild / total map
lostcart_rebuild_convert_rate: checkout after rebuild / total rebuild map
lostcart_promo_recover_rate: promo reapplied / total lostcart_promo map
lostcart_abandon_post_ticket: abandon after unresolved ticket low target map
Target: lostcart_recovery_rate greater than 60% and lostcart_login_first_rate greater than 90%.
LOSTCART anti-patterns
Five common cross-device lost cart support errors.
Rebuild without login test: LOGIN-FIRST-CITE account_recovery_policy_copy map
Promising guest sync: guest_recovery_policy_copy save or login map
Ignoring lost promo: promo_recovery_policy_copy cite rebuild map
Confusing abandonment #47: active ticket recovery distinct from passive follow-up
Saving unverified token: SCART437-REROUTE lookup saved_carts before rebuild
LOSTCART with Qstomy
Qstomy on Shopify: detect lostcart intent, LOSTCART-MAP RAG grounded, login first cite, handoff #752 bot tier 1 rebuild promo.
Pipeline: #752 bot find products variants promo tier 1 → #751 agents rebuild oos substitute escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
LOSTCART Checklist (8 steps)
LOSTCART-MAP v1: recovery guest account rebuild promo oos exclusions
LOSTCART-SUP Policy: 6 rules RECOVERY LOGIN-FIRST AUTH CROSSDEV749 SCART437
8 lostcart_* typologies: tags helpdesk cart_lost cross_device recovery
4 LOSTCART-* macros: RECOVERY LOGIN REBUILD PREVENT
Live lost cart help page: recovery_steps_policy_copy visible
30 min agent training: LOGIN-FIRST before rebuild LOSTCART-FLOW
Sync browse history lookup: rebuild_policy_copy agent test
KPI Dashboard: lostcart_* section 9 recovery login_first rebuild_convert
FAQ
What is the difference with cross-device #749?
#749 = preventive continuity between mobile and desktop. #751 = recovery of already lost cart post-switch.
What is the difference with saved cart #437?
#437 = customer has saved email link. #751 = loss without saving or login not attempted.
First recovery step?
LOSTCART-LOGIN-01 LOGIN-FIRST-CITE account_recovery_policy_copy map.
Connection with bot #752?
#752 = bot retrieve products variants promo tier 1. #751 = agents rebuild oos substitute escalate ops.
Go further
Cart abandonment (#47)
Support promo codes
This week: index LOSTCART-MAP recovery_steps, sync lost cart help page, test macro LOSTCART-LOGIN-01 guest device switch scenario.
Enzo
July 1, 2026
