Overview
TheTaskResponse model represents a single preparation task assigned to a kitchen station. Tasks are automatically created when orders are processed and distributed to the appropriate station based on product types.
Fields
Unique identifier for the task.
The ID of the order this task belongs to. Multiple tasks can belong to the same order if products need to be prepared at different stations.
The kitchen station responsible for this task.Possible values:
BAR- For drinksHOT_KITCHEN- For hot dishesCOLD_KITCHEN- For cold dishes
The table number this task is for. Used to deliver the prepared items to the correct table.
Array of products included in this task. All products in a task are prepared at the same station.
Timestamp when the task was created.Format:
YYYY-MM-DDTHH:mm:ssCurrent status of the task.Possible values:
PENDING- Task is waiting to be startedIN_PREPARATION- Task is currently being preparedCOMPLETED- Task has been finished
Timestamp when preparation started. Will be
null if the task hasn’t been started yet.Format: YYYY-MM-DDTHH:mm:ssTimestamp when the task was completed. Will be
null if the task hasn’t been completed yet.Format: YYYY-MM-DDTHH:mm:ssTask Lifecycle
Task Created
Task is created with status
PENDING when an order is submitted. The createdAt timestamp is set.Preparation Started
When a kitchen worker starts preparing the task, status changes to
IN_PREPARATION and startedAt is set.Example - Pending Task
Example - Task In Preparation
Example - Completed Task
Related Models
- CreateOrderRequest - Model for creating orders that generate tasks
- CreateOrderResponse - Response showing how many tasks were created