Keep every supplier certificate ready before the kashrut review.
KashrutReady turns WhatsApp photos, supplier documents, ingredient changes, and renewal tasks into a Hebrew readiness packet for kosher restaurants, caterers, and bakeries in Israel.
Certificate readiness
8 supplier proofs need action
Dairy supplier
Current certificate linked to renewal packet
Bakery flour
Expires before next event season
New sauce ingredient
Ingredient-change proof missing
Council handoff
Open questions and source links prepared
Who this is for
The owner who can run a busy kitchen but still has to prove every supplier is ready.
You operate a kosher restaurant, caterer, bakery, or food-service shop in Israel. You have multiple suppliers, a current or upcoming certificate cycle, and a mix of photos, PDFs, council notes, supplier messages, and staff memory.
The day-in-the-life pain is concrete: an event client asks whether the certificate is current, a supplier certificate has expired, an ingredient changed, the supervisor needs a handoff, and the proof is scattered between WhatsApp, binders, folders, and a spreadsheet nobody fully trusts.
Narrow buyer
Kosher food-service SMBs in Israel with several suppliers and an upcoming certificate renewal, opening, or supplier-change review.
Paid problem
Missing supplier proof can delay a certificate handoff, create event-booking uncertainty, and pull owners into last-minute calls and document chases.
Validation offer
Join for a one-cycle readiness check: redacted certificate inventory, missing-proof list, renewal packet, and supervisor handoff memo.
Product workflow
A readiness layer before the inspection scramble.
The first version does not replace a council process or decide certification. It organizes the evidence packet so the owner can see what is ready, what is due soon, and what still blocks a clean handoff.
Input
Forward supplier certificates, WhatsApp photos, product or ingredient-change notes, renewal dates, and the local council checklist.
Readiness checks
KashrutReady groups proof by supplier and product, flags expired or missing certificates, tracks open fee/inspection steps, and prepares supplier chase messages.
Output
A Hebrew renewal packet: safe / due soon / blocked status, missing-proof list, source links, packet history, and supervisor handoff memo.
Features tied to the evidence
Supplier certificate inventory
Track each supplier/product certificate with expiry state, source file, last checked date, and renewal-cycle status.
Missing-proof chase list
Turn messy WhatsApp and binder gaps into a prioritized list of suppliers to contact, with message drafts and evidence links.
Local workflow board
Map certificate opening or renewal steps to application forms, fees, meetings, inspection tasks, and supervisor questions.
Packet history
Keep quarterly or renewal-cycle handoff bundles so the next review does not restart from memory.
Concierge-first data handling
Early users can share a redacted folder or sample WhatsApp export for a one-cycle readiness review before any permanent integration.
Proof from public complaints
The page tests a repeated workflow signal, not a generic compliance idea.
GitHub · certificate renewal pain
A public issue describes kosher restaurants, caterers, and bakeries chasing supplier certificates, ingredient changes, fees, and inspection tasks before kashrut certificate renewal.
GitHub · city-level validation plan
A follow-up experiment narrows the wedge to Israel / Givat Shmuel and tests whether operators prefer a recurring Hebrew readiness workspace over WhatsApp, binders, spreadsheets, ERP, or generic AI folders.
Current workaround pattern
The source names paper binders, WhatsApp certificate photos, ad hoc spreadsheet reminders, calls to the religious council, and manual supplier follow-up when documents expire or ingredients change.
These are public signals, not proof of demand. The waitlist tests whether real operators will identify supplier count, renewal timing, and share redacted certificate samples for a concierge readiness packet.
Objections handled
This is deliberately narrower than restaurant ops software.
Why not just keep a binder?
Binders help when someone is standing in the restaurant. They do not proactively show which supplier proof is expired, missing, or tied to a changed ingredient.
Why not a spreadsheet?
Rows can track dates, but the actual certificate images, WhatsApp context, council questions, and handoff history still drift across tools.
Is this giving religious advice?
No. The product organizes readiness evidence, missing documents, and handoff packets. Certification decisions remain with the relevant authority.
Will this be too local?
The first validation intentionally starts narrow: one country/council workflow, Hebrew operator language, and one renewal-cycle packet.
Early waitlist offer
Share one redacted certificate folder. Get the first readiness map.
Early users get a one-cycle review: supplier certificate inventory, missing-proof chase list, renewal packet outline, and a short memo showing whether this wedge is urgent enough to become software.