Resolving Issues with Shopify Purchase Order Number Sync in Webgility Desktop

Before you begin:

Confirm that the customer has approved and paid the discounted $800 customization quote
Make sure you have the correct customization package (node and config file) for both US and Canadian profiles
Request remote access credentials or an installation window from the customer if needed

To install:

First, backup any existing configuration files in the Webgility Desktop
Deploy the provided custom node and configuration file into the correct directory for each environment (US and CA)
Confirm that the PO field mapping logic is included, based on the developer’s implementation notes

In Webgility Desktop:

Go to Connections > Accounting/POS/ERP > Sync Settings > Purchase order settings
Check that the new PO number field is visible
Map this field to the corresponding Shopify field used for both B2B and B2C orders
Save and apply the updated configuration

Tip: Make sure you configure field mapping separately for both the US and Canadian profiles.

To verify the setup:

Place test orders in Shopify (one B2B and one B2C) with unique PO numbers
In Webgility, run an order sync
Confirm that the PO number imports successfully for both order types in both environments (US and CA)

Note: If everything works, both types of orders should show PO numbers in the correct fields after sync.

Handling PO Field Name Discrepancies

Sometimes, the PO number may not import for B2C orders. If this happens:

Open the Shopify order object via API or admin
Compare the field names used for PO numbers in B2B vs. B2C orders
If discrepancies are found, adjust the config file or custom node accordingly

This article helps Webgility Desktop users deploy and troubleshoot the Shopify Purchase Order (PO) number customization in Webgility Desktop. The customization ensures that PO numbers from both B2B and B2C Shopify orders sync correctly into Webgility Desktop for U.S. and Canadian store profiles.