We have a potential issue with order statuses, we talked about making initial order statuses for everyone or filling them somewhere in the backend. One of the issues we have is the position column, we are going to be allowing the customer to have them show in any order they want but they wouldn't be able to change positions of the default order statuses, and this becomes an issue with either way we do this. It might be the best solution to just give every customer their own order statuses even if they're the same so we can keep those accurate. The other thing we could do is make a many-to-many relationship, though I feel this complicates the issue a bit more than needed since the majority of other order statuses aren't going to need the bridge table, unless we did a similar thing to the order statuses as we have with the brands tables.
We have a potential issue with order statuses, we talked about making initial order statuses for everyone or filling them somewhere in the backend. One of the issues we have is the position column, we are going to be allowing the customer to have them show in any order they want but they wouldn't be able to change positions of the default order statuses, and this becomes an issue with either way we do this. It might be the best solution to just give every customer their own order statuses even if they're the same so we can keep those accurate. The other thing we could do is make a many-to-many relationship, though I feel this complicates the issue a bit more than needed since the majority of other order statuses aren't going to need the bridge table, unless we did a similar thing to the order statuses as we have with the brands tables.