ForgeFlow-ERP/PRODUCT.md
2026-06-12 16:29:05 +08:00

2.4 KiB

Product

Register

product

Users

ForgeFlow ERP serves a roughly 50-person hardware manufacturing company. The primary users are managers, sales staff, planners, buyers, warehouse operators, workshop supervisors, production staff, finance users, equipment administrators, and system administrators. They use the system in office and shop-floor contexts to keep orders, materials, production, inventory, delivery, returns, and finance aligned.

Product Purpose

The product exists to make the full manufacturing loop visible and controllable: sales orders drive material requirements, procurement, warehouse batches, work orders, operation reporting, finished goods, delivery, returns, and cost reconciliation. Success means users can trace every important business fact back to orders, batches, operations, documents, and responsible roles without hunting through isolated screens.

Brand Personality

Modern, clear, and easy to adopt. The interface should feel calm, precise, and work-focused: a mature ERP that helps people finish high-stakes daily tasks without visual noise. It can carry a light industrial character where it supports manufacturing context, but the default posture is clean operational clarity rather than heavy factory theming.

Anti-references

Do not make the product look obviously AI-generated. Avoid decorative SaaS landing-page tropes, oversized hero sections inside work screens, generic card grids, glassmorphism, gratuitous gradients, fake depth, excessive roundness, and ornamental motion. Avoid a default Element Plus-style admin surface that feels assembled from common templates. Avoid dark big-screen dashboard aesthetics for routine operational pages. Avoid paper-like document styling outside formal business documents and archived forms.

Design Principles

  1. Make the next operational action obvious.
  2. Treat traceability as a first-class interface pattern.
  3. Preserve density where users compare records, but keep hierarchy calm.
  4. Use one consistent component vocabulary across modules.
  5. Let document-like visuals appear only when the user is handling a formal business document.

Accessibility & Inclusion

Target WCAG AA for text contrast and interaction states. Support keyboard navigation for core workflows, clear focus states, readable Chinese text on ordinary office and workshop displays, reduced-motion preferences, and status communication that does not rely on color alone.