Champ configuration is_multi_pack_box_allowed(for b2c) +1 more cponfig at channel level /wiki/spaces/AD/pages/471434257
same property will flow to order.
...
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.
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.
Packing Flow
Capturing B2C Dimensions
Manifest Flow
Handover Flow
B2B Order Creation
There will be no changes in the process/ flow if the configurations are disabled to allow multiple-pack boxes.
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.
...
Below case would be in rare scenarios
...
Manifest
Get Shipment details for a scanned AWB
A GET call in OMS is exposed in which an AWB and Transporter are provided.
OMS fetches the Shipping Label (SL)with above detail.
OMS extracts Shipment Id(S1) from SL.
Fetches all Shipping Labels using S1 from SL tables, If any PackBox Type SL exists, fetches box Ids from pack box details relation
Prepares a data , with all Shipping Label (PACK_BOX, SHIPMENT) level and sends to WMS.
Add AWB to Manifest
Scan the AWB to add.
WMS to trigger a proxy API to OMS to fetch the shipment details for the AWB.
Based on the workflow, UI to validate the scanned AWB as mentioned here.
Once all the validations are successful, trigger “Add AWB to manifest” API for the parent AWB (
the scanned child AWBs are temporarily saved at the UI end, if the user refreshes it they will have to scan it once again).Add validations in “Add AWB to manifest” API in OMS to support only parent AWBs.
- In case multiple boxes are present in a shipment, display the count of scanned Box AWBs for the shipment AWB. This will be temporarily saved in the UI until all the box AWBs are scanned.
Remove AWB from Manifest
Scan the AWB to remove.
WMS to trigger a proxy API to OMS to fetch the shipment details for the AWB.
Based on the workflow, UI to validate the scanned AWB as mentioned here.
Once all the validations are successful, trigger trigger “Remove AWB from manifest” API for the parent AWB (
the scanned child AWBs are temporarily saved at the UI end, if the user refreshes it they will have to scan it once again).Add validations in “Remove AWB from manifest” API in OMS to support only parent AWBs.
Close Manifest
...
During the close manifest request send list of Box ID for every parent AWB
...
Currently we will print the count of boxes in the document. In future, we can customize and print box IDs if required.
...
OMS to send all Box Details also to CIMS and Proxy during Close Manifest call
...
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
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
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
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 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 manifest handover document. Line items in Manifest Handover Doc to be sorted in descending order of box count.
Document should also have total box count in the end.
...
Handover
Handover By AWB
Scan the AWB to handover.
WMS to trigger a proxy API to OMS to fetch the shipment details for the AWB.
Based on the workflow, UI to validate the scanned AWB as mentioned here.
Once all the validations are successful, trigger “Confirm Handover” option will be enabled for the parent AWB.(
the scanned child AWBs are temporarily saved at the UI end, if the user refreshes it they will have to scan it once again).Send the list of Box ID for AWB in “Handover Shipments” API from OMS to CIMS.
RMS to use this list of box ID and include the count of boxes for every AWB during the handover document creation.
Handover By Manifest
Since we have done all the checks during adding AWB to manifest, no further checks are required here. No changes in this flow.
Generate Handover Document
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.
...
- Sample handover and manifest doc to be added
- 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:
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.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.
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.
...