ITADORDER: Disposition Order
IT Asset Disposition order grouping assets for coordinated disposal, recycling, or remarketing.
Default definition. This article describes the default
ITADORDER definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches ITADORDER.Entity properties
| Property | Value |
|---|---|
| Entity code | ITADORDER |
| Display name | Disposition Order |
| Plural | Disposition Orders |
| Level | 50600 |
Use cases
ITADORDER is the primary ITAD entity, grouping individual assets (ITADLINE) into disposition orders. Typical use cases: hardware refresh cycles, office closures, data centre decommissions, or ad-hoc end-of-life disposals. Each order tracks the ITAD vendor, collection site, financial estimates vs actuals, and links to child entities for line items (ITADLINE), shipments (ITADSHIPMENT), and compliance certificates (ITADCERT).
Fields
Order Details
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Ref. | |
name | text | Yes | Order Name. |
description | text (multi-line) | Description. | |
status | enum | Yes | Valid ids: draft (Draft), planned (Planned), inProgress (In Progress), completed (Completed), closed (Closed). |
priority | enum | Valid ids: low (Low), normal (Normal), high (High), urgent (Urgent). | |
type | enum | Yes | Valid ids: refresh (Refresh Cycle), officeClosure (Office Closure), dataCentreDecom (Data Centre Decommission), endOfLife (End-of-Life Batch), adHoc (Ad-hoc Disposal). |
requestedBy | reference → user | Requested By. | |
requestDate | date | Request Date. |
Dates
| Field | Type | Required | Notes |
|---|---|---|---|
plannedStartDate | date | Planned Start. | |
plannedEndDate | date | Planned End. | |
actualStartDate | date | Actual Start. | |
actualEndDate | date | Actual End. |
Vendor & Site
| Field | Type | Required | Notes |
|---|---|---|---|
vendor | reference → VEN | Primary ITAD service provider | |
site | reference → SITE | Collection Site. | |
orderManager | reference → user | Order Manager. | |
coordinators | array of references → user | Coordinators. | |
vendorRef | text | Vendor's job or ticket reference | |
notes | text (multi-line) | Notes. |
Financial Summary
| Field | Type | Required | Notes |
|---|---|---|---|
assetCount | number | Calculated from line items | |
totalWeightKg | number | Total Weight (kg). | |
estimatedCost | number | Estimated Cost. | |
actualCost | number | Actual Cost. | |
estimatedRecovery | number | Estimated Recovery. | |
actualRecovery | number | Actual Recovery. | |
netCost | number | Actual cost minus actual recovery |
Environmental
| Field | Type | Required | Notes |
|---|---|---|---|
landfillDivertedKg | number | Landfill Diverted (kg). | |
co2AvoidedKg | number | CO2 Avoided (kg). |
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
vendorpoints at aVENrecord;sitepoints at aSITErecord;requestedBypoints at a user;orderManagerpoints at a user;coordinatorspoints at multiple users. - Related lists:
ITADLINE(formatSUB|ITADORDER),ITADSHIPMENT(formatSUB|ITADORDER),ITADCERT(formatSUB|ITADORDER).
Creating a Disposition Order via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ITADORDER",
"level": 50600,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"status": "draft",
"type": "refresh",
"ref": "..."
}Listing Disposition Orders
# All records in your tenant
GET /v1/entities/ITADORDER/SUB:<your-sub-id>