Inspiration

Splitting a dinner evenly is easy and usually unfair. Splitting it properly means someone sits with the receipt working out who shared the starters, who skipped the wine, and how tax and tip should follow. Most groups give up and one person quietly overpays. We wanted the person holding the receipt to be able to describe the evening in a sentence or two and end up with shares that add up exactly, and a way for each guest to pay their own.

What it does

  • Start a table with 2 to 12 guests. Paste the receipt text (or read it from a photo on the device); Tabloom lists the items, tax and tip and checks them against the printed total.
  • Film the table: stand at the head of it, ask "what did everyone have?", and Tabloom hears the answers on the device, finds each face, and puts the split on the picture. Tap a face, then tap what is theirs.
  • Tell it who had what the way groups really do. Paste the group chat, typos and all, or drop in a video or recording of the table while everyone answers "what did you have?". Tabloom transcribes it on the device and you tap who said each line, with a frame of them speaking.
  • When someone just says "I had the chicken" and the receipt has two chicken dishes, it asks which one. Dishes nobody mentioned, drinks especially, are listed for the payer to hand out. It picks up the restaurant from the receipt and can use a pasted menu.
  • Or write a note in plain language, such as "Camille and Tomas shared the mezze, only Idris had the sea bass, it was Noor's birthday". A local AI model proposes who shared each item and shows the part of the note each choice came from.
  • The proposal changes nothing by itself. The organizer checks each item, corrects it, and confirms every line before applying.
  • Shares are calculated in integer cents. Tax and tip follow each person's food in proportion, with deterministic largest-remainder rounding, so the shares always sum to the receipt total.
  • Each guest gets their own PayPal request. Tabloom creates a PayPal Sandbox order for that guest's exact amount, the guest approves it on PayPal's page, and the organizer completes the capture. A share is only marked paid when PayPal reports the capture.
  • If a PayPal response is uncertain, the share is reconciled by reading the order status. A capture is never retried blindly.

In the demo, a $124.40 birthday dinner for four becomes $0.00, $58.59, $32.92 and $32.89, and one guest pays her $32.92 through the PayPal Sandbox.

How we built it

  • TypeScript on Node.js for the local service and the share calculation; the browser app is plain JavaScript, HTML and CSS.
  • PayPal REST APIs in the Sandbox: OAuth, Orders v2 create, capture and status. The API origin is fixed to the Sandbox and credentials stay on the server.
  • A local model served by Ollama (qwen2.5) for the note-to-assignment suggestions. Only a loopback model endpoint is accepted.
  • Tables, revisions and payment history are saved in a local JSON file, so closing the browser loses nothing.

Challenges we ran into

  • Cents. Proportional tax and tip across uneven shares leaves remainders; we had to make the rounding deterministic and prove the total is always preserved.
  • Getting the model to map loose human sentences onto receipt lines without overreaching. It still gets some items wrong, which is why every line needs a human check.
  • Locking the bill once the first payment is requested, so an amount a guest has already approved can't shift under them.

Accomplishments that we're proud of

  • A real end-to-end Sandbox payment per guest, tied to an exact-cent share.
  • An AI step that is visibly a proposal: each suggestion carries its source sentence and a required confirmation.
  • Totals that always reconcile with the receipt.

What we learned

People trust a split when they can see why each line landed where it did. Showing the sentence behind each suggestion did more for confidence than making the model smarter.

What's next

  • A hosted version with guest accounts so invitations work outside one network.
  • PayPal webhooks so paid status updates without the organizer checking.
  • Better receipt photo reading for unfamiliar layouts.
  • Currency support beyond USD.

Built With

Share this project:

Updates

Submission history