Skip to main content
Retailgrid supports multi-currency setups. This page explains how a currency value is chosen for any given price or cost.

​
Resolution order

For any price, cost, or transaction, Retailgrid evaluates currency in this order:
  1. Product-level currency - if currency is populated on the Products row, that value wins.
  2. Account-level (Organization) default - if the row’s currency is empty, the Organization’s default currency is used.
The backend resolves currency once per record. There are no hardcoded defaults - if neither layer is set, the value is treated as “currency unknown” and metrics that depend on currency comparison are flagged.

​
Setting the Organization default

Open Settings -> Organization and pick a default currency from the list (ISO 4217 codes). This becomes the fallback for any row missing a currency field.

​
Multi-currency workflows

If your products are sold in multiple currencies:
  • Provide currency on every Products row that differs from the Organization default.
  • Configure FX rates in the Organization settings so cross-currency comparisons (CPI, Price Gap against a competitor in a different currency) resolve correctly.
If you don’t set FX rates, Retailgrid won’t auto-convert - it will surface the mismatch instead of silently using a wrong rate.

​
What the frontend does

The frontend only formats and displays. It doesn’t merge or select currencies. If you see a currency formatted oddly, the issue is upstream in the data, not in the UI.