Postgres enum or text with a check constraint for order status?

For a list that will change, text + check constraint. Changing the list is one migration that drops and re-adds the constraint. With an enum, adding is easy (alter type ... add value) but removing or renaming a value is painful.

alter table orders add constraint orders_status_check
  check (status in ('pending','paid','shipped','cancelled','refunded'));

supabase gen types turns enums into a nice union type, while a check becomes plain string. That's the one thing you give up.

I'd keep the enum, for the typed output alone. Removing a status in practice almost never happens, you stop using it. Renaming is alter type ... rename value since PG 10, that's fine.

Third option: a small order_statuses lookup table with a foreign key. Overkill for 5 values, useful once statuses get labels, colors and sort order.