How to Fix Purchase Order Issues Caused by Tax Item Mapping in Webgility Desktop
This article helps Webgility Desktop users resolve issues with generating purchase orders caused by incorrect tax item mappings. It provides guidance on identifying and removing problematic tax item mappings to restore purchase order functionality.
Causes of Issues
Purchase orders may fail to generate due to:
-
Incorrect or redundant tax item mapping in Webgility Desktop.
-
Conflicts caused by a mapped tax item interfering with purchase order logic.
-
Item mapping discrepancies that block PO creation.
Step-by-Step Instructions
1. Reproduce and Confirm the Issue
-
Try generating a purchase order as usual.
-
If it fails, check for any system or in-app error messages referencing item mapping or tax items.
2. Locate Tax Item Mapping
-
Open Webgility Desktop.
-
Navigate to Connections > Accounting/POS/ERP > Sync Settings > Sales Tax > Configure your sales tax.
-
Locate mappings linked to tax items.
3. Delete Problematic Mapping
-
Select the tax item mapping that may be causing the issue.
-
Click Delete or Remove.
-
Confirm deletion when prompted.
4. Test Purchase Order Creation
-
Go to Orders > Purchase Orders.
-
Attempt to create a purchase order.
-
Confirm that the purchase order generates successfully without errors.
Notes
-
It’s best practice to periodically review and clean up item mappings, especially after major updates or accounting software changes.
-
If you’re unsure which tax item is causing the issue, temporarily disable all tax item mappings and test.