Solution for a single attribute in a table

Question

I am designing a database architecture. I have a user. The user makes an order request. Order related to payment. As soon as the payment is completed, I want to create a sticker for this user.
The sticker has an initial prize (i.e. $ 10). Now the administrator can edit the prize of the sticker. therefore, if the administrator changes the sticker award, then the order will generate a new prize after the change by the administrator.

By database architecture:

User (id, name, email address, password)
Order (id, user_id, no_of_sticker, sticker_prize, address, status)
Payment (id, order_id, amount, date)
sticker (id, order_id, name, content)
sticker_info (sticker_prize)

Now, my question is: is it good to create a new table for only one attribute. This sticker_prize file is only available for editing by the administrator.

Please give your valuable suggestion.
Thanks in adv.

Answer 1

Creating a sticker_info table to store a single value in order from the point of view of database design. You must make sure that you have the primary key in the table so that you cannot get duplicate rows.

On larger systems, there are often many such values, and often the solution is a table of the type: configuration( configId, configValue ) .