DemandFlow Support Centre

SCON: Sales Order

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A sales order capturing customer orders with deliverables, financials, fulfillment, approvals, and commission tracking.

SCON: Sales Order

The SCON entity: A sales order capturing customer orders with deliverables, financials, fulfillment, approvals, and commission tracking.

Default definition. This article describes the default SCON 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 SCON.

Entity properties

PropertyValue
Entity codeSCON
Display nameSales Order
PluralSales Orders
Level500

Use cases

SCON is the primary revenue-side transaction entity, representing a confirmed or in-progress sales order from a customer. It links to COM (customer) rather than CLIENT because sales orders may originate from companies not yet formalised as clients. The entity covers the full order-to-cash lifecycle: order creation (type, priority, PO number), customer information (contact details, billing/shipping addresses), financial summary (subtotal, discounts, tax, shipping, total, paid, balance due), deliverables (via SDEL relatedlist with SUB|ENT|SCON|SDEL comboKey), payment terms and contract details, fulfillment logistics (delivery scheduling, warehouse, inventory reservation, pick lists, tracking), multi-step approval workflows (credit approval and manager approval), commission tracking for sales reps, audit history via AUDIT entity, and document management.

The toolbar provides actions for invoice generation, order confirmation, duplication, and printing. Bulk actions support batch approval, status updates, and Excel export. The shipping carrier field links to VEN, reusing the vendor entity for logistics providers.

Fields

Order Information

FieldTypeRequiredNotes
nametextYesName
reftextRead-only. Order reference
orderDatedateYesOrder Date
statusenumYesStatus Valid ids: draft (Draft), pending (Pending Approval), approved (Approved), confirmed (Confirmed), inprogress (In Progress), partialdelivered (Partially Delivered), delivered (Delivered), completed (Completed), cancelled (Cancelled), onhold (On Hold).
priorityenumPriority Valid ids: urgent (Urgent), high (High), normal (Normal), low (Low).
orderTypeenumYesOrder Type Valid ids: standard (Standard Order), rush (Rush Order), blanket (Blanket Order), scheduled (Scheduled Release), dropship (Drop Ship), internal (Internal).
poNumbertextCustomer PO Number
salesRepreference → userYesSales Representative
accountManagerreference → userAccount Manager
dealreference → DEALDeal

Customer Information

FieldTypeRequiredNotes
customerreference → COMYesCustomer
customerContacttextContact Name
customerEmailtextContact Email
customerPhonetextContact Phone
billingAddresstext (multi-line)Billing Address
shippingAddresstext (multi-line)Shipping Address
sameAsBillingbooleanShipping same as Billing

Financial Summary

FieldTypeRequiredNotes
currencyreference → CURRENCYCurrency
subtotalnumberSubtotal
discountPercentnumberDiscount %
discountAmountnumberDiscount Amount
taxRatenumberTax Rate %
taxAmountnumberRead-only. Tax Amount
shippingCostnumberShipping Cost
totalAmountnumberTotal Amount
paidAmountnumberPaid Amount
balanceDuenumberBalance Due

Payment Information

FieldTypeRequiredNotes
paymentTermsenumYesPayment Terms Valid ids: net15 (Net 15), net21 (Net 21), net30 (Net 30), net60 (Net 60), net90 (Net 90), due_on_receipt (Due on Receipt), prepaid (Prepaid), 2_10_net30 (2/10 Net 30), cod (COD), credit_card (Credit Card), wire_transfer (Wire Transfer), custom (Custom Terms).
customPaymentTermstext (multi-line)Custom Payment Terms
paymentMethodenumPayment Method Valid ids: check (Check), wire (Wire Transfer), ach (ACH), credit_card (Credit Card), paypal (PayPal), other (Other).
paymentDueDatedatePayment Due Date
creditLimitnumberRead-only. Customer Credit Limit
creditAvailablenumberRead-only. Available Credit

Contract & Legal

FieldTypeRequiredNotes
contractNumbertextContract Number
contractStartDatedateContract Start Date
contractEndDatedateContract End Date
termsAndConditionstext (multi-line)Terms & Conditions
specialInstructionstext (multi-line)Special Instructions
internalNotestext (multi-line)Internal Notes

Delivery Schedule

FieldTypeRequiredNotes
requestedDeliveryDatedateRequested Delivery Date
promisedDeliveryDatedatePromised Delivery Date
actualShipDatedateActual Ship Date
actualDeliveryDatedateActual Delivery Date
deliveryMethodenumDelivery Method Valid ids: standard (Standard Shipping), express (Express Shipping), overnight (Overnight), twoday (2-Day Shipping), freight (Freight), white_glove (White Glove Service), pickup (Customer Pickup), digital (Digital Delivery).
shippingCarrierreference → VENShipping Carrier
masterTrackingNumbertextMaster Tracking Number

Warehouse & Inventory

FieldTypeRequiredNotes
warehousereference → WAREHOUSEFulfillment Warehouse
inventoryReservedbooleanInventory Reserved
inventoryReservationDatedatetimeRead-only. Reservation Date
pickListGeneratedbooleanPick List Generated
pickListDatedatetimeRead-only. Pick List Date
packingSlipNumbertextPacking Slip Number
shippingInstructionstext (multi-line)Shipping Instructions

Approval Workflow

FieldTypeRequiredNotes
creditApprovalenumCredit Approval Valid ids: pending (Pending), approved (Approved), rejected (Rejected), not_required (Not Required).
creditApprovedByreference → userRead-only. Credit Approved By
creditApprovalDatedatetimeRead-only. Credit Approval Date
managerApprovalenumManager Approval Valid ids: pending (Pending), approved (Approved), rejected (Rejected), not_required (Not Required).
managerApprovedByreference → userRead-only. Manager Approved By
managerApprovalDatedatetimeRead-only. Manager Approval Date

Order Confirmation

FieldTypeRequiredNotes
customerConfirmationbooleanCustomer Confirmed
customerConfirmationDatedatetimeConfirmation Date
orderAcknowledgementSentbooleanOrder Acknowledgement Sent
acknowledgementSentDatedatetimeRead-only. Acknowledgement Sent Date
signedOrderFormtext (URL)Signed Order Form URL
approvalNotestext (multi-line)Approval Notes

Commission Details

FieldTypeRequiredNotes
commissionRatenumberCommission Rate %
commissionAmountnumberRead-only. Commission Amount
commissionStatusenumCommission Status Valid ids: pending (Pending), approved (Approved), paid (Paid), cancelled (Cancelled).
commissionPaidDatedateCommission Paid Date
commissionPaymentReftextPayment Reference

Attachments

  • orderDocuments: file attachment field.
  • invoiceDocuments: file attachment field.

Additional panels

  • Activity timeline panel attached.

Relationships

  • Lookups: salesRep points at a user; accountManager points at a user; deal points at a DEAL record; customer points at a COM record; currency points at a CURRENCY record; shippingCarrier points at a VEN record; warehouse points at a WAREHOUSE record; creditApprovedBy points at a user; managerApprovedBy points at a user.
  • Related lists: SDEL (format SUB|ENT|SCON|SDEL), AUDIT (format comboKeyEntity).

Creating a Sales Order via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "SCON",
  "level":    500,
  "comboKey": "SUB:|ENT:",
  "name":    "Example name",
  "orderDate":    "2026-01-01",
  "status":    "draft",
  "orderType":    "standard"
}

Listing Sales Orders records

GET /v1/entities/SCON/SUB

See also

sconsales ordersales ordersentitydefinitionreference

Was this article helpful?

← Back to Knowledge Base