Skip to main content
The Omneo Remira integration connects Omneo to the Remira retail platform. It runs in both directions: Remira posts completed sales to Omneo, where they become Transactions attached to a Profile, and the Remira POS calls Omneo during a sale to find a Profile, read its history, and redeem incentives at the register.

​
What the integration does

​
How a sale reaches Omneo

Remira sends each sale to an endpoint the extension exposes for your tenant, in the form /{tenant}/api/v3/sales. Omneo supplies the full URL and the credentials during implementation. Omneo treats the sale according to its state:
  • A finished sale becomes a Transaction. Transactions are immutable, so posting the same sale again does not create a duplicate.
  • A sale in any other state, such as a layby or an unfinished receipt, becomes an Order only when order creation is enabled for your tenant. Otherwise Omneo ignores it.
Once the Transaction is written, Omneo processes it like any other: aggregations update, Points are issued, and Reactions fire. For the field-by-field detail, see Transaction mapping.

​
Regions

Remira is configured once per region, and each region carries its own currency, its own prefix for Transaction, location, and staff identifiers, and its own mapping of Remira discounts to Omneo Benefit Definitions. A brand trading in more than one market runs one configuration per market, so a Transaction identifier shows which region recorded the sale.

​
Identities

Omneo matches a Remira customer to a Profile through an Identity, using the handle remira by default. The Identity value is the Remira customerEntityId. Staff are matched separately through a staff Identity built from the Remira employee identifier.