I just set up a ShipStation account and connected to my BV site based on the blog instruction. Any idea why I'm getting this error as ShipStation tries to update the store?

I submitted a ticket with ShipStation and they have put it back on BV to figure it out. Here is what they say:

I took a look at your account and it does look like you have a Custom Store integration set up in your ShipStation account. This means that the integration and its parameters were built so that you can integrate it into ShipStation. We usually do not have much insight as to what you have to change or the limitations. However, it looks like in this case, the error we are getting is pretty self-explanatory.
In ShipStation, we do require a two-letter abbreviation for the country and the state codes that come in. In your case, it looks like the country codes are not coming in as two-letter abbreviations which are breaking the feed and causing you to see this error.
I would make sure that those are coming in as two-letter abbreviations by consulting with the team who built this custom store integration for you.

I don't think it's possible to have an order with a missing country code in BV, and so I would assume that it's trying to pull the country from the wrong location.

Edited by user Tuesday, January 2, 2018 12:53:29 PM(UTC)  | Reason: added comment

ShipStation is being hands-off with this issue and continually throwing in back in our court to figure out. ShipStation is still considered a BV Partner, right? Maybe they are more of an acquaintance than a partner, ha ha?

Here is what I have set up for statuses (attached). I'm open to suggestions. Also, I noticed that BV Commerce statuses are called different things in different locations. For instance, Pending Payment is also called Unpaid. I tried to cover all bases when mapping statuses in ShipStation.

Edited by user Tuesday, January 2, 2018 5:44:20 PM(UTC)  | Reason: added statuses screen shot attachment

Update: I changed my ShipStation Statuses mapping to exactly what is shown in the BVC Blog directions. Then I actually deleted the orders that ShipStation said were causing the problem, and still getting the error. But now if I filter orders by Unshipped I'm finding a ton of other orders with missing States as well as very old orders listed as Unshipped when they should be Shipped - too many to change manually. Actually, all orders from 2007 and older are coming up with missing 2-digit States. Is there a way to batch archive these?

Edited by user Wednesday, January 3, 2018 10:26:34 PM(UTC)  | Reason: added info

So this error with Ship Station is occurring again. Isn't there a way to permanently fix this bad State Field data in BV so that Ship Station will function properly?

I suspect that I made some changes to the Shipping methods, such as USPS Priority Mail, and that the modification is being pulled into ALL orders. Then SS reads the order as "modified" and tries to import them. And I suspect that SS is trying to bring in ALL old orders again since we surely are not going back by hand and modifying orders from 10+ years ago.

When I view older orders in Admin, I can see the State field as the full State name (eg. California). When I click "Edit" to edit the State field, the State field is actually empty. I would expect it to be empty, I suppose, since the full name does not exist any longer in the drop-down menu.

I'm looking for a permanent fix to this problem and I hope that between BV and SS, you guys can find it. If it's an SS issue, that it should not be updating old orders from a specified time period, then maybe SS fixes that since it is a needed system improvement. If there is residual State field information that needs cleaning up (eg. changing California to CA), then I would prefer BV fix this holistically, as a bug fix.

So I was looking into writing a SQL script to fix the bad (or missing) data in the STATE field for old, old orders. If I look at a test case (eg. Order 605) in the dbo.bvc_Order table of the database, it shows the correct two-letter state (eg. FL) even though it is missing from the STATE field on that particular order on the website edit page. I'm not sure I understand how the field on the website can be blank but the database be populated correctly. Any insight?

Ah, okay. So RegionBvin values for orders up until Sept 1, 2007 are between 1 and about 50. I assume that represents the states some how. After this date the RegionBvin has a long character string for the values. Could I not just write a script to replace the old 1-50 characters with the value that is in the Region field for all orders before this date?

So I had sampled a few of my older orders as test cases for writing the script to insert the missing State/Region field. It appears that simply opening these specific orders in the Admin and clicking Edit to confirm the missing data triggers Ship Station to try to import that order again. Nothing actually gets edited, but apparently Ship Station views it as being edited or changed. That causes Ship Station to lock up again and not import orders, and of course not tell us why until we ask Ship Station to send us the error with list of order numbers affecting it.

Yes, I can go ahead and edit it. However it's more difficult that it would seem. Change the State in Shipping and Billing fields. Save. It's an old shipping method so I have to choose a new shipping method. I have to remember the old shipping cost because that is different, too. Save. The product is then updated to the current product price so it throws off the balance. I better have written down the item cost to type it in. Save.