If the owner can’t change it, it shouldn’t be in the code
Delivery fees, opening hours, place names, colours, limits: every business value belongs in a setting, not in the code.
A developer builds a feature, needs a number, and types it straight into the code: 14 days ahead for bookings, a fixed delivery radius, a colour, a town name. It works, until the business changes.
On one ordering site, customers could only book for “today” because of a 24-hour limit nobody could see or change. The owner thought the site was broken. It was doing exactly what the code said.
The rule I build by
- Every place, price, fee, limit, time window, colour and piece of customer-facing text is a setting, with a sensible default.
- Settings live in the WordPress admin, written in plain words, so the owner can change them without a developer.
- The only numbers in the code are technical safety limits, and the admin explains them.
It takes a little longer to build. It saves a call to the developer every time the business moves.