Posh Nosh V2

Appearance

System Overview ​

Purpose ​

Define the high-level purpose and operating principles of the Posh Nosh V2 Production System.

Scope ​

This draft covers the shared operational platform for ordering, product data, production, stock, purchasing, distribution, and essential reporting. Detailed module behaviour is specified separately.

Actors ​

  • Posh Nosh operational staff
  • Production teams
  • Warehouse and purchasing teams
  • Management and authorised administrators
  • SF Media support and development staff

Orders, menus, products, Bills of Materials, stock locations, suppliers, users, roles, and integrations.

Business Rules ​

  • SYS-OVR-001 — The Markdown documents under /docs are the authoritative functional specification.
  • SYS-OVR-002 — The server and central database are authoritative for operational data; offline transactions are not supported.
  • SYS-OVR-003 — Requirements must be classified as 2026 Core, 2027 Phase 2, or Future / Optional.

Workflow ​

Orders create demand, demand drives production and stock requirements, and completed operational activity updates stock, reporting, and relevant integrations.

Validation ​

Cross-module processes must use consistent identifiers and reject incomplete or invalid data before creating downstream operational records.

Permissions ​

Users may only view or perform actions granted through their role and permission set.

Audit & History ​

Material operational and administrative changes must record who changed what and when.

Exceptions & Edge Cases ​

  • An upstream integration is unavailable.
  • An order changes after production has started.
  • Required stock is unavailable or will expire before use.
  • Security and permissions
  • Products and Bills of Materials
  • Orders
  • Production
  • Stock and purchasing
  • Integrations

Open Decisions ​

  • Confirm the final system name and terminology.
  • Confirm the definitive boundary between 2026 Core and deferred functionality.