Register administration
- Cashier profiles
- Register codes
- Shift policy
- Device sessions
인터넷 연결을 찾을 수 없습니다
다시 연결을 시도 중
문제가 발생했습니다!
다시 연결을 시도 중
Customer And Commerce
ERP-side control plane for offline-capable POS registers, cashier users, shift policies, sync visibility, and handoffs.
| 영역 | 상태 | 증거 |
|---|---|---|
| Cashiers | Profile managed | Offline login seed |
| 동기화 | Upload + download | Outbox visibility |
| Close packs | Finance handoff | Payment summary |
핵심 워크플로
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 | 관계 |
|---|---|
| 재고 | Stock updates, reservations, and endless-aisle handoff |
| 회계 | Payment, close pack, and settlement evidence |
| CRM | Customer selection, loyalty, and profile handoffs |
| 보안 운영 | Blocked-device and suspicious session incidents |
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: POS Bridge L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 5 registered tools, 6 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (POS Close Pack 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.