Task Concepts
Understanding the core building block of every delivery in Deliverty Hub.
What Is a Task?
A task is the fundamental unit of work in Deliverty Hub. It represents a single delivery assignment that connects a sender (pickup location) to a recipient (drop-off location), along with all the information needed to fulfill that delivery: the customer who requested it, the packages being transported, payment details, and the agent responsible for carrying it out.
Every delivery operation in the platform — whether it is a simple point-to-point package drop or part of a complex multi-stop job — is modeled as one or more tasks.
All tasks belong to an organization. When you create or view tasks, they are automatically scoped to your current organization. This means each tenant sees only their own tasks, customers, and delivery data.
Task Types
Deliverty Hub defines five distinct task types. Each type describes the nature of the operation being performed:
| Type | Code | Description |
|---|---|---|
| JOB | JOB |
A parent task that groups multiple child tasks into a single operation. Does not represent a physical delivery itself. |
| PICKUP | PICKUP |
Collect a package or item from a sender location. |
| DELIVERY | DELIVERY |
Deliver a package or item to a recipient location. |
| CASH_COLLECTION | CASH_COLLECTION |
Collect a cash payment from a customer (e.g., cash-on-delivery amount). |
| CASH_DROP | CASH_DROP |
Drop collected cash at a designated location (e.g., back to the merchant or office). |
The JOB type is special — it acts as a container for child tasks (pickups, deliveries, cash operations). See Jobs vs Tasks for details on how parent-child relationships work.
Anatomy of a Task
Every task is composed of several key pieces of information that together describe the full delivery assignment:
Customer
The customer is the person or business that requested the delivery. Each task is linked to exactly one customer record within the organization. The customer provides sender/recipient contact details and may receive real-time notifications about the delivery status.
Packages
A task can contain one or more packages. Each package has its own description, dimensions, weight, and barcode. Packages are the physical items being transported from pickup to drop-off.
Locations
Every task has associated locations — typically a pickup address and a drop-off address. Locations include GPS coordinates, a formatted address string, and optional contact information for the person at that location. These coordinates power the live tracking map and are used by assignment algorithms to calculate distances.
Payment
Tasks can have payment information attached, including the payment method (cash on delivery, prepaid, etc.), amount, currency, and payment status. This is especially important for CASH_COLLECTION and CASH_DROP task types.
Agent Assignment
An agent (delivery driver) is assigned to carry out the task. Assignment can happen automatically through the platform's assignment engine or manually by a dispatcher from the dashboard. Once assigned, the agent receives the task in their mobile app and can accept, navigate, and complete it.
Creating Tasks
There are two primary ways to create tasks in Deliverty Hub:
From the Dashboard
Dispatchers and organization admins can create tasks manually through the dashboard interface. The task creation form allows you to specify the customer, pickup and drop-off locations, packages, payment details, and whether the task should be dispatched immediately (ASAP) or scheduled for a later time.
Via Channel API
Tasks can also be created programmatically through channels. A channel represents an external integration (e.g., an e-commerce platform, a POS system, or a third-party order management tool) that pushes delivery requests into Deliverty Hub via the API. This enables fully automated order-to-delivery workflows without manual intervention.
Channels are configured per organization. Each channel has its own API credentials and can map external order fields to Deliverty task fields. Refer to the Developer Guide for API integration details.
Organization Scoping
Deliverty Hub is a multi-tenant platform. Every task is bound to the organization that created it. This means:
- Data isolation — Organization A cannot see or modify tasks belonging to Organization B.
- Automatic filtering — When you query tasks (from the dashboard or API), only tasks within your organization are returned.
- Agent scoping — Agents can only be assigned to tasks within their own organization.
- Customer scoping — Customer records are organization-specific; the same physical person may exist as separate customer records in different organizations.
Super Admins with platform-wide access can view tasks across all organizations for support and monitoring purposes.