Content and shopper tools · Last verified 2 November 2026
Configure Saved, Account and support
Set account content, saved-item behaviour and support links while respecting sign-in and returns readiness.
Open App builder > Wishlist and account. These settings control content and presentation; saving them does not activate customer sign-in, order access, returns or push delivery.
Make support reachable
Fill in Support email, Contact page link and Support phone as appropriate. Use a working contact destination, not a page that requires merchant authentication. Review policy summaries against your real policies and test every link on a phone.
Configure Account
Choose the sign-in photo, card title and whether to Show Create account next to Sign in. Set the signed-in header and notification explanation. Complete customer sign-in setup before promising orders or customer data.
In Orders and returns, Show Buy again on orders uses today's products and prices and may skip unavailable items. The signed-out order-tracking row and self-service returns depend on the configured customer-account capabilities. A returns-not-ready message is a setup requirement, not something that styling can remove safely.
Configure Saved
Choose the removal control, After Add to bag behaviour and item order. Review the empty Saved screen recommendation rail with a new shopper as well as a populated list.
Price-drop labels use a comparison against the price recorded when the product was saved. A watched sold-out item needs the active back-in-stock flow and consent before notification messaging is appropriate. Merely enabling its display is not proof that a message will send.
Cross-device saved items require their separate privacy setting and sign-in. Guest saves stay on the device. This is distinct from account reminder sync, which is excluded. See Privacy requests and saved-item sync.
Check the whole journey
Test signed-out and signed-in Account, contact links, add/remove in Saved, Add to bag and return navigation. Try a sold-out item and an order containing a now-unavailable product. Verify both notification permissions and the actual flow before describing alerts as active. Save and publish according to your workspace's current state.