Record a stock check count attempt
Stock Checks
Record a stock check count attempt
Log a physical count of a product at the stock check’s location. The system compares the supplied physical count against its expected (system) count for the matching product group and records whether the attempt succeeded or failed. Each product group can have up to two attempts; if both attempts fail the group must be resolved before the stock check can move on.
POST
Record a stock check count attempt
Request Structure
Key Fields
| Field | Required | Description |
|---|---|---|
product_id | Yes | ID of the product being counted |
physical_count | Yes | Quantity actually counted in the location |
batch | No | Batch identifier when the account uses batch tracking |
sell_by_date | No | Sell-by date when the account uses sell-by tracking |
best_before_date | No | Best-before date when the account uses best-before tracking |
Behavior
- The product, batch and date fields together identify a stock group within the stock check. Repeat counts for the same group accumulate as numbered attempts.
- The attempt is
successwhenphysical_countmatches the system count for that group, otherwisefailure. - A third attempt for the same group is rejected with 422; failed groups must be resolved via
POST /api/stock_checks/resolve. - The stock check and its associated task must still be active. Completed, cancelled or non-pending checks return 422.
Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Path Parameters
The unique identifier of the stock check
Body
application/json

