Can Taiwan Restaurants Forfeit a Deposit in Full? 5 Compliance Designs (with Template) — 2026

In 2026, what happens if a Taiwan restaurant gets sued over a forfeited deposit?

A recent news case sent chills through small restaurant owners in Taiwan: a customer drove three hours to a restaurant, arrived 5 minutes late due to parking, and the restaurant forfeited nearly NT$8,000 of deposit. The customer filed a complaint with the Consumer Protection Council; a lawyer went public to back the consumer; the restaurant got slammed on social media.

Reading the lawyer's argument it's easy to misread the verdict: "OK so charging deposits is illegal, no clauses allowed." That's not the actual answer.

For independent restaurants, deposits are one of the few real tools to control no-shows. Abandoning them entirely means absorbing all operating risk yourself. But if your clauses are designed wrong, you'll lose the Consumer Protection Council case AND take a brand hit. This piece walks through 5 compliance-design principles for owners, plus a usable clause template and three common dispute scenarios — so you collect the deposit AND hold legal ground.

The legal reality: what you can't write vs what you can

What you can't write (will be voided)

Consumer Protection Act Article 12: "Clauses in standard-form contracts that violate good faith and are manifestly unfair to the consumer are void." Combined with Civil Code Article 249 on deposit refund rules, these are the lawyer's go-to weapons against restaurants.

These clauses are voided ~90% of the time:

• "Late arrival = full reservation cancelled, deposit forfeited" — courts widely see this as disproportionate
• "If even one person from the party is absent, entire reservation cancelled, deposit forfeited" — 4 becomes 3 and you lose everything? Unbalanced
• "Final interpretation rests with the restaurant" / "Restaurant retains final decision rights" — explicit "tyrant clause" prohibited by Consumer Protection Act
• "Deposit non-refundable under any circumstances" — no carve-outs (cancellation window, damage calculation) violates Civil Code 249

What you can write (compliant and effective)

• "Deposit deducted in proportion to actual damages" — proportional model aligns with Civil Code 249
• "Cancellations require X-hour notice; otherwise deposit credits toward meal" — advance notice + credit (not forfeiture)
• "After X minutes of no-show, reservation auto-cancelled; deposit transferable to a future booking" — structured flexibility
• "Force majeure (natural disaster / major traffic incident / sudden illness) → full refund" — reserves a humane exit

The question is never "can I charge a deposit?" — it's "can I forfeit the full deposit?" Flexible designs hold up; "one-size-fits-all" clauses don't.

Why you still need to charge: the operational reality

Customers often complain "why does a restaurant need a deposit, do you not trust me?" From the owner's side the answer is straight:

• Real no-show cost: small restaurants in Taiwan lose 5–15% of monthly revenue to no-shows; weekend evening peaks hit 20–30%. Pure trust-based booking = pushing all financial risk onto yourself
• Ingredient prep risk: tasting-menu / prix-fixe restaurants prep ingredients per reservation count. No-show = direct food waste
• Table opportunity cost: peak slot table can be worth NT$3,000–8,000 in revenue. A no-show seat means you also turned away paying walk-ins
• Staffing cost: floor + kitchen are scheduled to expected volume. 20 reservations down to 10 means half the labor was wasted

One concrete example: a 40-seat restaurant with NT$800 ATV cutting no-shows from 20% → 5% recovers NT$90,000–120,000/month. Run your own numbers with our no-show loss calculator.

That's why deposits exist — not distrust, but signal-filtering the customers who'll actually show up. For the deeper tactical playbook see 5 strategies to reduce restaurant no-shows.

5 compliance-design principles

1. Deposit amount: design by restaurant type

Many assume "there's a statutory percentage cap" — for ordinary restaurant reservations, there isn't. Consumer Protection Act Article 12 regulates only "manifest unfairness" — no specific percentage. In Taiwan today 50%, even 100% prepayment is mainstream. The key isn't how much you charge — it's "the higher the deposit, the more complete the supporting design".

Industry ranges by restaurant type:

• Regular dine-in (single-table booking): NT$200–500 per person, or 10–20% of total
• Chef's table / tasting menu / high-ticket reservation-only: 20–50% of total (prep + labor cost justifiable)
• Special events / holiday-limited / collab seatings: 50–100% prepayment is common in Taiwan, provided you have reasonable cancellation policy + reschedule / transfer mechanism

Exception: banquet / catering / 訂席 services are subject to the Ministry of Health's "Mandatory and Prohibited Provisions of Standard-Form Contracts for Banquet & Catering Services" — 20% statutory cap. Doesn't apply to regular restaurant reservations, but worth knowing.

100% prepayment + free cancellation up to 7 days before is safer and more court-defensible than 30% + "no refunds ever". Full legal basis and percentage benchmarks available in the deep-dive guide.

2. Proportional deduction, not "all-or-nothing"

Design cancellation policies as a tier, not a binary. Example:

• 48+ hours before: full refund
• 24–48 hours: 50% deducted
• Within 24 hours / no-show: 100% deducted

