UPS XML: Support Thread

[GoldBuckle]

That constant (MODULE_SHIPPING_UPSXML_SHIPPER_NUMBER) has been part of the UPS-XML since at least v1.7.7.

My only suggestion is to enter the following in the admin's "Install SQL Patches" tool

DELETE FROM configuration WHERE configuration_key LIKE 'MODULE_SHIPPING_UPSXML_%';

That will remove all configuration elements for the UPS-XML shipping module (you'll have to re-enter all the settings).

Just ran the patch and now it is showing up in the shipping options.

Thank you!

john

[HeleneWallis]

We're running ZC 1.57d, and the UPS shipping module was working correctly. But it also displayed the red message that there was a new version. So I installed the new version and now Shipstation is unable to write the shipping info (date, shipping service and tracking number) back to the customer's order record. The error we're getting from Shipstation is "An error occurred attempting to update orders: Invalid XML. Error: 'Unexpected end of file has occurred. The following elements are not closed: Orders. Line 3, position 1.' We received: '<?xml version="1.0" encoding="utf-16"?> <Orders> '

There was nothing in our logs about the problem, so it's not causing an issue in Zencart itself.

At this point, we have to go into every order manually and add the shipping info, so my shipping people are understandably giving me a very hard time.

[lat9]

We're running ZC 1.57d, and the UPS shipping module was working correctly. But it also displayed the red message that there was a new version. So I installed the new version and now Shipstation is unable to write the shipping info (date, shipping service and tracking number) back to the customer's order record. The error we're getting from Shipstation is "An error occurred attempting to update orders: Invalid XML. Error: 'Unexpected end of file has occurred. The following elements are not closed: Orders. Line 3, position 1.' We received: '<?xml version="1.0" encoding="utf-16"?> <Orders> '

There was nothing in our logs about the problem, so it's not causing an issue in Zencart itself.

At this point, we have to go into every order manually and add the shipping info, so my shipping people are understandably giving me a very hard time.

Could you turn on the UPSXML debug and send me a copy of the file? I'll PM you my direct email address.

[HeleneWallis]

Could you turn on the UPSXML debug and send me a copy of the file? I'll PM you my direct email address.

Welp, the problem turned out to be something entirely different. What the shipping folk said to me was completely the opposite of what was actually happening. I had installed the latest Shipstation module that I downloaded from Shipstation itself, not realizing that it was only for 1.5.8. So Shipstation was failing to import orders from Zencart, not failing to update the Zencart orders with the shipment info--tracking number, etc. When I realized what had happened and reinstalled the older version of Shipstation's interface, it all worked fine.

But I do still have a question about UPS XML. UPS has a class called UPS Ground Saver, and I don't see any way to enable that in Zencart. It's available through Shipstation, so we can take advantage of it, but I'd like to be able to offer it to our customers as well. Is there any way to include that in the plugin?

[carlwhat]

...UPS has a class called UPS Ground Saver...

never heard of it.

in the feb 2023 UPS Rating Package XML Developer Guide, you can see a screenshot of the service options from the US.

best.

[HeleneWallis]

never heard of it.

in the feb 2023 UPS Rating Package XML Developer Guide, you can see a screenshot of the service options from the US.

best.

Yes, I had already seen that. Ground Saver is apparently what Shipstation calls the UPS SurePost service, their 'last mile' service that hands off packages under a certain size to the USPS. So that is probably why it isn't available in the XML interface, because it requires package size information in order to be an option. Oh well. I wish we could offer it to our customers, but without volume info being available, it wouldn't be feasible. Our products are frequently purchased together, so regardless of the size of each individual one, a total order could easily add up to not being SurePost eligible.

[swguy]

Small bug in a recent update.

line 387
if ($next_zone['zone_id'] < 1 || $next_zone['zone_id'] === $order->delivery['zone_id']) {

fails to work because of ===. $next_zone['zone_id'] is not an int the way $order->delivery['zone_id'] is.
Casting fixes.

The symptom is the shipping estimator does not show UPSXML rates prior to login for users who restrict UPSXML by Zone.