> For the complete documentation index, see [llms.txt](https://docs.nosto.com/shopify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/shopify/post-purchase-upsell.md).

# Post-Purchase Upsell

Introduction to Nosto’s Post Purchase Upsell extension for Shopify - what it does, how it works, and what you need to enable it.

## What is Post Purchase Upsell?

Nosto’s Post Purchase Upsell lets you present one last personalized product offer right after a customer completes payment but before they reach the Shopify Thank You page. This is done using Shopify’s Post Purchase Extensions framework, ensuring a seamless checkout flow with no redirects or popups.

The extension allows merchants to:

* Increase average order value with zero friction.
* Control the offer logic and experience via Nosto.
* Rely on Shopify to handle order editing and charging the payment method.

## How It Works in Shopify

1. Customer completes payment → Shopify creates the order and sets it to **On hold** status.
2. Nosto’s Post Purchase Upsell offer page is displayed inside the Shopify Checkout.
3. Customer accepts or declines the offer:
   * **If accepted**: Shopify edits the order and charges the payment method.
   * **If declined**: order continues to fulfillment.
4. Once the step completes, Shopify releases the order from **On hold** status.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nosto.com/shopify/post-purchase-upsell.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.