Fixing Settlement Report Posting Errors Caused by Inaccessible Orders in the Repository of Webgility Desktop
This article helps Webgility Desktop users resolve Amazon settlement report posting failures in Webgility Desktop caused by inaccessible or corrupt orders in their repository. It provides step-by-step guidance to identify and remove the problematic order without requiring database-level changes, enabling successful settlement report posting.
Symptoms You Might Encounter
-
Settlement report posting fails repeatedly
-
One or more specific orders are involved in the error
-
The affected order doesn’t appear during redownload attempts
-
Error persists until the order is removed from the repository
Step-by-Step Resolution
1. Identify the Problematic Order
-
Review the settlement posting error message for the order number or ID.
-
Check if that order is missing from your Orders tab or cannot be redownloaded.
-
If necessary, refresh your order list or use search filters to locate it.
2. Move the Order Out of the Repository
-
Go to the Order Repository module in Webgility Desktop.
-
If the order is visible, select it.
-
Use the Move, Archive, or similar function to remove it from the active repository.
-
If the order isn’t visible but is suspected to be corrupt, proceed with a full order list refresh to validate its absence.
Note: Make sure you have the appropriate permissions and backup procedures in place before performing repository changes.
3. Retry the Settlement Report Posting
-
Once the affected order has been moved out, attempt to post the settlement report again.
-
The posting should now complete successfully without triggering the previous error.