Distributionoperational

Preparation & Shipping Tasks

How does a consignment get prepared and shipped — and who is on the hook for each step?

Execution is two tracked phases with named owners. Creating a consignment can generate preparation tasks for warehouse staff and shipping tasks for drivers, each due on its own date, while separate preparation and shipping statuses record where the consignment stands.

What it records

  • Generated, dated tasks

    Preparation and shipping tasks are created in the platform task system with due dates from the consignment’s own dates.

  • Warehouse-registered preparers

    Preparation staff are selected from people registered in the source warehouse, not an open employee list.

  • Availability before assignment

    Existing task load around the due date is checked, so busy people are visible before work lands on them.

  • Independent phase statuses

    Preparation and shipping carry separate statuses through to completion, exposing exactly where a consignment stands.

  • Explicit delegation

    A consignment can be accepted by another named employee, recorded on the record itself.

How it works

Preparation staff are chosen from the people registered in the source warehouse, shipping persons from the employee register, and the availability check shows who is already carrying tasks around the due date. When task generation is switched on, the platform task system receives a named task per person — preparation tasks due on the preparation date, shipping tasks due on the cargo picking date — carrying the consignment’s reference and notes.

Status is per phase: the preparation status and the shipping status advance independently, so a consignment can be fully picked while transport is still pending, and the record shows exactly that. Delegation is explicit — a consignment can be accepted by another named employee — and a completion flag closes it. Where no transport is generated, the shipping phase simply carries no tasks.

See preparation & shipping tasks running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.