DemandFlow Support Centre

INVCOUNT: Stock Count

A record of a physical stock count for one component at one site, grouped by count batch for reconciliation and adjustment approval.

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

Entity properties

Property	Value
Entity code	`INVCOUNT`
Display name	Stock Count
Plural	Stock Counts
Level	55000

Use cases

Each record represents a single line in a stocktake: one component at one site. Records are grouped by countRef (batch reference) so a full site count creates multiple INVCOUNT records sharing the same countRef. Three-column layout: left (30%) has count identity (name/auto-ref, countRef batch, site, status, counted by, count date), middle (30%) has what was counted (component, INVSTOCK link, system qty at time of count, counted qty, variance auto-calculated), right (40%) has resolution (adjustment approved checkbox, approved by, adjustment date, adjustment notes).

Fields

Count Details

Field	Type	Required	Notes
`name`	text	Yes	Count Reference.
`countRef`	text		Shared reference grouping items counted in the same stocktake session
`siteId`	reference → `SITE`	Yes	Site.
`status`	enum	Yes	Valid ids: `pending` (Pending), `counted` (Counted), `reviewed` (Reviewed), `adjusted` (Adjusted), `noAdjustment` (No Adjustment Needed).
`countedBy`	reference → user		Counted By.
`countDate`	date		Count Date.

Count Results

Field	Type	Required	Notes
`componentId`	reference → `COMP`	Yes	Component.
`stockId`	reference → `INVSTOCK`		The INVSTOCK record being counted
`systemQty`	number		Qty on hand in the system at time of count
`countedQty`	number	Yes	Counted Qty.
`variance`	number		Counted minus system (negative = shortage, positive = surplus)
`binLocation`	text		Bin / Location.

Adjustment

Field	Type	Notes
`adjustmentApproved`	boolean	Adjustment Approved.
`approvedBy`	reference → user	Approved By.
`adjustmentDate`	date	Adjustment Date.
`reason`	enum	Valid ids: `accurate` (Count Matches System), `damaged` (Damaged / Unusable), `misplaced` (Misplaced / Wrong Location), `theft` (Suspected Theft / Loss), `dataEntry` (Data Entry Error), `unrecorded` (Unrecorded Movement), `other` (Other).
`notes`	text (multi-line)	Notes.

Relationships

Lookups: siteId points at a SITE record; componentId points at a COMP record; stockId points at a INVSTOCK record; countedBy points at a user; approvedBy points at a user.

Creating a Stock Count via the API

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

{
  "entity":   "INVCOUNT",
  "level":    55000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "siteId": "",
  "status": "pending",
  "componentId": ""
}

Listing Stock Counts

# All records in your tenant
GET /v1/entities/INVCOUNT/SUB:<your-sub-id>

DemandFlow Support Centre

INVCOUNT: Stock Count

INVCOUNT: Stock Count

Entity properties

Use cases

Fields

Relationships

Creating a Stock Count via the API

Listing Stock Counts

See also

Was this article helpful?