Proposal for WMS Customization Phase-1

Proposal summary 

This proposal covers that WMS implementation and customization for XSEED–Phase 1 and its proposed solution. 

Requirement 1 

Bulk Fulfilment 

On Waves being marked shipped/ Item fulfillments being marked shipped Transporter Integrations- API integration between Netsuite and Shiprocket (available) or any other transporter (to be integrated- not in WMS scope) to manifest these orders and get the pieces of information like Transporter Name, Waybill number, Tracking link etc. as per integration. 

Our Solution 

  • Single order Picking: As per NetSuite WMS standard functionality, Single order Picking works based on the SO document number. It cannot be filter by wave. So we will get the SO details only in the WMS. During the creation of IF from individual SO we can set the IF as shipped status by using custom script functionality. As per this solution ,there will not need any user instruction to set IF status to shipped stage, because custom script automatically set the IF as shipped. 
  • Multiple order Picking: As per NetSuite WMS standard functionality, multiple order Picking works based on the wave number. So multiple IF’s will be created together for all the orders under the wave. During the creation of IF from wave we can set the IF as shipped status by using custom script functionality. As per this solution ,there will not need any user instruction to set IF status as shipped stage for the wave, because custom script automatically set the IF as shipped. 

Requirement 2

Pre-Dispatch Verification/Investigation/ QC (new process)-  

Reason- As pasting shipping label happens on pallets a process to revalidate if correct item is being sent to correct way bill  

Process- Each time a way bill is scanned, the inventory & assembly items for that way bill to be scanned then (in any order). 

Once all boxes are correctly scanned the system populates, Two field Pre dispatch Verification date & Pre Dispatch verification done by to be created in Item Fulfillment. 

If any extra boxes is scanned, system shows scanning is already completed 

If any boxes are not scanned, the task should show the pending boxes 

Our Solution 

  • We will create an icon for pre-dispatch verification and when we click on the icon, we will enter to suitelet page.  
  • In the suitelet page first scan the Waybill barcode and will show list of items from the carton details subtab in the NetSuite  IF record. 
  • The sublist contain two columns: item name and custom column named:” Processing” which first contain the value “Not processed” in each line.  
  • Scan the barcode of each item. When we scan the first item, we compare the item using the script and if the item matches with item in the sublist, we changed the Processing column from “Not processed” value to “Processed”. 
  • Likewise, we scan each item, if all the item has status “processed”. We will set the button “Submit.”  
  • When the “Submit” button click, we will give the response “OK Ready to ship”. We will create two custom field in the IF record. 1. Pre dispatch Verification date 2. Pre Dispatch verification done by. 
  • If a wrong item is scanned, we will show an alert “Mismatch item” 
  • If the item is already scanned, we will show an alert “Scanning completed” 

Assumption 

  1. We will create two custom field in the IF record. 1. Pre dispatch Verification date 2. Pre Dispatch verification done by. 
  1. We assume that  we can  scan approximately 500 items at a time using the suitelet page. We will get the correct count of scan during the development stage. 

Risk 

  • There will be scanning limitation for number of items to be scanned using the suitelet page. 

Time & budget 

47 Hours 

Leave a comment

Your email address will not be published. Required fields are marked *