Use this spec to review and suggest additional fields, rules, or report columns. When building the application, this will be replaced with the actual screen.
Information to collect
Data fields / attributes to capture on this screen.
Functionality
Features and actions available on this screen.
Business rules
Validations, defaults, and constraints.
Activities / workflow
Steps, approvals, and state transitions.
Report columns (suggest additions)
Columns to show in related reports. Experts can suggest more.
Spec to be defined
This screen is in the menu hierarchy; detailed spec (information, functionality, rules, activities) can be added here. Suggest what should be captured and how it should behave.
Application Overview
Executive dashboard (sample data)
Representative KPIs and charts the built application will provide.
Revenue (MTD)
₹ 42.8L
+12% vs last month
Open orders
248
₹ 18.2L value
Stock value
₹ 31.5L
12 items below reorder
AR overdue
₹ 4.1L
23 invoices
Revenue trend (sample)
Orders by status (sample)
Inventory by warehouse (sample)
Cash & receivables (sample)
Why Palmyra ERP — How we differ from leading ERPs
Built for the modern stack and multi-tenant SaaS, with the depth of legacy ERPs and the agility of a single codebase.
vs Oracle (Oracle Cloud ERP / NetSuite)
- Single codebase, one stack — No Fusion + NetSuite + legacy splits; one product for finance, manufacturing, inventory, and industry variants.
- Configuration over customisation — Workflows, COA, tax, and industry behaviour live in the database; fewer code forks and upgrades.
- Modern API-first — REST, multi-tenant from day one, and optional real-time (e.g. SignalR) for tasks and support.
- Lower TCO for mid-market — Subscription without the Oracle enterprise premium; same ledger and compliance rigour.
vs SAP (S/4HANA, ECC, Business One)
- SAP-style manufacturing without the footprint — BOM, routing, work orders, MRP/MPS, capacity, and plant maintenance in one product, not separate modules.
- Deploy anywhere — Cloud or on-prem; no lock-in to SAP infrastructure or hyperscaler.
- Faster implementation — Industry templates and configuration-driven behaviour reduce customisation and go-live time.
- Unified inventory and finance — Double-entry stock ledger and valuation (FIFO/LIFO/Avg) aligned with GL; no reconciliation gaps.
vs Odoo / other mid-market ERPs
- Enterprise-grade finance — Multi-ledger, proper period close, inter-company, consolidation, and regulatory reporting (e-invoice, statutory) built in.
- Manufacturing depth — MPS, capacity planning, machine scheduling, maintenance (CMMS), and demand forecasting, not just basic MRP.
- Stronger compliance and audit — Document sequencing, workflow approvals, and audit trails designed for regulated industries.
- One product, many industries — Apparel, retail, EBO, agriculture, import/export via configuration and industry templates, not separate editions.
Prototype and menu hierarchy
This prototype defines the exact menu hierarchy and, for each screen, the information to collect, functionality, business rules, activities, and (where relevant) report columns. It is not a working application—it is a specification for investors and domain experts to review and extend before development.
- Masters — All foundational data: products, customers, vendors, COA, warehouses, tax, currency, HR, manufacturing, logistics.
- Transactions — Sales, procurement, inventory, finance, manufacturing, and logistics transactions with workflows.
- Configuration — Organization, workflows, schedules, industry/features, sequences, reports, print templates.
- Modules — Module-level overview and key screens for Finance, Inventory, Manufacturing, Sales, Procurement, HR, CRM, POS, Quality, Reporting, Task, Support.
Select a menu item from the sidebar to see the spec for that screen. When the ERP is built, this prototype will be replaced with the actual application.