Different formats for displaying subscription prices

The same order may show a different price in the customer view and in the external system, even if the information is correct. The order is stored with a human-readable amount formatted at the time of the order, along with a numeric value, currency code, and exchange rate used in the calculation. Customer documents use the stored representation, but the integration can generate the net, tax, currency, or decimal value required by the target system.

Distinguish between display value and calculated value of an order

The order display value is how the price was displayed at the time of the order. It can include tax or non-tax price, currency, rounding, and other formatting according to your store's display logic. The saved representation can be used in order summary, order confirmation, emails, and receipts to maintain a consistent historical customer view.

A calculated value is a numeric amount that can be processed by system logic and integrations. In addition, the order retains the currency code and exchange rate at the time of the order. The integration can further derive the value required by the target system from the prices and taxes on the lines. The display value and the calculated value should not be directly substituted for each other, as they have different functions.

Why can the same order show a different price in different systems?

The same order will show a different price when the systems present values intended for different uses. What is relevant for the customer and the merchant is the view at the time of the order. What is relevant for the target system may be the unit price excluding tax, tax percentage, base currency, a certain decimal precision, or another value according to the integration agreement.

Therefore, a difference alone does not indicate an error. A transformation must be placed somewhere whenever the human-readable representation and the target system contract differ. The customer view stored in the model is preserved and the technical transformation is performed at the system boundary. If a transformation is removed from one place, the need moves to another place.

Why is the price at the time of order kept?

Preserving the price at the time of ordering prevents the historical order from changing with later settings. If the displayed price were to be recalculated every time, the result would have to use exactly the same tax or tax-free display method, exchange rate, rounding, line spacing for promotions and discounts, shipping costs, payment method surcharges, and other terms and conditions at the time of ordering.

Reproducing all the input data later would increase complexity and risk of error and would not guarantee the same presentation. Therefore, the stored price text serves as a historical display truth, while the numerical values serve the calculation. For example, the amount visible to the customer may be 499 SEK , even if the base value used in the calculation or the integration value is treated in euros.

Where is the price conversion done?

The order price conversion is done in the integration when the data is transferred to the target system. For example, an ERP export can send the net price and tax percentage of a product as separate values, or generate a tax-free value for delivery, discount, and payment method surcharge. The exact method of conversion is always part of the agreement for the integration in question.

Performing the transformation at the integration boundary keeps the human-readable views of the order consistent. The same principle applies to other technical transformations: the representation of the transaction can be preserved even if the interface requires a different unit or format. This is a modeling solution, not an indication that the system cannot calculate the price in another way.

How do taxes, currency, and discounts make a difference?

Taxes, currency, and discounts on an order can make the same price appear different in different systems. A store may display products, shipping, and payment method surcharges as taxable, while an external system expects the net value and tax percentage separately. In this case, the same number does not belong in both views, but the integration converts the information into the agreed format.

Currency can produce a similar difference: the system base value can be in euros and the customer's order is 499 SEK . A historical order is not recalculated later with the new day's exchange rate. Campaigns, discounts and payment method surcharges can also include rounding or order-specific divisions. The final result shown to the customer is preserved, even if the integration processes the parts in a different format.

How can visible price differences be reduced?

The visible price differences on an order can be reduced by using a single, consistent price representation across the store. When customers always see prices with the same tax and currency, checkout, confirmations, and subsequent customer documents will naturally remain more consistent. However, this does not eliminate the need for the integration to use its own technical value.

If a store allows multiple representations for different customers or orders, differences will inevitably spread across views or systems. The goal should be to ensure that each view uses the correct value intended for it, not that each system always displays the same number regardless of taxation, currency, or integration agreement.

When is a price difference expected and when is it an error?

An order price difference is generally expected if the store and customer documents maintain the presentation at the time of the order, but the external system displays a different tax treatment or currency format as agreed. It is also expected that the historical price will be preserved if regulations, tax rules, or exchange rates change later. Different orders may display differently if multiple display models are allowed.

An error should be suspected if the checkout price changes in the order confirmation, email, or later customer view without an order change; the Dashboard Summary does not match the customer's order time; a historical order changes later; the integration sends something other than what its contract requires; or one view handles the same price internally inconsistently. Do not compare the gross presentation of a customer document directly to the net value in ERP if the conversion is intentional.

Check order amounts in the Dashboard

Checking the order amounts starts from the Orders view in the Control Panel. Open the order and compare the Total value on the Summary tab with the customer's order confirmation and receipt. Also check the Currency stored for the order: the currency code and Currency value describe the order's native currency and exchange rate.

If the discrepancy is only visible in the integration, check the definition of that integration: whether the net or gross price is sent, in which currency, and with what decimal precision. If the discrepancy is already visible between the customer's documents, first delimit the changed row: product, delivery, payment method surcharge, discount, campaign, tax, or other order amount.

What information is needed for a pricing error support request?

To request support for an order price error, you will need the order number and a screenshot or exact value from the checkout, order confirmation or email, and the Summary tab in your Dashboard. Please tell us in which external system the potential discrepancy is visible and what value is required by its integration agreement.

Additionally, please indicate whether the store uses one or more price formats and whether the observation is related to a tax or non-tax price, currency, shipping cost, payment method surcharge, discount, campaign, or other order line item. This information will help support distinguish between an actual error and an expected display or integration conversion and compare the correct values.