This pattern follows the "proportional calculation" spirit of Civil Code Article 249 and is widely upheld by courts.

3. Clear disclosure, not buried small print

The deposit policy must be communicated before the customer commits, and must be "clear":

• Prominently shown during the reservation flow (not footer fine print)
• Requires checkbox consent to complete booking

Transparent disclosure within the booking flow is enough. The Consumer Protection Act test for "manifest unfairness" looks at "whether the customer had a chance to review pre-booking" — the booking page satisfies this.

4. Reserve room for exceptions

Force majeure must be written in: natural disasters (typhoon, earthquake), major traffic incidents, sudden illness (with proof). These refunds look like a loss, but in practice:

• Brand reputation protected
• Consumer-council complaints sharply lower
• Customer remembers "this restaurant is reasonable" → return rate up

Handle case-by-case via mutual discussion. Don't require documentation — demanding a doctor's certificate or police report is too rigid and damages brand goodwill. Suggested wording: "For force majeure events (natural disaster, major traffic incident, sudden illness), reschedule or refund may be applied for, subject to the restaurant's reasonable case-by-case judgment." Keeps flexibility for both sides.

5. Records management: paper-trail every deposit transaction

If the Consumer Protection Council comes knocking, the burden of proof is on you. You must show:

• Customer saw and consented to terms before booking (screenshot / system log)
• Customer's actual breach (no-show timestamp / contact log)
• Your deduction amount is reasonable (food cost / opportunity cost estimate)

Manual LINE deposit collection is the biggest weakness here — no structured records. Once a dispute hits, you have nothing to show. A reservation system's value here is precisely automatic record-keeping.

Usable deposit clause template (reference version)

Generic template for a typical restaurant. Reference version only — have your retained legal counsel review before going live:

Reservation Deposit Policy

1. Reservations require an upfront deposit of NT$200 per person (or 10% of estimated total spend). Fully credited toward the meal upon arrival.

2. Cancellation:

• 48+ hours before meal: full refund
• 24–48 hours: 50% deducted
• Within 24 hours / no-show / arrival 15+ minutes late: deposit deducted up to actual damages (max 100%)

3. Force majeure (natural disaster, major traffic incident, sudden illness): reschedule or refund subject to restaurant's reasonable judgment.

4. Damage calculation: includes pre-purchased ingredients, table opportunity cost, staff scheduling cost. If actual damages are lower than deposit, the difference is refunded.

5. Party-size changes: adjustable for free up to 24 hours before; later changes of more than 1 person counted as partial cancellation per the policy above.

Key: proportional + credit-based + exception-handling + transparent disclosure. Every line covers a point a lawyer would attack.

3 common dispute scenarios + prevention

Scenario A: Customer 5–15 minutes late

Consumer Protection rulings lean against full forfeiture for short delays. Practical approach:

• 0–10 min late: seat normally, deposit credits the bill (no loss)
• 10–30 min late: hold the table but inform customer it may go to waitlist; deposit credits the bill
• 30+ min late: treat as no-show; apply cancellation policy (100% deduct within 24h)

Pair with automated reminders (24h + 2h pre-arrival LINE / SMS) to cut down on lateness disputes.

Scenario B: 6-person booking arrives with 4

"Entire reservation cancelled" loses in court. Reasonable handling:

• 24+ hours notice on party-size change: free adjustment
• Same-day or on-arrival notice: per-head proportional deduction (e.g., NT$1,200 deposit, -2 heads = -NT$400); remaining 4 dine normally

Reasonable flexibility wins return customers; rigid rules don't.

Scenario C: Customer claims traffic, demands full refund

"Traffic" usually doesn't qualify as "force majeure" (unless major public-incident bulletin). Handling:

• Customer contacts pre-arrival: try to hold the table; deposit transferable to next booking or normal seating
• Post-event complaint of "should be fully refunded": cite the policy, provide the screenshot of cancellation rules and customer's prior consent

Structured records save you here.

Bottom line: deposits are a safety net, not a punishment

The real question isn't "should we charge a deposit?" — it's "how do we design it so customers don't feel ripped off and you sleep at night?"

5 principles recap:

1. 5–15% practical range; no statutory cap for regular restaurants
2. Proportional deduction, not "all-or-nothing"
3. Clear disclosure, not buried small print
4. Reserve space for force-majeure exceptions
5. Structured per-transaction records

All five together → near-zero Consumer Protection Council exposure. Customers register "this restaurant is fair" — deposit becomes a trust signal, not a dispute source.

If your booking flow is still "LINE collection + Excel log," records management is your biggest exposure. Eatsy's reservation system bakes in deposit collection + cancellation-policy display + automatic consent logging + breach evidence archiving. Pay-as-you-go, no contract — compliant records from the very first booking.

Compliance isn't a luxury — it's the floor that turns "customer disputes" into "repeat reservations."

📖 The other side: curious how consumers view deposit rules? See our Consumer Rights Guide for Restaurant Deposits. Knowing both perspectives prevents one-sided clauses.