[{"data":1,"prerenderedAt":2054},["ShallowReactive",2],{"\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows":3,"translations-card-on-file-no-shows":243,"related-\u002Fen\u002Fblog\u002Fcard-on-file-not-prepayment-no-shows":1249},{"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,599,815,1033],{"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":591,"extension":229,"image":230,"locale":592,"meta":593,"navigation":233,"path":594,"seo":595,"stem":596,"tags":597,"translationKey":241,"__hash__":598},"blog\u002Fblog\u002Fcarta-registrata-non-pagamento-anticipato-no-show.md","Carta registrata, non pagamento anticipato — come Tablario riduce i no-show",{"type":8,"value":387,"toc":582},[388,394,401,411,414,418,421,441,448,452,455,462,465,472,476,483,486,490,501,504,508,515,519,539,543,549,566,569,572,574],[11,389,390,391],{},"I no-show al ristorante non sono un problema di comportamento degli ospiti. Sono un problema di attrito. Un ospite prenota martedì per sabato, riceve quattro promemoria che nessuno legge, i piani cambiano, il tavolo resta vuoto. Il ristorante assorbe il costo. ",[15,392,393],{},"In un locale tipico da 50 coperti, i no-show rappresentano il 5–8 % delle prenotazioni del weekend — €40.000–€60.000 di ricavi persi all'anno.",[11,395,396,397,400],{},"Il primo istinto è il pagamento anticipato: incassi prima, problema risolto. Solo che non funziona. Il pagamento anticipato sposta il tasso di conversione nella direzione sbagliata. Un ospite disposto a spendere €120 al tuo tavolo spesso ",[22,398,399],{},"non"," è disposto a bonificare €120 quattro giorni prima a un ristorante in cui non è mai stato. Converti meno prenotazioni, l'imbuto si stringe, e il problema dei no-show ritorna nella forma invisibile di \"non hanno proprio prenotato\".",[11,402,403,404,407,408],{},"C'è una via di mezzo più tranquilla: ",[15,405,406],{},"registrare la carta, addebitare solo se serve."," Stripe lo chiama SetupIntent — un'autorizzazione a €0 che cattura il metodo di pagamento senza prelevare nulla. L'ospite accetta una policy di cancellazione al momento della prenotazione. Se si presenta, non succede niente. Se cancella entro la finestra prevista o non si presenta, addebiti l'importo concordato. ",[15,409,410],{},"Resti nella corsia senza attrito fino al momento esatto in cui un ospite ti costa davvero soldi.",[11,412,413],{},"Questo è ciò che fa il plugin Booking Policy di Tablario.",[40,415,417],{"id":416},"tre-modalità-scelte-per-servizio","Tre modalità, scelte per servizio",[11,419,420],{},"Booking Policy ti dà tre modalità che puoi mescolare per servizio, per dimensione del gruppo, per canale:",[48,422,423,429,435],{},[51,424,425,428],{},[15,426,427],{},"Nessuna."," Default. Niente carta, niente policy, niente attrito. Pranzo del martedì, walk-in, clienti abituali — lascia spenta.",[51,430,431,434],{},[15,432,433],{},"Garanzia con carta."," Stripe SetupIntent registra la carta. Blocco a €0. La policy di cancellazione viene mostrata in prenotazione. L'addebito parte solo se l'ospite non si presenta o cancella tardi. Usala per i primetime venerdì\u002Fsabato, i gruppi grandi, le feste.",[51,436,437,440],{},[15,438,439],{},"Caparra."," SetupIntent + un'autorizzazione effettiva per un importo concordato (tipicamente €10–€20 per coperto). Da usare per menu degustazione, Capodanno, San Valentino — eventi in cui impegni davvero capacità di cucina in anticipo.",[11,442,443,444,447],{},"Il punto cruciale è la ",[15,445,446],{},"configurazione per servizio",". Una policy no-show attiva su ogni prenotazione infastidisce gli abituali. Una policy attiva solo il venerdì alle 19:00, solo per gruppi di 6+, cattura l'80 % del valore con il 10 % dell'attrito.",[40,449,451],{"id":450},"come-la-vive-lospite","Come la vive l'ospite",[11,453,454],{},"Quando una policy di Garanzia con carta è attiva, il flusso di prenotazione ha un passaggio in più. Dopo orario e numero di persone, l'ospite legge:",[84,456,457],{},[11,458,459],{},[22,460,461],{},"Tratteniamo la sua carta per cancellazioni dopo venerdì alle 17:00 o in caso di no-show. Addebiteremo €25 a coperto se non si presenta. La carta non viene addebitata in nessun altro caso.",[11,463,464],{},"Inserisce la carta, Stripe esegue il SetupIntent, la prenotazione viene confermata. La carta resta agganciata alla prenotazione sul lato Stripe — mai sul lato Tablario. In dashboard vedi \"Carta registrata: ✓\".",[11,466,467,468,471],{},"Se l'ospite cancella tre giorni prima, non succede niente. Se cancella due ore prima, ",[15,469,470],{},"la dashboard ti propone con un clic: \"Addebitare €50 (2 coperti × €25)?\""," Decidi tu — il sistema non addebita in automatico. Manteniamo apposta una persona nel loop, perché i casi limite (vera emergenza, preferisci costruire goodwill, la cucina era già sovraprenotata) capitano più spesso di quanto il marketing lasci pensare.",[40,473,475],{"id":474},"perché-deliberatamente-non-costruiamo-laddebito-automatico","Perché deliberatamente non costruiamo l'addebito automatico",[11,477,478,479,482],{},"L'addebito automatico in caso di no-show è tecnicamente una riga di codice. Non l'abbiamo fatto perché ",[15,480,481],{},"i dati sull'argomento sono brutti."," I ristoranti che addebitano in automatico vedono le recensioni degli ospiti crollare in 6–12 mesi. Il recupero finanziario è reale. Il danno al brand è reale e dura di più. Quasi tutti i ristoranti di successo con cui abbiamo parlato addebitano i no-show manualmente, e solo dopo una finestra di 24 ore di raffreddamento. È il workflow per cui abbiamo progettato.",[11,484,485],{},"L'addebito automatico potrai configurarlo più avanti se lo vorrai. Oggi, il design \"proponi-con-un-clic\" è il default, di proposito.",[40,487,489],{"id":488},"come-riduce-davvero-i-no-show","Come riduce davvero i no-show",[11,491,492,493,496,497,500],{},"Il meccanismo non è l'addebito. Il meccanismo è ",[15,494,495],{},"il momento di attrito dentro il flusso di prenotazione stesso."," Un ospite che inserisce una carta si è impegnato psicologicamente in un modo che una prenotazione solo via email non chiede. Dati di settore e i nostri ristoranti beta convergono sullo stesso numero: ",[15,498,499],{},"introdurre una policy di carta registrata sui servizi di primetime riduce i no-show del 30–60 %",", senza un calo misurabile del volume di prenotazioni su quei servizi.",[11,502,503],{},"La carta è una verifica di credibilità. L'addebito vero e proprio è raro. I ristoranti che adottano la policy tipicamente addebitano meno del 2 % delle prenotazioni — e anche questo piccolo flusso di ricavi è significativo quando copre una parte del costo di preparazione di cucina andato sprecato.",[40,505,507],{"id":506},"dove-tablario-archivia-cosa","Dove Tablario archivia cosa",[11,509,510,511,514],{},"La carta in sé è ",[15,512,513],{},"archiviata in Stripe",", contro il tuo oggetto Customer Stripe. Tablario conserva solo l'ID SetupIntent di Stripe sulla riga di prenotazione. Non registriamo numeri di carta, scadenze, CVC o BIN. Il Customer Portal di Stripe è disponibile per i tuoi ospiti che vogliano rimuovere la carta dalla loro prenotazione a posteriori (mostriamo un link \"Gestisci la tua carta\" nella mail di conferma). Tutti i flussi sono conformi PCI-DSS via Stripe, su infrastruttura UE.",[40,516,518],{"id":517},"cosa-non-è","Cosa non è",[48,520,521,527,533],{},[51,522,523,526],{},[15,524,525],{},"Non è un plugin di pagamento."," È un plugin no-show. Non esiste oggi un \"paga il conto via Tablario\". (Vedi: normative fiscali nazionali, Fase 2.)",[51,528,529,532],{},[15,530,531],{},"Non è membership."," Non conserviamo le carte oltre la prenotazione. Ogni prenotazione è un consenso fresco. Se ti servono abbonamenti ricorrenti è una feature diversa, oggi non disponibile.",[51,534,535,538],{},[15,536,537],{},"Non sostituisce la doppia conferma."," Le email di promemoria del giorno prima partono comunque. La carta è un'assicurazione aggiuntiva, non un sostituto dell'ospitalità.",[40,540,542],{"id":541},"come-si-configura","Come si configura",[11,544,545,546,178],{},"Nell'admin Tablario, ",[15,547,548],{},"Impostazioni → Booking Policy",[180,550,551,554,557,560,563],{},[51,552,553],{},"Scegli un servizio (o tutti i servizi).",[51,555,556],{},"Scegli una modalità (Nessuna \u002F Garanzia con carta \u002F Caparra).",[51,558,559],{},"Imposta la finestra di cancellazione (default: 4 ore prima della prenotazione).",[51,561,562],{},"Imposta l'importo di addebito per coperto.",[51,564,565],{},"In opzione, limita a un numero minimo di persone.",[11,567,568],{},"Salva. Attivo subito. Puoi cambiare servizio per servizio man mano che il pattern del tuo ristorante evolve.",[11,570,571],{},"Se non hai fatto opt-in, il default resta Nessuna — Tablario non ti spinge aggressivamente in un regime di attrito. Decidi tu.",[204,573],{},[11,575,576],{},[22,577,578,579,581],{},"Il plugin Booking Policy è parte del rilascio di Fase 1 di Tablario. Integrazione Stripe SetupIntent tramite la piattaforma Stripe Connect; PCI-DSS gestito su Stripe. Pricing su ",[212,580,214],{},". Il testo della policy di cancellazione è configurabile per ristorante in IT\u002FDE\u002FEN.",{"title":217,"searchDepth":218,"depth":218,"links":583},[584,585,586,587,588,589,590],{"id":416,"depth":218,"text":417},{"id":450,"depth":218,"text":451},{"id":474,"depth":218,"text":475},{"id":488,"depth":218,"text":489},{"id":506,"depth":218,"text":507},{"id":517,"depth":218,"text":518},{"id":541,"depth":218,"text":542},"Le prenotazioni prepagate allontanano gli ospiti. Una garanzia con carta più una policy di cancellazione chiara ferma i no-show senza far sembrare il ristorante una compagnia aerea. Il plugin Booking Policy, spiegato.","it",{},"\u002Fblog\u002Fcarta-registrata-non-pagamento-anticipato-no-show",{"title":385,"description":591},"blog\u002Fcarta-registrata-non-pagamento-anticipato-no-show",[238,239,240],"M77md_BQVRUpCmXG35UUlSw0-9jHZZhNiBluiz0gnaU",{"id":600,"title":601,"author":6,"body":602,"date":227,"description":807,"extension":229,"image":230,"locale":808,"meta":809,"navigation":233,"path":810,"seo":811,"stem":812,"tags":813,"translationKey":241,"__hash__":814},"blog\u002Fblog\u002Fcreditcardgarantie-geen-vooruitbetaling-no-shows.md","Creditcardgarantie, geen vooruitbetaling — zo verlaagt Tablario no-shows",{"type":8,"value":603,"toc":798},[604,610,617,627,630,634,637,657,664,668,671,678,681,688,692,699,702,706,717,720,724,731,735,755,759,765,782,785,788,790],[11,605,606,607],{},"No-shows zijn geen gedragsprobleem van gasten. Het is een frictieprobleem. Een gast reserveert dinsdag voor zaterdag, krijgt vier herinneringen die niemand leest, plannen veranderen, de tafel blijft leeg. Het restaurant draait op voor de kosten. ",[15,608,609],{},"In een gemiddeld restaurant met 50 zitplaatsen zijn no-shows goed voor 5–8 procent van de weekendboekingen — € 40.000–€ 60.000 misgelopen omzet per jaar.",[11,611,612,613,616],{},"De eerste reflex is vooruitbetaling: laat de gast vooraf afrekenen, probleem opgelost. Behalve dat het dat niet is. Vooruitbetaling drukt je conversie de verkeerde kant op. Een gast die bereid is € 120 aan tafel uit te geven, is vaak ",[22,614,615],{},"niet"," bereid om dat bedrag vier dagen van tevoren over te maken naar een restaurant waar hij nog nooit is geweest. Je converteert minder boekingen, de bovenkant van je funnel krimpt, en het no-show-probleem komt terug als een \"niet eens geboekt\"-probleem dat je niet meer ziet.",[11,618,619,620,623,624],{},"Er is een rustigere middenweg: ",[15,621,622],{},"leg de kaart vast, schrijf alleen af als het echt nodig is."," Stripe noemt dat een SetupIntent — een autorisatie van € 0 die de betaalmethode vastlegt zonder geld af te schrijven. De gast stemt bij de boeking in met een annuleringsbeleid. Komt hij opdagen, dan gebeurt er niets. Annuleert hij binnen het venster of komt hij niet, dan reken je het afgesproken bedrag af. ",[15,625,626],{},"Je blijft in de frictievrije baan tot het moment dat een gast jou daadwerkelijk geld kost.",[11,628,629],{},"Dat is wat de Booking Policy-plug-in van Tablario doet.",[40,631,633],{"id":632},"drie-modi-per-shift-te-kiezen","Drie modi, per shift te kiezen",[11,635,636],{},"Booking Policy biedt drie modi die je per shift, per groepsgrootte en per kanaal kunt mixen:",[48,638,639,645,651],{},[51,640,641,644],{},[15,642,643],{},"Geen."," Standaard. Geen kaart, geen beleid, geen frictie. Lunch op dinsdag, walk-ins, vaste gasten — laat het uit.",[51,646,647,650],{},[15,648,649],{},"Kaartautorisatie."," Stripe SetupIntent legt de kaart vast. € 0-blokkade. Annuleringsbeleid wordt bij de boeking getoond. Afschrijving alleen bij no-show of late annulering. Gebruik dit voor vrijdag- en zaterdagavondprimetime, grote gezelschappen, feestdagen.",[51,652,653,656],{},[15,654,655],{},"Borg."," SetupIntent + een echte autorisatie voor een afgesproken bedrag (typisch € 10–€ 20 per couvert). Geschikt voor proeverijen, oudejaarsavond, Moederdag — momenten waarop je daadwerkelijk keukencapaciteit vooraf vastlegt.",[11,658,659,660,663],{},"Het kruciale deel is ",[15,661,662],{},"configuratie per shift",". Een no-showbeleid dat op elke boeking draait, irriteert vaste gasten. Een no-showbeleid dat alleen op vrijdag 19:00 draait, en alleen voor gezelschappen van 6+, vangt 80 procent van de waarde met 10 procent van de frictie.",[40,665,667],{"id":666},"hoe-de-gast-het-ervaart","Hoe de gast het ervaart",[11,669,670],{},"Wanneer een kaartautorisatie actief is, krijgt de boekingsflow één extra stap. Na tijd en groepsgrootte ziet de gast:",[84,672,673],{},[11,674,675],{},[22,676,677],{},"Wij houden je kaart vast voor annuleringen na vrijdag 17:00 of voor no-shows. We rekenen € 25 per stoel af als je niet komt. Anders wordt je kaart niet belast.",[11,679,680],{},"De gast voert zijn kaart in, Stripe voert de SetupIntent uit, de boeking wordt bevestigd. De kaart wordt aan de boeking gekoppeld bij Stripe — nooit bij Tablario. Je ziet \"Kaart vastgelegd: ✓\" in het dashboard.",[11,682,683,684,687],{},"Annuleert de gast drie dagen van tevoren, dan gebeurt er niets. Annuleert hij twee uur voor de tijd, dan ",[15,685,686],{},"vraagt het dashboard je met één klik: \"€ 50 afschrijven (2 couverts × € 25)?\""," Jij beslist — het systeem schrijft niet automatisch af. We houden bewust een mens in de lus, want randgevallen (echte noodsituatie van de gast, jij liever een goodwill-gebaar, de keuken was toch al overboekt) komen vaker voor dan de marketing suggereert.",[40,689,691],{"id":690},"waarom-we-bewust-geen-automatische-afschrijving-bouwen","Waarom we bewust geen automatische afschrijving bouwen",[11,693,694,695,698],{},"Een automatische afschrijving bij no-show is technisch een wijziging van één regel. We hebben dat niet gedaan, omdat ",[15,696,697],{},"de data erover slecht zijn."," Restaurants die automatisch afschrijven, zien hun gastbeoordelingen over een venster van 6–12 maanden instorten. Het financiële herstel is reëel. De merkschade is reëel én blijvender. De meeste succesvolle restaurants die we spraken, schrijven no-shows handmatig af, en pas na een afkoelperiode van 24 uur. Daar hebben we de workflow op gebouwd.",[11,700,701],{},"Je kunt later automatische afschrijving instellen als je dat wilt. Vandaag is \"voorstel-met-één-klik\" het bewuste standaardgedrag.",[40,703,705],{"id":704},"hoe-het-no-shows-daadwerkelijk-verlaagt","Hoe het no-shows daadwerkelijk verlaagt",[11,707,708,709,712,713,716],{},"Het mechanisme zit niet in de afschrijving. Het mechanisme zit in ",[15,710,711],{},"het frictiemoment in de boekingsflow zelf."," Een gast die een kaart invult, heeft zich psychologisch op een manier vastgelegd die een puur e-mailboeking niet doet. Branche-data en onze eigen bètarestaurants komen op hetzelfde getal uit: ",[15,714,715],{},"invoering van een creditcardgarantie op primetime-shifts verlaagt no-shows met 30–60 procent",", zonder meetbare daling van het boekingsvolume in die shifts.",[11,718,719],{},"De kaart is een geloofwaardigheidstest. De daadwerkelijke afschrijving is zeldzaam. Restaurants die het beleid invoeren, schrijven typisch minder dan 2 procent van de boekingen af — en zelfs die kleine inkomstenstroom is zinvol als die de verspilde voorbereiding van de keuken deels dekt.",[40,721,723],{"id":722},"waar-tablario-wat-opslaat","Waar Tablario wat opslaat",[11,725,726,727,730],{},"De kaart zelf wordt ",[15,728,729],{},"opgeslagen bij Stripe",", gekoppeld aan je Stripe Customer-object. Tablario slaat alleen de Stripe SetupIntent-ID op bij de boekingsregel. Wij loggen geen kaartnummers, vervaldata, CVC's of BIN's. De Stripe Customer Portal is beschikbaar voor je gasten als ze achteraf hun kaart willen verwijderen (we tonen een \"Beheer je kaart\"-link in de bevestigingsmail). Alle flows zijn PCI-DSS-conform via Stripe, op EU-infrastructuur.",[40,732,734],{"id":733},"wat-dit-niet-is","Wat dit niet is",[48,736,737,743,749],{},[51,738,739,742],{},[15,740,741],{},"Geen betaalplug-in."," Dit is een no-show-plug-in. Er is vandaag geen \"betaal je rekening via Tablario\". (Zie: KassenSichV, TSE, fase 2.)",[51,744,745,748],{},[15,746,747],{},"Geen lidmaatschap."," Wij bewaren kaarten niet voorbij de boeking. Elke boeking is een nieuwe toestemming. Wil je terugkerende lidmaatschappen, dan is dat een andere functie die er nog niet is.",[51,750,751,754],{},[15,752,753],{},"Geen vervanging van dubbele bevestiging."," Herinneringsmails de dag ervoor gaan nog steeds uit. De kaart is extra zekerheid, geen vervanging van gastvrijheid.",[40,756,758],{"id":757},"configuratie","Configuratie",[11,760,761,762,178],{},"In Tablario-admin, ",[15,763,764],{},"Instellingen → Reserveringsbeleid",[180,766,767,770,773,776,779],{},[51,768,769],{},"Kies een shift (of alle shifts).",[51,771,772],{},"Kies een modus (Geen \u002F Kaartautorisatie \u002F Borg).",[51,774,775],{},"Stel het annuleringsvenster in (standaard: 4 uur voor de reservering).",[51,777,778],{},"Stel het bedrag per couvert in.",[51,780,781],{},"Optioneel: beperk tot een minimale groepsgrootte.",[11,783,784],{},"Opslaan. Direct actief. Je kunt het per shift aanpassen naarmate het patroon van je restaurant verandert.",[11,786,787],{},"Heb je niet ingestemd, dan blijft de standaard Geen — Tablario duwt je niet agressief in een frictieregime. Jij beslist.",[204,789],{},[11,791,792],{},[22,793,794,795,797],{},"De Booking Policy-plug-in is onderdeel van de fase 1-release van Tablario. Stripe SetupIntent-integratie via het Stripe Connect-platform; PCI-DSS afgehandeld bij Stripe. Prijzen op ",[212,796,214],{},". Tekst van het annuleringsbeleid is per restaurant configureerbaar in NL\u002FDE\u002FEN.",{"title":217,"searchDepth":218,"depth":218,"links":799},[800,801,802,803,804,805,806],{"id":632,"depth":218,"text":633},{"id":666,"depth":218,"text":667},{"id":690,"depth":218,"text":691},{"id":704,"depth":218,"text":705},{"id":722,"depth":218,"text":723},{"id":733,"depth":218,"text":734},{"id":757,"depth":218,"text":758},"Vooruitbetaalde reserveringen jagen gasten weg. Een kaartautorisatie met een duidelijk annuleringsbeleid stopt no-shows zonder dat je restaurant aanvoelt als een vliegmaatschappij.","nl",{},"\u002Fblog\u002Fcreditcardgarantie-geen-vooruitbetaling-no-shows",{"title":601,"description":807},"blog\u002Fcreditcardgarantie-geen-vooruitbetaling-no-shows",[238,239,240],"VUPRs3KbiV__EuYpbuRKIgWN9ifZsEAkOofOLdNEpC4",{"id":816,"title":817,"author":6,"body":818,"date":227,"description":1024,"extension":229,"image":230,"locale":1025,"meta":1026,"navigation":233,"path":1027,"seo":1028,"stem":1029,"tags":1030,"translationKey":241,"__hash__":1032},"blog\u002Fblog\u002Fempreinte-bancaire-pas-paiement-anticipe-no-shows.md","Empreinte bancaire, pas paiement anticipé — comment Tablario réduit les no-shows",{"type":8,"value":819,"toc":1015},[820,826,833,843,846,850,853,873,880,884,887,894,897,904,908,915,918,922,933,936,940,947,951,971,975,982,999,1002,1005,1007],[11,821,822,823],{},"Les no-shows en restaurant ne sont pas un problème de comportement client. C'est un problème de friction. Un client réserve mardi pour samedi, reçoit quatre rappels que personne ne lit, ses plans changent, la table reste vide. Le restaurant absorbe le coût. ",[15,824,825],{},"Dans une salle moyenne de 50 couverts, les no-shows représentent 5 à 8 % des réservations week-end — soit 40 000 € à 60 000 € de chiffre d'affaires perdu par an.",[11,827,828,829,832],{},"Le premier réflexe est le paiement anticipé : on facture le client à l'avance, problème réglé. Sauf que non. Le paiement anticipé fait chuter ton taux de conversion dans le mauvais sens. Un client prêt à dépenser 120 € à ta table n'est souvent ",[22,830,831],{},"pas"," prêt à virer 120 € quatre jours à l'avance à un restaurant où il n'est jamais venu. Tu convertis moins de réservations, ton haut de funnel se contracte, et le problème de no-show revient sous forme de « pas réservé du tout » que tu ne vois plus.",[11,834,835,836,839,840],{},"Il y a un chemin plus calme entre les deux : ",[15,837,838],{},"conserver la carte, débiter uniquement si nécessaire."," Stripe appelle ça un SetupIntent — une autorisation à 0 € qui enregistre le moyen de paiement sans débiter. Le client accepte une politique d'annulation au moment de la réservation. S'il se présente, rien ne se passe. S'il annule trop tard ou ne vient pas, tu débites le montant convenu. ",[15,841,842],{},"Tu restes en mode sans-friction jusqu'au moment précis où un client te coûte réellement de l'argent.",[11,844,845],{},"C'est exactement ce que fait le plugin Booking Policy de Tablario.",[40,847,849],{"id":848},"trois-modes-choisis-par-service","Trois modes, choisis par service",[11,851,852],{},"Booking Policy te donne trois modes que tu peux mixer par service, par taille de groupe, par canal :",[48,854,855,861,867],{},[51,856,857,860],{},[15,858,859],{},"Aucun."," Par défaut. Pas de carte, pas de politique, pas de friction. Déjeuner du mardi, walk-ins, habitués — laisse désactivé.",[51,862,863,866],{},[15,864,865],{},"Autorisation de carte."," Stripe SetupIntent enregistre la carte. Empreinte à 0 €. Politique d'annulation annoncée à la réservation. Débit uniquement en cas de no-show ou d'annulation tardive. À utiliser pour les vendredis\u002Fsamedis primetime, les grands groupes, les jours fériés.",[51,868,869,872],{},[15,870,871],{},"Acompte."," SetupIntent + véritable autorisation pour un montant convenu (typiquement 10–20 € par couvert). À utiliser pour les menus dégustation, le Nouvel An, la fête des mères — événements où tu engages réellement la capacité de la cuisine à l'avance.",[11,874,875,876,879],{},"Le point crucial est ",[15,877,878],{},"la configuration par service",". Une politique no-show appliquée à chaque réservation agace les habitués. Une politique no-show appliquée seulement le vendredi à 19 h, seulement pour les groupes de 6+, capture 80 % de la valeur avec 10 % de la friction.",[40,881,883],{"id":882},"comment-le-client-vit-lexpérience","Comment le client vit l'expérience",[11,885,886],{},"Quand une politique d'autorisation de carte est active, le parcours de réservation gagne une étape. Après l'heure et la taille du groupe, le client voit :",[84,888,889],{},[11,890,891],{},[22,892,893],{},"Nous prélevons une empreinte sur votre carte pour les annulations après vendredi 17 h ou les no-shows. Nous débitons 25 € par couvert si vous ne venez pas. Votre carte n'est pas débitée autrement.",[11,895,896],{},"Il entre sa carte, Stripe lance le SetupIntent, la réservation est confirmée. La carte est stockée chez Stripe, jamais chez Tablario. Tu vois « Carte enregistrée : ✓ » dans le tableau de bord.",[11,898,899,900,903],{},"Si le client annule trois jours à l'avance, rien ne se passe. S'il annule deux heures avant, ",[15,901,902],{},"le tableau de bord te propose en un clic : « Débiter 50 € (2 couverts × 25 €) ? »"," Tu décides — le système ne débite pas automatiquement. Nous gardons délibérément un humain dans la boucle, parce que les cas limites (urgence réelle, geste commercial, cuisine déjà sur-réservée) arrivent plus souvent que ne le suggère le marketing.",[40,905,907],{"id":906},"pourquoi-nous-ne-construisons-pas-de-débit-automatique","Pourquoi nous ne construisons pas de débit automatique",[11,909,910,911,914],{},"Le débit automatique en cas de no-show est techniquement un changement d'une ligne. Nous ne l'avons pas fait parce que ",[15,912,913],{},"les données dessus sont mauvaises."," Les restaurants qui débitent automatiquement voient leurs avis clients s'effondrer sur une fenêtre de 6 à 12 mois. Le recouvrement financier est réel. Le préjudice de marque est réel et plus durable. La plupart des restaurants à succès que nous avons rencontrés débitent manuellement, et seulement après un délai de 24 heures. C'est pour ce flux que nous avons construit.",[11,916,917],{},"Tu pourras configurer le débit automatique plus tard si tu le veux. Aujourd'hui, le design « propose en un clic » est le défaut, à dessein.",[40,919,921],{"id":920},"comment-ça-réduit-vraiment-les-no-shows","Comment ça réduit vraiment les no-shows",[11,923,924,925,928,929,932],{},"Le mécanisme n'est pas le débit. Le mécanisme est ",[15,926,927],{},"le moment de friction dans le parcours de réservation lui-même."," Un client qui saisit une carte s'est psychologiquement engagé d'une manière qu'une réservation par e-mail n'a pas. Les données du secteur et nos propres restaurants bêta convergent vers le même chiffre : ",[15,930,931],{},"introduire une politique d'empreinte sur les services primetime réduit les no-shows de 30 à 60 %",", sans baisse mesurable du volume de réservations sur ces mêmes services.",[11,934,935],{},"La carte est un test de crédibilité. Le débit réel est rare. Les restaurants qui adoptent la politique débitent typiquement moins de 2 % des réservations — et même ce petit flux de revenus est significatif quand il couvre une partie du coût de préparation gaspillé en cuisine.",[40,937,939],{"id":938},"où-tablario-stocke-quoi","Où Tablario stocke quoi",[11,941,942,943,946],{},"La carte elle-même est ",[15,944,945],{},"stockée chez Stripe",", sur ton objet Customer Stripe. Tablario ne stocke que l'ID Stripe SetupIntent sur la ligne de réservation. Nous ne loggons ni numéros de carte, ni dates d'expiration, ni CVC, ni BIN. Le portail client Stripe est disponible pour tes clients s'ils veulent retirer leur carte de leur réservation après coup (nous mettons un lien « Gérer votre carte » dans l'e-mail de confirmation). Tous les flux sont conformes PCI-DSS via Stripe, sur infrastructure UE.",[40,948,950],{"id":949},"ce-que-ça-nest-pas","Ce que ça n'est pas",[48,952,953,959,965],{},[51,954,955,958],{},[15,956,957],{},"Pas un plugin de paiement."," C'est un plugin no-show. Il n'y a pas de « payer votre addition via Tablario » aujourd'hui.",[51,960,961,964],{},[15,962,963],{},"Pas un abonnement."," Nous ne stockons pas les cartes au-delà de la réservation. Chaque réservation est un nouveau consentement.",[51,966,967,970],{},[15,968,969],{},"Pas un remplacement de la double confirmation."," Les e-mails de rappel la veille partent toujours. La carte est une assurance ajoutée, pas un remplacement de l'hospitalité.",[40,972,974],{"id":973},"configuration","Configuration",[11,976,977,978,981],{},"Dans l'admin Tablario, ",[15,979,980],{},"Paramètres → Politique de réservation"," :",[180,983,984,987,990,993,996],{},[51,985,986],{},"Choisis un service (ou tous les services).",[51,988,989],{},"Choisis un mode (Aucun \u002F Autorisation carte \u002F Acompte).",[51,991,992],{},"Définis la fenêtre d'annulation (par défaut : 4 heures avant la réservation).",[51,994,995],{},"Définis le montant de débit par couvert.",[51,997,998],{},"En option, restreins à une taille minimale de groupe.",[11,1000,1001],{},"Enregistre. Actif immédiatement. Tu peux changer service par service au fur et à mesure que le profil de ton restaurant évolue.",[11,1003,1004],{},"Si tu n'as pas opté pour la politique, le défaut reste Aucun — Tablario ne te pousse pas agressivement vers un régime de friction. Tu décides.",[204,1006],{},[11,1008,1009],{},[22,1010,1011,1012,1014],{},"Le plugin Booking Policy fait partie de la release Phase 1 de Tablario. Intégration Stripe SetupIntent via la plateforme Stripe Connect ; PCI-DSS géré chez Stripe. Tarifs sur ",[212,1013,214],{},". Le texte de la politique d'annulation est configurable par restaurant en DE\u002FEN\u002FFR.",{"title":217,"searchDepth":218,"depth":218,"links":1016},[1017,1018,1019,1020,1021,1022,1023],{"id":848,"depth":218,"text":849},{"id":882,"depth":218,"text":883},{"id":906,"depth":218,"text":907},{"id":920,"depth":218,"text":921},{"id":938,"depth":218,"text":939},{"id":949,"depth":218,"text":950},{"id":973,"depth":218,"text":974},"Le paiement anticipé fait fuir les clients. Une empreinte bancaire avec politique d'annulation claire stoppe les no-shows sans transformer le restaurant en compagnie aérienne. Le plugin Booking Policy expliqué.","fr",{},"\u002Fblog\u002Fempreinte-bancaire-pas-paiement-anticipe-no-shows",{"title":817,"description":1024},"blog\u002Fempreinte-bancaire-pas-paiement-anticipe-no-shows",[238,1031,240],"politique-reservation","iKD6PgrsaRoRLYbHjVg0mR5QjtFsoGMeTFhG8-oycnI",{"id":1034,"title":1035,"author":6,"body":1036,"date":227,"description":1240,"extension":229,"image":230,"locale":1241,"meta":1242,"navigation":233,"path":1243,"seo":1244,"stem":1245,"tags":1246,"translationKey":241,"__hash__":1248},"blog\u002Fblog\u002Fkarte-hinterlegen-statt-vorkasse-no-shows-reduzieren.md","Karte hinterlegen statt Vorkasse — wie Tablario No-Shows reduziert",{"type":8,"value":1037,"toc":1231},[1038,1044,1051,1061,1064,1068,1071,1090,1097,1101,1104,1111,1114,1121,1125,1132,1135,1139,1150,1153,1157,1164,1168,1188,1192,1198,1215,1218,1221,1223],[11,1039,1040,1041],{},"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,1042,1043],{},"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,1045,1046,1047,1050],{},"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,1048,1049],{},"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,1052,1053,1054,1057,1058],{},"Es gibt einen ruhigeren Mittelweg: ",[15,1055,1056],{},"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,1059,1060],{},"Du bleibst auf der friktionsfreien Spur — bis zu dem Moment, in dem ein Gast dich tatsächlich Geld kostet.",[11,1062,1063],{},"Das macht Tablarios Booking-Policy-Plugin.",[40,1065,1067],{"id":1066},"drei-modi-pro-schicht-wählbar","Drei Modi, pro Schicht wählbar",[11,1069,1070],{},"Booking Policy gibt dir drei Modi, die du pro Schicht, pro Personenzahl, pro Kanal mischen kannst:",[48,1072,1073,1079,1085],{},[51,1074,1075,1078],{},[15,1076,1077],{},"Keine."," Standard. Keine Karte, keine Richtlinie, keine Friktion. Mittagessen am Dienstag, Walk-ins, Stammgäste — aus lassen.",[51,1080,1081,1084],{},[15,1082,1083],{},"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,1086,1087,1089],{},[15,1088,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,1091,1092,1093,1096],{},"Der entscheidende Punkt ist ",[15,1094,1095],{},"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,1098,1100],{"id":1099},"wie-der-gast-es-erlebt","Wie der Gast es erlebt",[11,1102,1103],{},"Wenn eine Kartenautorisierung aktiv ist, bekommt der Buchungsablauf einen zusätzlichen Schritt. Nach Zeit und Personenzahl sieht der Gast:",[84,1105,1106],{},[11,1107,1108],{},[22,1109,1110],{},"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,1112,1113],{},"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,1115,1116,1117,1120],{},"Wenn der Gast drei Tage vorher storniert, passiert nichts. Wenn er zwei Stunden vorher storniert, ",[15,1118,1119],{},"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,1122,1124],{"id":1123},"warum-wir-bewusst-kein-auto-charge-bauen","Warum wir bewusst kein Auto-Charge bauen",[11,1126,1127,1128,1131],{},"Auto-Charge bei No-Show ist technisch eine einzeilige Änderung. Wir haben es nicht gebaut, weil ",[15,1129,1130],{},"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,1133,1134],{},"Auto-Charge kannst du später konfigurieren, wenn du es willst. Heute ist „Klick-zur-Bestätigung\" der Standard, mit Absicht.",[40,1136,1138],{"id":1137},"wie-es-no-shows-tatsächlich-reduziert","Wie es No-Shows tatsächlich reduziert",[11,1140,1141,1142,1145,1146,1149],{},"Der Mechanismus ist nicht die Abbuchung. Der Mechanismus ist ",[15,1143,1144],{},"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,1147,1148],{},"Eine Kartenautorisierung auf Primetime-Schichten reduziert No-Shows um 30–60 Prozent",", ohne messbaren Rückgang des Buchungsvolumens auf diesen Schichten.",[11,1151,1152],{},"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,1154,1156],{"id":1155},"wo-tablario-was-speichert","Wo Tablario was speichert",[11,1158,1159,1160,1163],{},"Die Karte selbst wird ",[15,1161,1162],{},"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,1165,1167],{"id":1166},"was-es-nicht-ist","Was es nicht ist",[48,1169,1170,1176,1182],{},[51,1171,1172,1175],{},[15,1173,1174],{},"Kein Zahlungs-Plugin."," Das ist ein No-Show-Plugin. Es gibt heute kein „Bezahl deine Rechnung über Tablario\". (Siehe: KassenSichV, TSE, Phase 2.)",[51,1177,1178,1181],{},[15,1179,1180],{},"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,1183,1184,1187],{},[15,1185,1186],{},"Kein Ersatz für die Doppelbestätigung."," Erinnerungs-Mails am Vortag laufen weiter. Die Karte ist Zusatzversicherung, kein Ersatz für Gastfreundschaft.",[40,1189,1191],{"id":1190},"konfiguration","Konfiguration",[11,1193,1194,1195,178],{},"Im Tablario-Admin, ",[15,1196,1197],{},"Einstellungen → Buchungsrichtlinie",[180,1199,1200,1203,1206,1209,1212],{},[51,1201,1202],{},"Schicht wählen (oder alle).",[51,1204,1205],{},"Modus wählen (Keine \u002F Karten-Auth \u002F Deposit).",[51,1207,1208],{},"Stornierungsfenster setzen (Standard: 4 Stunden vor der Reservierung).",[51,1210,1211],{},"Betrag pro Person festlegen.",[51,1213,1214],{},"Optional auf Mindestpersonenzahl beschränken.",[11,1216,1217],{},"Speichern. Sofort aktiv. Du kannst es schicht-für-schicht anpassen, wie sich das Muster deines Hauses entwickelt.",[11,1219,1220],{},"Wenn du nicht aktivierst, bleibt der Standard „Keine\" — Tablario drängt dich nicht in ein Friktionsregime. Du entscheidest.",[204,1222],{},[11,1224,1225],{},[22,1226,1227,1228,1230],{},"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,1229,214],{},". Stornierungstexte sind pro Restaurant in DE\u002FEN konfigurierbar.",{"title":217,"searchDepth":218,"depth":218,"links":1232},[1233,1234,1235,1236,1237,1238,1239],{"id":1066,"depth":218,"text":1067},{"id":1099,"depth":218,"text":1100},{"id":1123,"depth":218,"text":1124},{"id":1137,"depth":218,"text":1138},{"id":1155,"depth":218,"text":1156},{"id":1166,"depth":218,"text":1167},{"id":1190,"depth":218,"text":1191},"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":1035,"description":1240},"blog\u002Fkarte-hinterlegen-statt-vorkasse-no-shows-reduzieren",[238,1247,240],"buchungsrichtlinie","YP17GgLiY7UG5Xd6_gcnBMO7TPGrcUc6rpcccsVAfaI",[1250,1389,1705],{"id":4,"title":5,"author":6,"body":1251,"date":227,"description":228,"extension":229,"image":230,"locale":231,"meta":1386,"navigation":233,"path":234,"seo":1387,"stem":236,"tags":1388,"translationKey":241,"__hash__":242},{"type":8,"value":1252,"toc":1377},[1253,1257,1261,1267,1269,1271,1273,1287,1291,1293,1295,1301,1303,1307,1309,1313,1315,1317,1323,1325,1327,1331,1333,1347,1349,1353,1365,1367,1369,1371],[11,1254,13,1255],{},[15,1256,17],{},[11,1258,20,1259,25],{},[22,1260,24],{},[11,1262,28,1263,32,1265],{},[15,1264,31],{},[15,1266,35],{},[11,1268,38],{},[40,1270,43],{"id":42},[11,1272,46],{},[48,1274,1275,1279,1283],{},[51,1276,1277,56],{},[15,1278,55],{},[51,1280,1281,62],{},[15,1282,61],{},[51,1284,1285,68],{},[15,1286,67],{},[11,1288,71,1289,75],{},[15,1290,74],{},[40,1292,79],{"id":78},[11,1294,82],{},[84,1296,1297],{},[11,1298,1299],{},[22,1300,90],{},[11,1302,93],{},[11,1304,96,1305,100],{},[15,1306,99],{},[40,1308,104],{"id":103},[11,1310,107,1311,111],{},[15,1312,110],{},[11,1314,114],{},[40,1316,118],{"id":117},[11,1318,121,1319,125,1321,129],{},[15,1320,124],{},[15,1322,128],{},[11,1324,132],{},[40,1326,136],{"id":135},[11,1328,139,1329,143],{},[15,1330,142],{},[40,1332,147],{"id":146},[48,1334,1335,1339,1343],{},[51,1336,1337,155],{},[15,1338,154],{},[51,1340,1341,161],{},[15,1342,160],{},[51,1344,1345,167],{},[15,1346,166],{},[40,1348,171],{"id":170},[11,1350,174,1351,178],{},[15,1352,177],{},[180,1354,1355,1357,1359,1361,1363],{},[51,1356,184],{},[51,1358,187],{},[51,1360,190],{},[51,1362,193],{},[51,1364,196],{},[11,1366,199],{},[11,1368,202],{},[204,1370],{},[11,1372,1373],{},[22,1374,210,1375,215],{},[212,1376,214],{},{"title":217,"searchDepth":218,"depth":218,"links":1378},[1379,1380,1381,1382,1383,1384,1385],{"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":1390,"title":1391,"author":6,"body":1392,"date":1693,"description":1694,"extension":229,"image":230,"locale":231,"meta":1695,"navigation":233,"path":1696,"seo":1697,"stem":1698,"tags":1699,"translationKey":1703,"__hash__":1704},"blog\u002Fblog\u002Frestaurant-table-management-software-12-percent-more-covers.md","Restaurant table management software: how table-combinations add 12% covers in the same room",{"type":8,"value":1393,"toc":1676},[1394,1401,1408,1412,1415,1426,1437,1441,1444,1449,1452,1456,1459,1463,1470,1478,1481,1492,1495,1513,1520,1524,1527,1533,1536,1556,1563,1567,1570,1590,1603,1607,1610,1630,1634,1637,1657,1669,1671],[11,1395,1396,1397,1400],{},"Most restaurant table management software does the obvious thing: it lets you draw a floor plan and shows you which tables are reserved. That is the table-stakes. The actual ceiling on revenue in an independent restaurant is not whether the floor plan is digital — it is whether the software helps you say ",[15,1398,1399],{},"yes"," to one more party of six on a Friday night.",[11,1402,1403,1404,1407],{},"This post walks through what to look for in 2026, where most products plateau, and why Tablario's automatic table-combination logic adds a measurable ",[15,1405,1406],{},"8 to 12 percent in covers"," for the same room.",[40,1409,1411],{"id":1410},"the-structural-problem-tables-vs-parties","The structural problem: tables vs. parties",[11,1413,1414],{},"Run a quick mental audit on your last Saturday service. How many of these did you say no to?",[48,1416,1417,1420,1423],{},[51,1418,1419],{},"A party of six asking for 7 PM. You have plenty of free tables — just none for six.",[51,1421,1422],{},"A solo guest asking for the bar at 8 PM. You have plenty of bar space, but only two-tops were booked.",[51,1424,1425],{},"A group of eight at 9 PM. You have two free four-tops next to each other. Nobody mentally connected them in time.",[11,1427,1428,1429,1432,1433,1436],{},"Independents lose more revenue to ",[15,1430,1431],{},"shape mismatch"," than to actual capacity. The most common party size is two or four; the most common rejection is six or eight. The fix is not \"buy more tables\" — most floor plans are already maxed out spatially. The fix is ",[22,1434,1435],{},"recombining what you have",".",[40,1438,1440],{"id":1439},"what-table-management-software-should-actually-do-in-2026","What \"table management software\" should actually do in 2026",[11,1442,1443],{},"Five capabilities that separate a real tool from a glorified spreadsheet:",[1445,1446,1448],"h3",{"id":1447},"_1-drag-and-drop-floor-plan-that-mirrors-reality","1. Drag-and-drop floor plan that mirrors reality",[11,1450,1451],{},"If your floor plan can't represent a patio, a bar, two dining rooms, and a private back room — each with their own service rhythm — you will end up running them in your head anyway. Look for shape-accurate tables (round, square, banquette), explicit room boundaries, and per-room shift configuration. Tablario stores per-room service lengths so a 90-minute lunch turn in the main room can coexist with a 2.5-hour tasting menu in the back.",[1445,1453,1455],{"id":1454},"_2-live-status-per-table-not-is-it-reserved-but-is-it-being-used-right-now","2. Live status per table — not \"is it reserved\", but \"is it being used right now\"",[11,1457,1458],{},"Reservation status (free \u002F booked \u002F arrived \u002F seated \u002F departed) on a tablet in the service area changes what the host can do at the door. Without live status, every walk-in question turns into a phone-down-the-line whisper. With it, the host answers in two seconds.",[1445,1460,1462],{"id":1461},"_3-capacity-logic-with-service-lengths-and-buffer-times","3. Capacity logic with service lengths and buffer times",[11,1464,1465,1466,1469],{},"A 7 PM booking for 2 hours does not block the table until midnight, and not until 9 PM either. It blocks the table until 9:15 PM if you set a 15-minute buffer. The software should compute this automatically per shift — and it should accept your ",[22,1467,1468],{},"actual"," service lengths, not a fixed 120 minutes globally.",[1445,1471,1473,1474,1477],{"id":1472},"_4-automatic-table-combinations-the-differentiator","4. ",[15,1475,1476],{},"Automatic table combinations"," — the differentiator",[11,1479,1480],{},"This is where most products stop and Tablario starts.",[11,1482,1483,1484,1487,1488,1491],{},"The premise is simple: you tell the system once which tables are ",[22,1485,1486],{},"physically joinable"," — T3 (4-top) + T4 (4-top) = a single 8-top, with both halves removed from the inventory while they're combined. When a request for six or eight people comes in and no native six-top or eight-top is free, the system ",[22,1489,1490],{},"checks the combinable pairs"," in real time. If T3 and T4 are both free in the same time window, it offers the combination. You tap \"accept\".",[11,1493,1494],{},"Two things matter about the implementation:",[48,1496,1497,1503],{},[51,1498,1499,1502],{},[15,1500,1501],{},"Reversal logic."," If you accept the 8-top combination, the two 4-tops become unavailable as 4-tops — automatically. No double-booking risk. When the combined party leaves and the buffer expires, both tables go back into the 4-top pool.",[51,1504,1505,1508,1509,1512],{},[15,1506,1507],{},"Suggestion, not auto-action."," The system ",[22,1510,1511],{},"offers","; you confirm. Restaurants are not factories — the host should always have the option to say no.",[11,1514,1515,1516,1519],{},"In our beta program, restaurants enabling automatic table combinations added ",[15,1517,1518],{},"8 to 12 percent more covers per week",", sustained over multiple months. The mechanism is not magic; it is a 30-second mental check the algorithm runs 300 times per shift, that no human is going to run reliably during service.",[1445,1521,1523],{"id":1522},"_5-multi-location-single-screen","5. Multi-location, single screen",[11,1525,1526],{},"If you run two or more restaurants, the back office should show occupancy across all locations on one screen — without you logging in and out. Even single-location operators benefit from this when they open a second site; the migration is the painful part, not the operation.",[40,1528,1530,1531],{"id":1529},"what-table-management-software-is-not","What table management software is ",[22,1532,24],{},[11,1534,1535],{},"A frequent over-promise: \"AI for everything\". In reality:",[48,1537,1538,1544,1550],{},[51,1539,1540,1543],{},[15,1541,1542],{},"Predictive scheduling"," (which servers to put on Saturday based on weather) is real but requires 12–18 months of clean data and only works for operations with stable staff rotations.",[51,1545,1546,1549],{},[15,1547,1548],{},"Dynamic pricing"," of cover charges or deposits is technically possible (most reservation platforms support it) but consumer-side acceptance in DACH and EU markets is still cold.",[51,1551,1552,1555],{},[15,1553,1554],{},"Auto-confirmation of marketing emails"," is a different product (CRM \u002F marketing automation), not table management.",[11,1557,1558,1559,1562],{},"Pick a tool that does ",[15,1560,1561],{},"table management"," well first, and adds extensions later. A product that promises everything tends to be average at all of it.",[40,1564,1566],{"id":1565},"how-tablario-compares-to-the-market","How Tablario compares to the market",[11,1568,1569],{},"Three honest comparisons:",[48,1571,1572,1578,1584],{},[51,1573,1574,1577],{},[15,1575,1576],{},"vs. OpenTable \u002F TheFork:"," They handle the discovery channel (their marketplace), not the operations layer. Most operators end up running OpenTable + a separate floor-plan tool. Tablario does both, with no per-cover commission.",[51,1579,1580,1583],{},[15,1581,1582],{},"vs. resmio \u002F Zenchef:"," Both have solid floor plans. Neither offers built-in automatic table-combination logic at the time of writing (May 2026) — you simulate it by manually marking combinable tables and double-booking, with the corresponding risk.",[51,1585,1586,1589],{},[15,1587,1588],{},"vs. SevenRooms:"," SevenRooms targets fine-dining groups with $499+ pricing and no DACH presence. Different segment.",[11,1591,1592,1593,1598,1599,1436],{},"If you operate an independent restaurant in DACH or the EU, the realistic shortlist is Tablario, resmio, Zenchef, or aleno. For per-cover economics, ",[1594,1595,1597],"a",{"href":1596},"\u002Fen\u002Fpricing","see our pricing page","; for the automatic-combination logic specifically, ",[1594,1600,1602],{"href":1601},"\u002Fen\u002Ffeatures\u002Ftable-management","see the table management feature page",[40,1604,1606],{"id":1605},"what-to-ask-in-a-vendor-demo","What to ask in a vendor demo",[11,1608,1609],{},"Three questions that quickly separate marketing copy from substance:",[180,1611,1612,1618,1624],{},[51,1613,1614,1617],{},[22,1615,1616],{},"\"Show me what happens when a six-top request comes in and no six-top is free, but two free three-tops are nearby.\""," If the system can't offer the combination automatically, the operations savings will be smaller than the brochure suggests.",[51,1619,1620,1623],{},[22,1621,1622],{},"\"What's the data export format if I want to leave?\""," GDPR requires structured machine-readable export. A vendor that hesitates here is signalling lock-in.",[51,1625,1626,1629],{},[22,1627,1628],{},"\"What does your AI phone agent say at the start of a call?\""," From August 2, 2026 (EU AI Act Article 50), AI use must be disclosed audibly. A vendor that doesn't have a clean answer is a compliance risk.",[40,1631,1633],{"id":1632},"what-to-do-this-month","What to do this month",[11,1635,1636],{},"If you're evaluating now:",[180,1638,1639,1645,1651],{},[51,1640,1641,1644],{},[15,1642,1643],{},"Audit your current Saturday."," Count the parties you turned away due to shape mismatch, not capacity. That is the real opportunity size.",[51,1646,1647,1650],{},[15,1648,1649],{},"Run a parallel trial."," Most reservation systems offer 14- to 30-day free trials. Don't pick on the demo — pick on a real weekend.",[51,1652,1653,1656],{},[15,1654,1655],{},"Verify migration speed."," \"We can have you live in 24 hours\" should mean importing real guest history, not just creating an empty account. Ask for a reference customer who migrated in the last 90 days.",[11,1658,1659,1660,1663,1664,1668],{},"If you want to see what automatic table-combinations look like in practice, the ",[1594,1661,1662],{"href":1601},"Tablario table management page"," shows a live mockup, or you can ",[1594,1665,1667],{"href":1666},"\u002Fen\u002Fdemo","book a 15-minute call"," and we'll walk through it on your own floor plan.",[204,1670],{},[11,1672,1673],{},[22,1674,1675],{},"Sources: Tablario beta program operational data, 2025–2026 · DEHOGA capacity utilisation surveys, 2024 · OpenTable State of the Industry, 2025.",{"title":217,"searchDepth":218,"depth":218,"links":1677},[1678,1679,1688,1690,1691,1692],{"id":1410,"depth":218,"text":1411},{"id":1439,"depth":218,"text":1440,"children":1680},[1681,1683,1684,1685,1687],{"id":1447,"depth":1682,"text":1448},3,{"id":1454,"depth":1682,"text":1455},{"id":1461,"depth":1682,"text":1462},{"id":1472,"depth":1682,"text":1686},"4. Automatic table combinations — the differentiator",{"id":1522,"depth":1682,"text":1523},{"id":1529,"depth":218,"text":1689},"What table management software is not",{"id":1565,"depth":218,"text":1566},{"id":1605,"depth":218,"text":1606},{"id":1632,"depth":218,"text":1633},"2026-05-14","A practical guide to picking restaurant table management software in 2026 — what real differentiators look like, why automatic table-combinations matter, and how independents add 8 to 12% more covers without adding tables.",{},"\u002Fblog\u002Frestaurant-table-management-software-12-percent-more-covers",{"title":1391,"description":1694},"blog\u002Frestaurant-table-management-software-12-percent-more-covers",[1700,1701,1702],"table-management","reservations","operations","table-management-12-percent","UCFyW0_aMRY7vP6YArm-oTTni9NE1DTDQLs7a1zkdZE",{"id":1706,"title":1707,"author":6,"body":1708,"date":2042,"description":2043,"extension":229,"image":230,"locale":231,"meta":2044,"navigation":233,"path":2045,"seo":2046,"stem":2047,"tags":2048,"translationKey":2052,"__hash__":2053},"blog\u002Fblog\u002Fno-show-fee-restaurant-legally-compliant-2026.md","No-show fees for restaurants: legally compliant in the EU and UK in 2026",{"type":8,"value":1709,"toc":2033},[1710,1721,1728,1732,1743,1757,1760,1794,1798,1801,1806,1809,1831,1835,1842,1853,1868,1875,1895,1899,1902,1926,1930,1933,1959,1963,1966,1998,2002,2008,2014,2020,2026,2028],[11,1711,1712,1713,1716,1717,1720],{},"A no-show is not \"annoying\" for an independent restaurant — it is a direct loss. Industry surveys put no-show rates in DACH and Western Europe at ",[15,1714,1715],{},"5 to 15 percent"," of all reservations, depending on location and segment. At an average ticket of €50 per guest and 600 covers per month, that is ",[15,1718,1719],{},"€1,500 to €4,500 in lost margin"," — every single month.",[11,1722,1723,1724,1727],{},"Most restaurants know the problem. Few know the legally-clean answer. This post explains ",[15,1725,1726],{},"how to set up a no-show fee in 2026"," so it survives a small-claims dispute and stays GDPR-compliant.",[40,1729,1731],{"id":1730},"what-a-no-show-fee-actually-is-legally","What a no-show fee actually is, legally",[11,1733,1734,1735,1738,1739,1742],{},"A no-show fee is ",[15,1736,1737],{},"not a penalty"," — it is a claim for damages or a ",[15,1740,1741],{},"liquidated, lump-sum compensation"," for the operator's actual loss. The distinction is not academic: penalty clauses are scrutinised harder than damages clauses in nearly every EU jurisdiction.",[11,1744,1745,1746,1749,1750,1753,1754,1436],{},"In the UK, the framework is the ",[15,1747,1748],{},"Consumer Rights Act 2015"," plus the older Unfair Terms in Consumer Contracts Regulations — the clause must be \"transparent\" and represent a \"genuine pre-estimate of loss.\" In Germany, the equivalent hooks are §§ 280 + 309 No. 5 BGB. In France, art. 1231-5 of the Code civil treats it as a ",[22,1751,1752],{},"clause pénale",", which the court may reduce if manifestly excessive. The substance is the same everywhere: ",[15,1755,1756],{},"realistic amount + clear disclosure + opt-in by the guest",[11,1758,1759],{},"A workable clause needs four elements:",[180,1761,1762,1768,1778,1788],{},[51,1763,1764,1767],{},[15,1765,1766],{},"Explicit T&Cs"," on the booking page that the guest must actively accept (checkbox).",[51,1769,1770,1773,1774,1777],{},[15,1771,1772],{},"Realistic amount"," — the comfortable range across EU jurisdictions is ",[15,1775,1776],{},"€15 to €25 per person",". Higher figures are routinely struck down as penalties.",[51,1779,1780,1783,1784,1787],{},[15,1781,1782],{},"A clear cancellation window"," — typically ",[15,1785,1786],{},"24 hours before the reservation",". Cancellations earlier than that incur no fee.",[51,1789,1790,1793],{},[15,1791,1792],{},"An express right for the guest to prove the actual loss was lower"," — this is mandatory in most EU consumer law frameworks (in Germany under § 309 No. 5b BGB; an equivalent rule exists in nearly every member state).",[40,1795,1797],{"id":1796},"template-clause-for-booking-tcs","Template clause for booking T&Cs",[11,1799,1800],{},"The text below is a starting point; we recommend a short review by a local lawyer in your market:",[84,1802,1803],{},[11,1804,1805],{},"If the guest fails to appear without cancelling at least 24 hours before the reserved time, or does not honour the reservation, the restaurant will charge a flat compensation of €20 per reserved person. The compensation is a lump-sum estimate of the damage caused by the no-show (lost table capacity, prepared food, scheduled staff). The guest reserves the right to prove that no damage occurred or that the actual damage was substantially lower.",[11,1807,1808],{},"Three details are non-negotiable across jurisdictions:",[48,1810,1811,1818,1824],{},[51,1812,1813,1814,1817],{},"The word ",[15,1815,1816],{},"\"compensation\""," (not \"fine\" or \"penalty\") — the term you use steers the legal classification.",[51,1819,1820,1823],{},[15,1821,1822],{},"\"Lump-sum estimate\""," keeps the clause out of the penalty-clause regime.",[51,1825,1826,1827,1830],{},"The ",[15,1828,1829],{},"express right to prove a lower actual loss"," is mandatory in most EU consumer-protection statutes; without it the clause is unenforceable.",[40,1832,1834],{"id":1833},"implementation-card-on-file-not-pre-payment","Implementation: card-on-file, not pre-payment",[11,1836,1837,1838,1841],{},"The most effective technical form is ",[15,1839,1840],{},"card-on-file",": the guest stores a card at booking; the restaurant charges it only in the no-show case — no pre-payment, no cash tied up on the guest side.",[11,1843,1844,1845,1848,1849,1852],{},"Tablario uses ",[15,1846,1847],{},"Stripe Connect"," with the ",[212,1850,1851],{},"setup_intent"," flow:",[180,1854,1855,1858,1865],{},[51,1856,1857],{},"At booking, the card is verified; nothing is charged.",[51,1859,1860,1861,1864],{},"Stripe stores a reusable Payment Method on the ",[15,1862,1863],{},"restaurant's own Stripe Connect account"," — not on a Tablario master account. This is PCI-DSS-clean and GDPR-clean.",[51,1866,1867],{},"If the guest no-shows and the restaurant confirms the no-show in the Tablario back office, the compensation is charged. The guest receives an automated email with the receipt and dispute instructions.",[11,1869,1870,1871,1874],{},"Why not ",[15,1872,1873],{},"pre-payment","? Three practical reasons:",[48,1876,1877,1883,1889],{},[51,1878,1879,1882],{},[15,1880,1881],{},"Conversion killer."," Pre-payment measurably drops booking-widget conversion — by 18 to 24 percent in our beta tests.",[51,1884,1885,1888],{},[15,1886,1887],{},"Admin overhead."," Every legitimate cancellation requires an active refund.",[51,1890,1891,1894],{},[15,1892,1893],{},"Trust signal."," Pre-payment signals distrust. Card-on-file is neutral: \"We trust you, but we are covered for the rare exception.\"",[40,1896,1898],{"id":1897},"gdpr-what-to-watch-when-storing-a-card","GDPR: what to watch when storing a card",[11,1900,1901],{},"The General Data Protection Regulation imposes three requirements:",[180,1903,1904,1914,1920],{},[51,1905,1906,1909,1910,1913],{},[15,1907,1908],{},"Legal basis."," The card storage is justified by ",[15,1911,1912],{},"performance of the contract"," (Art. 6(1)(b) GDPR) — the booking is the contract, the card is the security for the potential compensation.",[51,1915,1916,1919],{},[15,1917,1918],{},"Data minimisation."," Tablario stores no card data locally — only a Stripe token. The actual PAN data lives only at Stripe (PCI-DSS Level 1).",[51,1921,1922,1925],{},[15,1923,1924],{},"Access and deletion rights."," Once the reservation is closed (guest arrived or cancelled in time), the Stripe setup intent expires or is deleted automatically. Tablario does this per booking — there is no \"card stored for 12 months\".",[40,1927,1929],{"id":1928},"when-a-no-show-fee-makes-sense-in-practice","When a no-show fee makes sense in practice",[11,1931,1932],{},"Not every restaurant needs the fee. Our pragmatic guideline:",[48,1934,1935,1941,1947,1953],{},[51,1936,1937,1940],{},[15,1938,1939],{},"Bistro \u002F casual dining (\u003C €30 ticket):"," no-show rate under 5 % — usually not worth the setup; the conversion hit dominates.",[51,1942,1943,1946],{},[15,1944,1945],{},"Mid-range restaurant (€30 – €70 ticket):"," no-show rate 5 – 10 % — card-on-file from group size 6 pays off.",[51,1948,1949,1952],{},[15,1950,1951],{},"Fine dining \u002F tasting menu (> €70 ticket):"," no-show rate often > 10 % — card-on-file from group size 2, plus a deposit for groups of 8+.",[51,1954,1955,1958],{},[15,1956,1957],{},"Event reservations (NYE, Valentine's, Mother's Day):"," always secured, regardless of usual ticket — that table time is not replaceable.",[40,1960,1962],{"id":1961},"what-tablarios-no-show-protection-module-ships-with","What Tablario's no-show protection module ships with",[11,1964,1965],{},"The Tablario no-show protection plugin (€14 \u002F month) includes:",[48,1967,1968,1974,1980,1986,1992],{},[51,1969,1970,1973],{},[15,1971,1972],{},"Card-on-file via Stripe Connect"," — the restaurant is the recipient of the compensation, not Tablario.",[51,1975,1976,1979],{},[15,1977,1978],{},"Threshold configuration"," — per shift, group size, or reservation value.",[51,1981,1982,1985],{},[15,1983,1984],{},"Automated 24-hour reminder SMS \u002F email"," — the single largest no-show reduction lever (industry studies put it at up to 60 % fewer no-shows just from automated reminders).",[51,1987,1988,1991],{},[15,1989,1990],{},"Legally vetted T&Cs template"," — you do not write it yourself; the template above ships with the module.",[51,1993,1994,1997],{},[15,1995,1996],{},"Audit log"," — every charge is recorded with reason, timestamp and Stripe charge ID, in case the guest later disputes.",[40,1999,2001],{"id":2000},"frequently-asked-questions","Frequently asked questions",[11,2003,2004,2007],{},[15,2005,2006],{},"Do we need to see the guest's card?","\nNo. Stripe Elements renders the card field iframe-based; the data goes from the browser session directly to Stripe, not through Tablario or the restaurant. You only see the last four digits.",[11,2009,2010,2013],{},[15,2011,2012],{},"What if the guest disputes?","\nThe Stripe charge can be refunded by the restaurant within 14 days. In a formal chargeback, Stripe investigates; the T&Cs clause plus the audit log are the strongest evidence.",[11,2015,2016,2019],{},[15,2017,2018],{},"Does this apply outside the EU?","\nThe logic (lump-sum damages estimate, express right to prove lower loss) is recognised in nearly every common-law and civil-law jurisdiction. The statutory hooks differ (Consumer Rights Act in the UK, Restatement (Second) of Contracts § 356 in the US). The technical implementation is identical.",[11,2021,2022,2025],{},[15,2023,2024],{},"Does the fee actually lower the no-show rate, or only recover the loss?","\nBoth. Industry data (DEHOGA, OpenTable) shows that simply communicating that a fee exists lowers no-show rates by 30 to 50 %. The actual charge is rarely triggered.",[204,2027],{},[11,2029,2030],{},[22,2031,2032],{},"Sources: German Civil Code (§§ 280, 309 BGB) · UK Consumer Rights Act 2015 · French Code civil art. 1231-5 · GDPR Art. 6 · Stripe Connect documentation (developer.stripe.com).",{"title":217,"searchDepth":218,"depth":218,"links":2034},[2035,2036,2037,2038,2039,2040,2041],{"id":1730,"depth":218,"text":1731},{"id":1796,"depth":218,"text":1797},{"id":1833,"depth":218,"text":1834},{"id":1897,"depth":218,"text":1898},{"id":1928,"depth":218,"text":1929},{"id":1961,"depth":218,"text":1962},{"id":2000,"depth":218,"text":2001},"2026-05-12","How independent restaurants in the EU and UK can charge no-show fees that stand up in court in 2026 — from the booking T&Cs clause to the Stripe card-on-file flow. Practical guide with template wording and a GDPR-clean implementation.",{},"\u002Fblog\u002Fno-show-fee-restaurant-legally-compliant-2026",{"title":1707,"description":2043},"blog\u002Fno-show-fee-restaurant-legally-compliant-2026",[2049,2050,2051],"no-show","compliance","deposits","no-show-fee-de","dX9KERn6dKnU8kkRS1Q_HioOKRVrTwvopsZOYMvMjSk",1783674834855]