Inventory Linking and Alternate SKUs
With marketplace integrations now in place (and active), we can match the inventory items from those integrations to the inventory we stock in the warehouse/have within Helm. A large amount of these will be 1:1 as the SKU on the marketplace will represent the SKU in Helm/Warehouse.
Many clients have alternative SKUs however, SKUs that are unique, but represent the same parent inventory item.
For these we need to match the alternate SKUs to the relevant SKUs within Helm.
One off SKUs (In Helm)
- Settings->Link Inventory
- The channel will tell you if there are unlinked SKUs, but you still may want to manual change linking even if all are 'matched'
- Select the Client/Integration and View Linking
- Scroll to a dropdown that's missing content (the DC SKU)
- Match the Channel SKU (SKU within the integration), to whichever item it is within Helm from the dropdown
Bulk SKUs (Requires Neuro)
To do this we will be using Neuro. It should be a one-off when migrating/on-boarding a new client.
- In Neuro select Channels
- Find the client integration and click into Actions
- Click Products
- Press Actions->Export All To CSV
This will generate the inventory list, and email the CSV to you - Update the content (as below)
- Upload the new CSV in Actions->Import
Within the CSV generated the only things we will be looking at and changing are the:
sku and more importantly the matched_sku
sku is the SKU from the Integration, Shopify, etc
matched_sku is the SKU within helm
While updating the file we will only need to edit the matched_sku for those lines that it is missing from.
The CSV needs to have the same lines as when it was exported, so do not delete or add any lines.
This is done in a specific way
<client_id>~<helm_sku>
The client_id is the non-numeric id we have set for the Fulfilment Client within helm
Follow this with a tilde ~ (with no space) and follow the tilde with the SKU of the item within Helm
e.g. onlinefulfil~ofctest
Hopefully we can match these with the export from mintsoft.
So the alt sku is what's from integration and the original sku should hopefully be on the export too, and we can just append <client_id>~ to it
Script
Will be working on a script that will take neuroExport.csv andĀ AltCodesReports.csvĀ loop through altCodes, store them, loop through neuro export, find any missing data and fill from altCodes if possible. If not possible will save a file called 'empty/missing' or the like with the SKUs that couldn't be matched.
Manual Linking in Helm