Intentionally left in English. Please leave a comment if this is needed in Dutch. 

Semi-automate creation of transport orders, called packages in Streamliner

The issue for the Streamliner user.

A supplier with a high N° of orders, must select one by one the orders to place them in the basket before the package/transport order can be created. This task consumes time and is not error-proof. But it is a necessary step to enable the carrier with all data to book slots. To give transparency in the inbound process, the receiver needs a view on which orders, complete or partially, will be delivered when a delivery slot is booked. 

Streamliner can offer an improved workflow if the supplier is able to provide an export from his TMS or WMS system with the minimum set of data to create these packages. And if the export contains the original numbers of the purchase orders that you received from your customer. 

Dataflow:

1. Export file with the created transport orders

Supplier books in his TMS or WMS the transport orders and is able to export this to a file. These transport orders have at least the following data:

Required

• A reference: a reference between supplier and carrier
• A N° of single SKU pallets (can be ‘0’) 
• A N° of mixed SKU pallets (can be ‘0’) 
• An expected delivery date when carriers need to book the slot
• A list of orders that will be delivered. 

Non-required

• A code to supplier (just a verification) 
• A reference to the pickup location if more than 1 pickup location is configured

See chapter 3 for file structure

Prerequisites

• The supplier defined a default carrier
• The supplier defined a default pickup location if no reference to a pickup location is available

2. Import the file. 

Manual action from supplier. 

Login in Streamliner and go to the packages screen

Select the function ‘Import packages’

Select JSON file

Based upon the contents of the file, the different packages/transport orders are created in Streamliner and the carrier is informed. Your customer can follow up order status. (Order received next state: transport order prepared; carrier informed) 

Suppliers can still adapt carrier, pickup location, volumes, dates, even order list if required. 

Advantage

We eliminate the need to select the orders manually if the supplier can generate this file. 

3. File structure. 

The file has a JSON structure, can contain as much transport orders as you wish and each transport order can have an unlimited list of linked orders

{

    "import_packages": [

        {

            "owner_code": "Supplier_code",

            "package_reference": "7009179311",

            "pickup_address_code": "ABC",

            "delivery_date": "202301230000",

            "quantity1": "33",

            "quantity2": "0",

            "purchase_orders": [

                "R3014577","R3045236","R562356","R123456" 

            ],

            “Line_info”: “C”

       },

        {

            "owner_code": "Supplier_code",

            "package_reference": "1514982640",

            "pickup_address_code": "SDF",

            "delivery_date": "202301170000",

            "quantity1": "10",

            "quantity2": "0",

            "purchase_orders": [

                "R3015307"

            ],

   “Line_info”: “C”

        }

    ]

}

4. Next steps. 

You can contact support for any further assistance, free of charge for this automation. We know that this procedure improves the customer experience and eliminates repetitive work.  We can check for you the structure of the file if needed.  

We hope to hear from you soon. 

support@streamliner.cloud