The group chat is not a planning tool
Twelve people are coming Saturday. By Thursday the thread has 60 messages in it. Someone said “I’ll do a salad” on Tuesday and nobody is sure whether that was a promise. Priya’s message about the sesame allergy is four screens up. Two people are bringing brownies and nobody is bringing bread.
You are doing two jobs at once, and the group chat is bad at both of them.
The first job is remembering who eats what. Not the fun preferences, the load-bearing ones: the shellfish allergy, the coeliac diagnosis, the toddler who will genuinely eat nothing that touches a sauce. The second job is tracking who is bringing which dish, so you find out about the brownie collision on Thursday instead of Saturday at 6pm.
Here is a way to run both without the thread.
Step one: write down each person’s rules once
Most potluck advice tells you to “ask about dietary restrictions.” That works exactly once, and then you do it again for the next dinner, and the answers live in a different chat.
Write them down instead, per person. In Pantryfy that is the Taste page, where each person you cook for gets their own set of rules:
- Allergens from the standard set: peanuts, tree nuts, milk, eggs, soy, wheat and gluten, fish, shellfish, sesame, mustard, celery, sulphites.
- Diets: vegetarian, vegan, gluten-free, dairy-free, nut-free, kosher, halal, pescatarian, and the rest.
- Spice tolerance, on a scale from none to extra hot.
- The never list: the specific things a person will not eat, whatever the reason. Cilantro. Anything with a skin on it. Mushrooms, forever.
Not everyone at your table has a phone, or wants an app. Your six-year-old does not need an account, and neither does your mother-in-law. You can add up to eight people as managed profiles: you hold the rules on their behalf, they never sign up for anything.
Once the rules exist, they stop being a thing you re-ask. They filter your weekly plan, your recipe recommendations, recipe search, Studio remixes, and Autopilot drafts. The potluck is just the loudest case.
The honest version of what that does: checked allergens are filtered out of suggestions. Pantryfy removes recipes that contain them. It does not inspect the jar of sauce your neighbour brought, and it will never tell you a dish is safe. You still read labels. Anyone cooking for a severe allergy already knows this, and we are not going to pretend a filter replaces it.
Step two: let the rules travel to whoever is cooking
The reason “ask about allergies” fails is that the answer lives with the wrong person. Priya knows about her sesame allergy. The person actually making the noodles does not.
A person’s rules can be sent, three ways:
As a link. It opens as a plain page showing a first name and food rules. Not an email address, not a phone number, not a medical history. You set how long it lasts, up to 30 days, and you can revoke it early. Revoking takes effect the next time someone opens it, not eventually.
To a household you cook with often. Your parents host the grandkids most Sundays. Share the kids’ rules once and their kitchen cooks around them until either side ends it. The rules travel. Your cooking history does not.
Into a party. Which is the next step.
Step three: run the potluck as a menu, not a thread
Start a party in Pantryfy and you get a date, a name, and a menu with courses. You set a target per course: three mains, two sides, one dessert.
Then you send the link. Guests open it in a browser. No app, no account, no download. They add their food rules in about a minute and they are on the board.
What the board shows, which the group chat never did:
- Every dish, and who is bringing it, with their face on it. Claimed dishes stop being a maybe.
- Open slots as their own cards. An unfilled dessert target does not appear as a scolding line at the bottom. It appears as a card that says the dessert slot is empty and gives you one tap to take it.
- A fit badge on every dish. “FITS ALL 6” in green. “NOT FOR GRANDMA” in gold, when a dish clears everyone except one person. You find out before Saturday, not during it.
- A strip at the top titled THE TABLE AVOIDS, built from everyone’s rules together. It shows what the room cannot eat as a set, without putting anyone’s name next to a condition on a screen twelve people can see.
- Votes that name names. “Sam, Maya and Priya want this” is more useful than a number.
- The latest thing that happened. “Zara claimed the salad.”
Someone can suggest a dish without committing to bring it, and someone else can pick it up. Someone who signed up and then got sick can leave; their dishes stay on the menu, unclaimed, so you can see the gap they left instead of discovering it.
Guest data does not stick around. A party and everything in it is deleted seven days after the event.
The chat that knows the menu
Every party has a chat that has read the board: the courses, the people, and every rule on the table. Ask it what to bring for a table with a coeliac and a vegan and it comes back with actual dishes, each one carrying its fit badge and a line on why it works. If you like one, you claim it from the message and it lands on the menu.
This is the paid piece. The party chat is a Pro and Family feature.
Hosting itself: your first party is free on any account. After that, hosting is Pro and Family. Joining someone else’s party is always free, and guests never pay for anything.
The run of show
The method, minus the software:
- Two weeks out. Decide the courses and how many of each you want. Three mains for twelve people, two sides, one dessert, bread. Write the numbers down.
- Ten days out. Send the link. Ask for two things: what they eat, and what they are bringing. In that order, because the first shapes the second.
- One week out. Look at the open slots, not the filled ones. This is the only real work.
- Three days out. Check the fit badges. A dish that clears everyone except one person is a fixable problem on Wednesday and a bad moment on Saturday.
- The day before. Claim whatever is still open yourself. Bread and ice are the traditional answers.
- The day of. Print nothing. Everyone already has the menu.
What this actually fixes
It does not make you a better cook, and it will not stop your uncle bringing the same potato salad for the ninth year running.
What it fixes is the tracking. Nobody has to hold twelve sets of dietary rules in their head, or scroll back through a thread to check whether the sesame thing was an allergy or a preference. The person cooking each dish knows what the room cannot eat, because they were told by the app instead of by a rumour.
Cooking for people you love and getting it wrong is a genuinely bad feeling. Most of the time it happens because the information existed and did not reach the right person in time.
If you want the everyday version of this, the same rules run your normal week: see personalized recipe recommendations for how per-person rules shape what gets suggested, and family meal planning for feeding a household where nobody agrees.