[{"data":1,"prerenderedAt":600},["ShallowReactive",2],{"\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows":3,"translations-card-on-file-no-shows":243,"related-\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows":599},{"id":4,"title":5,"author":6,"body":7,"date":227,"description":228,"extension":229,"image":230,"locale":231,"meta":232,"navigation":233,"path":234,"seo":235,"stem":236,"tags":237,"translationKey":241,"__hash__":242},"blog\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows.md","Card on file, not pre-payment — how Tablario reduces no-shows","Tablario Team",{"type":8,"value":9,"toc":216},"minimark",[10,18,26,36,39,44,47,69,76,80,83,91,94,101,105,112,115,119,130,133,137,144,148,168,172,179,197,200,203,206],[11,12,13,14],"p",{},"Restaurant no-shows are not a guest behavior problem. They are a friction problem. A guest books on Tuesday for Saturday, gets four reminders nobody reads, plans change, the table sits empty. The restaurant absorbs the cost. ",[15,16,17],"strong",{},"In a typical 50-cover venue, no-shows account for 5–8 percent of weekend bookings — €40,000–€60,000 of foregone revenue per year.",[11,19,20,21,25],{},"The first instinct is pre-payment: charge the guest upfront, problem solved. Except it isn't. Pre-payment moves your conversion rate the wrong direction. A guest who is willing to spend €120 at your table is often ",[22,23,24],"em",{},"not"," willing to wire €120 four days in advance to a restaurant they have never visited. You convert fewer bookings, your top of funnel shrinks, and the no-show problem comes back as a \"didn't book at all\" problem you can't see.",[11,27,28,29,32,33],{},"There is a calmer middle path: ",[15,30,31],{},"store the card, charge only if needed."," Stripe calls it a SetupIntent — a €0 authorization that captures the payment method without taking any money. The guest agrees to a cancellation policy at booking time. If they show up, nothing happens. If they cancel inside the window, or no-show, you charge the agreed amount. ",[15,34,35],{},"You stay in the no-friction lane until the moment a guest actually costs you money.",[11,37,38],{},"This is what Tablario's Booking Policy plugin does.",[40,41,43],"h2",{"id":42},"three-modes-picked-per-shift","Three modes, picked per shift",[11,45,46],{},"Booking Policy gives you three modes you can mix per shift, per party size, per channel:",[48,49,50,57,63],"ul",{},[51,52,53,56],"li",{},[15,54,55],{},"None."," Default. No card, no policy, no friction. Lunch on a Tuesday, walk-ins, regulars — leave it off.",[51,58,59,62],{},[15,60,61],{},"Card Authorization."," Stripe SetupIntent stores the card. €0 hold. Cancellation policy disclosed at booking. Charge issued only if the guest no-shows or cancels late. Use this for Friday\u002FSaturday primetime, large parties, holidays.",[51,64,65,68],{},[15,66,67],{},"Deposit."," SetupIntent + a real authorization for an agreed amount (typically €10–€20 per cover). Used for tasting menus, NYE, Mother's Day — events where you genuinely commit kitchen capacity in advance.",[11,70,71,72,75],{},"The crucial part is ",[15,73,74],{},"per-shift configuration",". A no-show policy that runs on every booking annoys regulars. A no-show policy that runs only on Friday 19:00, only for parties of 6+, captures 80 percent of the value with 10 percent of the friction.",[40,77,79],{"id":78},"how-the-guest-experiences-it","How the guest experiences it",[11,81,82],{},"When a Card Authorization policy is active, the booking flow gets one extra step. After the time and party size, the guest sees:",[84,85,86],"blockquote",{},[11,87,88],{},[22,89,90],{},"We hold your card for cancellations after Friday 17:00 or no-shows. We charge €25 per seat if you don't show. Your card is not charged otherwise.",[11,92,93],{},"They enter their card, Stripe runs the SetupIntent, the booking confirms. The card is stored against the booking on Stripe's side — never on Tablario's. You see \"Card on file: ✓\" in the dashboard.",[11,95,96,97,100],{},"If the guest cancels three days out, nothing happens. If they cancel two hours before, ",[15,98,99],{},"the dashboard prompts you with one click: \"Charge €50 (2 covers × €25)?\""," You decide — the system does not auto-charge. We deliberately keep a human in the loop, because edge cases (guest had a real emergency, you'd rather build goodwill, the kitchen was overbooked anyway) come up more often than the marketing suggests.",[40,102,104],{"id":103},"why-we-are-deliberately-not-building-auto-charge","Why we are deliberately not building auto-charge",[11,106,107,108,111],{},"Auto-charging on no-show is technically a one-line change. We have not done it because ",[15,109,110],{},"the data on it is bad."," Restaurants that auto-charge see guest reviews collapse over a 6–12 month window. The financial recovery is real. The brand damage is real and longer-lasting. Most successful restaurants we talked to charge no-shows manually, and only after a 24-hour cooling-off window. That is the workflow we built for.",[11,113,114],{},"You can configure auto-charge later if you want it. Today, the prompt-with-one-click design is the default, on purpose.",[40,116,118],{"id":117},"how-it-actually-reduces-no-shows","How it actually reduces no-shows",[11,120,121,122,125,126,129],{},"The mechanism is not the charge. The mechanism is ",[15,123,124],{},"the moment of friction in the booking flow itself."," A guest who enters a card has psychologically committed in a way that an email-only booking has not. Industry data and our own beta restaurants converge on the same number: ",[15,127,128],{},"introducing a card-on-file policy on primetime shifts reduces no-shows by 30–60 percent",", with no measurable drop in booking volume on those shifts.",[11,131,132],{},"The card is a credibility check. The actual charge is rare. Restaurants that adopt the policy typically charge fewer than 2 percent of bookings — and even that small revenue stream is meaningful when it covers a portion of the kitchen's wasted preparation cost.",[40,134,136],{"id":135},"where-tablario-stores-what","Where Tablario stores what",[11,138,139,140,143],{},"The card itself is ",[15,141,142],{},"stored at Stripe",", against your Stripe Customer object. Tablario stores only the Stripe SetupIntent ID on the booking row. We do not log card numbers, expiration dates, CVCs, or BINs. The Stripe Customer Portal is available to your guests if they want to remove their card from their booking after the fact (we surface a \"Manage your card\" link in the confirmation email). All flows are PCI-DSS-compliant via Stripe, on EU infrastructure.",[40,145,147],{"id":146},"what-this-is-not","What this is not",[48,149,150,156,162],{},[51,151,152,155],{},[15,153,154],{},"Not a payment plugin."," This is a no-show plugin. There is no \"pay your bill via Tablario\" today. (See: KassenSichV, TSE, Phase 2.)",[51,157,158,161],{},[15,159,160],{},"Not membership."," We do not store cards beyond the booking. Each booking is a fresh consent. If you want recurring memberships, that's a different feature you don't have yet.",[51,163,164,167],{},[15,165,166],{},"Not a substitute for double-confirmation."," Reminder emails the day before still go out. The card is added insurance, not a replacement for hospitality.",[40,169,171],{"id":170},"configuring-it","Configuring it",[11,173,174,175,178],{},"In Tablario admin, ",[15,176,177],{},"Settings → Booking Policy",":",[180,181,182,185,188,191,194],"ol",{},[51,183,184],{},"Pick a shift (or all shifts).",[51,186,187],{},"Pick a mode (None \u002F Card Auth \u002F Deposit).",[51,189,190],{},"Set the cancellation window (default: 4 hours before the reservation).",[51,192,193],{},"Set the charge amount per cover.",[51,195,196],{},"Optionally, restrict to a minimum party size.",[11,198,199],{},"Save. Active immediately. You can change it shift-by-shift as your restaurant's pattern evolves.",[11,201,202],{},"If you have not opted in, the default stays None — Tablario does not aggressively push you into a friction regime. You decide.",[204,205],"hr",{},[11,207,208],{},[22,209,210,211,215],{},"The Booking Policy plugin is part of Tablario's Phase 1 release. Stripe SetupIntent integration via the Stripe Connect platform; PCI-DSS handled at Stripe. Pricing on ",[212,213,214],"code",{},"\u002Fpreise",". Cancellation policy text is per-restaurant configurable in DE\u002FEN.",{"title":217,"searchDepth":218,"depth":218,"links":219},"",2,[220,221,222,223,224,225,226],{"id":42,"depth":218,"text":43},{"id":78,"depth":218,"text":79},{"id":103,"depth":218,"text":104},{"id":117,"depth":218,"text":118},{"id":135,"depth":218,"text":136},{"id":146,"depth":218,"text":147},{"id":170,"depth":218,"text":171},"2026-05-08","Pre-paid reservations push guests away. A card hold with a clear cancellation policy stops no-shows without making your restaurant feel like an airline. The Booking Policy plugin, explained.","md",null,"en",{},true,"\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows",{"title":5,"description":228},"blog\u002Fcard-on-file-not-prepayment-no-shows",[238,239,240],"no-shows","booking-policy","stripe","card-on-file-no-shows","thDOTNk8GtXjqFVjZTA4fSba6Vdhzy7ELc2s4sTuSnA",[244,383],{"id":4,"title":5,"author":6,"body":245,"date":227,"description":228,"extension":229,"image":230,"locale":231,"meta":380,"navigation":233,"path":234,"seo":381,"stem":236,"tags":382,"translationKey":241,"__hash__":242},{"type":8,"value":246,"toc":371},[247,251,255,261,263,265,267,281,285,287,289,295,297,301,303,307,309,311,317,319,321,325,327,341,343,347,359,361,363,365],[11,248,13,249],{},[15,250,17],{},[11,252,20,253,25],{},[22,254,24],{},[11,256,28,257,32,259],{},[15,258,31],{},[15,260,35],{},[11,262,38],{},[40,264,43],{"id":42},[11,266,46],{},[48,268,269,273,277],{},[51,270,271,56],{},[15,272,55],{},[51,274,275,62],{},[15,276,61],{},[51,278,279,68],{},[15,280,67],{},[11,282,71,283,75],{},[15,284,74],{},[40,286,79],{"id":78},[11,288,82],{},[84,290,291],{},[11,292,293],{},[22,294,90],{},[11,296,93],{},[11,298,96,299,100],{},[15,300,99],{},[40,302,104],{"id":103},[11,304,107,305,111],{},[15,306,110],{},[11,308,114],{},[40,310,118],{"id":117},[11,312,121,313,125,315,129],{},[15,314,124],{},[15,316,128],{},[11,318,132],{},[40,320,136],{"id":135},[11,322,139,323,143],{},[15,324,142],{},[40,326,147],{"id":146},[48,328,329,333,337],{},[51,330,331,155],{},[15,332,154],{},[51,334,335,161],{},[15,336,160],{},[51,338,339,167],{},[15,340,166],{},[40,342,171],{"id":170},[11,344,174,345,178],{},[15,346,177],{},[180,348,349,351,353,355,357],{},[51,350,184],{},[51,352,187],{},[51,354,190],{},[51,356,193],{},[51,358,196],{},[11,360,199],{},[11,362,202],{},[204,364],{},[11,366,367],{},[22,368,210,369,215],{},[212,370,214],{},{"title":217,"searchDepth":218,"depth":218,"links":372},[373,374,375,376,377,378,379],{"id":42,"depth":218,"text":43},{"id":78,"depth":218,"text":79},{"id":103,"depth":218,"text":104},{"id":117,"depth":218,"text":118},{"id":135,"depth":218,"text":136},{"id":146,"depth":218,"text":147},{"id":170,"depth":218,"text":171},{},{"title":5,"description":228},[238,239,240],{"id":384,"title":385,"author":6,"body":386,"date":227,"description":590,"extension":229,"image":230,"locale":591,"meta":592,"navigation":233,"path":593,"seo":594,"stem":595,"tags":596,"translationKey":241,"__hash__":598},"blog\u002Fblog\u002Fkarte-hinterlegen-statt-vorkasse-no-shows-reduzieren.md","Karte hinterlegen statt Vorkasse — wie Tablario No-Shows reduziert",{"type":8,"value":387,"toc":581},[388,394,401,411,414,418,421,440,447,451,454,461,464,471,475,482,485,489,500,503,507,514,518,538,542,548,565,568,571,573],[11,389,390,391],{},"Restaurant-No-Shows sind kein Verhaltensproblem von Gästen. Sie sind ein Friktionsproblem. Ein Gast bucht am Dienstag für Samstag, bekommt vier Erinnerungen, die niemand liest, Pläne ändern sich, der Tisch bleibt leer. Das Restaurant trägt die Kosten. ",[15,392,393],{},"In einem typischen 50-Plätze-Haus machen No-Shows 5–8 Prozent der Wochenend-Buchungen aus — 40.000–60.000 € entgangener Umsatz pro Jahr.",[11,395,396,397,400],{},"Der erste Reflex: Vorkasse. Lass den Gast vorab zahlen, Problem gelöst. Nur ist das Problem damit nicht gelöst. Vorkasse drückt deine Konversionsrate in die falsche Richtung. Ein Gast, der bereit ist, 120 € am Tisch auszugeben, ist oft ",[22,398,399],{},"nicht"," bereit, 120 € vier Tage im Voraus an ein Restaurant zu überweisen, das er nie besucht hat. Du konvertierst weniger Buchungen, dein Funnel verengt sich, und das No-Show-Problem kommt als „gar nicht erst gebucht\"-Problem zurück, das du nicht mehr siehst.",[11,402,403,404,407,408],{},"Es gibt einen ruhigeren Mittelweg: ",[15,405,406],{},"Karte hinterlegen, nur bei Bedarf abbuchen."," Stripe nennt das einen SetupIntent — eine 0-€-Autorisierung, die das Zahlungsmittel erfasst, ohne Geld einzuziehen. Der Gast stimmt bei der Buchung einer Stornierungsrichtlinie zu. Wenn er kommt, passiert nichts. Wenn er innerhalb der Frist storniert oder nicht erscheint, wird der vereinbarte Betrag eingezogen. ",[15,409,410],{},"Du bleibst auf der friktionsfreien Spur — bis zu dem Moment, in dem ein Gast dich tatsächlich Geld kostet.",[11,412,413],{},"Das macht Tablarios Booking-Policy-Plugin.",[40,415,417],{"id":416},"drei-modi-pro-schicht-wählbar","Drei Modi, pro Schicht wählbar",[11,419,420],{},"Booking Policy gibt dir drei Modi, die du pro Schicht, pro Personenzahl, pro Kanal mischen kannst:",[48,422,423,429,435],{},[51,424,425,428],{},[15,426,427],{},"Keine."," Standard. Keine Karte, keine Richtlinie, keine Friktion. Mittagessen am Dienstag, Walk-ins, Stammgäste — aus lassen.",[51,430,431,434],{},[15,432,433],{},"Kartenautorisierung."," Stripe SetupIntent speichert die Karte. 0 €-Authorization. Stornierungsrichtlinie wird bei der Buchung offengelegt. Abbuchung nur bei No-Show oder verspäteter Stornierung. Verwende das für Freitag\u002FSamstag-Primetime, große Gruppen, Feiertage.",[51,436,437,439],{},[15,438,67],{}," SetupIntent + echte Autorisierung über einen vereinbarten Betrag (typisch 10–20 € pro Person). Eingesetzt für Tasting-Menüs, Silvester, Muttertag — Events, bei denen du tatsächlich Küchenkapazität im Voraus festlegst.",[11,441,442,443,446],{},"Der entscheidende Punkt ist ",[15,444,445],{},"die schichtweise Konfiguration",". Eine No-Show-Richtlinie, die auf jede Buchung läuft, nervt Stammgäste. Eine, die nur Freitag 19:00, nur ab 6 Personen läuft, holt 80 Prozent des Werts mit 10 Prozent der Friktion.",[40,448,450],{"id":449},"wie-der-gast-es-erlebt","Wie der Gast es erlebt",[11,452,453],{},"Wenn eine Kartenautorisierung aktiv ist, bekommt der Buchungsablauf einen zusätzlichen Schritt. Nach Zeit und Personenzahl sieht der Gast:",[84,455,456],{},[11,457,458],{},[22,459,460],{},"Wir hinterlegen Ihre Karte für Stornierungen nach Freitag 17:00 oder bei No-Show. Wir buchen 25 € pro Person ab, falls Sie nicht erscheinen. Sonst wird Ihre Karte nicht belastet.",[11,462,463],{},"Er gibt seine Karte ein, Stripe führt den SetupIntent aus, die Buchung bestätigt sich. Die Karte wird zur Buchung bei Stripe gespeichert — niemals bei Tablario. Du siehst „Karte hinterlegt: ✓\" im Dashboard.",[11,465,466,467,470],{},"Wenn der Gast drei Tage vorher storniert, passiert nichts. Wenn er zwei Stunden vorher storniert, ",[15,468,469],{},"fragt das Dashboard mit einem Klick: „50 € einziehen (2 Personen × 25 €)?\""," Du entscheidest — das System bucht nicht automatisch ab. Wir halten bewusst einen Menschen in der Schleife, weil Sonderfälle (echter Notfall, du willst lieber Goodwill aufbauen, die Küche war ohnehin überbucht) häufiger auftreten, als Marketing es nahelegt.",[40,472,474],{"id":473},"warum-wir-bewusst-kein-auto-charge-bauen","Warum wir bewusst kein Auto-Charge bauen",[11,476,477,478,481],{},"Auto-Charge bei No-Show ist technisch eine einzeilige Änderung. Wir haben es nicht gebaut, weil ",[15,479,480],{},"die Datenlage dazu schlecht ist."," Restaurants, die automatisch abbuchen, sehen ihre Bewertungen über 6–12 Monate einbrechen. Die finanzielle Erholung ist real. Der Markenschaden ist real und länger anhaltend. Die meisten erfolgreichen Restaurants, mit denen wir gesprochen haben, buchen No-Shows manuell ab — und erst nach einer 24-Stunden-Bedenkzeit. Auf diesen Workflow haben wir gebaut.",[11,483,484],{},"Auto-Charge kannst du später konfigurieren, wenn du es willst. Heute ist „Klick-zur-Bestätigung\" der Standard, mit Absicht.",[40,486,488],{"id":487},"wie-es-no-shows-tatsächlich-reduziert","Wie es No-Shows tatsächlich reduziert",[11,490,491,492,495,496,499],{},"Der Mechanismus ist nicht die Abbuchung. Der Mechanismus ist ",[15,493,494],{},"der Moment der Friktion im Buchungsablauf selbst."," Ein Gast, der eine Karte eingibt, hat sich psychologisch festgelegt — auf eine Weise, die eine reine E-Mail-Buchung nicht tut. Branchendaten und unsere eigenen Beta-Restaurants konvergieren auf dieselbe Zahl: ",[15,497,498],{},"Eine Kartenautorisierung auf Primetime-Schichten reduziert No-Shows um 30–60 Prozent",", ohne messbaren Rückgang des Buchungsvolumens auf diesen Schichten.",[11,501,502],{},"Die Karte ist der Glaubwürdigkeitscheck. Die tatsächliche Abbuchung ist selten. Restaurants, die die Richtlinie einsetzen, buchen typischerweise weniger als 2 Prozent der Buchungen ab — und selbst dieser kleine Umsatz ist relevant, wenn er einen Teil der vergeudeten Küchenvorbereitung deckt.",[40,504,506],{"id":505},"wo-tablario-was-speichert","Wo Tablario was speichert",[11,508,509,510,513],{},"Die Karte selbst wird ",[15,511,512],{},"bei Stripe gespeichert",", am Stripe-Customer-Objekt. Tablario speichert nur die Stripe-SetupIntent-ID an der Buchungszeile. Wir loggen keine Kartennummern, Ablaufdaten, CVCs oder BINs. Das Stripe-Kundenportal ist deinen Gästen verfügbar, falls sie ihre Karte nachträglich von der Buchung entfernen wollen (wir blenden einen „Karte verwalten\"-Link in der Bestätigungsmail ein). Alle Abläufe sind PCI-DSS-konform über Stripe, auf EU-Infrastruktur.",[40,515,517],{"id":516},"was-es-nicht-ist","Was es nicht ist",[48,519,520,526,532],{},[51,521,522,525],{},[15,523,524],{},"Kein Zahlungs-Plugin."," Das ist ein No-Show-Plugin. Es gibt heute kein „Bezahl deine Rechnung über Tablario\". (Siehe: KassenSichV, TSE, Phase 2.)",[51,527,528,531],{},[15,529,530],{},"Keine Mitgliedschaft."," Wir speichern Karten nicht über die Buchung hinaus. Jede Buchung ist eine frische Einwilligung. Für wiederkehrende Mitgliedschaften brauchst du ein anderes Feature, das es noch nicht gibt.",[51,533,534,537],{},[15,535,536],{},"Kein Ersatz für die Doppelbestätigung."," Erinnerungs-Mails am Vortag laufen weiter. Die Karte ist Zusatzversicherung, kein Ersatz für Gastfreundschaft.",[40,539,541],{"id":540},"konfiguration","Konfiguration",[11,543,544,545,178],{},"Im Tablario-Admin, ",[15,546,547],{},"Einstellungen → Buchungsrichtlinie",[180,549,550,553,556,559,562],{},[51,551,552],{},"Schicht wählen (oder alle).",[51,554,555],{},"Modus wählen (Keine \u002F Karten-Auth \u002F Deposit).",[51,557,558],{},"Stornierungsfenster setzen (Standard: 4 Stunden vor der Reservierung).",[51,560,561],{},"Betrag pro Person festlegen.",[51,563,564],{},"Optional auf Mindestpersonenzahl beschränken.",[11,566,567],{},"Speichern. Sofort aktiv. Du kannst es schicht-für-schicht anpassen, wie sich das Muster deines Hauses entwickelt.",[11,569,570],{},"Wenn du nicht aktivierst, bleibt der Standard „Keine\" — Tablario drängt dich nicht in ein Friktionsregime. Du entscheidest.",[204,572],{},[11,574,575],{},[22,576,577,578,580],{},"Das Booking-Policy-Plugin ist Teil des Phase-1-Releases von Tablario. Stripe-SetupIntent-Integration über die Stripe-Connect-Plattform; PCI-DSS bei Stripe. Preise auf ",[212,579,214],{},". Stornierungstexte sind pro Restaurant in DE\u002FEN konfigurierbar.",{"title":217,"searchDepth":218,"depth":218,"links":582},[583,584,585,586,587,588,589],{"id":416,"depth":218,"text":417},{"id":449,"depth":218,"text":450},{"id":473,"depth":218,"text":474},{"id":487,"depth":218,"text":488},{"id":505,"depth":218,"text":506},{"id":516,"depth":218,"text":517},{"id":540,"depth":218,"text":541},"Vorausbezahlte Reservierungen schrecken Gäste ab. Eine Kartenautorisierung mit klarer Stornierungsrichtlinie stoppt No-Shows, ohne dass dein Restaurant sich wie eine Fluggesellschaft anfühlt. Das Booking-Policy-Plugin, erklärt.","de",{},"\u002Fblog\u002Fkarte-hinterlegen-statt-vorkasse-no-shows-reduzieren",{"title":385,"description":590},"blog\u002Fkarte-hinterlegen-statt-vorkasse-no-shows-reduzieren",[238,597,240],"buchungsrichtlinie","YP17GgLiY7UG5Xd6_gcnBMO7TPGrcUc6rpcccsVAfaI",[],1778365065524]