CSF - Customer Shipment Entry Unable To Ship

Hello,

is anyone else having issues since the 2026.1 upgrade on customer shipment entry coming up with this error then having to refresh multiple times then ship for it to work ?

I haven’t seen any reports of that. Have you done a trace to see what record it might be missing?

its been with epicor since upgrade day looks like CSFUK issue referencing the packaging but there stumped

We’ve had the same issue.

I’ve dug quite deep into it and it seems the UK CSF module hadn’t been upgraded to EFCore.

Have you logged a ticket? You’ll need to ask for that DLL to be reinstalled. This will incur some downtime. It seems like they’ve fixed the DLL but not rolled it out to everyone. It’s still not totally correct for us, but we’re able to ship now as the Biscit handheld was causing many of the issues.

Hello yes raised with epicCare and now its under a problem ticket, the reinstall CSF twice now for us but it has not fixed it

So we’re still unable to close packs from the handheld. Before our warehouse couldn’t even ship a pack before the reinstallation.

Are you simply entering the customer shipment entry screen and the error appears?

I can see the faulty extension module behaving differently depending on how extensively it’s being used. So it behaving differently for us makes sense.

so yeah our situation is similar to yours.

We pick and pack on Biscit, then we go to the computer enter box data then ship and we get fedex label, however currently when we ship we get the error on the computer, when we first went live we had the error when converting picked orders to packs we encountered HTTP404 errors where it made blank pack’s aswell as the correct pack

It seems as though Epicors method of development is to let its end users find the bugs and then fixing them in hotfixes.

But we’ve had this issue for nearly 2 months now. It doesn’t seem prioritised when the impact for us was as fundamental as being unable to ship.

I’ll post in here if we get any major movements but the only real solution I had was reinstalling the DLL.

unfortunately we are cloud…

As are we, I meant reinstalling the DLL via a support ticket :grinning_face:

I do wish I had the ability to do it myself though!