Multi Pack Boxes Support for a B2C Shipment

Internal backend configurations to allow multiple pack boxes and to allow box labels at the channel level are added for B2C orders. The same values of properties will flow against orders to OMS and WMS. These values would be set by the Increff team while configuring a channel for a client.

These configurations can be enabled/ disabled for a client and channel pair on raising a request to the Omni Success team.

Below B2C processes/flows will have changes on enabling the B2C Multi Pack Box feature.

1. Packing Flow

2. Capturing B2C Dimensions

3. Manifest Flow

4. Handover Flow

5. B2B Order Creation

Packing Flow

Packing Screen Configuration to allow Multiple Packboxes

Increff WMS now provides flexible Packing Options for B2C shipments.

Users can pack orders in multiple boxes or a single packet, depending on the order requirements. Users can enable/ disable the toggle Allow Multiple Packboxes configuration in the Piece Packing screen’s Configuration. The toggle is provided for users to generate multiple Pack boxes for an order, allowing for easy management of multi-pack box orders
This allows for better handling of orders with large or bulky items, as well as orders containing items from multiple categories.

Packing process when Multiple Packboxes configuration

When Allow Multiple Packboxes configuration is tuned off, users can scan the Item codes as usual.

• add 2 sections: single shipment partial and other 1 for normal processing

Packing process when Allow Multiple Packboxes configuration is turned On

When Allow Multiple Packboxes configuration is tuned on, user will have to scan the item code and place the item code into a box while scanning the Box Id at the same time.

User can print a new box Id after scanning Item Code if required.

• pack order in a Single Box in UI- If the flag is true from backend and Ui flag is turned on, then user

In below case pack order in single box won’t come if any 1 box is already closed

Below case would be in rare scenarios

WMS UI - Capture B2C Packet Dimensions screen

When more than 1 pack box is present for an AWB, UI to show a warning and ask user to capture dimensions via Box ID

OMS UI: Add isMultiPackBoxAllowed & areBoxLabelsAllowed flags while creating internal order

Manifest Flow

Steps to create and close manifest for Multiple Pack Box shipments

1. A manifest is created in Manifest screen as usual.

2. For shipments without multiple boxes, AWB number can be scanned as usual and there is no change in the user interface.

3. For shipments with multiple boxes, when any of the AWB for shipment(either parent AWB or any Child AWB) is scanned, the pop-up as shown below will be displayed. We display the count of scanned Box AWBs for the shipment AWB.
   Please note, if the user refreshes screen while scanning Box Ids against an AWB, user will have to scan all child AWBs once again for the particular AWB to add shipment to manifest.
   

   

4. User will have to scan all the box Ids that belong to that specific shipment.
   

   

5. Post that, please click on Add Shipment button to continue scanning other AWBs

Please find the sample manifest document where multiple boxes for the same shipment are present.

• Line items in Manifest Doc are sorted in descending order of box count.

• The document also has a total box count at the end.

• Rahul Singh To attach the document.

Handover

Steps to Handover by AWBs for Multiple Pack Box shipments

1. For shipments without multiple boxes, AWB number can be scanned as usual and there is no change in the user interface.

2. For shipments with multiple boxes, when any of the AWB for shipment(either parent AWB or any Child AWB) is scanned, the pop-up as shown below will be displayed. We display the count of scanned Box AWBs for the shipment AWB.
   Please note, if the user refreshes screen while scanning Box Ids against an AWB, user will have to scan all child AWBs once again for the particular AWB to add shipment to manifest.
   

   

3. User will have to scan all the box Ids that belong to that specific shipment.

4. Post that, please click on Confirm button to continue scanning other AWBs for handover.

Handover By Manifest

No changes in this flow.

Generate Handover Document

Please find the sample handover document where multiple boxes for the same shipment are present.

• OMS to include the count of boxes for every AWB in the handover document. Line items in Handover Doc to be sorted in descending order of box count.

• Document should also have total box count in the end.

• Rahul Singh Sample handover and manifest doc to be added

Error Handling

The system will display errors in the user interface, guiding users to remove items from the Pack Box if needed. This helps prevent issues such as extra boxes being added after shipment closure or unclosed boxes with items.

Error scenario where the Pack Box gets closed but adding box to shipment is not successfull.

After the boxes are added in the shipment some qty gets cancelled in OMS

• Error will be displayed to remove items from the Pack Box. The user would have physically added the items to the box, hence those items which are cancelled should be removed from the box.

• User will navigate to Remove Items from Outward Box screen in WMS

• The discrepancy will be displayed here. Currently the user can refer report to know the box where the items of the discrepancy SKUs are present. The cancelled items can be removed from the box by scanning those items.

• User can sync the order to ensure that all the discrepancy is corrected.

After the boxes are added to the shipment all the items of the box are removed

• While closing the shipment if there are any empty CLOSE box associated with it (resulted from removing items from box), then error will be displayed.

• The empty box IDs will be displayed in the error message and user is prompted to physically remove them from shipment.

• The user has to remove the box from the shipment by clicking Remove button.

Dimension Capturing misses

In case where dimension capturing is mandatory, but for all the closed boxes dimensions are not captured. Insuch case user has to capture the dimensions for all the close boxes (with some items) and then proceed with the close shipment.

The Pack Box not closed

User has added items to the box, but has not closed the box. This box will not get added to shipment, hence error will be thrown since the order is BLOCK_COMPLETE. We display the Box ID - Status - Count of Items in the packing screen. Here the user scan and close the box first.

The Multi Pack Boxes Support for B2C Shipment feature from an end-user perspective includes the following key points in more detail:

1. Users can create new boxes by pressing the "Create New Box" button and scan items to these pack boxes for tracking.

2. Efficient Tracking and Management: The system handles both pack box and shipment AWBs, ensuring proper tracking and management of multi-pack box orders. This includes support for child AWBs used by some couriers to track multi-piece shipments, as well as the main AWB for the entire shipment.

3. Seamless Integration: The feature integrates with RMS and OMS systems, ensuring smooth handling of multi-pack box orders and AWB management. This includes sending a flag "is_pack_box_label_reqd" from CIMS to proxy, which needs to be sent to RMS, and populating this field during order creation in WMS.

4. Invoicing and Shipping Labels: For multi-pack box orders, there will be one invoice for the entire shipment. Shipping labels will have multiple pages for each box, with markings like "1/2" and "2/2" to indicate the box number within the shipment.

5. Manifest and Handover Management: The multi-piece shipments need to be treated as a unit, so if some packets are not scanned and added to the manifest, manifest close should not be allowed. This ensures that all child boxes are accounted for and scanned during the handover process.

Please note that this is a more detailed explanation of the feature release note from an end-user perspective, and more details can be found in the provided documents.

Today system will be relying on operator to decide whether multi-box or not.

There will be following types of parent & child AWB combinations:

• Child AWB to be a unique number just like parent AWB.

  • Derived: Child AWB will be derived from the parent AWB. If parent AWB is 1234 then child AWBs will be 1234-1 and 1234-2 for two piece shipment.

  • Coming from Logistics aggregator : Child AWB on a box level will be given by Logistics agrator.

• Child AWB is same as parent AWB.

We will need to have Increff pack box Id pasted on box

No changes will be there for single box packing flow.

All boxes of a shipment can be manifested at once only.

like if 3 boxes are there then all the should be together.