Skip to main content
Some conversions happen at the moment Omneo needs them rather than when a Transaction arrives. For these, Omneo asks the Currencies extension for today’s rate between two currencies, unless you have configured a fixed rate. Each converted record keeps the rate it used, so the value stays auditable after rates move.

​
Tier points across regions

The tier-point.create.with.region Reaction action issues tier points into the Profile’s region. With convert_currency set to true, the amount is converted from the Transaction’s currency into the currency of the Profile’s region: If the live rate cannot be obtained, the tier points are issued at face value (a rate of 1). The tier point’s meta records transaction_currency, profile_currency, exchange_rate and exchange_rate_date.

​
Region switches

When a Profile moves to a different region and its tier is defined per region, Omneo moves the Profile onto the matching tier in the new region. It then adds one adjustment tier point that converts the Profile’s tier points from the last year into the new region’s currency. If no rate can be found, no adjustment is made and the tier points stay as they were. The adjustment tier point carries is_converted: true in its meta, so a later switch only converts tier points earned after it.

​
Omneo Clienteling

Profile aggregation blocks in Omneo Clienteling can show spend figures in the store’s local currency. The store currency comes from the location’s clienteling.currency_code custom field, or from its country. Clienteling asks the extension for today’s rate from your default currency to the store currency, and falls back to yesterday’s rate when today’s is not yet published. A block configured with its own fixed rate table uses that table instead.