The Multi Pack Boxes Support for B2C Shipment feature from an end-user perspective includes the following key points in more detail:
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.
Seamless Integration: The feature integrates with RMS and OMS systems, ensuring smooth handling of multi-pack box orders and AWB management.
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.
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 is not be allowed. This ensures that all child boxes are accounted for and scanned during the handover process.
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.
Child AWBs Coming from Logistics aggregator : Child AWB on a box level will be given by Logistics aggregator like Clickpost.
Child AWB is same as parent AWB.
Internal backend configurations to allow multiple pack boxes and to allow box labelsat 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.
...
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.
...
When Allow Multiple Packboxes config is turned OFF in Packing
...
screen Configurations, the user can process the Block Complete B2C orders as usual and there is no change in the packing process.
Packing process for Single Shipment Partial Orders(When Allow Multiple Packboxes config is turned OFF in Packing screen Configurations)
SINGLE_SHIPMENT_PARTIAL orders refer to a specific order fulfillment type in which not all items of a BLOCK_COMPLETE order can be fulfilled. In such cases, the fulfillment type is updated to SINGLE_SHIPMENT_PARTIAL. For these orders, all unscanned items will be automatically canceled in WMS during the Complete Packing process.
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
at Packing screen configurations, below steps should be followed for orders with type SINGLE_SHIPMENT_PARTIAL.
Scan the Item Codes as usual in Piece Packing screen.
Once all Item Codes which user wants to pack are scanned, please click Partially Pack in Box button. This will allow user to only pack the scanned line items even when the number of line items in order were more than scanned.
User can complete the packing by clicking Complete Packing button.
User can print invoice and shipping label by clicking Print Invoice & Shipping Label button.
...
Packing process for Block Complete Orders when Allow Multiple Packboxes configuration is turned On
When Allow Please follow below steps when the 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 - turned On.
On scanning first item, the Scan Box pop up will be displayed. Here, user can generate and print a Box Id. Box ID should be sticked to Box.
Since it’s first box of the shipment, user is still given the choice to pack the order in single box. User can click the button Pack Order in a Single Box to still go ahead with packing in single box.
If a box Id was generated in previous step, user will scan required items while physically adding those to the box.
Please click Close Box button once required items are added into it.
After closing previous box of same shipment, when user scans the next item, the Scan Box pop up will be displayed. Please print the Box Id and scan. Please stick the Box Id to the box.
Please keep on scanning all the items while physically adding those to the box. The count of items SKU-wise in the box is present in the screen as shown below.
Please close the box once the required items are added to that box. A close box confirmation will pop up, please click Confirm button.
If the package SKU, dimensions or weight capturing is enabled, te Capture Package details pop up will appear. Capture the required details and Submit.
Please scan all the all the box AWBs to complete the shipment.
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 IDOMS UI: Add isMultiPackBoxAllowed & areBoxLabelsAllowed flags while creating internal order
- To discuss on this
Manifest Flow
Steps to create and close manifest for Multiple Pack Box shipments
A manifest is created in Manifest screen as usual.
For shipments without multiple boxes, AWB number can be scanned as usual and there is no change in the user interface.
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.
User will have to scan all the box Ids that belong to that specific shipment.
Post that, please click on Add Shipment button to continue scanning other AWBs
Generate Manifest Document
Please find the sample manifest document where multiple boxes for the same shipment are present.
...
- Rahul Singh To attach the document.
Handover Flow
Steps to Handover by AWBs for Multiple Pack Box shipments
For shipments without multiple boxes, AWB number can be scanned as usual and there is no change in the user interface.
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.
User will have to scan all the box Ids that belong to that specific shipment. If some packets are not scanned and added to the manifest, manifest close is not be allowed.
Post that, please click on Confirm button to continue scanning other AWBs for handover.
Handover By Manifest
No changes in this flow.
...
- Rahul Singh Sample handover and manifest doc to be added
Creating Internal Order with Multi-Pack Boxes & labels
Add isMultiPackBoxAllowed & areBoxLabelsAllowed flags while creating internal order
- To discuss on the requirement & use case
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.
...
In case where dimension capturing is mandatory, but for all the closed boxes dimensions are not captured. Insuch In such case user has to capture the dimensions for all the close boxes (with some items) and then proceed with the close shipment.
...
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:
Users can create new boxes by pressing the "Create New Box" button and scan items to these pack boxes for tracking.
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.
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.
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.
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.
...
Provision to capture the number of pack boxes at the time of packing.
...
As a warehouse operator I should be able to enter the number of pack boxes and scan items to these pack boxes for tracking.
The same data should flow to integration layer.
...
Provision to consume child and parent AWBs for the shipment from the aggregator or marketplace.
...
Shipping labels & Package SKU to be consumed for each child packet.
...
Each child box will have the same shipment attributes as we now have for a single B2C shipment.
...
Manifest/Handover addition and removal for multi-piece shipments to track that all child boxes are accounted for and scanned.
...
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.
...
Manifest and handover docs to have multi-piece shipment information.
...
For seamless operations one would need this data on the documents as well.
We will need to have Increff pack box Id pasted on box
No changes will be there for single box packing flow.
...
Will pack box stickers be printed for B2C shipments as well?
Will one need to scan Increff pack box Ids?
...
yes stickers will be printed.
we can get them to scan items id and then box id.
no need for a separate scan to validate box id
All boxes of a shipment can be manifested at once only.
like if 3 boxes are there then all the should be together.After the errors are resolved by user on taking required actions, the below message will be displayed.
...