Tracking/Return ID Split RI
As in Arcade2 instance, for RiverIsland (https://riverisland.wearepentagon.com/alpha/en/home) there is a custom Export → Import that splits the tracking number and return ID. The reason behind that is that both values come in the same field with the shipping imports from ProSKU. What happens is we read the first shipping import from ProSKU and do not raise the update shipping pending flag (at least for some marketplaces). After that an export (you can find the SQL querry below) splits the tracking number and return ID in different fields after which they get imported in Hemi that way.
Export Layout ID: 21 (Shipping Export (TrackingNumber split))
Export Feed ID: 15 (Shipping Export (TrackingNumber split))
Import ID: 154 (Shipping Import (TrackingNumber split))
Important: For Next orders, we do not receive any tracking information (tracking number, carrier) from the ProSKU shipping update, so we need to have a different clause regarding those orders. The SQL logic is simillar, but a bit different compared to the Arcade’s one.