Replication Intelligence

Overview

Replication Intelligence monitors iVend's data synchronization system — the engine that keeps store databases in sync with HQ. It tracks 20 object types across all your stores.

The 20 object types

iVend replicates these categories of data between HQ and stores:

• Product data: Items, prices, barcodes, categories
• Promotion data: Promotions, discounts, coupons
• Loyalty data: Loyalty programs, member records, point balances
• Configuration: Store settings, POS configuration, tax rules
• Transaction data: Sales, returns, exchanges (store → HQ)
• Inventory data: Stock counts, adjustments, transfers

Each object type has its own replication queue. Pulse monitors each queue independently.

Queue depth and health

For each object type, you see:

• Queue depth: Number of pending records waiting to sync
• Status: Healthy (below threshold), warning (approaching threshold), or critical (above threshold)
• Failed records: Records that attempted to sync but failed
• Last sync: Timestamp of the most recent successful synchronization

Troubleshooting backlogs

When a queue enters warning or critical status:

1. Check the affected store's connectivity (is the store online?)
2. Look for failed records — they indicate data conflicts or schema issues
3. Check the iVend Replication Service on the store server (is it running?)
4. Look at the HQ server's CPU and disk — resource constraints can slow replication

Failed records

Click the failed records count to see the error log. Common failure reasons include data conflicts (duplicate keys), schema mismatches between HQ and store versions, and network timeouts. Most failures resolve by restarting the replication service. Persistent failures may indicate a version mismatch that requires an iVend update.