Data structure heleped

Ask for Help
1

Hi everyone,

I’m looking to build a POS app for my business and could use some advice from anyone who has experience with this. I currently have two locations, each handling an average of 50 to 200 sales per day. Both locations share the same Customer and Gift Card databases, but I want to keep the sales records separate for each location.

So far, I’ve created my first app that stores the Customer and Gift Card tables using BigTable. I’ve also set up a second app as the POS system for each location, with sales data stored separately. However, when I consider adding a new location in the future, I realize I need to duplicate the app and ensure it doesn’t share all the data. My challenge is that I still want the new location to connect to the shared Customer and Gift Card tables.

My questions are:

  1. How can I duplicate the POS app with a separate sales database while keeping the shared Customer and Gift Card tables? I’m open to any suggestions or restructuring ideas, as I’m just starting.
  2. I currently have a customer using Stripe with their card reader (for a lower transaction rate). Can Glide support this, or will I need to link to a payment page instead?
  3. When building my POS app, I want to include a booking feature for around 10 staff members. I’m using a booking software that has a layout like the one in the picture. Is it possible to recreate something similar in Glide?

I know this is a lot to tackle, but any insights or ideas would be greatly appreciated. Thanks so much for your help!

Untitled
Untitled1920×1080 184 KB

2

Why do you need a separate sales database?
Why not just include a column that has a store identifier?
That will allow you to easily filter data per location.
If you need to secure the data so that it is completely isolated, then you could use the store identifier as a role/row owner.
But separate databases is just creating extra un-necessary work for yourself.

1 Like
3

Thanks Darren for your idea. I think you are right. I was just thinking about sales volume but it doesn’t help me in the long run. I guess just setting up a way to archive the old data to another source will help.

4

If you are using Big Tables, then you don’t really have to worry about volume.

5

Thank you for square it out. I’m spending too much time for that and your advice would give me a lot better.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.