How to import tax mapping and solve performance Issues in Webgility
This article helps Webgility Desktop users manage state-specific tax mappings by explaining the importance of updating tax jurisdiction data regularly. It also highlights how large CSV imports or complex tax mappings can affect performance, causing slow UI response or freezing.
When working with state-specific tax mappings (e.g., for NY or PA zip codes), it's important to periodically update tax jurisdiction data within Webgility. High-volume CSV imports or overly complex tax mappings can impact performance, resulting in slow UI response times or application freezing.
Step 1: Review Current Tax Mappings
-
Open Webgility Desktop.
-
Navigate to:
Connections > Accounting / POS / ERP > Sync Settings > Sales Tax -
Ensure the option "Enable Sales Tax for Multiple Sales Tax Jurisdictions" is enabled.
-
Click Setup Tax Location.
-
Use the Export Mappings option to review current zip code entries.
-
Confirm whether high-volume zip codes (e.g., NY, PA) are already mapped.
Step 2: Prepare the Updated Mapping CSV
-
Make sure the CSV file includes proper headers and a clean format.
-
Typical columns:
-
Zip Code
-
Tax Rate
-
State
-
(Optional: County, City)
-
-
Remove:
-
Duplicate records
-
Any zip codes already present in your current mapping
-
-
Save the cleaned file for import.
Step 3: Import the CSV into Webgility
-
Return to:
Connections > Accounting / POS / ERP > Sync Settings > Sales Tax -
Confirm "Enable Sales Tax for Multiple Sales Tax Jurisdictions" is still active.
-
Click Setup Tax Location.
-
Use the Import Mappings option and upload the prepared CSV.
Step 4: Troubleshoot Performance Issues
If you experience slowness or application freezing:
-
Monitor system resources (CPU, RAM) on the machine running Webgility.
-
Temporarily close other heavy applications (e.g., browsers, accounting software).
-
Split the CSV file into smaller batches (e.g., 500–1000 rows per file) and import them incrementally.