ProductManager
  • Home
  • Getting Started
  • Features
  • Bulk Operations
  • Import & Export
  • Collections
  • Multi-Store
  • Reports
  • Troubleshooting
Show / Hide Table of Contents
  • Store Management
  • Sync to Store
  • Conflict Resolution
  • Send to Store
  • Sales Data Sync

Sync Conflict Resolution

When syncing products between stores, conflicts occur when the same product was modified in both stores since the last sync. The Conflict Resolution window helps you decide how to handle these conflicts.

What is a Sync Conflict?

A conflict occurs when:

  1. Product exists in both source and target stores
  2. Product was modified in BOTH stores since last sync
  3. The changes are to the same field(s)

Without conflicts, sync proceeds automatically. Conflicts require your decision.

Opening Conflict Resolution

The Conflict Resolution window opens automatically when:

  1. You start a sync operation
  2. ProductManager detects conflicting products
  3. You need to decide how to resolve each conflict

Understanding the Interface

Header

Shows the number of conflicting products detected.

Quick Actions

Buttons to resolve all conflicts at once:

Button Action
Use Source for All Overwrite all target values with source
Keep Target for All Keep all target values unchanged
Skip All Don't sync any conflicting products

Conflict List

Each conflict shows:

  1. Product Header - Title and SKU
  2. Conflicting Fields - Side-by-side comparison
  3. Resolution Dropdown - Your choice for this product

Conflict Details

Field Comparison

For each conflicting field:

Panel Shows
Source (green) Value in source store
Target (red) Current value in target store

The arrow (→) indicates direction of potential sync.

Common Conflicting Fields

Field Conflict Cause
Title Name edited in both stores
Price Price changed differently
Description Content updated separately
Inventory Stock adjusted in both
Status Published/draft changed

Resolution Options

For each conflicting product, choose one option:

Use Source (Overwrite Target)

  • Target store values will be replaced
  • Source store values become the truth
  • Use when source has correct data

Keep Target (Don't Sync)

  • Target store values are preserved
  • Source changes are not applied to this product
  • Use when target has correct data

Skip (Ignore This Product)

  • Product is excluded from sync entirely
  • Neither store is modified
  • Use when you need to investigate later

Resolution Workflow

Step 1: Review Conflicts

Scroll through the list to understand each conflict:

  • Which products are affected?
  • Which fields conflict?
  • What are the differences?

Step 2: Choose Resolutions

For each conflict:

  1. Compare source and target values
  2. Decide which is correct
  3. Select resolution from dropdown

Or use Quick Actions for bulk resolution.

Step 3: Apply and Continue

  1. Verify resolution choices
  2. Check "Resolved X of Y" counter
  3. Click Apply & Continue
  4. Sync proceeds with your decisions

Best Practices

Before Syncing

  1. Coordinate edits - Avoid editing same products in both stores
  2. Sync frequently - More frequent syncs = fewer conflicts
  3. Designate primary - Choose one store as authoritative

During Resolution

  1. Check timestamps - Consider which edit was more recent
  2. Consider context - Why was each change made?
  3. When unsure, skip - Investigate before deciding

After Resolution

  1. Verify results - Check affected products in target store
  2. Document decisions - Note why you chose each resolution
  3. Update workflow - Prevent similar conflicts

Common Scenarios

Price Conflict

Scenario: Price was updated in both stores.

Resolution:

  • Use Source if source has correct pricing
  • Keep Target if target has local market pricing
  • Skip to review pricing strategy

Description Conflict

Scenario: Description edited in both stores.

Resolution:

  • Check which description is more complete
  • Consider merging manually after sync
  • Keep Target if target has localized content

Inventory Conflict

Scenario: Stock levels differ.

Resolution:

  • Usually Keep Target (inventory is location-specific)
  • Or Skip and manually verify counts

Status Conflict

Scenario: One store published, other kept draft.

Resolution:

  • Depends on intentional status per store
  • Consider if product should be live everywhere

Troubleshooting

"Too many conflicts"

  • Sync more frequently
  • Review edit workflows between stores
  • Consider using sync field filters

"Wrong resolution applied"

  • Sync again after fixing source data
  • Manual correction in affected store
  • Use Backup Manager if available

"Conflicts keep recurring"

  • Identify products being edited in both stores
  • Assign ownership to one store
  • Use sync field selection to limit synced fields

Understanding the Counter

Footer shows progress:

Resolved: 5 of 12
  • All conflicts must be resolved before continuing
  • Skipped products count as resolved

Keyboard Shortcuts

Shortcut Action
Enter Apply resolutions
Escape Cancel sync

See Also

  • Sync to Store
  • Store Management
  • Multi-Store Overview
In this article
Back to top ProductManager - Shopify Product Management Tool