u/ForceNineG

I have been building TabChop, a web app for the one-check-at-dinner problem. The lesson so far is that the hard part is not payment, it is making the split happen live while everyone is still at the table.

The design choices I ended up with:

- host uploads or scans the receipt

- guests join by link, QR, or code

- no accounts for guests

- everyone claims line items from the same live receipt

- shared items, discounts, tax, and tip roll into personal totals

- payment handoff happens at the end instead of becoming the whole product

The biggest product question I am testing is whether the share-and-claim flow is obvious enough for a group dinner without explanation.

Demo/overview: https://tabchop.app/overview

I would love feedback on the workflow or receipt edge cases that would break this.

TabChop is a web app for the one-check-at-dinner problem: one person uploads/scans the itemized receipt, shares a link or QR, and guests claim their own items without creating accounts. It handles shared items, discounts, tax/tip allocation, and gives each person a final total.

I have been working on TabChop, a small web app for the exact dinner problem where the restaurant drops one itemized check and everyone starts trying to remember who ordered what.

The flow is:

1. Host scans/uploads the receipt.

2. The app turns it into line items.

3. Host shares a link or QR.

4. Guests claim their own items without creating accounts.

5. Shared items, discounts, tax, and tip get allocated into personal totals.

6. The host can hand people off to Venmo, Cash App, or Zelle details where available.

The side-project bet is that dinner splitting is not really an expense-tracking problem. It is a live group workflow problem. If guests have to download an app or make an account, the table will just go back to guessing in the group chat.

Demo/overview: https://tabchop.app/overview

I would especially like feedback on the guest claim flow and any weird receipt edge cases you think would break this.

Restaurants often drop one check, and the awkward part is not the payment itself - it is figuring out who had what without turning dinner into accounting.

I built TabChop for that moment: one person uploads or scans the itemized receipt, shares a QR/link, and everyone claims their own items. It handles shared plates, discounts, tax/tip allocation, and then gives exact totals with Venmo, Cash App, or Zelle handoff where available. Guests do not need an account.

The main use cases I had in mind were large group dinners, birthday dinners, and restaurants that do not split checks.

Would love feedback on the flow: is the share/claim model obvious enough at the table, and what edge cases would make this break for your friend group?

https://tabchop.app