Warehouse Management Feeds
Overview
Warehouse management feeds are part of the Radial warehouse implementation. Clients who have inventory managed in Radial warehouses must implement these feeds.
Warehouse management feeds exchange data between a client's business systems and the Radial warehouse management system. The client notifies Radial of expected receipts at the warehouse, and Radial sends warehouse inventory levels and inventory transactions to the client.
A client's customized implementation might not completely match the following integration details.
The following data diagram shows the warehouse management feeds:
- Receiving Detail (ASNPO) lists goods to be received at the Radial warehouse.
- Inventory Status is a snapshot of Radial inventory levels of the partner's inventory.
- Inventory Transactions lists transactions of the partner's inventory. Transactions include receipts, adjustments, return-to-vendor (RTV), and physical counts. This feed does not include sales or returns, because these transactions are included in the POS (Point-of-Sale) feed.
Message Transport
For a standard implementation of the warehouse management feeds, files are delivered through FTP. Radial can implement secure VPN access, if required. Radial can support other transports including web services, MQ, HTTPS, or SOAP. Details of the specific implementation are based on the contract with the client and the client's capabilities.
File Formats and Data Types
The warehouse management feeds use flat files. The Receiving Detail feed uses a pipe-delimited flat file format. The Inventory Status and Inventory Transactions feeds use a flat file with fixed-length fields. In fixed-length field formats, all fields are accounted for. A blank value must still utilize all of its field's positions.
The feed files use two field types:
- Numeric fields represent numbers.
- Character fields represent everything else: characters, numbers, alphanumeric, and any combination.
The listed field type might not match the field's database field type.
All date fields are in ISO format yyyy-mm-dd-hh.mm.ss unless otherwise specified.
The CCSID (Coded Character Set Identifier) used internally at Radial is 819. Notify Radial in advance of development if you plan to use any other CCSID, or if any data values could contain extended characters. Examples of extended characters include the following: àèìòùÀÈÌÒÙ.
The specific file format for each warehouse management feed is detailed in the following sections.
Receiving Detail Feed
The client sends the Receiving Detail feed to Radial. The feed includes the expected receipt detail needed to create receiving files and to perform merchandise receiving in the warehouse.
This feed supports two types of files, based on the value entered in the Receiving Type field (field 2).
- A value of A identifies the file as an Advance Shipping Notice (ASN).
- A value of P identifies the file as a Purchase Order (PO).
Exchange Frequency: As needed. Daily to weekly, one or more times each day.
Timing: TBD
File Name: eircdtyyyymmddhhmmss.rdl, where yyyymmdd is the date and hhmmss is the time when the file was created
File Format: Pipe (|) delimited
Receipt Acknowledgment: Required. File name is eircdtrecackyyyymmddhhmmss.rdl
Exception Reporting: When errors occur, a processing failure report email is sent to the Business Management Team and/or the client.
Data Format:
ID | Field | Description | Type | Length | Req. | I/U | Comments |
---|---|---|---|---|---|---|---|
1 |
Radial Store Number |
Store number that is assigned by Radial to represent the client's webstore |
Character |
5 |
Yes |
I |
Radial-assigned store number |
2 |
Receiving Type |
P = purchase order A = Advance Shipping Notice |
Character |
1 |
Yes |
I |
Values: A, P |
3 |
Client's Shipment Number |
Client's purchase order or ASN number |
Character |
15 |
Yes |
I |
Required for purchase orders (field 2 = P) |
4 |
Order Date |
Date of purchase order in YYMMDD format |
Numeric |
6,0 |
No |
I/U |
Date when the client placed the order with the vendor for products |
5 |
Shipment Receipt Date |
Date the shipment is expected to arrive at the Radial warehouse, in YYMMDD format |
Numeric |
6,0 |
Yes |
I |
|
6 |
Shipper's Name |
Name of shipper sending goods to the Radial warehouse |
Character |
30 |
Yes |
I |
If goods are shipped from the client: name of the client's warehouse If goods are shipped directly from vendor: vendor name Only the first 15 characters are used. |
7 |
Partner Item Number |
Client's item number for the product in the Radial Order Management Item Master |
Character |
15 |
Yes |
I |
|
8 |
Quantity Shipped |
Quantity, in units, shipped to the Radial warehouse |
Numeric |
6,0 |
Yes |
I/U |
|
9 |
Item Cost |
Item cost per unit |
Numeric |
8.2 |
No |
I |
Should not be greater than 99999.99 |
10 |
Shipping Comments |
Miscellaneous comments about the shipment or items within the shipment |
Character |
100 |
No |
I |
|
11 |
Trailer Number |
Trailer at the Radial warehouse |
Character |
25 |
No |
I |
|
12 |
Carton ID |
Carton identifier |
Numeric |
25,0 |
No |
I |
Only the first 20 characters are used in the POS feed. |
13 |
ASN Number |
Client ASN identifier, if the file is used as ASN |
Character |
25 |
No |
I |
|
14 |
Date/Time Stamp |
Date and time when the file was generated (format yyyy-mm-dd-hh.mm.ss) |
Character |
19 |
Yes |
|
|
15 |
Warehouse Number |
Radial warehouse that is expected to receive the products |
Numeric |
3,0 |
Yes |
I |
Configured field Type: D (default) Value assigned by Radial |
Trailer Record:
ID | Field Name | Field Description | Field Type | Field Length | Req | Comments |
---|---|---|---|---|---|---|
1 |
Record Identifier |
Record identifier |
Character |
10 |
Yes |
Value: "TRAILER" (all caps) |
2 |
# of total records |
Total number of records in the file including the Trailer |
Numeric |
7,0 |
Yes |
|
3 |
Batch ID# |
Batch number |
Numeric |
9,0 |
Yes |
Sequential number |
Inventory Status Feed
Radial sends the Inventory Status feed to the client. This feed provides an end-of-day inventory snapshot for client-owned items in the Radial warehouse. This file provides SKU-level inventory counts, including return quantity on hand, sellable quantity on hand, available quantity on hand, and non-sellable (usually damaged) quantity on hand.
Exchange Frequency: Daily
Timing: TBD
File Name: EOINSTSyyyymmddhhmmss.dat, where yyyymmdd is the date and hhmmss is the time when the file was created
File Format: Flat file, fixed field length
Receipt Acknowledgement: Required. File name is eoinstsrecackyyyymmddhhmmss.dat
Data Format:
ID | Field | Description | Type | Length | Req. | Comments |
---|---|---|---|---|---|---|
1 |
Radial Store Number |
Store number that is assigned by Radial to represent the client's webstore |
Character |
5 |
Yes |
Radial-assigned store number |
2 |
Partner Item Number |
Client's item number for the product in the Radial Order Management Item Master |
Character |
15 |
Yes |
|
3 |
Radial Item Number |
Radial item number for the products in the Radial Order Management Item Master |
Character |
9 |
Yes |
|
4 |
Return On-Hand |
Quantity in inventory for processing of customer returns |
Numeric |
9,2 |
Yes |
The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
5 |
Sellable Quantity On-Hand |
Quantity in inventory that has a sellable condition |
Numeric |
9,2 |
Yes |
The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
6 |
Quantity Available |
Sellable quantity on hand minus the quantity allocated to customer orders |
Numeric |
9,2 |
Yes |
The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
7 |
Non-Sellable Quantity On-Hand |
Quantity in inventory that is not in a sellable condition |
Numeric |
9,2 |
Yes |
Typically used for damaged inventory or inventory to be returned to the client or vendor The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
8 |
Total Quantity On-Hand |
Total inventory in the Radial warehouse (sum of fields 4+5+7) |
Numeric |
9,2 |
Yes |
The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
9 |
Date/Time Stamp |
Date and time when the file was generated (format yyyy-mm-dd-hh.mm.ss ) |
Character |
19 |
Yes
|
|
Trailer Record:
ID | Field Name | Field Description | Field Length | Req | Field Type | Comments |
---|---|---|---|---|---|---|
1 |
Record Identifier |
Record identifier |
10 |
Yes |
Character |
Value: "TRAILER" (all caps) |
2 |
# of total records |
Total number of records in the file including the Trailer |
7,0 |
Yes |
Numeric |
|
3 |
Batch ID# |
Batch number |
9,0 |
Yes |
Numeric |
Sequential number |
Inventory Transactions Feed
Radial sends the Inventory Transactions feed to the client. This feed lists the inventory activities for client-owned inventory within the Radial warehouse. Activities can include inventory receipts, adjustments, return to vendor (RTV) transactions, and physical inventory transactions.
Sales and return transactions are reported to the client in the Shipped Order (POS) feed and are not included in the Inventory Transactions feed.
Exchange Frequency: Daily
Timing: TBD
File Name: EOINTRNyyyymmddhhmmss.dat, where yyyymmdd is the date and hhmmss is the time when the file was created
File Format: Flat file, fixed field length
Receipt Acknowledgement: Required. File name is eointrnrecackyyyymmddhhmmss.dat
Data Format:
ID | Field | Description | Type | Length | Req. | Comments |
---|---|---|---|---|---|---|
1 |
Radial Store Number |
Store number that is assigned by Radial to represent the client's webstore |
Character |
5 |
Yes |
Radial-assigned store number |
2 |
Partner Item Number |
Client's item number for the product in the Radial Order Management Item Master |
Character |
15 |
Yes |
|
3 |
Radial Item Number |
Radial item number for the product in the Radial Order Management Item Master |
Character |
9 |
Yes |
|
4 |
Transaction Type |
Type of inventory transaction: 31 - inventory receipt 51 - return to vendor (RTV) 61 - inventory adjustment 71 - physical inventory |
Character |
3 |
Yes |
Configured field Type: A - Allowed Values Values: 31, 51, 61, 71 |
5 |
Transaction Date |
Date of the transaction (format YYMMDD) |
Numeric |
6,0 |
Yes |
|
6 |
Transaction Quantity |
Transaction quantity in units |
Numeric |
9,2 |
Yes |
The decimal point is implied but not actually included in this field. For example, a quantity of 10 is shown as 000001000. |
7 |
Transaction Reference 1 |
For inventory receipt (transaction type 31): purchase order or advance shipping notice number For RTV (transaction type 51): Radial Order Management RTV number For inventory adjustment (transaction type 61) and physical inventory (transaction type 71): reason code |
Character |
20 |
Yes |
For a PO, the value is less than 15 characters. This is 7 bytes before the decimal and 2 bytes after the decimal (for example, a quantity of 10 = 10.00). Whole quantities only In a standard implementation, client product is not returned in fractions. |
8 |
Transaction Reference 2 |
Additional customized information such as carton ID for receipts |
Character |
25 |
No |
|
9 |
Transaction Retail |
Extended value based on the current retail price in the Radial merchandise management system |
Numeric |
9.2 |
No
|
The decimal point is implied but not actually included in this field. For example, a price of $10.00 is shown as 000001000. |
10 |
Transaction Cost |
Extended value based on the current cost in the Radial merchandise management system |
Numeric |
9.2 |
No |
The decimal point is implied but not actually included in this field. For example, a cost of $10.00 is shown as 000001000. |
11 |
Date/Time Stamp |
Date and time when the file was generated (format yyyy-mm-dd-hh.mm.ss) |
Character |
19 |
Yes |
|
Trailer Record:
ID | Field Name | Field Description | Field Length | Req | Field Type | Comments |
---|---|---|---|---|---|---|
1 |
Record Identifier |
Record identifier |
10 |
Yes |
Character |
Value: "TRAILER" (all caps) |
2 |
# of total records |
Total number of records in the file including the Trailer |
7,0 |
Yes |
Numeric |
|
3 |
Batch ID# |
Batch number |
9,0 |
Yes |
Numeric |
Sequential number |