1. Home
  2. New Packing Flow
  3. Staging and Bundling Workflow

Staging and Bundling Workflow

Let’s understand the Staging and Bundling Workflow.

Applicability

Version: Enterprise version
Traceability: NONE, SKU and ITEM

Configuration

Staging Dock for a Shipment Staging or Bundle Staging Picklist-

  • Enforce Shipment Sorting at Staging Dock: (Yes and No)
  • Enforce Bundle Sorting at Staging Dock: (Yes and No)

Invoicing Dock for an Invoicing Picklist coming directly to the Invoicing Dock (without going through Staging)-

  • Enforce Shipment Sorting at Invoicing Dock: (Yes and No)
  • Enforce Bundle Sorting at Invoicing Dock: (Yes and No)

Note:-

  • By default, these configs would be ON.
  • In case of HandHeld, Enforce Shipment Sorting at Staging Dock and Enforce Shipment Sorting at Invoicing Dock configs would be OFF.
  • For any assistance related to the mentioned configs, kindly connect with our Chat Support Team.
  • For businesses who have enabled the enforced shipment sorting at the staging dock will not need to perform the sorting at the invoicing dock too as this will be taken care of in the staging dock itself.

  • The user can select the shipment to be processed from the Shipment details page.

Use Cases

a) Enforce Shipment Sorting at Staging Dock :

Let us consider Shipments- S1, S2 with SOI1, SOI2 and SOI1 and SOI3 respectively.

If the configuration is ON:

  • User picks and scans an item (SOI1)
  • The shipment associated with the item is enabled for processing viz. S2.
  • Now, the User has to scan SOI3 to complete the processing of S2.
  • If SOI2 is scanned instead of SOI3, an error message needs to be shown on the interface.
  • With this flow, the User cannot hop around multiple shipment while scanning.

If the configuration is OFF:

  • User picks and scan an item (SOI1)
  • The shipment associated with the item is enabled for processing viz. S2
  • Now, the User can scan either SOI3 or SOI2 as per his/her convenience.
  • If SOI2 is scanned instead of SOI3, then the shipment associated i.e. S1 is enabled for processing.
  • With this flow, the User can hop around multiple shipment while scanning.

b) Enforce Bundle Sorting at Staging Dock: 

Let us consider Bundles- B1, B2 with SOI1, SOI2 and SOI1 and SOI3 respectively.

If the configuration is ON:

  • User picks and scans an item (SOI1).
  • The bundle associated with the item is enabled for processing viz. B2.
  • Now, the User has to scan SOI3 to complete the sorting of B2.
  • If SOI2 is scanned instead of SOI3, an error message needs to be shown on the interface.
  • With this flow, the User cannot hop around multiple bundles while scanning.

If the configuration is OFF:

  • User picks and scan an item (SOI1)
  • The bundle associated with the item is enabled for processing/kitting viz. B2
  • Now, the User can scan either SOI3 or SOI2 as per his/her convenience.
  • If SOI2 is scanned instead of SOI3, then the bundle associated i.e. B1 is enabled for processing.
  • With this flow, the User can hop around multiple bundles while scanning.

c) Enforce Shipment Sorting at Invoicing Dock:

Note:- This applies to picklists coming directly to the Invoicing Dock, without going through the Staging Dock.

Let us consider Shipments- S1, S2 with SOI1, SOI2 and SOI1 and SOI3 respectively.

If the configuration is ON:

  • User picks and scans an item (SOI1).
  • The shipment associated with the item is enabled for processing viz. S2.
  • Now, the User has to scan SOI3 to complete the processing of S2.
  • If SOI2 is scanned instead of SOI3, an error message needs to be shown on the interface.
  • With this flow, the User cannot hop around multiple shipment while scanning.

If the configuration is OFF:

  • User picks and scan an item (SOI1).
  • The shipment associated with the item is enabled for processing viz. S2.
  • Now, the User can scan either SOI3 or SOI2 as per his/her convenience.
  • If SOI2 is scanned instead of SOI3, then the shipment associated i.e. S1 is enabled for processing.
  • With this flow, the User can hop around multiple shipment while scanning.

d) Enforce Bundle Sorting at Invoicing Dock:

Note:- This applies to picklists coming directly to the Invoicing Dock, without going through the Staging Dock.

Let us consider Bundles- B1, B2 with SOI1, SOI2 and SOI1 and SOI3 respectively.

If the configuration is ON:

  • User picks and scans an item (SOI1).
  • The bundle associated with the item is enabled for processing viz. B2.
  • Now, the User has to scan SOI3 to complete the sorting of B2.
  • If SOI2 is scanned instead of SOI3, an error message needs to be shown on the interface.
  • With this flow, the User cannot hop around multiple bundles while scanning.

If the configuration is OFF:

  • User picks and scan an item (SOI1).
  • The bundle associated with the item is enabled for processing/kitting viz. B2.
  • Now, the User can scan either SOI3 or SOI2 as per his/her convenience.
  • If SOI2 is scanned instead of SOI3, then the bundle associated i.e. B1 is enabled for processing.
  • With this flow, the User can hop around multiple bundles while scanning.

Note:-

  • By default, these configs would be ON.
  • In case of HandHeld, Enforce Shipment Sorting at Staging Dock and Enforce Shipment Sorting at Invoicing Dock configs would be OFF.
  • For any assistance related to the mentioned configs, kindly connect with our Chat Support Team.
  • For businesses who have enabled the enforced shipment sorting at the staging dock will not need to perform the sorting at the invoicing dock too as this will be taken care of in the staging dock itself.

  • The user can select the shipment to be processed from the Shipment details page.

Related Articles