Customer lifecycle
- Leads
- 会计
- Opportunities
- Activities
找不到互联网连接
正在尝试重新连接
出现错误!
正在尝试重新连接
Customer And Commerce
Customer lifecycle, opportunities, quotes, sales orders, delivery handoffs, service cases, and reports.
| 区域 | 状态 | 证据 |
|---|---|---|
| Opportunities | Stage tracked | Activity history |
| 报价 | Approval aware | Workflow evidence |
| Cases | Service queue | Customer timeline |
核心流程
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 | 关系 |
|---|---|
| 库存 | Availability, reservations, and delivery commitments |
| 会计 | Invoice and revenue handoff after order execution |
| CRM Portal | Customer-facing case and account touchpoints |
| BI | Pipeline, forecast, and customer trend dashboards |
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 coverage ready| Coverage claim | Current AI coverage: Sales / Order Management L2/L2 ready; CRM L2/L2 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 5 registered tools, 5 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (Sales Quote Follow-up 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.