GEAR

Manages the full sales order lifecycle across eight states: Draft → Awaiting Payment → Payment Confirmation → Stock Validation → Ready to Ship → In Shipping → Completed (or Cancelled). Product stock is deducted only at stock validation. A versioned delivery note is created automatically at that point and can be revised until the order ships. On completion, customer transaction statistics are updated.

Handles raw material purchasing through a three-step state machine: Pending → Received → Payment Validated. Receiving the order creates raw-material stock movements and increments stock. Payment validation generates an expense finance entry and updates supplier transaction statistics. Voiding at any stage reverses all created stock movements and finance entries.

Tracks raw-material and finished-product stock through signed movement rows. Daily production records use a versioned snapshot pattern: each revision first reverses movements from the previous snapshot, then replays the new quantities. Bill of Materials lines define the raw-material consumption required per product batch. Stock opname (adjustment) creates a corrective movement for the delta between physical and system stock.

Centralizes all income and expense entries. Entries generated by sales payment confirmation and purchase payment validation are system-owned and cannot be manually edited. Corrections are applied through document cancellation or void, which creates linked reversal entries. Manual entries support soft deletion and restoration. Entry categories are also soft-deletable, except for protected system categories.

Read-only dashboards over operational data: sales performance by rep (frequency, revenue, AOV); finance P&L by week, month, or year with PDF export via ReportLab; raw-material and finished-product stock time series; customer loyalty segmentation (New, Loyal, At Risk, Moderate, Inactive); and sales lifecycle funnel metrics.

Recommends product selling prices using BOM cost plus a configurable margin percentage. The base cost is computed from each BOM line's quantity multiplied by the weighted-average unit price of that raw material across finalized purchase orders. A worksheet UI and a JSON API allow managers to review and push recommended prices directly to product records.

Uses a custom Account model with phone number as the login identifier instead of username. Role-based access is enforced through Django groups (Sales, Warehouse, Finance) with Owner represented by is_superuser. Supports account creation, deactivation, restoration, self-service password change, and password reset via email (Anymail/Resend).

Provides two access interfaces: a web chat UI and WhatsApp via Twilio. Both channels share the same service layer and session management, with access scoped to the authenticated user's Django permissions.

Sessions operate in two modes. In default mode, the bot responds to a set of pre-defined commands (stok jadi, create so, create po, daftar so, detail so, stok mentah) with deterministic outputs routed through the same service functions used by the web UI. Each command is permission-checked before execution.

Sending ai switches the session to AI mode, where free-form messages are combined with the session's temporary context and forwarded to Ollama Cloud. The system prompt is assembled per-request from a base ERP context plus module-specific context files for only the modules the user can access, with live DB snapshots injected when the user has the relevant permissions. The conversation history (each exchange of user message and model reply) is stored as temporary context in the session using a bounded data structure to prevent unbounded memory growth. Sending exit or idling for 30 minutes clears the session and returns to default mode.