The VTEX shopping cart default behavior is to keep the cart alive until an order is placed. When this happens, a new cart is created. If a business rule requires a new cart every time a user logs out, we can use the Session Watcher to clear cart information.

It is not possible to get a brand new cart, but we can repurpose the current cart by removing any existing information on it.

This document will guide you on how to use the Session Watcher app to clean up an existing cart during logout.

VTEX IO Service Context gives you access to external clients. Clients are additional services with methods that give you access to different core applications. Here is a list of out-of-the-box client services available.

• apps
• assets
• billing
• billingMetrics
• builder
• events
• id
• licenseManager
• masterdata
• messagesGraphQL
• metadata
• registry
• router
• segment
• settings
• session
• tenant
• vbase
• workspaces
• catalogGraphQL
• paymentProvider

You can always extend your App Clients if you need to give it access to external or internal providers.

The VTEX IO Service Context does not have an out-of-the-box checkout client. The following steps will guide you on this setup of a client from our internal APIs.

1. Create a new ./node/clients/checkout.ts file where you can keep all the methods for the Checkout class. This class will extend JanusClient (VTEX’s internal router), you can import it from @vtex/api. It should look like the example below. Types are also imported from @vtex/api.

2. These internal APIs are going through portal.vtexcommercestable.com.br/api/*, which means we need to declare it as an outbound-access in our manifest.json file under "policies".

The same thing is required if you're accessing an external endpoint. Always add the host and path as an outbound-access.

Do not use protocol in the host (http, https). The host does not support wildcard within the address. It can be either fixed host or only * , never both. The path supports wildcard.

3. Now that you have an initial class setup, you can let your application know that it exists. Do this by importing it to the Clients constructor under ./node/clients/index.ts

The checkout client will now be available to our handler, just like the others.

4. Now you need to create your methods. The first thing you need is to change our orderForm (shopping cart) to anonymous. This will erase the clientProfileData, but will not remove the items from the cart, which will be done in another moment.

This method uses a path starting with /checkout, which means we need to include it to our policy by creating a new outbound-access entry. Back tocheckout.ts, add a new public method inside the Checkout class.

JanusClient gives you access to http and its methods. This example uses getRaw, which will return the entire response, including httpCode, headers, etc. If you do not need it, you can use only get instead. This metric property is used for logging, it is not not strictly necessary.

5. Create the other methods, orderForm, and updateItems, as shown below.

Back to ./resolvers/index.ts load the checkout client from the context of our method clearCart and expose both orderFormId and email from the request body.

The logical flow is:

You should have code similar to the example below.

Don't forget to change the vendor in your ./manifest.json file.

To link the app, run this command:

If you wish, you can download this complete example