Next-generation platform

Configuring batch picking

To configure batch picking and shipment-based batch picking, enable appropriate resource permissions, bar code types, and configure the Store Inventory ManagementAPIs.

Note: For configurations required for shipment-based batch picking, see Configuring shipment-based batch picking.

Applications Manager

  • Resource permissions
    Enable the following resource permissions for batch picking by using Applications Manager:
    • Pick batches
    • Assign all
  • Bar code types

    Configure the following bar code types for your store by using Applications Manager:

    • Store Scan Item or Location. Used to scan either the product or the location. The bar code validation sources are SIM location, SIM Serial, and Item.
      Note: The Store Scan Item or Location bar code is not used in no-inventory stores.
    • Item. Used by no-inventory stores. To use the Item bar code type, source should be Item
    • Hold Location. Used to translate the bar codes by scanning either a product, a tote or, a staging locations to deposit orders.
      Note: This configuration is not required if staging location scan is not required during batch pick. If the store is configured as a no-inventory store and if staging location scan is required as part of batch picking and locations are maintained in an external system, then the Barcode Validation Source must be set as External Source and provide a validation service for this bar code type.
    • Location. Used to assign a staging location.
    • Serial Scan. Used to scan the serial number to remove a product picked using that serial number. The bar code validation source is SIM serial.
      Note: This configuration is not required if you do not maintain serials or the store is configured as a no-inventory store.
    By default, bar code types are provided for the default organization. When you set up a new enterprise, you must create these bar code types again or copy it from the Default organization. For more information, see Configuring bar codes.

Order modification

In case of any shortage during batch picking, if you want to add a note, ADD_NOTES order modification permission must be enabled at the order line level for the appropriate status.

Sales orders

In Applications Manager, enable the on_success event of createShipment transaction to change the shipment status to Ready for batch pick. Enabling this event invokes the action that changes the shipment status to Ready for backroom pick. You must also add the Change Status Required condition and Change Shipment Status to Batch Pick alert.

System Management Administrator (SMA)

For sales orders and transfer orders, the ISFCreateSIMPickRequest service is called to create a pick request task. If you want to use any other custom service, configure the isf.ydm.createPickRequestService property to be the name of the custom service that you want to be invoked. If this property is blank, then no service will be called to create a pick request task.

Sterling Business Center

In Sterling Business Center, under Batch Pick Rules, select the following options:
  • Pickup and Shipping - It allows the pickup and shipping orders to move to Ready for Batch Pick status. It is mandatory to set these options as Y.
  • Move transfer order shipments to Ready for Backroom Pick status - It allows picking and shipping to be done for transfer orders in store. If this is unchecked then batch picking is skipped and shipment status is moved to Ready for Packing.
  • The Staging location required and Staging location translation required options are not applicable.

Catalog data

Ensure that the catalog data from Sterling Order Management System is synchronized with Sterling Store Engagement. For more information about how to synchronize catalog data, such as serialized flag, department, and product velocity, see Updating catalog data.

Store Inventory Management APIs

  • batch-pick-configurations API

    Create the batch pick configuration by using the batch-pick-configurations API.

  • Update and delete batch pick configuration APIs

    Use the Update batch pick configuration and Delete batch pick configuration APIs to modify or delete your batch pick configurations.

  • scheduled-jobs API

    Create batch pick schedules by using the scheduled-jobs API.

  • exception-codes API

    Create the shortage reasons for backroom pick using the exception-codes API.

  • store-rules API

    Configure whether location scanning is mandatory or not by setting the IS_LOC_SCAN_MANDATORY to Y or N in the store-rules API. The default value is Y. To disable automatic staging, call store-rules API and set AUTO_STAGE_PRODUCTS as N. Automatic staging is enabled by default. To enable scanning each of the products during deposit flow, call store-rules API and set BP_ALWAYS_SCAN_STAGING_LOCATION as Y as the default value is N.

  • pick-preferences API

    Set the default inventory status and configure whether to exclude or include locations from being considered for stamping as a source location during backroom pick task by using the pick-preferences API. The autoStagingLocationId should be configured when the AUTO_STAGE_PRODUCTS rule is set to Y.

  • locations API
    Create locations for the store by using the locations API. The batch pick flow does not work without an intermediate location. Therefore, you must create a location PICK-VIRTUAL, of the location type VIRTUAL, and set the virtual flag as True.
    • If the store is configured as a no-inventory store, it is not mandatory to configure locations. Create Totes by using the Location type as TOTE
    • It is mandatory to create totes for batch picking when sort while pick is used.
    • Tote creation is supported in single location and no-inventory store.

Print service

The ISFPrintSIMBatchPickList print service is implemented to print pick ticket. The ISFPrintBatchPicks_multiApiInput.xsl.sample and ISFPrintBatchPicks_output.xsl.sample templates are stored in the /template/prints/ycd/xsl/ directory as part of the add-in workspace and built into the <INSTALL_DIR>/jar/platform/9_5/resources.jar. You can continue to use the sample XSL or remove .sample from the file name and customize it as required.

The ISFPrintSIMBatchOrderDetails print service is implemented to print order slip with deposited products. The ISFPrintBatchOrderDetails_multiApiInput.xsl.sample and ISFPrintBatchOrderDetails_output.xsl.sample templates are stored in the /template/prints/ycd/xsl/ directory as part of the add-in workspace and built into the <INSTALL_DIR>/jar/platform/9_5/resources.jar. You can continue to use the sample XSL or remove .sample from the file name and customize it as required.