> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-portal/coda-portal-appendix/codas-pricing-template.md).

# Coda’s Pricing Template

Here’s the [Sample Google Sheet (Pricing template)](https://docs.google.com/spreadsheets/u/0/d/1QBehJqAGAtEnOdZcqrxkkFYWJnhQCSTkc8HOVoPYFtU/edit). Download and create a copy to submit the pricing information. Convert the Price & SKU info tab in the sheet in CSV format and upload it to the Coda Portal.

You can also download and view the sample or from the Coda Portal.

{% file src="/files/KU7gQjdzlIlW29DjT7VF" %}
Coda Product (SKU) Price Template
{% endfile %}

The sample file contains an example product. Your import file probably contains many more products and variants. If you use the sample file to create your own import file, then make sure that you create a copy of the file and remove all the example products.

## <mark style="color:purple;">**Column headers and Descriptions for Pricing template (Please Refer Carefully):**</mark>

<table><thead><tr><th width="147.33333333333331">Column</th><th width="188">Chinese Translation</th><th>Description</th></tr></thead><tbody><tr><td><strong>ProductID</strong></td><td>档位ID</td><td>- Product ID or SKU ID<br>- Product ID is mandatory (max 100 characters)</td></tr><tr><td><strong>EventPackage</strong></td><td></td><td>- Used as an identifier by the Publisher to deliver correct package items associated with a product. If the Publisher can identify the package items using Product ID then this field is not mandatory.<br>- Integer value<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></td></tr><tr><td><strong>Title_LanguageCode</strong></td><td>档位名称</td><td>- Product Name. The default language code is <strong>en</strong> for English. Please add additional columns if you want to provide translations in other languages.<br>- The column header should be <strong>Title_LanguageCode</strong><br>- Refer to the table in the sample Google sheet for Language Codes.<br>- At least one language is required for every product else the product will be discarded<br>- max 100 characters</td></tr><tr><td><strong>Description_LanguageCode</strong></td><td>档位描述 (英文)</td><td>- Product description. The default is <strong>en</strong> for English. Please add additional columns if you want to provide translations in other languages.<br>- The column header should be <mark style="color:purple;"><strong>Description_LanguageCode</strong></mark><br>- Refer to the table in the sample Google sheet for Language Codes.<br>- <mark style="color:purple;"><strong>Not mandatory</strong></mark><br>- max 1000 characters</td></tr><tr><td><strong>Category_LanguageCode</strong></td><td>档位分类(英文)</td><td>- Product category. The default is <mark style="color:purple;"><strong>en</strong></mark> for English. Please add additional columns if you want to provide translations in other languages.<br>- The column header should be <mark style="color:purple;"><strong>Category_LanguageCode</strong></mark><br>- Absence of a category field will place the Products under the default category - <mark style="color:purple;"><strong>Uncategorized</strong></mark><br>- Refer to the table in the sample Google sheet for Language Codes.<br>- max 50 characters</td></tr><tr><td><strong>Main_IconPath</strong></td><td>档位图片(請列出压缩档案路径)</td><td><p>- Image icon path or url for identifying Product/SKU images in zip folder. If the zip file has following folders is > Dynamic Texture, ItemIcon, Money and the name of the image is Icon_Crystal.png then the icon path will be: <strong>DynamicTexture/ItemIcon/Money/Icon_Crystal.png</strong></p><p></p><p><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></p></td></tr><tr><td><strong>Price_US_Default</strong></td><td>档位价格 (美元)</td><td>- Default Pricing information of the products in USD currency.<br>- Default Price is mandatory<br>- Prices should be inclusive of taxes</td></tr><tr><td><strong>Price_CountryCode</strong></td><td>如果档位价格 不是美元， 請添加带标题 (Price_CountryCode) 的列， country code 可以查看這裏。<br><br>例子: 印尼盾 - "Price_ID"</td><td>- Pricing information provided by Publishers for countries other than the United States (US). Please add additional columns with header Price_CountryCode to provide local prices.<br>- Products without local price will be calculated using the default Price and Coda's fx rates.<br>- Refer to the table in the sample Google sheet for Country Codes.<br>- Prices should be inclusive of taxes</td></tr><tr><td><strong>Sku_Purchase_Limit</strong></td><td></td><td>This sets a purchase cap at the SKU level for each user. Once a limit is defined for a SKU, it restricts how many times a user can purchase it.<br><br><strong>Example</strong>:<br>If User 1 is assigned a limit of 2 for SKU_1, they can only buy it twice. After reaching this limit, they’re restricted from further purchases until the limit is refreshed.<br>This is directly tied to the Refresh_Rate.</td></tr><tr><td><strong>Refresh_Rate</strong></td><td></td><td><p>This defines how often the SKU purchase limit resets for a user.<br><br> <strong>Examples</strong>:</p><ul><li>If User 1 has a limit of 1 for <em>SKU_1</em> and the Refresh_Rate is set to 1 day, they can buy it once per day.</li><li>If the Refresh_Rate is 20 days, they can only buy it once every 20 days.</li><li>If the limit is 10 and the user buys it 4 times, after the refresh period, the limit is fully restored back to 10.</li></ul></td></tr><tr><td><strong>Purchase_Limit_Start_Date</strong></td><td></td><td>This defines the start date from which the Sku_Purchase_Limit and Refresh_Rate become active. <br><br>It’s especially useful for promotional SKUs that need limits enforced only from a certain date.<br><br>Example: 2022-07-27 18:00:00 [Format: yyyy-mm-dd hh:mm:ss]<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></td></tr><tr><td><strong>Web Store Exclusive</strong></td><td></td><td><p>This is a front-end banner on the shop page that indicates a SKU is only available for purchase via the web store—not through in-app purchases.</p><p></p><p> If the SKU is webstore exclusive, enter T in the column</p><p>Default empty is F<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></p></td></tr><tr><td><strong>Start_Time</strong></td><td>如果想档位在指定日期时间上架，请填写日期时间</td><td>- Product availability start time (UTC+0) Example: 2022-07-27 18:00:00 [Format: yyyy-mm-dd hh:mm:ss]<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></td></tr><tr><td><strong>End_Time</strong></td><td>如果想档位在指定日期时间下架，请填写日期时间</td><td>- Product availability end time (UTC+0) Example: 2023-01-11 17:59:59 [Format: yyyy-mm-dd hh:mm:ss]<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark></td></tr><tr><td><strong>Personalized</strong></td><td>個人化</td><td><p>- Signifies whether a SKU is personalizable for a given user; If personalizable, enter T, if not enter F (For eg, if there are purchase limits per user)</p><p>- Default: F<br><strong>- </strong><mark style="color:purple;"><strong>Not mandatory</strong></mark> </p></td></tr></tbody></table>


---

# 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.coda.co/coda-portal/coda-portal-appendix/codas-pricing-template.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.