> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/shoppy-dashboard/settings/app-settings/miscellaneus.md).
# Miscellaneus
### **Quick purchase**
Quick purhcase button
**Faster checkout, fewer clicks!** With the **Quick Purchase** feature, a **"Quick Purchase" CTA button** appears directly below each product card on the **Product Listing Pages**. This allows app users to add items to their cart and proceed to checkout without having to open the product page—making shopping quicker and more seamless.
**Customization Options:** Once enabled, you can personalize:
* **CTA button color**
* **CTA text color**
* **CTA button text**
### **Hide Shoppy Watermark**
In this section you can decide to hide the Shoppy watermark that appears on the splash page and in the application Settings view.
### My Team: Push Notification Testing
To test push notifications and ensure that they are working correctly, you can add team members' **email address** to test push notifications on a specific device. This functionality is only available for the Bloom plan.
{% hint style="warning" %}
Make sure to insert the email address associated with the Shoppy account, and to be logged into that account on the test device for the best results.
{% endhint %}
{% embed url="" %}
---
# 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-en.shoppy.is/shoppy-dashboard/settings/app-settings/miscellaneus.md?ask=&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.
