SDEL: Sales Deliverable
The SDEL entity: A line item on a sales order representing a specific product, service, or deliverable with pricing and delivery details.
SDEL 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 SDEL.Entity properties
| Property | Value |
|---|---|
| Entity code | SDEL |
| Display name | Sales Deliverable |
| Plural | Sales Deliverables |
| Level | 1000 |
Use cases
SDEL is a child entity of SCON (Sales Order), linked via the SUB|ENT|SCON|SDEL comboKey. Each SDEL record represents one deliverable line item on an order. It captures product identification (part/SKU number, serial number), pricing (unit price, quantity, discount percentage, and a computed totalPrice via formula), delivery logistics (shipping method, tracking, carrier, delivery address, installation requirements), and technical details (specifications, version/model, license keys, activation/expiration dates, warranty).
The deliverableType field links to SDELTYPE for classification, enabling reporting by deliverable category. The status workflow (pending through delivered/installed/cancelled) tracks individual line item progress independently of the parent order status. This separation from SCON allows partial delivery scenarios where some items ship before others.
Fields
Deliverable Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Deliverable Name |
deliverableType | reference → SDELTYPE | Yes | Deliverable Type |
description | text (multi-line) | Description | |
partNumber | text | Part/SKU Number | |
serialNumber | text | Serial Number | |
quantity | number | Yes | Quantity |
unitPrice | number | Yes | Unit Price |
discount | number | Discount % | |
totalPrice | number | Read-only. Total Price |
Delivery Information
| Field | Type | Required | Notes |
|---|---|---|---|
status | enum | Yes | Status Valid ids: pending (Pending), confirmed (Confirmed), inprogress (In Progress), ready (Ready), shipped (Shipped), delivered (Delivered), installed (Installed), cancelled (Cancelled), onhold (On Hold). |
expectedDeliveryDate | date | Expected Delivery Date | |
actualDeliveryDate | date | Actual Delivery Date | |
shippingMethod | enum | Shipping Method Valid ids: standard (Standard Shipping), express (Express Shipping), overnight (Overnight), freight (Freight), pickup (Customer Pickup), digital (Digital Delivery), na (Not Applicable). | |
trackingNumber | text | Tracking Number | |
shippingCarrier | text | Shipping Carrier | |
deliveryAddress | text (multi-line) | Delivery Address | |
installationRequired | boolean | Installation Required | |
installationDate | date | Installation Date | |
installationNotes | text (multi-line) | Installation Notes |
Specifications
| Field | Type | Required | Notes |
|---|---|---|---|
technicalSpecs | text (multi-line) | Technical Specifications | |
version | text | Version/Model | |
licenseKey | text | License Key | |
activationDate | date | Activation Date | |
expirationDate | date | Expiration Date | |
warrantyPeriod | number | Warranty Period (Months) |
Dependencies & Requirements
| Field | Type | Required | Notes |
|---|---|---|---|
prerequisites | text (multi-line) | Prerequisites | |
dependencies | tags | Dependencies | |
compatibilityNotes | text (multi-line) | Compatibility Notes |
Attachments
documents: file attachment field.
Additional panels
- Activity timeline panel attached.
Relationships
- Lookups:
deliverableTypepoints at aSDELTYPErecord.
Creating a Sales Deliverable via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SDEL",
"level": 1000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"deliverableType": "",
"quantity": 1,
"unitPrice": 1
} Listing Sales Deliverables records
GET /v1/entities/SDEL/SUB