> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/shopper-apis/shopper-basics/common-use-cases/guest-checkout.md). # Guest checkout Sometimes, when browsing a site or app, a shopper might add an item to their cart but then leave without completing the purchase. Cart abandonment occurs in about 34% of cases where the store prompts the shoppers to create an account before completing a purchase. To reduce the likelihood of this happening, we can offer shoppers the option to check out as a guest and simplify the checkout process. It allows shoppers to view orders and update payment information without creating an account. ## Post-order management flow for guest checkout Managing post-order processes for guest shoppers is essential to ensure a smooth and satisfying purchasing experience. This section outlines the steps in handling various scenarios, such as notifications, accessing order details, and updating subscriptions for shoppers who opt to check out as guests. By providing clear and straightforward processes, we aim to facilitate order management and enhance shopper satisfaction even without an account. 1. The notification system [sends a notification](/commerce-api/admin-apis/subscription-management/subscription-notifications/sending-a-subscription-renewal-reminder-notification.md) to the shopper about their subscription. 2. The notification redirects the shopper to the site or app that displays the solution. \ \ **Note**: You determine the solutions such as [order management](/commerce-api/admin-apis/order-management.md), [subscription management](/commerce-api/admin-apis/subscription-management.md), [email notification](/commerce-api/admin-apis/subscription-management/subscription-notifications.md), self-service web page, or app notice and app. 3. The shopper goes to the solution page that contains the subscription summary, where you [create an anonymous guest checkout session](/commerce-api/shopper-apis/oauth/tokens.md#creating-an-anonymous-shopper-session-guest-checkout). 4. You [can get the subscription details](/commerce-api/admin-apis/order-management/downloading-the-invoice.md#step-1-getting-the-order-details) and decide what information to expose to the shopper. For example, if the shopper lands on a page without signing in, you can limit the information displayed. 5. The shopper can go to the subscription details page from the subscription summary page. From the subscription order details page, the shopper can: * Download the invoice PDF. * See all the details of their order. * See their subscription orders. * Update their payment information. * Manually renew a subscription. * Update the subscription. 6. After updating the subscription (by editing the payment, manually renewing, or updating the subscription): * You will receive the relevant webhook. * You will receive the relevant SSN. * The shopper will receive the pertinent email. 7. After the shopper places the order to renew the subscription manually, the shopper returns to the subscription order details page to check the order status. ## Check the order details Order details offer valuable insights into a shopper's purchase status, items, and nuances. This section provides instructions on how authenticated and guest shoppers can access their order details, ensuring transparency and satisfaction throughout the buying process. For authenticated shoppers, order details are conveniently accessible via specific API calls, while administrators can assist anonymous shoppers in obtaining this information. An authenticated shopper can conveniently access their order details using either the [`GET /v1/shoppers/me/orders/{orderId}`](https://docs.digitalriver.com/commerce-api-references/shopper-apis/orders/orders#v1-shoppers-me-orders-orderid) API or the [`POST /v1/shoppers/order-lookup`](https://docs.digitalriver.com/commerce-api-references/shopper-apis/orders/order-lookup#v1-shoppers-order-lookup) API. However, checking order details can be complicated for anonymous shoppers. It could prevent them from resuming the anonymous shopper token and accessing your order information. For more information, see [Order lookup](/commerce-api/shopper-apis/orders-1/order-lookup.md). {% hint style="success" %} An administrator can easily check the order details for an anonymous shopper using the [`GET /v1/orders/{orderId}`](https://docs.digitalriver.com/commerce-api-references/shopper-apis/orders/orders#v1-shoppers-me-orders) API. {% endhint %} ## Cancel the order If you need to cancel an order or a specific line item that has yet to be shipped or fulfilled, you can easily do so using [Global Commerce](https://gc.digitalriver.com/gc/ent/login.do). Configuring notifications ensures that the shopper will be informed of the cancellation, providing clarity and prompt updates regarding their order status. ## An authenticated shopper wants to return the goods Returning goods is a straightforward process for authenticated shoppers. Suppose the shopper is unsatisfied with their purchase or needs to exchange an item. In that case, they can conveniently initiate a return request through the provided [`POST /v1/shoppers/me/orders/{orderId}/returns`](https://docs.digitalriver.com/commerce-api-references/shopper-apis/orders/returns#v1-shoppers-me-orders-orderid-returns) API. It ensures a seamless and efficient way for shoppers to manage their returns and get refunded appropriately. For more information, see [Request the return of one or more line items in an order](/commerce-api/shopper-apis/orders-1/returns/retrieving-returns-for-a-specified-order.md#request-the-return-of-one-or-more-line-items-in-an-order). ## Query the available refund amount for the order Administrators can use the [`GET /orders/{orderId}/refunds-available`](https://docs.digitalriver.com/commerce-api-references/admin-apis/order-management/refunds#orders-orderid-refunds-available) API to query the available refund amount using the designated API endpoint to determine the refundable amount for a specific order. It allows precise and accurate refund handling, ensuring the refund process is transparent and manageable. For more information, see the [Getting the available refunds](/commerce-api/admin-apis/refunds/retrieving-refunds-available-for-an-order.md) section for a specific order. ## Refund the order Refunding an order is a pivotal aspect of maintaining customer satisfaction and trust. Administrators can use the [`POST /orders/{orderId}/refunds`](https://docs.digitalriver.com/commerce-api-references/admin-apis/order-management/refunds#orders-orderid-refunds-1) API to manage a return request for an order. Administrators can ensure accurate and timely reimbursements by querying the available amount and initiating the refund. See the [Creating a satisfaction refund](/commerce-api/admin-apis/refunds/creating-a-satisfaction-refund.md) section for more information. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digitalriver.com/commerce-api/shopper-apis/shopper-basics/common-use-cases/guest-checkout.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.