Why are sales caps editable in the UI?
Because they change and should never be frozen in calculation logic.
Guide
Compare how cottage food sales limits work, why they change, and how to verify the current cap from official state sources.
Sales caps are one of the worst things to hardcode because they move. Legislatures change them. Agencies update guidance. Sites go stale. BakeBadge handles this by treating caps as dated references, not permanent truths.
The result page makes the cap visible when the source supports it, but it also marks it as an as-of value and expects the user to verify the live rule before acting.
Because they change and should never be frozen in calculation logic.
Yes. That is exactly why the app separates data from decision logic.