ID530 - UPS Integration Troubleshooting & FAQ

Before you complete an e-automate upgrade, please search the WorldShip Computer for these two files: eautoexport.dat and eautoimport.dat. These should be saved in a safe location before the upgrade in case they are needed.

Server Move affecting UPS Integration:

1. The SQL login from the original server used in the integration must be manually deleted from the converted e-automate production database "Security" section.

2. Recreate or create a new SQL login for the ODBC and WorldShip integration on new server with the default schema +_custom_placeholder" on the converted e-automate production database for versions prior to 20201008. For versions 20201008 and later, the SQL login must be set so it has db_datareader and db_datawriter permissions on the CEO Juice and e-automate production databases. The schema needs to be set to "dbo."

3. The ODBC driver used in the integration on the WorldShip workstations must be updated and configured to point to the new server using the new SQL login and password.

4. The eautoimport and eautoexport WorldShip import/export mapping logins must be updated in WorldShip with the new SQL user ID & password.


New WorldShip workstation added:

  1. The eautoimport and eautoexport files can be copied from the original workstation, another WorldShip workstation, or your backup location.
    1. The files must be placed in the appropriate UPS sub-folder (the installation path can vary, but is usually C:\Program Data\UPS\WSTD\ImpExp\Shipment on stand-alone work stations.  If WorldShip is set up using the LAN configuration, the remote workstations should automatically detect these files
    2. The ODBC DSN name used in the integration on the original or other WorldShip workstations must be created on the new workstation. Note: DSN name is CaSE SenSiTivE! Use ODBC Data Sources (32-bit) and create the ODBC under the "System" tab. The mapping files are linked to the ODBC, so the new ODBC must be an exact match.

If the files are copied into the correct folder, but they do not show up in the WorldShip client as an option for Keyed Import or Export After Shipment Processing, then typically the DSN name is wrong (or the DSN user ID & password login connection isn't working.

New User on WorldShip Computer:

If the ODBC is created under the "System" tab, it is available to anyone who logs in to the workstation.
If the ODBC is under the "User" tab, the new user must have the exact same ODBC USER DSN name created under their user profile. Remember, WorldShip stores a lot of the data on the user profile, which is why most clients setup a domain user called ‘shipping’ so that they aren’t constantly having to reset the mapping.
To create the new user: look at that user's ODBC DSN configurations. There might be one called ‘WorldShip’ or something to that effect. If you see a WorldShip ODBC connection, then you need to create the exact same ODBC connection under the new user. Remember, the name is CAsE SensITive and has to match exactly.
Why doesn't the UPS Shipping Label Address Info match the SHIP TO info from the packing list/sales order?
Do you have your customer address imported into the WorldShip address book and/or are you using the pencil edit on either the sales order or the shipment in e-automate to change the ship to address?
ODBC Error State:

Open the Import/Export Menu in WorldShip, to eautoexport to verify the user pointing to the ODBC.


Updating WorldShip:
Historically, updating WorldShip to a new version does not affect the integration. Make sure you have copies of the two mapping files in case there is a problem.  You will need to enable the import and export functions:
Let us know at if you run into any issues.
No records found:
The integration uses the sales order shipment record in e-automate.  This record is create in one of two ways--shipping the sales order in e-automate or fulfilling the sales order. There must be a shipment record for the integration to work.
The preferred method is to ship the order in e-automate, then process the shipment in WorldShip. You can then set up an e-agent to invoice your shipped sales orders after business hours.  This preserves the option to add a customer freight charge to the shipment.
You can fulfill the sales order prior to processing the shipment in WorldShip.  Once the order is fulfilled, changes to the shipment record are limited.
No tracking information in e-automate:
Make sure the export function is turned on (see above).
The import function must be used.  It not only populates the recipient information in WorldShip, it also brings in data which link the shipment to a shipment record. Without those data, the integration has no way to link the exported data to a shipment record.
On versions 20201008 and later, the shipment records are updated by a task that runs every 10 minutes.  Make sure you wait at least 10 minutes before checking to see if a shipment record updated.
Customer Freight Charge:
The integration can calculate a basic freight charge and add it to the shipment record. This is usually a flat rate, UPS cost plus a flat rate, or UPS cost plus a markup. Many clients only charge for freight if the sales order is greater than $0. We also have these options for customer freight charges:
If you are interested in using the integration to add a customer freight charge, please let us know what you want the charge to be and how you determine when and which customers to charge.  Complex calculations are beyond the scope of the integration.
How many workstations are included in the fee:
For non-CEO Juice clients, the fee includes two workstations. Additional workstations are $75.00 each.
There is no charge for CEO Juice clients.  If you have multiple workstations, we will walk you through the setup process on the first couple of workstations.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk