> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/monetization/create-in-app-product.md).

# Create In-App Product

### How to create an in-app purchase product in AppMySite

Before configuring in-app purchases in App Store Connect or Play Console, you must first create the product in your AppMySite dashboard. This will generate the Product ID required for store configuration.

{% embed url="<https://scribehow.com/viewer/Create_In-App_Purchases__0HIZL7UYR92cAreTtvp8sA>" %}

#### Step 1: Create an in-app purchase product

* Log in to your AppMySite account.
* Select the app where you want to offer in-app purchases.
* From the side menu, go to Monetisation > [In-app purchase](https://app.appmysite.com/app/in-app-purchase/products).
* Click Create in the top-right corner.
* Select the item type.

You will see a pop-up displaying all screens and elements of your app.

* Select the screen where you want to enable in-app purchase.
  * This can be a screen in the bottom bar
  * A menu item
  * Homepage
  * App launch screen
  * Or other available sections
* You can select multiple screens at once.
* To apply in-app purchase on an external link, select webview.
* After selecting the required screens, click Create.

A pop-up will appear displaying the Product ID.

{% hint style="warning" %}
The Product ID generated here is required while configuring App Store Connect or Play Console. You can also find the Product ID later on the in-app purchase product listing screen.
{% endhint %}

* Use the pen icon to edit a product.
* Use the bin icon to delete a product.

#### Step 2: Configure the product layout

You can customize how the in-app purchase screen appears in your app. Click the Layout button on the in-app purchase screen. Here you can:

* Update the product icon.
* Edit the text fields:
  * Heading (14–150 characters)\
    This is the main title shown on the in-app purchase screen. Use it to clearly highlight the offer, such as unlocking premium content or accessing exclusive features.
  * Description (47–250 characters)\
    Provide a brief explanation of what the user will receive after purchasing. Clearly describe the benefits or features being unlocked.
  * Button text (8–20 characters)\
    This is the call-to-action button users will click to complete the purchase. Keep it short and action-oriented.
  * Cancel button text (8–20 characters)\
    This text appears on the secondary button that allows users to decline the purchase and return to the app.
* Change the background
  * Select an image from the image library
  * Upload your own pre-designed image
  * Create a new image within AppMySite
* Modify the theme to match the overall app design.

Once the product is created and customized, you can proceed to configure it in App Store Connect or Play Console using the generated Product ID.


---

# 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.appmysite.com/app/monetization/create-in-app-product.md?ask=<question>&goal=<endgoal>
```

`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.