> ## 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. # Adjust inventory stock > Adjust on-hand stock for any given product in a given location. Either the product `sku` or `product_id` is required to identify the product. Up to 3000 entries may be submitted per request. Requests with more than 500 entries are processed asynchronously: the adjustment header is created and returned immediately, while the individual stock changes are applied in the background shortly after. ## OpenAPI ````yaml /api-reference/build.yaml post /inventory/adjustments 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: Purchase Orders description: Get and modify purchase orders - 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 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: Integration Mappings description: Manage integration mappings for external systems - name: Integration Field Mappings description: Manage field-level mappings between Luminous and external systems paths: /inventory/adjustments: post: tags: - Inventory summary: Adjust inventory stock description: >- Adjust on-hand stock for any given product in a given location. Either the product `sku` or `product_id` is required to identify the product. Up to 3000 entries may be submitted per request. Requests with more than 500 entries are processed asynchronously: the adjustment header is created and returned immediately, while the individual stock changes are applied in the background shortly after. operationId: createInventoryAdjustment requestBody: required: true content: application/json: schema: type: object required: - adjustment_entries properties: remarks: type: string description: Optional remarks for the adjustment adjustment_entries: type: array maxItems: 3000 description: >- One entry per stock adjustment. A maximum of 3000 entries may be submitted in a single request (exceeding this returns a 422). Payloads larger than 500 entries are posted asynchronously in the background: the response returns the created adjustment header immediately, but the individual stock changes finish posting shortly afterward rather than within the request. items: type: object required: - warehouse_id - location_id - qty_onhand properties: warehouse_id: type: integer description: ID of the warehouse location_id: type: integer description: ID of the location within the warehouse product_id: type: integer description: ID of the product, required if sku is not provided sku: type: string description: >- SKU of the product, required if product_id is not provided qty_onhand: type: integer description: >- Additive change to on-hand quantity (a delta, not an absolute target): a positive value adds to current on-hand, a negative value removes. There is no single-call "set on-hand to X" mode. lot_id: type: integer nullable: true description: >- ID of the product lot to adjust. Provide either `lot_id` or `lot_number`, not both. Required when the product has lot tracking enabled. lot_number: type: string nullable: true description: >- Lot number to adjust (resolved to a lot for the product). Use instead of `lot_id`. Required when the product has lot tracking enabled. lot_name: type: string nullable: true description: Alias for `lot_number`. create_lot: type: boolean description: >- Opt-in lot auto-create. When `true` and the given `lot_number` does not yet exist for the product, the lot is created (metadata only, seeded from the fields below) before the stock is posted. Defaults to `false`. production_date: type: string format: date nullable: true description: >- Production date used to seed a lot created via `create_lot`. Ignored when the lot already exists. expiry_date: type: string format: date nullable: true description: >- Expiry date used to seed a lot created via `create_lot`. Ignored when the lot already exists. manufacturer_code: type: string nullable: true description: >- Manufacturer code used to seed a lot created via `create_lot`. Ignored when the lot already exists. responses: '200': description: Successful response content: application/json: schema: type: object properties: id: type: integer description: ID of the created adjustment remarks: type: string description: Remarks for the adjustment posted_by: type: integer description: ID of the user who posted the adjustment created_at: type: string format: date-time description: Timestamp of when the adjustment was created updated_at: type: string format: date-time description: Timestamp of when the adjustment was last updated '422': description: Validation error 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. ````