List of warehouses and Cold Storages. Should have logic in that if a product has a cold storage linked to it, it can't be deleted.

Since ANY and ALL Sales data is listed under the Sales table, it is accessable via the Customer UUID and UUID of the Sale. Therefore, anything that is associated on a separate table will be JOINed together on the frontend. Routing seems hectic, but it makes sense database wise.

This is the barebones table. It will utilize IDs to make it quick! ANYTHING that is listed in another table can be pulled up from just using the ID from another table and joining the details. Crazy! This means I don't add the following: customer billing city and state, This pertains to the specific details of this order. Order Items pertains to all the products apart of the order! **Since pulling the customer over by the UUID, do I really need to have the data of the following or can I just JOIN or grab it:? Billing City and Billing State ??? Why are there PKs that I can't delete??? Need to do more research on when to PK and Not. Also, need to do FKs, but need to know how to later!

This is the master list of the web app customers. Company IDs are assigned in here and those are the UUIDs. Allowsing SOFT DELETE for the system. Hard Deteting for select options. Most are SOFT DELETE via is_delete or is_voided

You can name roles here. Need to figure out how it works

Think this will be a table, but not fully sure. Still processing and thinking things through. Same as Sellable table...

More thought needs to go into this! Currently added, but more thought out is needed!

Need to think this one through more as well!!

simply lists it on the order. Not for us, but for them. But, if Pre-Paid, it automatically makes it a custom Trucking PO we make.

Each section title and any other text can be stored with a language identifier.

Products -> These are details that you set and don't change or add to. Inventory-> these are variable details that get assigned to prducts when received in.

An idea with this is to be able to build a spec sheet if need be for web app customers instead of doing them by hand. A template will need to be made.

will be a work in progress... Divvy up based off Inventory, CRM, etc...

I think I need a global settings table to house customer settings. Advanced settings is for advanced settings that don't belong in standard settings like theme, langauage, time zone, ltr, etc. Global is the DEFAULT settings.

I do want settings for a per user basis. For example, some like a specific theme whereas some like darkmode. I want to be able to offer that to them. Not sure if languages would be for global for the customer or on a per user basis. The issue is how would it be a specific language? Like, global is English, but the user is Spanish. Would an admin or manager be able to add another language description to the product? More things to consider and think out!!

More in-depth thinking needs to figure what this is for specifically! would we need UTM???

**Need to figure out how to tie products to a specific vendor. Would it be divvy'd up with "vendor details" and "vendor products" I think the details are JOINed together with the Vendors table

This is for recalls. *Might need to add another table or more for all the things pertaining to one.

Considering it to be named "Order Products" This actually houses the items/products in the actual order. The Order table just houses the order details because customer_orders_id (changing to orders_id) has to be 1 number and it can't repeat. This is where multiple products can be added Same goes for Invoices... Same concept!

**How to void??

follows the same rule as Orders and Order Items tables

These are the main settings for the actual overall web app.

This is for helping salesmen sell when they might be on a call or selling something to someone or a prospect.

CHECK ( -- Ensure that either product_id or service_id is set, not both (product_id IS NOT NULL AND service_id IS NULL) OR (service_id IS NOT NULL AND product_id IS NULL) This makes sure that either or is NOT NULL. Might need to use "DECIMAL" as the data type.

This stores sessions for all users. It only stores 1 session per user.

This stores activities of the last 5 or 10(?) sessions of a user to help compare if there is any anomolies to trigger MFA (2-factor authentication).

Using Aproach 2 Conection Limit 5 (max by user_id or by IP). user_id might be best. But maybe 2 or 3 connections max. I would have to see if browser tabs open relate to this max connection. But, it might be based off browser id... Idk?

These are module specific settngs. IE: CRM, Inventory, Products Site, Accounting, etc...

Not sure if I need this. It seems to be a table used for admins for low-level settings. But, IDK...

This is for housing more than 1 buyer per customer. Keep adding details to it!

This is for housing more than 1 delivery address per customer

This is for housing more than accounant per customer

Some of the fields like "created_at" and "last_modified" might be for internal or deeper things for insights in the future...

**How to resize images to a specific size? Need to use Python app

Is the product sold by the lb, case, etc.?

Logic will split the data up into separate areas for viewing. If days have the same "time" then only 1 will be shown and the 1st day of the week till the end will be. A potential issue is do I set Sunday-Saturday as the start of the week or Monday-Sunday??? Global standard might be it...

EXAMPLE: INSERT INTO subscription_addons (name, description, price, duration_in_days) VALUES ('50 GB Storage', 'Add 50 GB of storage to your plan.', 10.00, 30), ('100 GB Storage', 'Add 100 GB of storage to your plan.', 18.00, 30);