Do you control updating the site and location tables? If you don't, how can you control the values if they are in a table in the BE? How can you stop the client from changing the values if he is so inclined?
Let's put it this way and I'm going to pull rank. You are a pharmacist. You are an expert in your field. I have been designing and developing applications for 50 years. I am an expert in my field. Your method may in fact work for now even if I consider it to be clunky. But, it is not scalable and therefore will become an obstacle sooner or later. Sooner, you hope because you want to sell more copies of the FE
Plus, you don't actually know that it works.
What's going to happen when you have a hundred copies of the FE out in the wild? Then you have to issue an update. What happens? Will you be sending the updated FE's to the client and leaving it to them to distribute? How will you know that they have replaced ALL the old FE's
Have you thought about how you will update the BE if necessary?
Another thing to consider. I don't know about the corporate ethics and IP (Intellectual Property) protections in the Bahamas. All I know is that you have great beaches and heart stoppingly beautiful turquoise blue water. In the US, the larger the corporation, the less likely they are to cheat on licenses (at least deliberately). They don't want to get involved in a legal battle they will lose. So, as long as the cost of your software is reasonable in their opinion, they will comply with your licensing agreement. If they don't consider the price reasonable, they will look at competitive offers or simply copy your design. They have a database and form designs. That cuts off a huge chunk of the development cycle. You might want to look into copywrite and patent law to see what you need to do. Software usually is protected by copywrite but there may be some parts that you can patent which is actually stronger protection against reproduction.