E-commerce
July 1, 2026
A customer may discover a product on mobile, add it to the cart, and then want to finalize the purchase on a computer. If the cart, promo code, or session do not carry over, they might think the shop has lost their information.
The chatbot must explain what synchronizes with the account, what remains linked to the device or browser, and how to retrieve the cart or order without starting over.
This guide shows how to support e-commerce journeys that move from one device to another.
Summary
Why does multi-device usage create friction?
The customer does not think in terms of sessions, cookies, or browsers. They expect to find their selection everywhere, especially if they are logged in or if they received a link by email.
When the cart disappears, the chatbot must calmly explain the possible causes: account not logged in, different browser, expired session, local cart, or a promo code linked to a device.
For the customer, the journey is a single purchase, even if it spans multiple devices.
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
What information should be checked?
The bot must check if the customer was logged in, the original device, the browser, the account, the email, the products in the cart, the promo code, the link received, and the step where the issue occurs.
It must also distinguish between a lost cart, a different cart, an already validated order, and an attempted payment without confirmation.
How can I help find the cart?
If the cart is synchronized with the account, the bot can advise logging in with the same email on the other device. If the cart is local, it can suggest recreating the cart from viewed products or sharing a link if the feature exists.
The customer must know why some information follows and other information does not.
How to manage promo codes?
A promo code can depend on the account, channel, country, device, or a campaign. The chatbot must verify the rule before concluding that the code is invalid.
If the customer received the offer on mobile and is using it on desktop, the bot can ask for the link or screenshot to understand the source.
How to secure the payment?
If the customer has started a payment on one device and resumes on another, the chatbot must check if the order is confirmed before recommending another attempt.
In case of doubt about a charge, the priority is to forward to payment support with the time, amount, email, and any potential screenshot.
Which flow to follow?
The flow must restore the continuity of the journey.
Identify original device, current device, account, browser, shopping cart, code, and step.
Check if the customer was logged in and if the cart is synchronized or local.
Guide the login, cart recovery, shared link, or reconstruction.
Check promo code, currency, country, and payment status before recommending a retry.
Transfer important lost carts, suspicious payments, disputed codes, and untraceable orders.
Which messages should be used?
To explain: "If you were not logged in, the cart may have remained linked to the browser of the first device."
To guide: "Try logging in with the same email on the computer to see if the cart synchronizes."
For payment: "Before making another payment, let's check if an order has already been confirmed."
When to transfer?
The transfer is necessary if the cart contained a limited offer, if payment was attempted, if the promo code disappears, if the order cannot be found, or if account synchronization seems to be failing.
The bot must transmit account, devices, browser, cart, code, time, error message and customer expectations.
Which KPIs should be monitored?
Track abandoned baskets, multi-device connections, untransferred promo codes, interrupted payments, drop-offs after switching devices, and recovered conversions.
This data reveals the invisible gaps in the cross-device journey.
Which mistakes should be avoided?
Avoid assuming that the customer made an error, recommending a new payment without verification, ignoring local carts, or not explaining the difference between account and browser.
The chatbot should help continue the purchase, not make them start over.
How can Qstomy help?
Qstomy can connect the chatbot to country-specific payment rules, the catalog, inventory, currencies, carts, crowdfunding campaigns, authorized history, and support procedures to respond clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing country availability, a final currency, a banking restriction, a crowdfunding delivery promise, or a multi-device synchronization that has yet to be confirmed by a reliable source.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key Takeaways
The cross-device journey depends on the connection, the cart, the browser, the promo code, and the payment status.
What the customer must understand
The customer must understand why some information follows their account and other information remains linked to the device.
The chatbot's correct limit
The chatbot can guide the recovery, but it must transfer doubtful payments, large lost carts, and disputed codes.
Enzo
July 1, 2026
