I have a client on 9.0.2 that has an intermittent issue with ShipStation not synching all of the shipped orders.

All the orders publish to ShipStation as they should.

The orders are not marked shipped in AbleCommerce.

They process the orders in ShipStation but when they try to synch with AbleCommerce only some of the processed orders are marked shipped with the tracking number. Many orders remain unchanged in AbleCommerce. There aren't any errors and it appears as the synch finished.

This started a few weeks ago and was intermittent but now seems more frequent.

Does anyone have any insight on what may be causing this to happen after working correctly for a couple of years?

Thanks

Good Morning,

I'm not sure about the specific issue you are having, but we fixed one ShipStation issue in 9.0.3 and several more in 9.0.4. To see them all, you can go to help.ablecommerce.com and search on "ShipStation"

Did you upgrade or is this the 9.0.2 version?

Well, if they are trying to update 3000 orders at a time, that makes it extremely difficult to troubleshoot. Maybe they can try smaller batches and try to narrow down the problem.

I do hope that you had a chance to review the change logs and see the issues that were fixed in 9.0.3 and 9.0.4. If there is any particular issue you need more information on, I'd be happy to do that for you.

Fixed in 9.0.4:
[AC9-1225] - Unable to export unpaid shipstation orders
[AC9-1677] - ShipStation Allow to stop an export of orders
[AC9-1676] - ShipStation order marked manully shipped doesn't sync tracking number
[AC9-1673] - Display information with progress bar on Shipstation Sync Order page
[AC9-1668] - ShipStation sync statuses page must show total number of orders
[AC9-1350] - Shipstation: add support for discounted prices so customs forms are accurate

Fixed in 9.0.3:
AC9-1576 ShipStation Order Filter issues with order Id and exporting over 5 at a time

You are right, for the sync process, it doesn't give the option to filter by date or number of orders.

You can try increasing the timeout. That might help, but I'm guessing it's going to take a really long time to sync 3000 orders. You could also try during early AM hours, or at a time when the server isn't busy.

Hi Katie,

I got some information from ShipStation about what they are seeing on their end for sync requests. this is from their tech support:

"Generally valid authentication doesn't get passed along the first time, and then a duplicate request with your authorization is sent, and we respond 200. These timestamps are in Central Time, and they are when we send back our responses. Your requests with/without auth info tend to be received within in a range of about 50 - 400 ms, and each time we're ultimately responding 200.

This is also not unique to just this order. This with/without auth discrepancy is happening for the majority (if not all) of requests coming from this IP address, but ultimately we're responding 200 OK every time.

Is this something you're intending to do? Are you running requests asynchronously, or are you using the response header WWW-Authenticate with the challenge Basic realm="shipstation" to trigger the re-run of the request with your authorization? If the latter, I don't imagine this is a good idea."

Is this something that has been improved since 9.0.2? I can't tell from the change logs.

Thanks

I used wendi's account. Since thats what she used to buy the new license. Just tagging on the get notified on replys

Yes, it shows up but if you leave the page it disappears. The export continues to run, all 220,000 orders. The stop is secondary. It shouldn't be exporting those to start with. It happens when we only select processing status to export. Now we are being very careful to not leave the page until export is correct and done.

I did try to publish again while the first was running, hoping to break it or show me the stop button again. That didn't work , I assume it wont run again until the current one is complete.

Our web page did restart in the night so that stopped it. I had to break the credentials to stop it before that.