Connected business operations
One workspace.
Seven operating modules.
Module foundations for inventory, selling, procurement, people, manufacturing, projects and customer support. These screens describe the workflows planned for the platform; live write operations must be enabled and verified module by module before production use.
▦
Inventory & Stock
Serial and batch/lot tracking, multiple warehouses, transfers, stock counts and reconciliation, FIFO or moving-average valuation, expiry awareness and reorder suggestions.
Core recordsItems · Warehouses · Lots · Movements · Counts
Control ruleAdjustments require a reason and audit event
Schema foundation
♙
Selling & CRM
Lead capture, pipeline stages, next follow-ups, quotations, sales orders and customer relationship history.
Core recordsLeads · Quotes · Quote lines · Sales orders
Control ruleQuote acceptance and order confirmation are explicit
Schema foundation
▣
Buying & Procurement
Material requests, supplier records, purchase orders, goods receipts, supplier invoices and three-way matching of PO, receipt and invoice.
Core recordsRequests · Suppliers · POs · Receipts · Bills
Control ruleInvoice mismatches go to exception review
Schema foundation
♧
Human Resources & Payroll
Employee records, attendance, leave, expense claims, controlled payroll runs and payslip records.
Core recordsEmployees · Attendance · Leave · Claims · Payroll
Control rulePayroll approval is separate from payroll preparation
Schema foundation · calculations require validation
⚙
Manufacturing (MRP)
Versioned bills of materials, nested components, work orders, job cards, production scheduling and work-centre capacity planning.
Core recordsBOMs · Components · Work orders · Job cards
Control ruleMaterial issue and finished-goods receipt must reconcile
Schema foundation · planning engine pending
◷
Projects & Tasks
Projects, task ownership, dependency links, timesheets, approved hours, project cost and time-based billing.
Core recordsProjects · Tasks · Dependencies · Timesheets
Control ruleOnly approved billable time can be invoiced
Schema foundation
✉
Support & Helpdesk
Ticket lifecycle, assignment, priority, response/resolution targets, SLA due dates, internal notes and a publishable knowledge base.
Core recordsTickets · Messages · SLA fields · Knowledge articles
Control ruleInternal notes stay separate from customer-visible replies
Schema foundation
Implementation status
Transparent readinessDatabase structures are being added first. This does not yet mean each module has complete forms, authenticated API endpoints, approval workflows, reporting, or end-to-end tests. Existing finance, invoices and customer workflows remain separate and are not replaced by this extension.