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

How to Undo and Reprocess Errored Shopify Payouts in Webgility Desktop

This article helps Webgility Desktop users fix payout posting errors that occur after making data or settings changes. It provides step-by-step instructions to update Webgility Desktop, undo synced orders, delete incorrect payout data, re-download the correct payouts, and repost them to QuickBooks Desktop.

Overview

If you've made recent data changes or updated settings in Webgility Desktop, you might run into payout posting errors. These issues are usually easy to fix by clearing old sync data and reposting the correct information. Here’s how to get everything back on track.

Step-by-Step Guide

1. Make Sure Webgility is Updated

  • Open Webgility Desktop

  • Go to Help > Check for Updates

  • If an update is available, install it and restart the application

2. Undo the Affected Orders

  • Go to Dashboard > Posted Orders

  • Find the orders linked to the payout that failed

  • Use Undo Sync to reset them to their pre-posting state
    (This helps avoid duplicates and clears any stuck transactions.)

3. Remove the Faulty Payout Data

  • Navigate to Orders > Shopify > Payouts

  • Find the payout that caused the error

  • Select and delete it to clear incorrect or partial data

4. Re-download the Payout

  • Still in Orders > Shopify > Payouts, click remove under the status option.

  • Now select the redownload option.

  • Check that the new payout data matches your store records and doesn't show any error flags

5. Repost the Payout

  • Select the corrected payout batch

  • Click Post to QuickBooks.

  • Monitor the sync and ensure the payout is posted without errors

6. Final Verification

After reposting, review the following:

  • The order status in Webgility

  • The payout record in your QuickBooks.

  • Any logs or error messages to confirm a clean sync

Tip

Payout errors after updates or data changes are common but usually easy to fix. Keeping Webgility updated and regularly reviewing synced data can help prevent these issues.