BLUE_BANANA_CONCESSION = 9001

There's also less enterprisy and more "1990s engineering" variant of this:

  enum PricePoint {
    //all the 500+ price points defined above...

    REGULAR_PRICE = 1023;
    PROMO1_PRICE = 1047552;
    PROMO2_PRICE = 1072693248;
    AUTOHINT_ROUND_99 = 1073741824;
    AUTOHINT_BUYING_POWER = 2147483648;
  }

Little bit twiddling, and you can encode 3 prices + some flags in an uint32.

Negative - if these are going to be treated like keys where the integer value needs to retain the same meaning between builds, then an enum is the wrong abstraction to use.