{"id":116,"date":"2026-09-25T09:00:00","date_gmt":"2026-09-25T07:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=116"},"modified":"2026-09-20T21:40:42","modified_gmt":"2026-09-20T19:40:42","slug":"bevestigen-voor-winkelwagen-vervangen","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/confirming-before-a-shared-cart-replaces-the-current-cart\/","title":{"rendered":"Confirming before a shared cart replaces the current cart"},"content":{"rendered":"

Always ask visitors to confirm before a shared basket replaces their current basket.<\/strong> A sharing link is an invitation to view a selection, not permission to erase existing choices. First show what will be taken over, what is already in the recipient\u2019s own basket and what the chosen action will do.<\/p>\n

This detail determines whether sharing feels trustworthy. Someone may open the link from a chat, newsletter or internal email and forget that a personal order is already prepared. If that content immediately disappears, the harm is greater than one extra click could ever be. A clear intermediate step protects both the user and customer service.<\/p>\n

Choose deliberately between replacing, merging and keeping<\/h2>\n

Replacing is technically simplest: after approval, the existing basket is emptied and the shared selection is rebuilt. Merging sounds friendlier but raises difficult questions. What happens to the same product in two quantities, conflicting configurations or a coupon that applied to only one selection? Offer merging only if those rules have been explicitly designed and tested.<\/p>\n

A third option is temporary storage. The online store saves the current cart under a recognisable name, then restores the shared selection and offers a way back. This suits logged-in business customers, but requires sound access and retention management. For a simple guest journey, a clear preview with \u201cCancel\u201d and \u201cReplace my cart\u201d is often sufficient.<\/p>\n

\n\n\n\n\n\n\n\n
Action<\/th>\nWhen suitable<\/th>\nMain risk<\/th>\n<\/tr>\n<\/thead>\n
Replace<\/td>\nA clear, separate selection<\/td>\nThe existing cart disappears without a clear warning<\/td>\n<\/tr>\n
Merge<\/td>\nSimple products without configuration conflicts<\/td>\nDuplicate lines, quantities and discount logic<\/td>\n<\/tr>\n
Save first<\/td>\nLogged-in B2B customers with several working lists<\/td>\nUnclear ownership or outdated saved carts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Make confirmation specific and accessible<\/h2>\n

Do not just ask \u201cAre you sure?\u201d. For example, write: \u201cYour current cart contains 4 items. If you continue, we will replace them with the 7 items in this shared selection.\u201d Give the safe exit a full button beside the confirmation. Visitors must be able to move between controls with the keyboard, the dialogue needs an understandable name, and cancelling should return focus to the button that opened it.<\/p>\n

Provide feedback after confirmation. State how many lines were added and which could not be restored. A product may have disappeared or have insufficient stock in the meantime. Announce errors prominently and only move focus when necessary. A successful action can be announced more quietly through a status region.<\/p>\n

Consider closing the dialogue too. Escape, cancelling and the back button should produce predictable outcomes. Temporarily disable the confirmation button while the server is working, but restore it with a specific error message if the request fails. A partially completed replacement is unacceptable: build the new cart completely first, or restore the previous contents if an unexpected error occurs.<\/p>\n

Fictional example: an installer shares a customer selection<\/h2>\n

Installer Noor creates a selection of a thermostat, sensors and installation materials for a customer. The customer opens the link on a laptop whose cart already contains filters for another order. The online store shows both item counts and offers to save the existing cart as \u201cKitchen maintenance\u201d first. The customer chooses this, then reviews the thermostat selection and confirms the replacement.<\/p>\n

During restoration, one sensor turns out to be temporarily unavailable to order. The store adds the other items, flags the sensor and lets the customer return to choose an alternative. The original filters have not been lost, and the customer understands exactly why the total differs. If the final order then needs to enter business software, only that confirmed order belongs in the integration flow. Read how to keep that transfer manageable in reliably integrating an online store and ERP<\/a>.<\/p>\n

Acceptance criteria before launch<\/h2>\n