Why are statuses data-driven instead of hard-coded?

Statuses are data the admin defines, not values baked into code, because every business runs its operations differently and each product type has its own natural lifecycle. A grocery's physical flow isn't a repair shop's service flow. By making statuses data-driven — created, named, ordered, and colored from settings — Okommerce lets each business model its real process exactly, and change…

Statuses are data the admin defines, not values baked into code, because every business runs its operations differently and each product type has its own natural lifecycle. A grocery's physical flow isn't a repair shop's service flow. By making statuses data-driven — created, named, ordered, and colored from settings — Okommerce lets each business model its real process exactly, and change it later without a code release. It's a direct expression of the "everything configurable" principle: the system adapts to your workflow rather than forcing your workflow into fixed states.