Pulling Custom Fields into Shipstation

HI @amgill

The issue you’re facing might be due to various factors. First, make sure that the meta keys you’re using are correct. They should match exactly with the custom fields you’re trying to pull in. If you have any extra spaces or incorrect case, it might not work.

Second, please ensure that the custom fields you’re trying to pull are linked to the products in the order. If the fields are not linked, they won’t get pulled into ShipStation.

If you’ve checked these and it’s still not working, it might be a compatibility issue with your current version of WooCommerce or ShipStation Integration plugin. Make sure both are updated to the latest version.

Finally, there might be a conflict with another plugin. Try deactivating other plugins temporarily to see if that resolves the issue.

Let us know how that goes. Looking forward to helping you.

Thanks for responding. I have checked all you suggested….except deactivating plugins which is tough to do on a very busy site, but I may have to do that in the evening and put it on maintenance mode to do some testing. We do have a lot of plugins on this complex site so that may be it. I will let you know what we find.

Hi @amgill

I understand that deactivating plugins on a live site can be challenging. However, it is an essential step in troubleshooting as some plugins may conflict with WooCommerce, causing issues on your site.

To minimize disruption, you can plan the maintenance during off-peak hours or test in a staging site.

Once you’ve completed the testing, please share the results with us. We’re here to assist you through the process and help resolve any issues you might encounter.

Thank you for your patience and understanding.

@shameemreza Sorry to say this still is not working. I set up maintenence during off-hours, deactivated all plugins except what was needed, changed to a default theme, and tested an order pushed to shipstation and still custom fields 2 and 3 do not show up despite the function code being correct. I have reached out for support from Woocommerce and Shipstation and they have been unable to help me further. I am only told to hire an “expert” which will cost $$$ when I feel like this could be a bug in the plugin.

I have been searching for a solution for several weeks on this. Even comments on Github show people back in 2019 have had trouble with this feature: https://gist.github.com/woogists/53d13508835276e66578f9c6f2398d03
Has the export of custom fields been tested recently? I really don’t think it is working and it is very frusterating because it would save my client a lot of time if these fields were pulled in as noted AND I cannot seem to find any solution – only trying steps that never resolve the problem.

Can I ask…am I looking for meta keys in the correct spot? I found the meta keys I needed in the MySQL table “wp_woocommerce_order_itemmeta”. I even tested _qty as one of the custom fields to see if it would bring in that info and it does not.

• This reply was modified 1 year, 1 month ago by AMGill.

Hi there @amgill ??

Thank you for reaching back, elaborating futther on this.

I set up maintenence during off-hours, deactivated all plugins except what was needed

Just to clarify, which plugins were active while testing? Troubleshooting should be done with only WooCommerce and WooCommerce ShipStation Integration active, in this case.

Also, just to be sure, were you already able to find the culprit of why the custom fields are not imported from your site to ShipStation, or otherwise? I noticed this thread is marked as resolved.

Tools to help with troubleshooting

Meks Quick Plugin Disabler will remember what plugins you had active when you switch it back on.

You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin.

Please let us know how that goes.

Sorry @anastas10s this ticket is not resolved. That must have been an accident. Correct – only woocommerce and shipstation were active during the testing.

Yes I do know how to set up staging and do it quite often but wanted to set up on the live site as to not mess with the shipstation connection.

Also Custom Field 1 pulls in the coupon as it should. But custom 2 and 3 have nothing!

This question was not answered

Can I ask…am I looking for meta keys in the correct spot? I found the meta keys I needed in the MySQL table “wp_woocommerce_order_itemmeta”. I even tested _qty as one of the custom fields to see if it would bring in that info and it does not.

Is this feature working for other people? Has it been tested recently?

Hello @amgill,

I replied to your ticket in WooCommerce.com a few weeks ago. ?? I wanted to confirm that this code snippet is still working as expected. I created a brand-new test site just now and the custom fields I created were moved over to ShipStation.com perfectly.

For your reference, I created fields with the Checkout Field Editor, replaced “_meta_key” and “_meta_key_2” in the snippet with the field names I created, and injected the snippet using the Code Snippets plugin.

It should work. If it doesn’t, then it is most likely something else on the site causing the issue as my colleagues mentioned earlier, so it might make sense to hire someone to look into it.

Hope this helps!

• This reply was modified 1 year ago by Paulo P - a11n. Reason: typo