Iconic Marketplace - Delivery Address issues - line1 too long/too many characters
Is anyone experiencing Iconic Marketplace - Delivery Address issues - where line1 is too long/too many characters & is rejected by our 3PL integration (limited by labels, courier booking systems etc)
Iconic Marketplace delivery address displays across several lines, but Cin7 doesn't interpret new lines correctly and instead populates data for 2 lines all on line 1 causing errors in our integrations.
Since Iconic Marketplace sends a character to flag the start a new line “n/”, I'm requesting that Cin7 tweak the integration to interpret customer delivery addresses as Iconic Seller Center does.
Related to
Comments
5 comments
Hi Kate,
Hope you are well.
I had a very similar issue, some orders that flowed from Shopify into CIn7 did not have a “State” in the state field.
This is due to some countries not having States (IE New Zealand).
Due to the lack of state, these orders would fail to be transmitted to the 3PL.
So I created a tool using Excel and the CIn7 API.
It runs as an automated process on a NON-USER PC.
Process:
Gets latest orders via API into Excel
Excel Checks for missing state, if detected, it updates the state in CIN7 against the order (copies the suburb) via APi.
It then, again via API, changes the status to resubmit the order to the 3PL for processing and emails a log to the person in charge of the area.
A fix from CIN7 is preferable and best practice, however it may take a while to get it fixed.
Regards
Jamie
Thx so much for this info. I'm not too cluey with custom back end jobs. We use our API forRefundid and can't justify an additional $150 pre month for a 2nd API. (We already miss out on the Excel API reporting)
I've never noticed the State issue in Shopify - only too many characters.
The issue is with our 3PL - it's their 40 character limit, that they cannot change due to courier and systems.
However, the lovely Francis suggsted switching on the “n/” to our 3PL to see if the 3pL can work with this - not sure about Shopify -if it also sends a “/n”
It's super annoying as it means in our small team, I can't take a holiday from checking these address errors….
Hi Kate,
Each 3PL integration will have its nuances, the state issue won't happen to all integrations.
API connections can be used by multiple services and would only be limited to one service if it is heavily used.
So it is likely your single API connection could be used for reporting etc if you wanted.
Might warrant looking into.
Jamie..
Thx for the tip on multiple API uses.
I'll update this post if the “n/” fix works out, or plead for your assistance with the API solution!
👍
Please sign in to leave a comment.