Update prices¶
Target Audience: Users, Developers, Stakeholders, Customer service
Introduction¶
When you don't want to adjust the prices of your products manually via PAP and/or use our API's, you can raise a fee-based ticket and we'll do it for you.
Before we can perform this task for you, you'll need to fill out the spreadsheet-templates corresponding to your needs. For us to be able to process your request in time, we strongly suggest you submit the request at least 3-4 weeks prior.
There are two ways to deliver the price list:
| Method | Use when |
|---|---|
| Lists specifying each known payment period | You want full control: every row points out one existing payment period in Payway and states both its current and its new price. |
| Lists from subscription system | Your price list is exported from your subscription system and identifies packages/campaigns by their integration code. |
How the price update is performed¶
- We first do a test run with your list. No prices are changed in the test run.
- You receive a report from the test run with the rows that will be updated, the rows that could not be processed (and why) and any warnings.
- When you have approved the report, we perform the actual price update.
A price change applies to the payment period. Existing subscriptions on that payment period will be charged the new price from their next renewal.
Update prices using lists specifying each known payment period¶
The list must be created such that each row identifies one specific payment period to update in Payway. This process currently does not support the complex price model. Should you wish to use this process for changing the prices on packages that are using the complex price model then you must raise your ticket at least 4 weeks prior to when the price change is scheduled to be done.
This process supports both packages and campaigns, including campaigns that transition to a package, flex campaigns and campaigns that end without a transition. Only the price of the payment period is changed. The payment period is not activated or deactivated, and campaign transitions are left intact.
| Column name | Description | Allowed values |
|---|---|---|
| ProductCode | The product code of the package or campaign in Payway | String, must match the product code |
| PurchaseType | The purchase type of the period to update | String, recurring or limited |
| PaymentMethod | The payment method of the period to update | String, e.g. adyen-scheme See all payment options here |
| PeriodType | The period type of the period to update | String, day, week, month or year Fixed campaign periods: fixed |
| PeriodLength | The length of the period to update | Integer |
| Activated | Is the period to update enabled for purchase or not | String, true or false |
| CurrentPrice | The current price of the period to update | Number, e.g. 247.5 or 247,5 No thousand separators, currency or text |
| NewPrice | The new price of the period | Number, e.g. 260 or 260,00 No thousand separators, currency or text |
How rows are matched¶
- Each row must match exactly one existing payment period on all columns: product code, purchase type, payment method, period type, period length, activated and current price. Make sure the current price is the price in Payway today.
- A row that does not match an existing payment period is reported back to you. No new payment periods are created by this process unless separately agreed.
- Each payment period may only appear once in the list. Every payment method is its own payment period, e.g.
adyen-scheme,adyen-applepayandadyen-googlepaymust be given as three separate rows. - Rows where the new price is the same as the current price are skipped.
- Rows with a price that is not a plain number (e.g.
19.877,00orSEK 199) are rejected. - For campaigns, the purchase type column is not used to find the payment period.
Attention
Rows that change a price of 1 or more to 0 are flagged in the test run report. We will confirm these rows with you before the actual price update is performed.
Download template¶
| Description | Type | link |
|---|---|---|
| Update prices with period specific list | .csv | Tulo_Payway_Change_Prices.csv |
Update prices using lists from subscription system¶
Good to know
- Payment periods are matched on integration code, purchase type, payment method and period length. If no existing payment period matches a row, a new payment period is created.
- When using the complex price model, rows with the same integration code, purchase type and period length are combined into one payment period with several price details. These rows must therefore have identical payment options.
- Prices must be plain numbers (e.g.
260or247.5) without thousand separators, spaces, currency or text.
Update prices with standard price model¶
A description of the columns found in the template when updating packages/campaigns using the standard price model. This means you define a single price for all products included in your package.
| Column Name | Description | Allowed Values |
|---|---|---|
| integration_code | Integration code of the package / campaign in Payway | Must match the integration code in Payway |
| purchase_type | The purchase type of the subscription period | limited / recurring |
| payment_options | The payment methods of the subscription periods separated by comma | E.g. invoice,adyen-scheme See all payment options here |
| period_length | The length of the subscription period | Integer |
| price | The new price of the subscription period | Decimal |
Update prices with complex price model¶
A description of the columns found in the template when updating packages/campaigns using the complex price model. This means you define one or more price rows for one payment period.
| Column Name | Description | Allowed Values |
|---|---|---|
| integration_code | Integration code of the package / campaign in Payway | Must match the integration code in Payway |
| purchase_type | The purchase type of the subscription period | limited / recurring |
| payment_options | The payment methods of the subscription periods separated by comma | E.g. invoice,adyen-scheme See all payment options here |
| period_length | The length of the subscription period | Integer |
| price | The new price of the subscription period | Decimal |
| price_detail_name | The name of the price detail | paper / digital |
Download templates¶
| Description | Type | Link |
|---|---|---|
| Update prices with standard price model | .csv | Tulo_Payway_UpdatePrices_Template.csv |
| Update prices with complex price model | .csv | Tulo_Payway_UpdateComplexPrices_Template.csv |
Payment options¶
| Name | Value |
|---|---|
| Adyen Apple Pay | adyen-applepay |
| Adyen Credit card | adyen-scheme |
| Adyen Finnish e-banking | adyen-ebanking_FI |
| Adyen Google Pay | adyen-googlepay |
| Adyen Klarna Paylater | adyen-klarna |
| Adyen Klarna Paynow | adyen-klarna_paynow |
| Adyen Mobilepay | adyen-mobilepay |
| Billecta Autogiro | billecta-autogiro |
| Billecta E-invoice | billecta-invoice_einvoice |
| Billecta Invoice by e-mail | billecta-invoice_email |
| Billecta Invoice by mail | billecta-invoice_mail |
| External subscription system Autogiro | autogiro |
| External subscription system Invoice | invoice |
| External | external |
| Free | free |
| Klarna Payments | klarna_payments |
| Ropo | ropo |
| Visma Pay Credit card | creditcard |
| Visma Pay online bank payment (limited) | directdebit |
| Visma Pay online bank payment (recurring) | directdebit_recurring |