Pacejet Speed Issues

Hi ​@Jeff96 

I’m going to reach out by email with proposed meeting date/times to hear more about what your experiencing. 

Dana

​@Jeff96 How does your team handle the “Update Shipment with Pacejet Data” action?

It does not seem to work too well through the “process shipments” screen - it does not seem to process every record. I added a business event to process through the shipment screen, but I think it is processing very slowly due to API request limits which slows down all of the other business events.

hi ​@bwhite49 in our most recent release, we made some design improvements to the pacejet integration. To find out more please see:

Let us know if you see improvements.  We’re always open to hearing feedback if you would like to meetup via Teams.

-Dana

We pack and ship in Acumatica. 

Am meeting with ​@bwhite49 soon via Teams. 

If others want to share feedback as well, please feel free to indicate your interest here on the post.

-dana

We have several issues with the Pacejet Integration as well, while i see there have been some changes in 2026 R1, per the release notes they do not seem they apply to the “Pack and Shipping in Acumatica ERP ” which is what we use as we had hoped to keep everything in Acumatica. 

The Pacejet API response time is wildly variable depending on the carrier / size of shipment, etc.  I believe Acumatica currently sends the ship request then checks in after the delay to see if the shipment is done and the documents are ready to download and if it fails it retries the number of counts specified in the carrier settings. I believe there are issues with the integration on both the Acumatica & Pacejet side, have opened tickets with each but haven’t made much headway, maybe someone here can help get the right people involved. 

While we have tried to increase the delay and retry counts we still face multiple failed shipments per day. It’s unacceptable to set an arbitrarily high value and make our shipping team wait that long for every shipment. Some issues we believe are related to this are:

• 500 Errors
• Duplicate Shipment Number errors (likely because the first request for documents failed). 
• We also have seen that documents coming back to Acumatica overwrite previous documents attached to other shipments (completely different customers) instead of creating new attachments which is a major issue. Pacejet has a rule to fix by creating unique file names, but apparently it may not always run before the documents are available for download, Acumatica should handle this better on their side by never overwriting old documents regardless of the file name. 
• Because of the above issues  the affected shipments can no longer be processed without manual intervention, which involves manually voiding the shipment in Pacejet and then retrying (even though the initial shipment was successful except the Acumatica Update). Or manually confirming the shipment in Acumatica with the ship via disabled for Pacejet integration and manually updating the documents, tracking numbers, cost , etc. 

Beyond the shipping issue there are numerous other smaller issues that we’ve found that need to be addressed. 

Hi ​@acuerp3813 ,

I will send you some date/time options so that we can meet via Teams for a deep dive.

-Dana

​@Dana Moffat  Thanks for setting up a meeting and hearing our issues with the Acumatica <> Pacejet integration. Look forward to working on these issues further with you. 

We've been using Pacejet within Acumatica since ~2017, also with Packing and Shipping in Acumatica ERP as the scenario. ​@acuerp3813 , I have the same issues you have, and more, and sadly things really haven't improved over the years. Confirming shipments still takes too long and fails too often, forcing our warehouse staff to void shipments in the Pacejet portal just so they can retry from the Acumatica side.

To add to your bullet list:

• Slow performance. It's 20–40 seconds from Confirm Shipment in Acumatica to a printed label on a good day. We've modified the delay and retry counts without much effect.
• UOM issues on commercial invoices. Shipments (domestic or international) with shipment lines using a UOM other than EACH are exponentially multiplied on the Pacejet commercial invoice. We've been hit with surprise bills from UPS/FedEx because of this. We built our own commercial invoice as a workaround, which held up until carriers started requiring digital invoices. For these shipments, we can no longer ship through Acumatica/Pacejet and instead have to ship through the Pacejet portal or the carrier's website directly, then copy-paste everything back into Acumatica manually. Defeats the purpose.
• Non-stock kits don't play well. Component items don't carry individual prices or pass HTS codes through. Component items can’t be assigned to multiple boxes, so we quit assigning items to boxes altogether. From an audit standpoint, this is not ideal.

I hope Pacejet’s integration gets more attention now that it’s baked into Acumatica and will watch for updates.

Can you let us know what you changed those settings to? We are also experiencing slowness and have each of those settings at 3.

Thanks

Celeste

​@CelesteKopp For my tenant, I have both values set to 5. This combination has done the most to reduce manual voids in the Pacejet portal, though it's still not perfect. My sense is that it comes down to responsiveness on the Pacejet side, and even upstream of them, with the carriers themselves. Some days are worse than others.