ข้ามไปยังเนื้อหา
ERPStack

ซัพพลายเชนและการดำเนินงาน

สินค้าคงคลัง

Operational stock control for items, warehouses, movements, reservations, replenishment, counts, and traceability.

ใช้งานแล้ว Evidence-first module page
Primary users
Warehouse manager Inventory controller Store operator Procurement team
/app/inventory
App-derived visual
Inventory execution console
Open app route
Stock state
Tenant scoped
Transfers
Evidence logged
ข้อยกเว้น
SIEM visible
พื้นที่ สถานะ หลักฐาน
สต็อก On hand + reserved Movement ledger
Cycle counts Variance review Count evidence
การติดตามย้อนกลับ Lot/serial path Audit chain

เวิร์กโฟลว์หลัก

What the module helps operators complete.

Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.

Step 1
Receive, transfer, and adjust stock
Step 2
Reserve stock for orders and production
Step 3
Run cycle counts and variance review
Step 4
Trace lots, serials, and stock movement evidence

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Stock execution

  • Receipts
  • Transfers
  • Adjustments
  • การจอง

Warehouse control

  • Warehouse master
  • Cycle counts
  • Barcode tasks
  • เติมสินค้า

การติดตามย้อนกลับ

  • Lot and serial tracking
  • Movement evidence
  • Export visibility
  • Exception review

Connected module map

How this module exchanges business context with the rest of ERPStack.

Module ความสัมพันธ์
จัดซื้อ Purchase receipts and supplier response handoffs
ขาย Reservations, delivery readiness, and fulfillment handoffs
การผลิต Material reservation, issue, and output completion
คุณภาพ Inspection, disposition, and blocked-stock evidence

Governance and reporting

Controls and management visibility expected from a serious ERP module.

การกำกับดูแล
  • Adjustment authorization
  • Suspicious-transfer SIEM events
  • Audit history
  • ส่งออกหลักฐาน
รายงาน
  • Stock on hand
  • Movement history
  • Aging
  • เติมสินค้า

AI coverage policy

What ERPStack can honestly claim for this module today.

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

Module pages explain value, workflow, control, and proof in one place.

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.

Feature clarity

Buyers can see concrete function groups instead of vague capability claims.

Operational fit

Workflows, users, and connected modules show where the module belongs.

Governance proof

RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.

Review path

Public pages link back to app routes so reviewers can compare page claims to product surfaces.