Skip to main content

How do I properly use batch picking in Logentic?

Use batch picking when similar orders can be grouped, keep pick and pack work clear, and collect evidence when a batch or route flow does not progress.

Written by Max Villemure

Quick answer

Use batch picking when your team wants to group similar orders so they can be picked more efficiently. Confirm the warehouse, eligible orders, and pick/pack process before creating or progressing batch work.

Common use cases

  • Warehouse lead: Group similar orders into a batch for more efficient work.

  • Picker: Work from the batch picking queue when batch work has been prepared.

  • Packer: Pack picked batch work using the process your warehouse has confirmed.

When to use this

  • Multiple eligible orders can be grouped operationally.

  • Your warehouse process supports batch picking for the selected orders.

  • The team is ready to keep batch pick and pack steps clear.

Before you start

  • Confirm the correct warehouse and merchant context.

  • Confirm the orders are eligible to be grouped together.

  • Do not mix workflows unless your warehouse lead has confirmed the process.

  • If your flow uses scanning, confirm the accepted product barcode or scan code before training operators.

  • Creating or progressing a batch may affect live warehouse work, so pause if the order set is unclear.

Steps

  1. Open the batch picking area your team uses, such as Fulfill Orders batch queues or the batch order workflow.

  2. Select the correct warehouse and confirm the visible order set.

  3. Review whether the orders should be grouped together for batch picking.

  4. Create or open the batch only when the selected orders are correct.

  5. Pick the batch using your warehouse process.

  6. Pack the picked batch using your warehouse process.

  7. If your process uses totes, labels, or scanning, confirm those steps before progressing live work.

  8. If the batch, route, or picking activity does not appear or update as expected, contact support with the evidence below.

What good looks like

The team groups the right orders, keeps pick and pack work clear, and can explain exactly where a batch stopped if support needs to investigate.

Common issues and next actions

If this happens

What to do next

The batch does not appear after creation.

Check the warehouse, batch queue, and filters. Then contact support with the batch ID and approximate time.

A route or batch generation step shows an unclear technical error.

Do not retry at scale. Capture the warehouse, merchant, order count, route method or batch context, and approximate time.

A product scan is rejected.

Scan the configured product barcode or scan code. Do not assume the visible SKU is the accepted scan value.

Contact us when

Contact support when a batch does not appear, does not progress, shows unexpected quantities, rejects expected scans, or could affect fulfillment work if the wrong action is taken.

Send us this information

  • Warehouse and merchant.

  • Batch ID, if visible.

  • One or two example order IDs.

  • Which step stopped: creation, picking, packing, route generation, or scanning.

  • Route method and parameter values, if route generation was involved.

  • Expected result and actual result.

  • Screenshot with private customer data masked.

Useful links

Screenshots

Fulfill Orders page showing warehouse selection, search, sort, and batch workflow tabs.

Steps 1-4: Start from Fulfill Orders, confirm the warehouse, then use batch-related queues only when the order set is ready to be grouped.

Tote Manager page header used for tote-based picking and packing context.

Steps 5-7: If your batch process uses totes, confirm the tote workflow before picking or packing live batch work.

Did this answer your question?