Key takeaway: traditional ERP charges for every change because the change touches rigid, shared module code. SimpleGrid models your operation as an SG Schema, so a change is a configuration edit, not a software project, which is why it takes minutes instead of months.
In most ERPs, changing a business rule is a software project. In SimpleGrid, it is a row in a table.
That is not marketing language. It is literally how the system works. Here is the architecture behind it.
Two levels: knowledge and operations
Every SimpleGrid deployment has two distinct layers in its database.
The Knowledge Level defines what the business looks like. What types of things exist (Sales Orders, Purchase Orders, Job Orders). What states each type can be in (Draft, Approved, In Production, Dispatched). What transitions are allowed between states. What rules must hold. What happens automatically when an event occurs.
The Operational Level holds the actual data. The real Sales Order SO-4521. The real Purchase Order PO-0089. Their current states, their field values, their event histories.
The Knowledge Level is the blueprint. The Operational Level is the factory floor. The blueprint rarely changes. The floor changes every minute.
This separation is the key to everything.
Three types of rules, three tables
Every business rule in a manufacturing operation falls into one of three categories. Each lives in its own table.
Transition Guards. Rules that must be true BEFORE a state change happens. Stored in the invariants table.
Example: "received_qty cannot exceed ordered_qty." If a warehouse manager tries to receive 600 units against a PO for 500, the system checks this rule before committing anything. The action is rejected. No override. No workaround.
Approval Rules. Conditional permission escalations. Stored in the approval_rules table.
Example: "If PO amount exceeds $10,000, require founder approval." The planner creates a PO for $12,000. The system automatically routes it to the founder for approval instead of letting the planner approve it directly.
Role Permissions. Who can do what. Stored in the transitions table.
Example: "Only warehouse supervisors can receive material." "Only the founder can skip a production stage." Each state transition specifies which roles can execute it.
What a change looks like
Your founder calls and says: "Starting next week, we need QC approval before any dispatch over $5,000."
In a traditional ERP, this goes through a scoping call with the vendor. A change order is written. A developer modifies the dispatch module. Testing. Staging. Deployment. 3 to 6 weeks. $8,000 to $20,000. A change order is written. A developer modifies the dispatch module. Testing. Staging. Deployment. 3 to 6 weeks. $8,000 to $20,000.
In SimpleGrid, we open the approval_rules table and add one row:
Done. The SG Engine reads this rule immediately. The next dispatch over $5,000 automatically routes to the QC head for approval. No code change. No deployment. No downtime.
Real examples from live deployments
Furniture manufacturer: "We need founder approval for the first PO to any new vendor." One row in approval_rules: if vendor is new (first PO), require founder approval. All subsequent POs to the same vendor go through normal channels.
Apparel contract manufacturer: "Dual size systems per brand. Brand A uses S/M/L. Brand B uses 38/40/42." One configuration per brand in the knowledge tables. System validates size entries against the brand's registered system automatically.
Pharma distributor: "Supplier offers have no formal expiry. Rank by recency." One configuration in the offer_rules table. No expiry field. Offers ranked by timestamp.
Each of these would be a multi-week customization project in a conventional ERP. In SimpleGrid, each is a row in a table.
Why this matters over time
After 6 months of operation, a typical SimpleGrid deployment has 40 to 60 invariants, 15 to 20 approval rules, and 30 to 40 permission configurations. All in tables. All readable. All changeable without a developer.
A traditional ERP with the same business logic has it scattered across 20 modules, 50 source files, and 3 consultant engagements worth of custom code. Nobody has a complete picture of all the rules. Changing one risks breaking another.
The Knowledge Level gives you something code never will: a single place to see every rule your business enforces. Your operations head can read it. Your founder can audit it. Your new planner can understand the rules on day one.
SimpleGrid stores every business rule in a table. Change a rule in minutes. See every rule in one place. No developer needed.