The lot is resolved to the SKUs received under it during goods-in; Released and Conditional releases are relayed to the warehouse so the quality-held items become eligible for putaway (a Conditional release is tracked via its conditionNote). Rejected decisions are captured and acknowledged, but the warehouse-side blocked-stock transition is pending, so they are not yet applied in the warehouse (status CapturedNotRelayed). Each request is stored as one immutable audit record; re-sending the same decision is allowed.
If you want to emulate, please enter TenantId.
Push payload for POST /openapi/v1/QualityRelease. Reports the caller's quality decision for a lot held in quality control during goods-in; all quality-held items of the lot are handled together.
Lot number the quality decision applies to.
Quality decision: Released, Conditional or Rejected (English name, case-insensitive). Released and Conditional move the lot from quality hold to putaway; a Conditional release is tracked via its conditionNote. Rejected is captured for blocked stock (disposal) — the warehouse-side blocked-stock transition is pending, so Rejected decisions are stored and acknowledged but not yet applied in the warehouse.
Reason/note of a conditional release. Required when releaseType is Conditional.
User who approved the quality decision (e.g. SAP user code).
Approval date, ISO 8601.
Caller-side quality decision reference (e.g. "QC-2026-0891").
Optional; disambiguates when the tenant has more than one OpenApi integration.