Use an automation rule to create the picklist for you once the last assembly order on a sales order is completed.

Before you start: the new trigger, condition and action are rolled out behind an account flag. If you don't see them in the automation builder, ask Luminous support to enable them. The rule only applies to assembly orders created from sales order lines, because those store their source sales order.

Set up the rule

  1. Go to Tools → Automation and click Create Rule.
  2. In Trigger Settings, set Event Trigger to Assembly Order Completed.
  3. Click Add Global Condition. Under Condition Type, choose All Linked Assembly Orders Completed (in the Manufacturing group). This condition is true only when every assembly order linked to the sales order is completed.
  4. Add the action Create Picklist.
  5. Optional: tick Create fulfillment orders if the sales order has none. Luminous then generates the fulfillment orders first. Leave it unticked if you want the rule to skip sales orders that have no fulfillment orders.
  6. Save and activate the rule.

What happens when it runs

  • The action picklists the sales order's open fulfillment orders and creates one picklist per warehouse group. This is the same logic as Create Picklist on the Sales Order grid.
  • Fulfillment orders that are shipped, cancelled, on hold or already on a picklist are left out.
  • If another assembly order of the same sales order is completed at the same moment, only one run creates the picklist. The other run is skipped.

Why a run was skipped

The run log records a skip, not an error, for these cases. A skip does not trip the rule's error protection.

  • The sales order has no fulfillment orders and the checkbox is off.
  • The sales order is deleted or inactive.
  • The sales order is already picklisted or has nothing left to pick.
  • The picklist can't be created, for example because there is no stock in the warehouse group. The run log shows the same message the Sales Order grid would give.

The condition's result is also shown in the run log, for example "2 of 3 linked assembly orders completed".