Catalog-Account Sync Block Architecture
Catalog and account data synchronize from Core Aria to Aria Allegro. The following describes the key components involved in catalog and account sync.
Core Aria
Core Aria configures the Data Feed Last Order Milestone (LOM) subscription for your account. The data feed must be enabled before sync can occur; this is typically managed during client onboarding. Catalog and account activities trigger Data Feed events that publish Data Feed LOM JSON to a Kafka topic.
Aria Allegro Sync Service
The Aria Allegro Sync Service consumes messages from the Data Feed Kafka topic and performs the following.
- Creates an activity log with the Data Feed LOM JSON for audit and reconciliation.
- Marks the activity log as IGNORED if the data feed is not relevant. To reduce noise, review the data feed notification settings in Core Aria.
- Converts the JSON payload into the structure required by Aria Allegro.
- Uses a common library to call APIs that create catalog and account objects in the database.
- If the Data Feed LOM errors, updates the activity log status to Error with the reason. You can reprocess these records after correcting the cause. Common errors include:
- Kafka topic producer and consumer setup issues.
- Data Feed LOMs received out of order—reprocess after subsequent messages arrive.
- Missing configuration in Aria Allegro. Core Aria catalog sync requires configuration in Aria Allegro; set all configurations before reprocessing. Account data is view-only and requires no setup.
Allegro UI lets you review and reprocess account and catalog sync activities.