Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 3 additions & 12 deletions docs/DEVELOPER/roku-pay/quickstart/product-catalog.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@

- [**Cancellation offers:**](#creating-cancellation-offers) Create discount offers to retain customers when they try to cancel their subscription to your app.

- [**Price change scheduling**](#scheduling-a-price-change-for-a-purchase-option). Schedule price increases/decreases and apply them to new subscribers only or both new and existing subscribers.
- [**Price change scheduling**](#scheduling-a-price-change-for-a-purchase-option). Schedule price increases/decreases and apply them to new subscribers or existing subscribers.

- [**Purchase options**](#creating-purchase-options): Add a single product and then create multiple purchase options for it (a purchase option includes the pricing, billing, and offers for a product). This means that, for example, you can create a subscription product for the content you offer, and then add monthly and annual purchase options for it. This structure simplifies and streamlines the catalog workflow.

Expand Down Expand Up @@ -71,15 +71,6 @@

Limited-time offers (active or scheduled) created in Catalog 1.0 cannot be updated in Catalog 2.0. The limited-time offers continue to work as expected in Catalog 2.0; however, they are not editable and must run for their full duration before you can set up another offer for the same purchase option SKU. Limited-time offers created and scheduled in Catalog 2.0 are editable.

**Price changes to existing customers in Catalog 1.0 are applied to both new and existing customers in Catalog 2.0**

In Catalog 2.0, when you schedule a price change for a purchase option, it is always applied to new subscribers (you can apply price changes to new subscribers only or both new and existing subscribers). As a result, price changes applied to only existing customers in Catalog 1.0 are applied to both existing and new customers after you upgrade to Catalog 2.0.

To maintain separate pricing for new and existing customers, schedule a price change for new customers at the new price (the earliest price changes can go into effect is the next calendar day after you upgrade to Catalog 2.0).

**15-day notice required for price increases to existing subscribers**

If you increase the price of a purchase option for existing subscribers, you must give them a 15-day notice.

**Purchase options for deleted products are in the Purchases>Ended tab**

Expand Down Expand Up @@ -171,45 +162,45 @@
<th>
Billing plan setting
</th>

Check warning on line 165 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<th>
Description
</th>
</tr>
</thead>

Check warning on line 171 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<tbody>
<tr>
<td>
Billing frequency
</td>

Check warning on line 177 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<td>
Select the billing period to be used for the subscription product: <strong>monthly</strong>, <strong>quarterly</strong>, or <strong>annual</strong>. Using quartely billing requires [additional API work](doc:add-ons-integration#appendix-a-add-on-api-reference).
</td>
</tr>

Check warning on line 182 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<tr>
<td>
Regular price
</td>

Check warning on line 187 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<td>
Select one of the predefined price tiers for the product. Tiers are used to enforce 99-cent or 49-cent pricing (in USD) on app products:&#x20;

Check warning on line 190 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-in-cell] blank line inside HTML table cell content (breaks GitHub/IDE preview) — replace with <br /> or restructure
- One to three-digit tier numbers are used for 99-cent pricing. Subtract 1 cent from a tier to get the corresponding price. For example, Tier 1 is 99 cents, Tier 2 is $1.99, Tier 10 is $9.99, Tier 100 is $99.99 and so on. The highest tier is 400 ($399.99).
- Four-digit tier numbers are used for 49-cent pricing. Append 49 cents to the last digit or last two digits in the tier to get the corresponding price. For example, Tier 1000 is 49 cents, Tier 1001 is $1.49, Tier 1010 is $10.49, Tier 1020 is $20.49, and so on. The highest tier is 1030 ($30.49).

Check warning on line 193 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-in-cell] blank line inside HTML table cell content (breaks GitHub/IDE preview) — replace with <br /> or restructure
See the [Price tier reference guide](doc:price-tiers) for the complete list of price tiers for each Roku Streaming Store.<br /><br />A chart displays the price, in the appropriate local currency, for each Roku Streaming Store where the product will be available:&#x20;

Check warning on line 195 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-in-cell] blank line inside HTML table cell content (breaks GitHub/IDE preview) — replace with <br /> or restructure
- The **Currency code** is the three-letter ISO-4217 code of the currency in which the customer will be billed.
- The **Purchase price** reflects the amount to be paid by the customer. The purchase price for EU Streaming Store countries includes VAT. Proceeds are based on pre-tax (net) prices.
- The **Net price** field displays the pre-tax price. The **Proceeds** field displays the amount that you receive from Roku for the sale of the product. Based on exchange rate fluctuations, the proceeds in one Channel Store may not equal the amount to be received in another.

Check warning on line 199 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-in-cell] blank line inside HTML table cell content (breaks GitHub/IDE preview) — replace with <br /> or restructure
If you are creating a <a href="/dev/docs/tvod-app-catalog">TVOD-exclusive app</a>, select any price tier. The price passed in the <a href="/dev/docs/channelstore">ChannelStore APIs</a> overrides the price corresponding to the selected price tier. <br /><br />**Certification requirement**: SVOD apps must provide a 30-day notice to existing customers before changing the price of their service.<br /><br />If you want certain products to only be available in specific countries, create in-app products for each country and filter out the product by the country in the app business logic. Specifically, you can call the **getUserRegionData** command to determine the country associated with the user's Roku account, and then implement business logic to filter the results of the ChannelStore **getCatalog** command to only display products that should be available for that country. In this case, the publisher is responsible for handling currency coversions.
</td>
</tr>

Check warning on line 203 in docs/DEVELOPER/roku-pay/quickstart/product-catalog.md

View workflow job for this annotation

GitHub Actions / Lint changed docs

docs-lint

[html-blank-between-tags] blank line between tags inside HTML table (breaks GitHub/IDE preview)
<tr>
<td>
Base offer
Expand Down Expand Up @@ -424,7 +415,7 @@

### Scheduling a price change for a purchase option

You can schedule a price increase/decrease of a purchase option. The price change may be applied to new subscribers only or both new and existing subscribers. If you increase the price for existing subscribers, you must give them 15-days notice.
You can schedule a price increase/decrease of a purchase option. The price change may be applied to either new subscribers or existing subscribers. If you increase the price for existing subscribers, you must give them notice at least 7 days prior but no more than 30 days of the day the increase takes effect. The notice should provide a simple and easy method to cancel.

> The price change goes into effect based on the location associated with your developer account; therefore, you may need to consider time zones for when you want the price change to start.

Expand All @@ -448,7 +439,7 @@

a. For new subscribers, the earliest that a price change can go into effect is midnight the next day.

b. For existing subscribers, the selected date must be 15 days in advance of the listed date. You must give current subscribers 15-days notice per Roku's certification requirements..
b. For existing subscribers, the selected date must be 15 days in advance of the listed date.

6. Click **Review and publish** to review the price change before publishing it.

Expand Down
Loading