How to Create Merge Configurations

How to Create Merge Configurations

Merge configs let you combine vehicle data from multiple sources (e.g., vAuto + HomeNet) into a single unified view with field-level priority control.

When to Use Merge Configs

• •You have the same vehicles in multiple systems
• •Different systems are authoritative for different fields
• •You want a "best of both worlds" view combining pricing from one source and photos from another

Creating a Merge Config

POST /api/v1/merge-configs
{
  "name": "Combined Inventory View",
  "sourceIntegrationIds": ["vauto-uuid", "homenet-uuid"],
  "priorityOrder": ["vauto-uuid", "homenet-uuid"],
  "fieldPriority": {
    "price": "vauto-uuid",
    "internet_price": "vauto-uuid",
    "description": "homenet-uuid",
    "photos": "homenet-uuid"
  }
}

How Merging Works

• 1VIN Match: Vehicles are matched across sources using their VIN
• 2Priority Order: For fields without explicit priority, the first source in priorityOrder wins
• 3Field Priority: For specific fields, the designated source takes precedence regardless of priority order
• 4Missing Data: If the priority source doesn't have a value for a field, the next source fills in

Example

Vehicle VIN 1HGCM82633A004352 exists in both vAuto and HomeNet:

Querying Merged Data

GET /api/v1/merge-configs/:id/data?limit=50&offset=0&search=Honda

This returns the merged vehicle data with source attribution for each field.

Updating a Merge Config

PATCH /api/v1/merge-configs/:id
{
  "name": "Updated Name",
  "fieldPriority": {
    "price": "homenet-uuid"
  }
}

Best Practices

• •Use your pricing/DMS system as the priority for financial fields (price, cost, markup)
• •Use your listing platform as the priority for marketing fields (description, photos)
• •Review merged data periodically to catch any mapping issues
• •Start with 2 sources; add more once you're comfortable with the merge behavior