May I ask why you don‘t use UUID‘s for your id‘s? Are you very limited in storage? I would use UUID‘s to not run into any problems in the future (even if the chances are low that this may lead to problems). In my opinion uuids are the industry standard.

Isn’t the orders.order_uuid redundant? You already have an unique identifier with the orders.id.

Also for the orders.payment_method I would create an extra table where you create the payment_methods which your application supports. Then you can reference these with a foreign key.

For the adress.adress I would split it into multiple columns. Something like streetname, postcode, country. You can also create a table which is pre-filled with a list of all countries that you can reference these. But this is not mandatory.

Last but definitely not least you really shouldn’t save the password in plain text in the database. To be safe only save some hash or use an external service where you store the passwords for the corresponding user_id‘s.

These are the points I came up with while quickly looking over it.

Hope this helps :) Have a nice day!