Batches are one of the most powerful tools in SKULabs for processing high volumes of orders efficiently, but when something goes wrong it can slow your whole team down. This guide covers the most common batch issues and how to resolve them.
All the settings below are in the Batch type editor. Open it from Settings > Profile Settings > Change batch settings, or with the Settings button on the Batches page. If you use saved batch types, pick the batch type and click Edit.
Issue 1: Out-of-stock orders are being pulled into batches
Two settings decide whether SKULabs checks stock when it builds a batch:
Allow out-of-stock orders/items (default Yes)
Allow partial fulfillment (default No)
How they work together:
Both No: only orders that are fully in stock join the batch, and pickers never see out-of-stock items. This is the strictest setup and the best choice if you do not partially ship.
Out-of-stock Yes, partial fulfillment No (the default): only orders that are fully in stock join. If stock changes after the batch is built, pickers can still see out-of-stock items.
Out-of-stock No, partial fulfillment Yes: an order can join when at least one of its items is fully in stock; missing items are hidden from pickers. Use this if you partially ship.
Both Yes: no stock check at all. Any order can join, even with nothing in stock.
Stock is counted only in the warehouses selected under Warehouses in the batch type, or in your user's warehouses if none are selected. If out-of-stock orders still join after you change these settings, open the batch type and click Save once so the settings are stored.
Ship mode does not affect stock checks. Batch ship (default) and Bulk ship pull in the same orders. The only difference is that Bulk ship takes orders in the order they come in instead of following Order preference.
Dropshipped orders appearing in batches
Orders where every item is dropshipped on your sales channel are never added to batches.
When SKULabs sends an order to a supplier on a dropship purchase order, the order's status becomes Awaiting fulfillment, which can still be batched. It is kept out only when stock is checked, so set Allow out-of-stock orders/items or Allow partial fulfillment to No (see above).
Issue 2: Orders split across warehouses aren't batching correctly
If you pick from more than one warehouse, set up each part below. All of them are needed; batch settings alone are not enough.
Link stores to warehouses and restrict picking. Go to Settings > Inventory > Stock sync, click the pencil icon for each store, choose the warehouses linked to it and turn on Restrict picking to linked warehouses, so items are only picked from those warehouses.
Set each user's warehouses. On the Users page, edit each user and, under Warehouses, set Default warehouse and Picking warehouses to the warehouse they work in. A user only sees and picks inventory in their picking warehouses.
Create one batch type per warehouse. In the Batch type editor, tick only that warehouse under Warehouses (orders not assigned to it are skipped, and stock is counted only there) and tick the stores it should pull orders from under Stores.
Set the stock settings in each batch type. Set Allow partial fulfillment to Yes, since each batch picks only the part of the order its warehouse holds, and Allow out-of-stock orders/items to No, so a batch never takes a line it has no stock for.
Let the second warehouse's batch take a started order. If your batch type has a Statuses filter, include Not started, Awaiting fulfillment, Opened, In progress, Partially cleared and Partially shipped, and leave Cleared out. Otherwise, set Allow partially shipped orders to Yes; the second batch can then take the order once the first warehouse has shipped its part.
Issue 3: A batch was accidentally cleared or deleted
Clearing a batch cannot be undone from the app. Contact SKULabs support with the batch number and we can look into it.
Tip: To avoid accidentally clearing an entire batch when trying to remove a single order, use the individual order removal option rather than the batch-level clear action. These are separate controls, so take care to select the right one.
Issue 4: Batch type editor, what each setting does
Which orders join the batch
Name and Share: the batch type's name, and whether other users on your account can use it.
# of orders/bins: the maximum number of orders per batch (default 3). Some accounts also have Minimum # of orders/bins.
Order preference: which orders go first: Simplest first, Complex first, Random distribution, Oldest first or Newest first.
Memorized shipments: Include both, Include only memorized, or Include only unmemorized.
Order total value, Number of lines in order, Number of items in order: minimum and maximum limits.
Same orders only: every order in the batch has the same combination of items and quantities.
Allow out-of-stock orders/items and Allow partial fulfillment: see Issue 1.
Allow partially shipped orders: whether orders with status Partially shipped can join. Not used while any status is selected in Statuses.
Statuses (if shown): include or exclude orders by status. Leave every status untouched to keep the default (see Issue 5). Shipped and cancelled orders can never be batched.
Address validation: Required (default) skips US orders without a validated address.
Payment status: Include only paid orders (default) or Include all orders.
Warehouses, Stores and Tags: limit the batch to orders from those warehouses and stores, and include or exclude orders by tag.
Picking, shipping and printing
Picking Order: Ascending (A-Z) or Descending (Z-A).
Display and allow picking from out-of-stock locations: lets pickers choose a location that shows no stock.
Picking mode: Guided steps (default), Reverse scanning, Paper pick list, Paper packing slips, No picking or Pick after shipping. Modes other than Guided steps use Bulk ship.
Ship mode: Batch ship (default) or Bulk ship.
Bin scans: Required (default) or Optional.
Post-shipping audit: Required or Optional.
Warning unprocessable orders: checks the batch for cancelled, archived and deleted orders before picking and shipping. Leave it on.
Print packing slips and Print shipping labels: when each document prints during the batch.
Issue 5: Orders aren't appearing in batches at all
Check these in the Batch type editor:
Order status: by default only orders that are Not started or Awaiting fulfillment join, plus Partially shipped if that setting is Yes. Orders that are opened, in progress, cleared, delayed (on hold), shipped or cancelled are skipped. If your batch type has a Statuses filter and any status is selected there, that list decides instead (shipped and cancelled orders are always skipped).
Stores and Warehouses: the order's store must be ticked, and the order must be assigned to a ticked warehouse.
Tags: an order with an excluded tag, or without a required tag, is skipped. Orders tagged Hold - Archived are always skipped.
Stock: with stock checks on (Issue 1), orders that are not in stock in the selected warehouses are skipped.
Payment status and Address validation.
Order total value, Number of lines in order and Number of items in order limits.
Orders where every item is dropshipped on the sales channel.
Frequently asked questions
Can I remove a single order from a batch without clearing the whole batch?
Yes. Inside an active batch, you can remove individual orders without affecting the rest of the batch. Be careful not to use the batch-level clear action; use the per-order removal control instead.
Can two people work on the same batch?
Any user can open any batch, and SKULabs shows a notice when another user changes it. For multi-warehouse orders, it is still best to give each warehouse its own batch type (see Issue 2).
How do I know which settings are causing the problem?
Open the Batch type editor and review the out-of-stock settings, Warehouses, Stores and Tags. If you're still unsure, contact SKULabs support with an example batch or order number and we can look at the specific configuration.