Price template imports and transfers can propagate incorrect country currencies

If a Price Template is imported from a spreadsheet that does not include currency information, country-specific prices can be interpreted with the wrong currency. For example, prices intended for local currencies such as Serbian dinar or Ukrainian hryvnia may be imported as euro values instead.

If items or offers that use those Price Templates are later moved from sandbox to live using Transfer, the associated Price Templates can be transferred along with them. This can carry the incorrect pricing configuration into the live environment.

What to check

• Review any Price Templates that were imported from spreadsheets.
• Pay special attention to countries whose local prices may look numerically correct but are assigned the wrong currency.
• Before using Transfer from sandbox to live, verify the linked Price Templates in the source environment.

Recommended response

• Restore or manually correct the affected Price Templates in live.
• Also roll back or fix the same templates in sandbox so future transfers do not reintroduce the issue.
• If price values need to be updated, editing the values manually in the existing production templates is the safer path than reusing a bad imported template.

Known incident pattern

In one confirmed case, Price Templates were imported into sandbox from a spreadsheet without currency data. Later, some offers/products were transferred to live, which brought those templates with them and caused country prices to appear in euro instead of the intended local currency.