Stock execution
- Receipts
- Transfers
- Adjustments
- Dat truoc
Khong tim thay ket noi internet
Dang thu ket noi lai
Da xay ra loi!
Dang thu ket noi lai
Chuỗi cung ứng và vận hành
Operational stock control for items, warehouses, movements, reservations, replenishment, counts, and traceability.
| Khu vực | Trang thai | Bằng chứng |
|---|---|---|
| Tồn kho | On hand + reserved | Movement ledger |
| Cycle counts | Variance review | Count evidence |
| Truy xuat | Lot/serial path | Audit chain |
Quy trình chính
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Feature checklist
How this module exchanges business context with the rest of ERPStack.
| Module | Quan hệ |
|---|---|
| Mua hàng | Purchase receipts and supplier response handoffs |
| Bán hàng | Reservations, delivery readiness, and fulfillment handoffs |
| Sản xuất | Material reservation, issue, and output completion |
| Chất lượng | Inspection, disposition, and blocked-stock evidence |
Controls and management visibility expected from a serious ERP module.
AI coverage policy
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L3 ready| Coverage claim | Current AI coverage: Inventory L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 6 registered tools, 5 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (Inventory Replenishment Exception Monitor). |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Buyers can see concrete function groups instead of vague capability claims.
Workflows, users, and connected modules show where the module belongs.
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Public pages link back to app routes so reviewers can compare page claims to product surfaces.