POST /wms/inventory/lots/(?P\d+)/adjust¶
What it does¶
#^/wms/inventory/lots/(?P<id>\d+)/adjust$# accepts POST and is declared in app/systems/WMS/inventory/api_routes.php:941 as a regex pattern.
The route handler delegates to wmsInventoryWrite(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
wmsInventoryWrite()—app/systems/WMS/inventory/api_routes.php:20 - ↳
wmsInventoryPostHandle()—app/systems/WMS/inventory/post_handler.php:4 - ↳
inventory_post_handle()—app/systems/OMS/inbound-order/inventory_post_helper.php:2
Who calls it¶
No literal caller path was found in frontend/, public/ or new-system/.
The endpoint may be called through a constructed path, a helper wrapper, or only by
an external client. Treat the route table and owner function as the authority.
Input¶
| Where | Key |
|---|---|
path |
id |
Request bodies must not use TYPE, ACTION or USERNAME as contract fields.
Output¶
The response is produced by a shared helper, so the key set is not visible at the route. Read the owner function to confirm the shape before writing a client.
SQL executed¶
UPDATE T_INVENTORY_LOT SET $setClauses WHERE ID = ? AND CLIENT_ID = ? AND DELETED_AT IS NULL
Data¶
No table reference is visible in the owner function body.
Access¶
- module-gated on
wms.inventory, so tenant module access applies
Validation and failure messages¶
- Remaining quantity and net weight are both required for an inventory count check.
- Inventory lot status is controlled by unload and source-consumption lifecycle events.
- Warehouse location is required when moving an active inventory lot.
These strings come from the owner function and are the messages a client can receive. They are also the cheapest way to tell a rejected request from a broken one.