Key takeaway
Judge by change frequency, impact, versioning needs, and verification cost. Thresholds, lists, templates, and time windows fit configuration. Core calculations, cross-system invariants, and accounting rules belong in controlled releases. Configuration needs versions, approval, effective dates, and regression checks.

Suppose the following happens. Operations wants to lower a discount threshold from 299 to 259. They file a development request and get a two-week slot. By the time it ships, the campaign has peaked. Next time, the product manager proposes making every business rule configurable so operations can change things without waiting.
Six months later the settings area holds more than eighty items. Someone mistypes a decimal in an approval limit, someone sets a notification window to zero minutes, someone edits a formula nobody understands. Every misconfiguration sends development into the logs to restore data. Configuration did not reduce communication; it moved risk from code to an admin screen.
"It changes often" is not enough
Judge a rule on at least four dimensions:
Change frequency. Several times a month, or once a year? A yearly rule with a settings page may cost more to maintain than a code change.
Business impact. Does the change affect display wording, or money, stock, permissions, and external commitments? The heavier the impact, the more it needs approval and verification rather than anyone editing at will.
Versioning need. Will anyone need to know which rule applied last month? If so, the rule needs versions and effective dates whether it lives in code or configuration.
Verification cost. After the change, can the business verify the result themselves? If yes, configuration genuinely saves time. If not, configuration only shifts testing to someone without testing tools.
Only when all four are light does a rule fit ordinary configuration. If any is heavy, it belongs in a controlled release or approval flow.
Four kinds that fit configuration
Thresholds and tolerances. Discount thresholds, free-shipping amounts, stock alerts, reconciliation tolerances. They change often, their effects are calculable, and the business can verify them.
Lists and calendars. Holidays, suspended regions, allowlists, blocklists, bookable time slots. The maintainer is clear and the change involves no logic.
Templates and wording. Notification templates, optional contract clauses, page messages. They need versions and previews but do not change calculations.
Time limits and reminders. Approval reminders, notification lead time, automatic closure. Configuration should bound them to sensible ranges, such as no negative or zero values.
What these share: single meaning, visible result, and a change that can be reversed.
What should not become freely editable settings
Core calculations. Commission, tax, depreciation, performance scores, interest. One misplaced parenthesis affects money. Parameters may be configurable, but changes need confirmation from finance or the business owner and full testing.
Cross-system invariants. Order total equals line sum, stock cannot go negative, receipts cannot exceed receivables. These are correctness rules, not business preferences, and must not become toggles.
Rules with accounting or filing meaning. Revenue recognition conditions, invoice header rules, tax applicability. These changes need professional confirmation and should not be edited by operations alone. This article does not decide any specific tax treatment; it states only that changes need professional sign-off.
Permissions and approval chains. Who approves and how many levels involve separation of duties. They can be configurable, but only with approval and audit, not on the same page as display text.
Configuration items need versions, approval, and effective dates
A configuration item needs at least: name, business meaning, current value, allowed range, effective date, modifier, approver, version history, and rollback method.
Overwriting the old value is the most common design flaw. Lower the threshold from 299 to 259 today, and next month nobody can answer which threshold applied to last month's campaign. Keep versions and effective intervals so reports match the rule in force when the business happened.
High-risk configuration needs approval. The approver is not a developer but the business role accountable for the consequence. What they see is not only "299 → 259" but the impact: which running campaigns, quotes, or orders change overnight.
The settings screen itself must prevent mistakes
A settings page is not a database column exposed to the browser. It limits input type and range, states business units, previews before and after, and shows affected objects before saving.
Separate who may edit, who may approve, and who may only view. An operator who may edit notification text is not thereby allowed to change approval limits. Changes go into the activity log under the same traceability standard as business records.
Configuration must be reversible. Rollback does not delete the new value; it makes the old version effective again and records why. Whether affected business should be recalculated is stated separately.
A rule trade-off table
Rule | Frequency | Impact | Needs versions | Business can verify | Recommendation |
|---|---|---|---|---|---|
Discount threshold | Several times a month | Money, medium | Yes | Yes | Configurable with effective dates |
Holiday suspension list | Quarterly | Fulfillment | Yes | Yes | Configurable with approval |
Notification template | Monthly | Display | Optional | Yes | Configurable |
Approval amount limit | A few times a year | Permissions and money | Yes | Partly | Controlled release with business and finance sign-off |
Commission formula | Once a year | Money, high | Yes | No | Code with full regression tests |
Order total invariant | Should not change | System correctness | Not applicable | Not applicable | Not configurable |
The table is not a standard answer; it demonstrates the judgment. The same rule may land differently in different companies, but the dimensions should stay the same.
Start with a rule inventory
List every rule that "changes often," then record the four dimensions, who changes it now, how long a change takes, and what happens if it is wrong. Fewer than half usually qualify as ordinary configuration. The rest need a shorter release path and clearer approval, not a freer admin screen.
What a rule change affects in data, permissions, and interfaces is a separate impact assessment. How to organize current flows and owners is covered in the system preparation guide; when scoping rules and configuration within business system development, agree first on which settings need approval. The choice between custom development and SaaS is covered in custom development or SaaS; that article does not judge individual rules.