Skip to content
  • There are no suggestions because the search field is empty.

How to Fix Product Price Sync Issues Between Webgility Desktop and Clover

This article helps Webgility Desktop users who encounter product price synchronization failures between Webgility Desktop and the Clover channel. Users may notice that price updates made in Webgility Desktop are not reflected on their Clover channel. The guide provides step-by-step instructions to diagnose the issue, isolate root causes, and restore accurate price syncing between the platforms.

Overview

This article guides you through diagnosing and resolving product price synchronization failures between Webgility and Clover devices. Use the following steps to isolate the problem and ensure correct data flow between platforms.

Preliminary Checks

  • Confirm the issue:  Review the specific products and price discrepancies reported.
  • System prerequisites: Ensure both Webgility and Clover accounts are active with valid subscriptions and that the affected products are present in both platforms.

 

Step 1: Verify Webgility Settings

  1. Log in to Webgility.
  2. Navigate to Connections > Sales Channel > Manage Sales Channel.
  3. Verify that Clover is listed as a connected sales channel.
  4. Review Product Mapping to ensure products are linked by SKU or product code.
  5. Under Sync Settings, confirm price data is set to sync from the intended source (Webgility or Clover) to the correct direction.

Step 2: Check Connectivity Between Webgility and Clover

  1. From Webgility, run a Test Connection for the Clover integration (found under Connections > Manage Connections).
  2. Review the result. If the test fails:
    • Confirm internet connectivity on both platforms.
    • Check that Clover API keys/credentials have not expired or changed.
    • Ensure there are no firewall or network restrictions blocking the sync.



Step 3: Initiate Manual Price Sync

  1. In Webgility, use the Sync Now option for products or entire catalog.
  2. Monitor errors or warnings. Note any product IDs or error messages specific to price updates.
  3. Address errors as follows:
    • Authorization errors: Re-authenticate the Clover connection.
    • Mapping errors: Adjust SKU/product associations to resolve mismatches.
    • API Limitations: Consult Webgility and Clover documentation for known sync constraints.