cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
web4
First-timer (legacy)
Status: No status
Have Shopify's "Additional Details" and "Notes" sections import to different ShipStation fields! They are currently importing to 1 field in Shipstation, "Customer Order Notes". Currently, if an order in Shopify has any information stored in the "Additional Details" column of an order, that information is imported into Shipstation in the "customer Order Notes" Field. This is the same field that the Shopify "Notes" section imports to. Shopify businesses commonly use the Shopify "Notes" section for gift messages. So, when all this info is imported, you get a gift message + any data from the "Additional Details" column funneling all together in the same Shipstation field. This causes a huge headache for fulfillment and shipping teams that have to then manually separate a gift message from any other data that the import is capturing. Check out my images to see a live example.
5 Comments
rob16
First-timer (legacy)
Hello, ShipStation will likely not be able to map this due to how Shopify sends the data as a string with attributes. However, I have written an automated tool that can process these automatically! If interested, let me know. rob@robwiddick.com
info8
First-timer (legacy)
I having the same problem. It is such a hassle. Plus, additional information is an internal documentation that in no way should appear within packing slips or invoices, especially merged with customer notes. What is the point of selecting what fields to appear on your packing slip when the system does whatever it wants.
Status changed to: No status
SuperMgr-Sarah
Employee
Employee
 
KC1
First-timer

We are having the same issue. Has anyone came up with a fix for this??

fritsh
New Contributor

We had the Exact same issue with your Shopify (and shopify 3rd party apps) integration and though clearly an Shopify issue they really not take too serious or accountability for we had no other way then fixing on the Shipstation side. 

meetstring.com  did SOLVE for us and the unwanted text is parsed out and works great as we incorporate STRING for our Rate optimization (and some do for packaging selection as well) this is solved with a band aid as work around but very effective and functional. If a remaining issue I suggest to reach out to tyler@meetstring.com