v1
Materials
Materials

Allocate Stock To Project

Claim shop stock for a project - the financial event, split by lot.

ONE MIRRORED BOM ROW PER LOT CONSUMED, never one row for the whole claim. A part restocked three times is three lots at three prices under three INY- POs. Collapsing 12 units into a single row at an averaged price destroys the only thing that makes a claim auditable: which purchase order the metal on this job actually came from, and what it truly cost. That trace runs from a finished weld back to a dock inspection and an MTR, and an average has no MTR behind it.

So each row carries its OWN lot's po_number and unit_price, and the project materials table groups them by PO exactly like a vendor purchase - which is what makes "click through to the receiving log" work with no new screen.

FIFO, oldest lot first: the shop consumes what it bought first, and the cost it books is the cost that lot was bought at.

post/api/v1/materials/inventory/allocate

Request

  • Base URL: https://api.jeevyfabrication.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.jeevyfabrication.com/api/v1/materials/inventory/allocate
  • Auth: none declared

Request body

material_item_idinteger required
project_idinteger required
material_list_idinteger nullable
qtynumber required
task_idinteger nullable

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.