Feature - Guest Checkout

Guest Application (Web/iOS/Android)

• Guest Checkout
  The Guest Checkout feature accommodates the users who wish to order online without registering for an account. This will allow for capturing incremental sales resulting from a conversion lift at the /cart to /payment step. Current version of this feature does not include:

  • Marketing communication opt-in

  • Option to register after order placement

This feature is newly developed and not yet enabled across all markets. It may undergo A/B testing in selected markets to ensure optimal performance. If you’re interested in enabling this feature in your market and participating in A/B testing, please contact the CSM team for early access.

CMS (Sanity)

• Guest Checkout - Time To Live

  • Guest Checkout Time to Live configuration - allows you to specify period in which transactional data will be stored in Sanity. Read further on the <Knowledge Base>-placeholder.

Support Tool

• Guest Checkout - Refunds

  • As a support tool user you are able to perform refunds via Support Tool for guest orders as normal. Please keep in mind that you will not be able to search for a guest order using customer email address and you will not be able to access a user profile.

How to enable:

The feature is controlled by two flags - one for the backend and one for the frontend

• FE: enable-guest-checkout (example)

• BE: enable-guest-checkout (example)

At the frontend is one dependent flag - enable-move-signup-after-cart (example)

Translations (Lokalise strings specific to Guest Checkout):

payWithCreditCard
payWitPaymentChequeGourmet
choosePaymentMethodOption
payWithPaymentSodexo
payWithPrepaidCard
payWithBlik
payWithIdeal
signUpOrGuestToContinueDisclaimer

continueAsAGuest

Analytics:

You may monitor performance by filtering eCommerce Purchase events by an attribute guestID or by event property Is Guest Order:

You may also track the following event:

Please follow the following document for most recent updates on event tracking.

Email communication

Notification Service should send all transactional communication to guests. We shouldn't use Braze for that.

It’s controlled by LD flag – enable-notification-service-email (example)

You should set the following targeting end enable flag: