> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joinluminous.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recount a bin/lot row (PickFlow)

> Set one stock row's on-hand to an absolute counted quantity (recorded as a manual recount adjustment). Send `expected_quantity` — the on-hand the operator was shown — and the recount is refused with `409` if stock moved in the meantime (a pick or receipt), rather than overwriting a quantity nobody looked at.

Supports the optional `Idempotency-Key` header: a retry with the same key replays the original response (with `Idempotent-Replay: true`) instead of posting a second adjustment.



## OpenAPI

````yaml /api-reference/build.yaml post /pickflow/inventory/recount
openapi: 3.0.0
info:
  title: Luminous API
  version: 1.0.0
  description: API documentation for Luminous
servers:
  - url: https://{companyName}.api.joinluminous.com/external/api/v1
    variables:
      companyName:
        default: companyName
        description: Your company-specific subdomain
security: []
tags:
  - name: Products
    description: Get and manage products
  - name: Pricing
    description: Manage price schedules, levels, and customizations
  - name: BOMs
    description: Manage Bills of Materials (BOMs)
  - name: Labels
    description: Label rendering via Labelary ZPL service
  - name: Companies
    description: Manage business accounts and their associated data
  - name: Contacts
    description: Manage contact information for individuals
  - name: Suppliers
    description: Manage suppliers (factories) — vendors used on purchase orders
  - name: Supplier SKUs
    description: Manage per-supplier SKU and unit-cost overrides for products
  - name: Locations
    description: Manage warehouses and locations
  - name: Inventory
    description: Get and adjust product stock levels
  - name: Lots
    description: Create, update, and delete product lots (batches)
  - name: Transfer Orders
    description: Manage transfer orders
  - name: Fulfillment Orders
    description: Manage fulfillment orders and picklists
  - name: Freight
    description: >-
      Freightview LTL freight — quotes, booking and documents for fulfillment
      orders
  - name: Fulfillment Priority Lists
    description: Configure fulfillment routing priority lists
  - name: Purchase Orders
    description: Get and modify purchase orders
  - name: Supplier Portal
    description: >-
      Read a supplier's response to a purchase order and control the one-click
      portal link
  - name: Receiving Reports
    description: Manage receiving reports
  - name: Payment Obligations
    description: Manage payment obligations for purchase orders
  - name: Sales Orders
    description: Manage sales orders and sales order shipments
  - name: Purgatory
    description: >-
      Inspect and resolve non-posted sales orders in the purgatory staging
      workflow
  - name: PickFlow Warehouse
    description: >-
      Warehouse-floor lookups for PickFlow — barcode resolution, bin and product
      stock, bin search, and receivables
  - name: PickFlow Shipping
    description: >-
      Provider-agnostic shipping rates, services, packages, and label purchase
      for PickFlow
  - name: Cycle Counts
    description: >-
      Create, drive, and post PickFlow cycle counts — batches, per-warehouse
      sessions, and CSV import/export
  - name: Print Stations
    description: List paired print stations and enqueue print jobs to them
  - name: Invoices
    description: Get and manage invoices
  - name: Work Orders
    description: >-
      Manage work orders — production lifecycle, steps, materials, links,
      shipments, and comments
  - name: Production Batches
    description: Group and manage work orders as production batches
  - name: Bills
    description: >-
      Accounts payable bill management, payments, attachments, allocations, and
      variance
  - name: Prepayments
    description: Manage vendor prepayments and applications
  - name: Vendor Credits
    description: Manage vendor credits and applications
  - name: Vendor Returns
    description: Manage vendor returns and credit generation
  - name: Customer Returns
    description: Manage customer returns (sales returns), receiving, and restock behavior
  - name: Stock Snapshot
    description: Point-in-time stock snapshots with export support
  - name: Consumption
    description: Consumption reports and exports
  - name: Inventory Aging
    description: Cost-layer-based inventory aging reports
  - name: Bills Reports
    description: Accounts payable bills aging reports
  - name: Forecast
    description: Materialized forecast data
  - name: Reports
    description: Close the books, inventory discrepancy, transaction COGS, and EDI reports
  - name: Tags
    description: Add/remove tags across various resources
  - name: Custom Fields
    description: Get and set custom fields across various resources
  - name: Currency
    description: Currency configuration, exchange rates, and conversion
  - name: Drive
    description: >
      Browse, upload, tag and manage files in your Luminous Drive. An API token
      sees the shared

      drive only, never My Files or restricted folders and files. Every write
      and download made

      through the API is recorded in the file's activity log (`GET
      /file-cabinet/files/{id}/activity`)

      with `actor_kind: api_token`.
  - name: Integration Mappings
    description: Manage integration mappings for external systems
  - name: Integration Field Mappings
    description: Manage field-level mappings between Luminous and external systems
  - name: Automations
    description: Create, test, and inspect automation rules and their runs
paths:
  /pickflow/inventory/recount:
    post:
      tags:
        - Inventory
      summary: Recount a bin/lot row (PickFlow)
      description: >-
        Set one stock row's on-hand to an absolute counted quantity (recorded as
        a manual recount adjustment). Send `expected_quantity` — the on-hand the
        operator was shown — and the recount is refused with `409` if stock
        moved in the meantime (a pick or receipt), rather than overwriting a
        quantity nobody looked at.


        Supports the optional `Idempotency-Key` header: a retry with the same
        key replays the original response (with `Idempotent-Replay: true`)
        instead of posting a second adjustment.
      operationId: recountPickflowInventory
      parameters:
        - in: header
          name: Idempotency-Key
          required: false
          schema:
            type: string
          description: >-
            Optional opt-in idempotency token. A retry carrying the same key
            replays the stored response; reusing a key for a different request
            returns `409`.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - rfq_stock_location_id
                - quantity
              properties:
                rfq_stock_location_id:
                  type: integer
                  description: Stock row to recount (from the bin/product stock endpoints).
                quantity:
                  type: number
                  minimum: 0
                  description: The counted on-hand quantity.
                expected_quantity:
                  type: number
                  nullable: true
                  description: >-
                    On-hand the operator saw before counting. Enables the
                    stale-count check.
                remarks:
                  type: string
                  maxLength: 1000
                  nullable: true
      responses:
        '200':
          description: Recount applied
          content:
            application/json:
              schema:
                type: object
                properties:
                  previous_quantity:
                    type: number
                  quantity:
                    type: number
                    description: New on-hand.
                  delta:
                    type: number
                    description: quantity − previous_quantity.
                  item:
                    type: object
                    description: >-
                      One on-hand row — a product in a specific bin (and lot,
                      for lot-tracked products). `rfq_stock_location_id` is the
                      id that `POST /pickflow/inventory/transfers` and `POST
                      /pickflow/inventory/recount` target.
                    properties:
                      rfq_stock_location_id:
                        type: integer
                        description: Stock-row ID (product × warehouse × bin × lot).
                      product_id:
                        type: integer
                      sku:
                        type: string
                      name:
                        type: string
                        description: Product name.
                      image_url:
                        type: string
                        nullable: true
                      lot_tracked:
                        type: boolean
                      lot_id:
                        type: integer
                        nullable: true
                      lot_number:
                        type: string
                        nullable: true
                      expiry_date:
                        type: string
                        format: date
                        nullable: true
                      location:
                        allOf:
                          - type: object
                            description: A bin (child location) inside a warehouse.
                            properties:
                              id:
                                type: integer
                                description: Bin location ID.
                              name:
                                type: string
                                description: Bin name. Only unique within its warehouse.
                              warehouse_id:
                                type: integer
                                description: ID of the warehouse the bin belongs to.
                              warehouse_name:
                                type: string
                                nullable: true
                                description: Name of the warehouse the bin belongs to.
                        nullable: true
                      onhand_quantity:
                        type: number
                      reserved_quantity:
                        type: number
        '401':
          description: Authentication credentials were missing or invalid
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    example: Unauthorized
                  message:
                    type: string
                    example: Authentication credentials are missing or invalid
                  status_code:
                    type: integer
                    example: 401
        '404':
          description: Stock location not found.
        '409':
          description: >-
            On-hand changed since it was displayed (`expected_quantity` no
            longer matches), or an idempotency-key conflict.
        '422':
          description: Validation error, or the adjustment could not be applied
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                  errors:
                    type: object
                    additionalProperties:
                      type: array
                      items:
                        type: string
      security:
        - BearerAuth: []
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        Authenticate using a bearer token. To create a token, navigate to
        /settings/api-tokens and click Create API Token.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.