User Tools

Site Tools


Menu

Company Website

Video Tutorials

Documentation for Streamline 4.x

User Guide

1. General Information

2. Starting Up

3. Connecting data

4. Demand and Sales Forecasting

5. Inventory Planning

6. Reference

stitch-connection-guide

3.5.8. How to Import Data from Stitch

Key Terms Correspondence

The key entities that Stitch handles are products, variants, warehouses, and channels. Streamline treats variants as items, product as item category, warehouses as locations, and channels as channels.

It also imports Stitch's product description field (via the item info field) that you can use, for example, to import your custom item categories. This field is shown in the Inventory report and can be also used for filter needs.

Integration Limitations

The integration between Streamline and Stitch is one-directional currently. It means that Streamline pulls all necessary data from Stitch, however, can't push recommended POs back due to limitations of the API.

Stitch Labs offers two versions of software, Classic Stitch and Stitch X (an improved version of Classic Stitch). While the API provides reading open purchase orders (POs) and transfer orders (TOs) for Classic Stitch, it doesn't expose them for Stitch X. Thus, there is a workaround to import them using a CSV file in this case.

The API does not currently expose the on-hand history. It means that Streamline is not able currently to:

  • calculate inventory turn-over,
  • compute the number of days in the period you had run out of inventory (Stockout days), and
  • automatically determine whether lost sales are caused by a stock-out or zero demand.

Partially Shipped Sales Orders

Another specificity relates to importing data of partially shipped sales orders. Streamline considers all the lines of a partially shipped order as if they have been already shipped completely and includes this order into the sales history. Streamline has to follow this logic because of a limitation of the API.

This situation is pretty rare and may happen when you have a partially shipped backorder. Consider an example. Let's an order has two lines:

1. Apples, qty = 100.
2. Pears, qty = 1000.

Until this order is shipped completely or partially, it is in the Pending sales orders in Streamline.

If Streamline considers that the demand can't be fulfilled with the current stock, in transition quantity, and pending sales orders, it shows purchase recommendations for ordering the necessary quantity of these fruits. If you create a purchase order in Stitch for these lines based on the recommended quantities and then synchronize that with Streamline everything will be okay.

However, if you make, for example, apples shipped in Stitch (we have a partially shipped order now) before creating the recommended purchase orders in Stitch and synchronize the project then, Streamline will show incorrect purchase recommendations for the unshipped pears.

Thus, make sure you have placed a PO based on Streamline's recommendations for the necessary lines of an open sales order before a part of it is shipped in Stitch.
The current on hand for all your variants are fully synchronized with Stitch after you update the project. Thus, Streamline always shows inventory on hand correctly for all your variants (including partially shipped variants).

As soon as API limitations will be removed, we improve the logic for partially shipped orders and make the integration bi-directional.

Imported Data

Data imported into Streamline is described in the Inventory Management Systems article.

Data Import Workflow

Streamline uses Stitch's legacy API to import the data. The API requires you to provide an access token in order to allow Streamline to connect to Stitch. To get the token, please, contact Stitch's support.

To create a new Streamline project based on Stitch data:

1. Go to the menu File > New > Stitch connection. Streamline shows the Stitch connection dialog (see figure below).

2. Type your access token into the Access token field.

3. Enter or choose the date you want to start the import from in the Starting date control.

4. Choose the data aggregation period in the Group by control. Streamline automatically aggregates your data in the given periods (days, weeks, or months). For example, if you want to see the forecasts, replenishment plans, and other reports in months, group the data by months.

If you use Stitch X, there is an additional step - setting a CSV file containing transactions of open purchase orders (POs) and open transfer orders (TOs) (described below).

5. Set a CSV file with open POs and TOs. (Necessary for Stitch X only.)

The format of the CSV file matches the format of Stitch X's purchase orders import file. The columns that should be given are:

  • Expected Arrival Date (mm/dd/yyyy)
  • Warehouse
  • SKU / Variant ID
  • Qty
  • Unit Cost (optional)

The file should contain open transactions. For OPs, these lines contain products that are being delivered now from your suppliers to your warehouses. For TOs, these are the lines that have been already dispatched from a source warehouse (the on hand has been decreased), however, have not been yet received to the destination warehouse (the on hand has not been changed).

To set the file, click the folder icon near the In transition CSV file, browse to the file, and click the Open button.

6. Click OK to start the import. In this case, Streamline imports all the warehouses and channels that you have in Stitch. The demand of all your channels is combined in one virtual channel. The inventory is imported by each warehouse separately.

Due to API limitations historic sales orders are exported into Streamline one at a time. Streamline doesn't import all orders when you update the project, just the new orders. But still, the first import might take up to 24 hours.

If you combine your data by warehouse and find a channel with an empty name in the Tree view after the import has been completed, this channel will contain variants that have some inventory in stock, however, have not been yet sold via any of imported channels (see figure below).

Advanced Import

The Advanced button of the Stitch connection dialog shows some additional settings helping you to select a particular set of warehouses and channels you want to import (see figure below). These settings also allow you to combine channels, warehouses, or both of them.

To make use of the settings:

1. Scan Stitch for available warehouses and channels. To do this, click either Quick scan button or Deep scan button.

Quick scan finds all channels and those warehouses that are attached to them. Thus, if you need to import only the warehouses that are attached to your channels, use this type of scan. As the scan is completed, Streamline shows found warehouses and channels in the lists.

Deep scan scans for all available Stitch's warehouses and channels.

2. Select the necessary warehouses and channels in the lists.

3. Choose your combine option.

  • Warehouses – combines all the selected warehouses into one virtual warehouse. If this option is active, you can plan your demand by channel.
  • Channels – combines all the selected channels into one virtual channel. This is the default option.
  • Both – combines all the selected channels and warehouses into two separate virtual entities.

4. Click OK to start the data import.

Updating a Project

The data update workflows for Classic Stitch and Stitch X are different.

Classic Stitch

If you use Classic Stitch, updating the project is quite simple – just click the Update data button found on the program toolbar.

Stitch X

As mentioned above, the API doesn't currently expose information about open POs and TOs for Stitch X. It means that you should handle synchronization of this information manually. It should be done through a CSV file that is a part of configuration settings of the Stitch connection. Below we describe the steps you need to take to do the synchronization.

Assume, you have set a CSV file with current open PO/TO transactions when first import your data. To synchronize these data correctly as they change in the future, follow these steps:

  1. Receive/add open PO/TO lines in Stitch. If you receive, the on hand should change.
  2. Open your CSV file and update the transactions manually according to received/added lines in Stitch.
  3. Save the file.
  4. Open your project in Streamline and click the Update data button found on the program toolbar. This will read updated information from Stitch as well as from the CSV file.

Resetting Connection Configuration

You can reset your connection configuration at any time. To do this:

1. Open your Streamline project.
2. Go to the menu File > Change connection > Stitch connection. Streamline shows you current configuration (see figure below).

3. You can reset the CSV file with open POs and TOs. (Necessary for Stitch X only.)
4. Scan for new warehouses or channels (see figure below).

5. Select or deselect necessary warehouses/channels.
6. You can reset your combine option.
7. Click the Save button to save the connection changes.

Typically, the next step is to find out, either update the project or reimport it completely.


Next: TradeGecko

Download PDF

stitch-connection-guide.txt · Last modified: 2019/08/12 13:39 by admin