> For the complete documentation index, see [llms.txt](https://docs.platter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platter.com/resources/faqs/what-is-a-post-purchase-page-vs-thank-you-page.md).
# What is a post-purchase page vs thank you page?
A **post-purchase page** (like Platter+'s) appears **immediately after checkout** but **before the thank you page**.
The key benefit? Customers can accept an offer with just one click. N**o need to re-enter payment information**.
In contrast, a **thank you page** is displayed **after checkout is fully complete**. While you can promote additional products on a thank you page, customers would need to go through the friction of re-entering their payment details to make another purchase.
{% tabs %}
{% tab title="Post-purchase page" %}
{% endtab %}
{% tab title="Thank you page" %}
{% endtab %}
{% endtabs %}
### Why does this matter?
1. **Increases revenue without disrupting checkout**: The post-purchase offer comes *after* the customer has already completed checkout, so there’s no risk of losing the original sale.
2. **Frictionless experience**: One-click post-purchase offers feel seamless. Customers don’t have to re-enter payment details, making it easier for them to say “yes” to an offer.
3. **Higher conversion rates**: With less effort required, post-purchase offers often convert better than thank you page upsells.
4. **Adds to the original order**: The post-purchase offer is added to the same transaction, simplifying order fulfillment and reducing shipping costs.
### Quick Comparison
| | Post Purchase Offer Page | Thank You Page |
| ---------------------------------------- | ------------------------ | -------------- |
| Displays personalized offers | :white\_check\_mark: | |
| Adds to original order | :white\_check\_mark: | |
| Increases average order value | :white\_check\_mark: | |
| Doesn't require re-entering payment info | :white\_check\_mark: | |
| Multi-currency | | |
| Detailed summary of order | | |
---
# 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.platter.com/resources/faqs/what-is-a-post-purchase-page-vs-thank-you-page.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.