Merging LPNs

This document outlines the process for merging LPNs using the Build LPN app on the Flexe mobile device. 

IN THIS TOPIC

• About Merging LPNs
  • Key Details
• Merge LPN Process
• Confirming LPN Contents
  • Mobile Device Through the Lookup App
  • Flexe UI Through The Locations Page
• Understanding the LPN Details Page
• Troubleshooting Common Errors

⚠️ Before you start

This feature is only available for reservations with shipment consolidation enabled. To learn more about this feature, please contact [e-mail].

About Merging LPNs

The Merge LPN tool allows warehouses to consolidate staged LPNs that are ready for loading. This process optimizes pallet capacity and provides customers with improved visibility of the inventory within each LPN.  

Key Details

• Only active LPNs with the same Destination ID and Load Group can be merged. This ensures that the pallets are going to the same store. Both fields can be found on the Shipment Details page. To learn more refer to Navigating the Shipments Page. 

• The merge process is complete, meaning all LPN contents (child LPNs) from the source LPN are moved to the destination LPN. 
• The system automatically updates the LPN contents (child LPNs) to reference the destination LPN as their new parent LPN.
• The source LPN is archived after all its contents are moved.
• Once merged, LPNs cannot be unmerged within the Build LPN app. Do not use the merge LPN feature unless you plan to move the entire contents of an LPN onto another. Contact [e-mail] to resolve any issues related to merging LPNs. 

Merge LPN Process

1. Navigate to Build LPN app on the mobile device. 

2. Go to Edit LPN.

3. Scan or type the Source LPN. 

4. Scan or Type the Destination LPN.

5. A window displays to verify the move of the source LPN contents to the destination LPN. Click Complete Move.

6. A message confirms the source LPN is now empty. Click OK. You have successfully merged the two LPNs.

Confirming LPN Contents

It may be helpful to confirm LPN contents if you are unsure whether the system successfully moved goods. You can confirm LPN contents in through:

1. Mobile Device: Through the Lookup Details App.
2. Flexe UI: Through the Locations Page. 

Mobile Device Through the Lookup App

1. Open the Lookup Details on the mobile device. 

2. Scan the Destination LPN. The screen will display the SKUs and total quantity now contained in the pallet. 

3. Scan the Source LPN. The system will display a message stating that the LPN is archived, confirming the Source LPN is empty.

Flexe UI Through The Locations Page

1. Navigate to the Locations page on the Flexe UI. 

2. Filter by the pallets’ outbound Location Name or Location Category outbound_staging and click the check mark. 

3. This will now display all of the child LPNs on the outbound staging location. 

4. Select the desired LPN to view its details. 

Understanding the LPN Details Page

The LPN Details page provides comprehensive information about an LPN, including:

• LPN Type 
  • Pallet: A standalone LPN or a parent LPN. 
  • Carton: A child LPN associated with the nested LPN process. 
  • Flexible: A child LPN associated with the merged LPN process. 
• LPN Status 
  • Stored: an active LPN within the Flexe system. 
  • Archived: an LPN that is no longer active in the Flexe system, typically due to being outbounded or merged as part of the merge LPN process. 

• Inventory History (Child LPNs): Located in the lower section of the LPN Details page for child LPNs, this section provides insights into the LPN’s movement history. Two key fields confirming movements within the Merge LPN process are:
  • Initial Parent LPN: The source LPN from which the contents were moved during the merge. 
  • Destination Parent LPN: The Destination LPN that received the contents during the merge. 

Troubleshooting Common Errors

Issue or Error	How to Troubleshoot
“Same as source LPN”	You have scanned the Source LPN twice. Ensure you scan the correct Destination LPN when prompted.
“Bad Request, There is a conflicting Destination ID or Load Group on one of the LPNs you are trying to merge”	The LPNs have different Destination IDs or Load Groups, meaning they are being shipped to different end destinations or not going to the same truck. Verify the Destination IDs and/or Load Groups on the Shipment Details page.
“Bad Request, LPN Not Found”	The scanned LPN does not exist in the system. Double check the LPN number and try again. If the issue persists, contact [e-mail].