Raytio's XRM (External Relationships) module manages merchant and external commercial relationships within the platform. It builds on the PRM (Party Relationships) foundation to model merchants as a specialisation of parties, then layers on classification, geographic presence, item catalogues, inbound email handling, authentication configuration, and webhook integration.
The XRM data model is built around merchants - business entities that extend the platform's party model - with supporting records for classification, geographic presence, product catalogues, and external system integration. Understanding how these relate is the key to understanding how Raytio's merchant management works.
The XRM module includes a subsystem for managing inbound email routing and filtering. Four configuration areas work together to define how incoming email is handled: domain-level rules filter by sender domain, email address configuration defines recipient behaviour, email-level rules filter by sender address, and quarantine records hold messages flagged for review.
Merchant authentication configuration stores OAuth settings for authenticating with external merchant systems. Each record defines the full OAuth flow parameters for a specific merchant, enabling the platform to obtain and refresh access tokens from merchant APIs.
Merchant classifications categorise merchants by their type of business. Rather than storing category data directly on the merchant profile, the platform links merchants to classification items in the general product catalogue. This design enables a rich, hierarchical classification taxonomy shared across the platform.
Two supporting record types define what a merchant offers and where they operate:
Merchants are the central entity of the XRM module. A merchant represents a marketplace participant or external business that offers goods or services through the platform. Every merchant is linked to a party profile, inheriting foundational identity data while adding merchant-specific attributes.