wms.inbound¶
Inbound import and processing. It extracts a delivery order with AI into an actual inbound, and serves the transload check-in and completion lists.
6 endpoints - system wms - module gate applies
What this module covers - Transloads and inbound master data.
Endpoints¶
| Method | Path | What it does | Evidence |
|---|---|---|---|
| POST | /wms/inbound/import-delivery-orders/ai-extract |
Extract items from a delivery order file with AI | handler ctcAiApiExtract() · calls api_catalog.php |
| GET/PATCH | /wms/inbound/import-delivery-orders/ai-prompt |
Read or edit the delivery order AI extraction prompt | handler ctcAiApiPrompt() · calls api_catalog.php |
| POST | /wms/inbound/imports/delivery-orders |
Run the actual import of delivery orders | handler wmsInboundWrite() · calls popup.core.js, import-delivery-order-modal.js |
| POST | /wms/inbound/imports/transload |
Receive a transload as inbound | handler wmsInboundWrite() · calls container-edit-modal.js, popup.core.js |
| GET | /wms/inbound/transloads/check-in-list |
List the transloads due in (checked in) | handler wmsInboundQueryHandle() |
| GET | /wms/inbound/transloads/completed |
List the transloads whose inbound is complete | handler wmsInboundQueryHandle() · calls inbound-completed.php |
Topics this module shares with other modules¶
- AI item extraction - this topic is spread across 7 modules and 8 endpoints.
- Delivery order import - this topic is spread across 2 modules and 6 endpoints.
The description is a summary read off the route path, the handler, the tables it reaches and the screens that call it. Nothing is guessed without evidence: where the handler has to be read, it says so. The full evidence is on each endpoint page.