Database field to describe if data should be high or low?

Question

So I'm making a web app for tracking various data for a bakery. Initially I want to track 3 different key performance indicators:

1. Baguettes sold per day
2. Complaints per day
3. Tips per day

However, I want to make an extensible system so rather than hard-code this I am looking to make a table where I can store my different KPIs. I have a table where I am defining my key performance indicators for the bakery, including fields such as:

• KPI name e.g. "baguettes sold"
• KPI unit e.g. "units" (for baguettes sold), "USD" (for "tips per day")
• KPI...order?

This last field has me a bit confused - I want to basically describe if the KPI should be a high value (the more baguettes sold per day, the better) or a low value (the fewer complaints per day, the better).

Is there a terminology for such a thing, or an accepted best practice of how to define and store such a value? Thanks!