There are two layouts supported for managing an offline inventory file. Offline inventory files are not to be confused with a product upload file found on the wwsitemupload.wws page. Offline inventory files may contain hundreds of thousands of products or more. An offline inventory file is used by the Sophio system to behave like a 'connected' site. In fact, when a store uses an offline inventory file the supplier settings in your storesetup will show as CONNECTED. A disconected store will not use a remote connection or an offline inventory file. Instead, a disconnected store will use the cost, price, and 'stock' fields in the systems wws_items table.
The first file format below is designed for distributors who have multiple locations. The second is for a single master location. Both files are to be created in standard CSV format. For more information on csv files please visit wikipedia. If you are creating your files with a progra such as Microsoft Excel, you can 'save as' file type CSV.
Create a CSV file with the following fields below. When finished upload the file to a folder named data/dailydownload in your site's HTML folder. Sophio Support will need to update your store configuration and system scheduler to process the file. So if your site is called autoparts.com. You ftp the file to the folder /inetpub/autoparts/data/dailydownload/offlineinv.csv . The /inetpub will only be shown in your ftp account if you have root access and host on your own server. If you are hosting on Sophio's network you will not see a data folder when you connect. You will need to create the 'data' folder and the folder below it called 'dailydownload'. Each time our system processes the file, we will delete the source file.
Format 1 - Distributors uploading inventory information for multiple locations. A max of 14 locations can be uploaded in a single file.
Linecode - The distributors id for a given brand. This can be an alpha numeric value up to three characters long
Part Number - Your part number should match the formatting of part numbers in the application catalog.
Description - an optional short description
Price - If you are the seller of parts to consumers, this is your selling price to the end user. If you are fulfilling orders for your customers this is the merchants cost
Core Price - This is the core cost and sell price
Min Sales Qty - Normally a value of 1, but could be a pack qty
Loc 1 qty (on hand) - self explanatory
Loc 2 qty
Loc 3 qty
Loc 4 qty
Loc 5 qty
Loc 6 qty
Loc 7 qty
Loc 8 qty
Loc 9 qty
Loc 10 qty
Loc 11 qty
Loc 12 qty
Loc 13 qty
Loc 14 qty
Format 2 - Distributors uploading inventory information for ma single master location.
Brand Name - optional brand name
Linecode - The distributors id for a given brand. This can be an alpha numeric value up to three characters long
Part Number - Your part number should match the formatting of part numbers in the application catalog.
Sku - stock keeping unit, aka suppiler part number. We will use this field for matching the values in the catalog
vendor_cost - If you are the seller of parts to consumers, this is your selling price to the end user. If you are fulfilling orders for your customers this is the merchants cost
pkg_qty - Normally a value of 1, but could be a pack qty
core_price - This is the core cost and sell price
upc - uniform product code
part_description - short descrpition
stock1 - stock on hand
weight - weight of product
list_price - msrp
