HemiKnowledge BaseHemiHemi Platform Integrations
Table of Contents
Related Articles
Knowledge Base
Hemi System Administration Integrations Hemi PRD Library Hemi Content Stream General Information Custom additions Core Integrations & Marketplace Documentation Hemi Advanced Functionalities Data Management MP Tokens generation Hemi Technology Trainings Hemi Platform Integrations Release Notes
FAQs

ProSKU / ProSKU User Guide

ProSKU User Guide

ProSKU is the warehouse management system (WMS) that connects us with our warehouse (Warehow) and is used as an orders management tool.

1.How do we integrate with ProSKU

We integrate both via API and FTP.

1.1 Stock management.

If the supplier is stock based, i.e the the stock in Warehow, we use API integration to get stock levels.

In order for this integration to work, we need to have seller created in ProSKU and the API key provided by ProSKU. Once we have the API key provided, we need to fill this information for the relevant seller/supplier in the Sellers (form 1150) in Hemi under ‘Reference code’. In the Location we need to fill in the ID of the location where we want the stock to be fed into.

NB! Don't forget to activate the cron in the ProSKU tab once you have set the integration.

1.2 Orders Management

The orders management is done via FTP integration. The specific thing here is that since ProSKU imports the files instantly (before they are completed), the files cannot be created directly on their sFPT. We have to export initially to our FTP (in most cases it’s arcade’s ftp) and then there is a script which transfers the created file from Arcade’s FTP to ProSKU’s ftp. The process is as follows : HEMI → Arcade FPT → ProSKu sFTP → ProSKU.

Arcade’s FTP credentials are as follows : Host: arcade.myhemisphere.com User : WAP_sftp Password : ask The path where we should create the export is : /Orders_to_ProSKU_StockBased/CLIENTNAME

Once we have created the automatic export to Arcade’s FTP we need to set the script which moves the files between the two FTPs. The first step is to set the FTP Credentials in table (130). We need to set the credentials for the two FTPs - ProSKU’s and Arcade’s (or the FTP we want the script to pick the orders from).

For FTP Paths we need to set a label :

ProSku Order Mover - this is the path where the script will exchange the order files.

1.2 Shipping Updates Management

Again this is set from the same FTP Credential table and record, we just need to add an additional label:

ProSku Shipping Grouper - There are two scenarios - 1) If it is ProSKU FTP Credential - this is the path where we will group the shipping files from 2) If it is Arcade’s ProSKU FTP Credential - this is the path where the grouped filled will be dropped and then picked by Hemi.

We also need to create standard automatic shipping import in Hemi which will pick the grouped file from the path we have set it.

2.Setting up the ProSKU automation

Now that we have set the exports/imports and FTP Credentials, we need to set up the whole automation of moving files between FTPs. This is done in a table called ProSKU FTPs (15400).

We need to create a new record and simply choose :

1)From which FTP to which FTP we want the automation

2)The type of automation (i.e Order File Mover or Shipping File Grouper)

If Order File Mover : We need to select Arcade’s FTP in the “From FTP”: label and ProSKU’s FTP in “To FTP” label.

If Shipping File Grouper : Again we need to set the “From FTP” and “To FTP” which will now be vice versa (as we want to pick files FROM ProSKU and drop them IN arcade’s FTP)

The difference here is the Seller code. It is used as a file name prefix e.g. “AZR1028_1657633569944.csv“ and if we have set any Seller Code we will need to group only files with that prefix. If the Seller Code is empty we group everything. The File Name field is how we want the grouped file to be named once moved on Arcade’s FTP so the Shipping Import can consume it.

What is the flow for adding new sellers?

  • First of all, the seller should be created in ProSKU. This is done by ProSKU staff, we cannot create the seller.
  • If the supplier is stockbased, API key should be requested from ProSKU and the information should be populated in the seller’s details along with location ID (the seller’s location in Hemisphere).
  • Then an order export should be created - you can use the template attached to this document. This is a standard order’s export which will be used for most clients. Please communicate this with the implementation manager if any differences will be needed in the export.
  • All feeds should be tested. After each run, check ProSKU for products, orders and manifest. You can ask Hristiyan for logins or help with the checks.
  • The last thing is for a shipping file to be processed. Really important thing is to make sure our script is transferring files to and from ProSKU’s sFTP.

warehouse orders.xlsx

Changes For new projects, all sellers, starting with Champion, Muchachomalo, Diligent, and each subsequent one, will go through InModa's FTP folder and its order exports. ProSKU will be able to differentiate between each Owner in the order export, thus separate exports for each owner were not necessary.

By ProSKU's request, each order export that goes through ProSKU should contain a new column named Depot and be populated with D1,D2,D3 etc. In the future more depots will be introduced.

Is this article helpful?
0 0 0