Onetrail TPN™ Seller PDE: Product Data Delivery
Introduction
Onetrail TPN™ connected Sellers can upload their Product Data using three CSV formatted files: Generic Product, Generic Stock and Customer Price file. The combination of these three files enables Onetrail to generate and deliver the required output files to your customers (hereinafter called Customer or Customers) containing those products that you want to make available to them (where you have indicated a Customer specific price) as well as to correctly send changes and related product stock availability.
Remark: Stock files may be processed on an hourly basis if possible.
Process
The Onetrail Product Data Delivery requires three file types:
Product file
This file should contain ALL products that you want to make available through Onetrail TPN™ to your customers. The file is to be delivered on a daily basis as early as possible but no later than 4:00am.
Onetrail usage: Based on this file Onetrail updates the Onetrail TPN™ Product Data Management (PDM) database that contains all products from all suppliers with a unique reference to the vendor part number.
Onetrail matches your new products with the unique vendor part number within Onetrail TPN™ PDM, applies changes or deletions and adds a unique classification based on the UNSPSC standard. Apart from this, brands are mapped to a uniform brand code. The stock information in this file is used to perform a daily update of the stock position within Onetrail TPN™ PDM. This will consequently be updated with the (hourly) Generic Stock file.
Remarks:
- All price information in this file is ignored
- Empty fields are not allowed
- A full file is expected every time
Stock file
This file should contain ALL products with accurate stock availability that you want to make available through Onetrail TPN™ to your Customers. This file is to be delivered on an hourly basis.
Onetrail usage: Onetrail processes this file to update stock availability for your products in Onetrail TPN™ PDM. Onetrail generates an output of stock information to the (ERP) system of the Customer. This information is used as an indication when selling/buying products.
Remarks:
- Apart from the (hourly) stock updates Onetrail allows Customers to perform a Real time Price and Availability check from within their (ERP) system which results in a real-time request to your environment (if available). It is common practice for Onetrail TPN™ connected Customers to perform such checks before sending a purchase order so errors can be avoided.
Customer Price file
Onetrail expects a separate Customer Price file per Customer you wish to trade with through Onetrail TPN™. This file is to be delivered on a daily basis as early as possible but no later than 4:00am. This file should contain the products with their net prices to be made available to a specific Customer.
Onetrail usage: Onetrail processes this file, combines it with the product data available within PDM data, and delivers the output to the Customer’s (ERP) system.
Customer files may contain only the changes or be send as a full file with prices only for those products available to the specific Customer. Products without a price (empty price field) will not be delivered to the Customer, a “0” (zero) price is regarded an actual amount.
Remarks:
- For support and demo purposes Onetrail requires one additional Customers file for Onetrail itself (Onetrail account). This file normally contains all products with default prices (i.e. highest price).
Delivery Schedule
Please set up a schedule and inform Onetrail when your files will be delivered to the Onetrail FTP server. Below you will find examples of the schedules Onetrail requires. Keep in mind that Onetrail needs to process and subsequently deliver the files to the Customers system before start of business (8:00am). Therefore Onetrail requires the files no later than 4:00am. The Generic Stock file may obviously be delivered every hour during business hours.
Example delivery schedules
Generic Product File:
Always a full file with all products.
Day | Frequency / Time | Remarks |
---|---|---|
SUN: | Once a day / 2.00am | |
MON: | Once a day / 2.00am | |
TUE: | Once a day / 2.00am | |
WED: | Once a day / 2.00am | |
THU: | Once a day / 2.00am | |
FRI: | Once a day / 2.00am | |
SAT: | No file (* Once a day / 2.00am) | * Only if Saturday is a business day |
Generic Stock File:
Always a full file with all products.
Day | Frequency / Time | Remarks |
---|---|---|
SUN: | No file | |
MON: | Hourly between 08.30am – 6.00pm | |
TUE: | Hourly between 08.30am – 6.00pm | |
WED: | Hourly between 08.30am – 6.00pm | |
THU: | Hourly between 08.30am – 6.00pm | |
FRI: | Hourly between 08.30am – 6.00pm | |
SAT: | Hourly between 08.30am – 6.00pm |
Customer Price File:
Day | Frequency / Time | Remarks | Full/mutation |
---|---|---|---|
SUN: | Once a day / 2.00am | Full | |
MON: | Once a day / 2.00am | Mutation | |
TUE: | Once a day / 2.00am | Mutation | |
WED: | Once a day / 2.00am | Mutation | |
THU: | Once a day / 2.00am | Mutation | |
FRI: | Once a day / 2.00am | Mutation | |
SAT: | No file (* Once a day / 2.00am) | Mutation | * Only if Saturday is a business day |
Syntax
The table below shows an overview of the field definitions per file type (Product, Stock, (Customer Price) and their status (Mandatory (M), Optional (O) or Not Applicable (N/A)).
Fieldname | Description | Product | Stock | Price | Example |
---|---|---|---|---|---|
Stock Keeping Unit (SKU) | Supplier (your) Product Number | M | M | M | 78GK3LL12 |
Price | Net Purchase Price, excl. VAT | N/A | N/A | M | 650,00 |
Currency | ISO Code EUR / USD / GBP etc. | N/A | N/A | M* | EUR |
Special Price | Net Purchase Price, excl. VAT (i.e. Promotional price) | N/A | N/A | O | 625,38 |
Manufacturer Product Identifier | Vendor Product Number | M | N/A | N/A | C4151A |
Brand | Brand name or Code | M | N/A | N/A | HP or 654 |
Stock | Stock Position | M | M | N/A | 54 |
Product EAN (GTIN) | EAN Product Number (GTIN) | O | N/A | N/A | 8714123456789 |
Short Description | Short Description of the Product | M | N/A | N/A | Wonderful product |
Long Description | Long Description of the Product | M | N/A | N/A | This is the most wonderful product there is. |
Classification (i.e.UNSPSC) | Product group (Text or Code) | M | N/A | N/A | i.e. “Server” or “45AW5” |
VAT | Tax Level of the Product i.e. High, Low, Null | M* | N/A | N/A | High |
Status | New, Modify, Delete, Equal | O* | N/A | O* | N |
Key Assortment | Code Representing Deliverability of the Products within the Key Assortment i.e. A= Within 24hrs., B= 48hrs etc. | O | N/A | N/A | B |
Signal Code | Code Representing delivery time of Stock Position i.e. 48h | O | N/A | N/A | 48h |
On Order | Number of Units on Order at Vendor | O | N/A | N/A | 500 |
Data Available On Order Stock | Excepted Availability Date Ordered Units at Vendor | O | N/A | N/A | 20071231 |
Recommend Price | i.e. Gross Price | O | N/A | N/A | 874,00 |
URL | URL to Product and/or Picture on Website | O | N/A | N/A | http://www.seller.com/picture.jpg |
Serial Keeping | Product Serial Numbers will be Scanned Yes/No | O | N/A | N/A | Y |
Intrastat number | Intrastat Reference Number | O | N/A | N/A | 12244 |
UOM | Unit Of Measurement Code i.e. Piece, Blister | O | N/A | N/A | Blister |
UOM Quantity | Unit Of Measurement Quantity, Number of Units in UOM | O | N/A | N/A | 12 |
Minimum Order Quantity | i.e. 1, 5, 12 | O | N/A | N/A | 1 |
- Price – "Currency" field: The Currency field is not necessarily mandatory if Currency is well communicated by the Seller. For example, if the Currency is Euro only, Onetrail can set Euro as a default value.
- Product and Price – "Status" field: In most cases Onetrail determines the status. The status needs to be delivered when Sellers also deliver mutation files to Onetrail TPN™.
- Product File – "VAT" field: The VAT field is necessarily mandatory if VAT is i.e. always HIGH, then Onetrail can set VAT as a default value.
Format
The format for the three files is Comma Separated Values. Onetrail's definition of CSV: Each record is put on 1 line with a CR/LF or LF as line separator. Each field is separated by a separator. This separator cannot be used inside the data, therefor Onetrail suggests to use "|" as a separator.
Communication
All files can be stored on the Onetrail FTP server. To enable connectivity to the Onetrail FTP server, Onetrail requires your external “STATIC” IP address. Onetrail will provide you the necessary login settings.
FTP server
Please refer to Communication guide: FTP Server for more details.
File naming convention
File Type | File Name | Example |
---|---|---|
Product | .8714253023809.product.csv | test_seller.8714253023809.product.csv |
Stock | .8714253023809.stock.csv | test_seller.8714253023809.stock.csv |
Price | ..price.csv | test_seller.8714231442455.price.csv |
- Replace “” with either
:*your company name (abbreviated)
or
:*the GLN address code of your company (If you don’t already have GLN address codes, Onetrail will assign GLN address codes to your Company).
- Replace “<Buyer GLN Code>” with the GLN code of that specific Customer. This code is supplied to you by Onetrail.
- The Customer Price file name for Onetrail support and demo purposes will be for example: test_seller.8714231442455.price.csv where “8714231442455” is the Onetrail specific Customer GLN address code.