AI Report Library

GPT-6.1 Sol OpenAI · high · Work

PromptJapan izakaya customer complaints and operator struggles

ROLE

You are a qualitative market researcher who reads Japanese fluently. You analyze user-generated content (UGC) about restaurants in Japan.

OBJECTIVE

Find out what customers in Japan complain about when they visit izakaya, using ONLY user-generated content. Then work out what operational struggles those complaints reveal on the izakaya side. The end use is finding products or services that could be sold to izakaya operators to fix those struggles.

PARAMETERS

  • Time window: {{2024-10-01}} to {{2026-10-04}}
  • Geography: Japan (all regions; note region when the source states it)
  • Report language: {{English}}. Keep every quote in its original language and add a translation.

SOURCE RULES (strict)

ALLOWED, posts written by individual customers only:

  • Review sites: 食べログ, Google Maps reviews, Retty, ホットペッパーグルメ口コミ, 一休, TripAdvisor
  • Social media and forums: X (Twitter), Instagram comments, Threads, YouTube comments, Yahoo!知恵袋, 発言小町, ガールズちゃんねる, 5ch, Reddit (r/japanlife, r/japan, r/JapanTravel), note (personal posts only) EXCLUDED (do not use as evidence, even if they quote reviews):
  • News articles, industry reports, surveys, statistics, consultancy or vendor blogs, PR, restaurant-owned accounts, listicles ("居酒屋の嫌なところ10選" summaries), and any AI-generated summary (including review-site AI summaries) If you cannot open a source and read the original post yourself, do not cite it. If you have no browsing access, say "NO BROWSING" at the top and stop. Do not answer from memory.

SEARCH GUIDANCE

Search mainly in Japanese. Treat these as starting points, not limits: 居酒屋 最悪 / 居酒屋 二度と行かない / お通し 不満 / 席料 チャージ 知らなかった / 飲み放題 ラストオーダー 早い / 料理 出てこない 居酒屋 / 店員 態度 居酒屋 / モバイルオーダー 居酒屋 不便 / タッチパネル 注文 / 居酒屋 うるさい 狭い / 居酒屋 タバコ 臭い / 予約 取れない 居酒屋 / 会計 間違い 居酒屋 / 2時間制 追い出された Also search in English for complaints from foreign visitors. Cover chain izakaya and independent izakaya, and say which one each piece of evidence concerns.

METHOD

  1. Collect complaint posts. Aim for 40 or more distinct posts from at least 4 different platforms. Do NOT pad. If you find fewer, report the real number.
  2. Group the complaints into themes. Map every theme to exactly ONE of these fixed domains so the results can be compared: D1 Food quality/portion | D2 Drinks/飲み放題 rules | D3 Staff attitude/service D4 Speed/wait times | D5 Ordering system (tablet/QR/mobile order) | D6 Price/billing/お通し/charges | D7 Seating/space/noise | D8 Smoking/smell | D9 Cleanliness/hygiene | D10 Reservations/time limits | D11 Payment methods | D12 Foreign-visitor/language | D13 Other (explain)
  3. For each theme, separate three layers and never mix them:
    • OBSERVED: what the users actually said (backed by quotes)
    • INFERRED: the operator-side struggle that likely causes it (for example, a labor shortage that causes slow service). Label it as inference.
    • OPPORTUNITY: what kind of product or service could address it. Label it as speculation.

OUTPUT FORMAT (follow exactly)

0. Run metadata

Model name, browsing/research mode, date run, number of posts reviewed, platforms used.

1. Evidence table

One row per post: | ID | Platform | URL | Post date | Venue type (chain/independent/unknown) | Region | Domain | Original quote (verbatim, max 2 sentences) | Translation | IDs: E01, E02, ... Copy quotes exactly. Do not paraphrase inside the quote column. If the post date or region is not shown, write "unknown". Do not guess.

2. Complaint themes (ranked by number of supporting posts in YOUR sample)

For each theme:

  • Theme name / Domain code
  • Supporting evidence IDs (e.g. E03, E11, E27) and the count
  • OBSERVED: 2-3 sentence summary
  • Severity signal: does it cause "never coming back", lower star ratings, or only mild annoyance? Cite IDs.
  • INFERRED operator struggle: [inference] ...
  • Confidence: High / Medium / Low, with a one-line reason Do not state percentages or claim anything about the whole population. Counts describe your sample only.

3. Operator struggle map

| Struggle (inferred) | Themes it explains | Evidence IDs | Confidence |

4. Sales opportunity hypotheses

| Struggle | Solution category | Why the complaints suggest the izakaya would pay for it | Counter-evidence or risk | Label every row [speculation]. Do not name vendors unless asked.

5. Self-audit

  • Claims you are least sure about
  • Platforms you could not access or search well
  • Possible biases in the sample (for example, angry reviewers are over-represented, or tourist-area venues dominate)
  • Anything you EXCLUDED because it was not genuine UGC

6. Machine-readable summary

A JSON block in this shape: {"model":"","run_date":"","posts_reviewed":0, "themes":[{"name":"","domain":"D1","evidence_ids":[],"count":0,"confidence":"High"}], "struggles":[{"name":"","theme_names":[],"confidence":"Medium"}]}

ACCURACY RULES

  • Every factual statement in sections 2 and 3 must cite evidence IDs.
  • Never invent a URL, quote, date, or reviewer. If you are unsure that a quote is exact, leave it out.
  • Prefer fewer, verified items over many unverified ones.
Model
GPT-6.1 Sol
Effort
high
Operator
OpenAI
Mode
Work
Search type
Web Search
Run date
Oct 5, 2026
Pack
None
Content language
English
Length
6259 words
Links
40
Domains
5
Tables
4

as of

Output

0. Run metadata

FieldValue
ModelGPT-6-based Codex; exact model variant unavailable
Research modeWeb search and direct reading of original customer posts; manual qualitative coding
Date run2026-10-04, Japan time
Requested window2024-10-01 to 2026-10-04
Posts reviewed and retained40 distinct complaint-bearing posts
Platforms usedHot Pepper Gourmet: 27; Tabelog: 5; TripAdvisor: 7; personal note posts: 1
SamplingPurposive complaint search, mainly in Japanese, with English searches for foreign visitors

Date convention: A month-only date means the page explicitly identifies that publication month. Where only the visit date appears, publication date is unknown, and the visit date is shown separately. Such posts were retained when the reported visit fell within the window and the post was readable on the run date.

Coding convention: Each post receives one primary domain and one primary theme. Secondary complaints remain relevant context but are not counted again. Venue ownership is marked unknown when the retrieved material does not establish it; “independent” follows an explicit customer description.

Evidence boundary: These are customer accounts, not independently established findings against the venues. Operator causes and willingness to pay are not verified by customer posts.

1. Evidence table

Quotes are short, contiguous verbatim excerpts. Original spelling and errors are preserved. For the English-language post, the translation column provides Japanese.

IDPlatformURLPost dateVenue type (chain/independent/unknown)RegionDomainOriginal quote (verbatim, max 2 sentences)Translation
E01Hot Pepperえんな review ホットペッパーグルメ2026-09; day unknownUnknown: 鉄板小町エキニシ店HiroshimaD4席のみ確保で時間指定しましたが、料理の提供が驚くほど遅いです。I reserved seats for a specified time, but the food service was astonishingly slow.
E02Hot Pepperみこっち review ホットペッパーグルメ2026-08; day unknownChain: 魚民 丸亀店Marugame, KagawaD4最初はまだ良かったんですが、途中から、注文した物が全然来なくなり、お酒以外は何もない時間が20分以上はありました。It was initially okay, but later our orders stopped arriving, and we had nothing except alcohol for more than 20 minutes.
E03Hot Pepperにのみ review ホットペッパーグルメ2026-09; day unknownUnknown: 轟 浅草駅前店Asakusa, TokyoD4テーブル席は自分たちしかいないくらい空いているのに、焼き物30分もかかる。予めその旨一言もなし。The table area was so empty that we were practically the only customers, yet grilled dishes took 30 minutes. There was no advance warning.
E04Tabeloghappiness_ym33 review 東京/居酒屋 [食べログ]Unknown; visit 2025-12Chain: 八重洲もつ焼き酒場てけてけYaesu, TokyoD2ウイスキーは飲まず、他の飲み放題の飲み物頼むから下げてくれといってもダメだと。We said we would not drink the whisky and would order other drinks included in the plan, but they refused to remove it.
E05TabelogKazun0907 review 新橋/居酒屋 [食べログ]Unknown; visit 2025-11Unknown: 魚の昌Shimbashi, TokyoD10利用時間は2時間とのことだったので、そのつもりで、食事していたが、40分でラストオーダーといわれたので、追加注文せず、精算し、店をでた。We were told we had two hours, but last orders were announced after 40 minutes, so we ordered nothing more, paid, and left.
E06Hot Pepperてだこけんたろう review ホットペッパーグルメ2026-08; day unknownChain: 魚民 丸亀店Marugame, KagawaD7隣の席の輩共がとてもうるさく下品で下ネタばかり喋るThe people at the next table were extremely loud and vulgar, talking only about sexual topics.
E07Hot Pepperかおっぺ review ホットペッパーグルメ2026-09; day unknownUnknown: 猿々楽々 大手町店HiroshimaD4料理は普通でしたが、食べ飲み放題で飲み物のオーダーは来ないし、オーダーが通ってなかったばかりで最悪でした。The food was ordinary, but during the unlimited food-and-drink plan, drinks did not arrive and orders repeatedly had not been registered. It was awful.
E08Hot Pepperむう review ホットペッパーグルメ2026-09; day unknownChain: ひとめぼれ 岐阜駅前店GifuD13メニューはほとんど売り切れ。店として機能していなかった。Almost everything on the menu was sold out. The restaurant was not functioning as a restaurant.
E09Hot Pepperゆか review ホットペッパーグルメ2026-05; day unknownChain: 新時代 赤羽駅東口店Akabane, TokyoD3味は良いが女性の店員が最悪です。自分の機嫌くらい自分で取ればいいのに非常に不愉快、二度と行きたく無いです。The food tastes good, but the female staff member was awful. Her apparent bad mood made the experience extremely unpleasant; I never want to return.
E10Hot Pepperきよ review ホットペッパーグルメ2026-03; day unknownChain: 新時代 塩釜口駅前店AichiD3いらっしゃいませも少しお時間いただきますなどの一言もなし。There was neither a welcome nor even a word saying we would have to wait.
E11Hot Pepperクロちゃん review ホットペッパーグルメ2026-09; day unknownChain: 音音 池袋店Ikebukuro, TokyoD7笑い声が煩さ過ぎて友人との会話が全く聞こえないくらいで少しストレスでした。Their laughter was so loud that I could not hear my conversation with my friend, which was somewhat stressful.
E12Hot Pepperしげ review ホットペッパーグルメ2026-05; day unknownUnknown: 原価酒場 司 池袋店Ikebukuro, TokyoD13一番高いコースにしたがメニュー名にある和牛すき焼きは売り切れで出せないと言われたI chose the most expensive course, but was told that the wagyu sukiyaki named in the menu was sold out and could not be served.
E13Hot Peppermieko review ホットペッパーグルメ2025-10; day unknownUnknown: いと。をかしMeguro, TokyoD7店内小さめなので カウンターの角席は 隣の方と膝が当たる距離感だったのが 少し残念でしたThe restaurant was small, and at the corner of the counter our knees were close enough to touch the neighboring customer’s, which was a little disappointing.
E14Hot Pepperbibiyou review ホットペッパーグルメ2026-08; day unknownUnknown: あきない 宮崎橘通店MiyazakiD13着席と同時にメニューを持ってきましたがその時点でおすすめのものはすでに品切れ。だったらその時点で教えていただきたかった。They brought the menu when we sat down, but the recommended items were already sold out. I wanted them to tell us then.
E15Hot Pepper内野宮 千里 review ホットペッパーグルメ2026-08; day unknownUnknown: あきない 宮崎橘通店MiyazakiD4ドリンクの提供が遅いのと頼んだ料理が全然来ないのはちょっと残念でした。次回も利用したいとは思わなかった。Slow drinks and food that never arrived were disappointing. I did not feel like returning.
E16Hot Pepperりん review ホットペッパーグルメ2026-09; day unknownUnknown: まんぷく屋 三宮店Sannomiya, HyogoD9たこ焼きソースの容器、マヨネーズの容器、メニュー表、全てベタベタしていて気持ち悪かった。The takoyaki sauce container, mayonnaise container, and menu were all sticky and unpleasant.
E17Hot Pepperミッフィー review ホットペッパーグルメ2026-08; day unknownChain: 新時代 塩釜口駅前店AichiD9お店の方の接客は普通に良かったのですが、トイレやテーブル周り、椅子の汚い部分が目立ちました。The service was reasonably good, but dirt around the toilets, tables, and chairs stood out.
E18Hot Pepperたけ review ホットペッパーグルメ2026-04; day unknownUnknown: 名物家 品川店Shinagawa, TokyoD5スマホ注文自体は問題ないのですが、フリーWi-Fiがない点は少し不便に感じました。Smartphone ordering itself was fine, but the absence of free Wi-Fi was somewhat inconvenient.
E19Hot Pepperひろまる review ホットペッパーグルメ2026-08; day unknownUnknown: 炭火焼鳥 とりたけしTokushimaD5スマホでの注文に変わっていた。で、メニュー表も無くなっていた。Ordering had changed to smartphones. The printed menu had also disappeared.
E20Hot Pepperなおきん review ホットペッパーグルメ2026-08-18Unknown: Mission 新宿店Shinjuku, TokyoD10店の雰囲気は悪くない、が予約してるのに予約席のテーブルセッティングがされてない。The atmosphere was not bad, but despite our reservation, the reserved table had not been set.
E21Hot Pepperスージー review ホットペッパーグルメ2026-08; day unknownUnknown: Mission 新宿店Shinjuku, TokyoD2はじめに飲み物オーダーで勝手がわからず別料金が発生した(自己責任)のはちょっと残念でした。I did not understand how the initial drink order worked and incurred an extra charge, which was a little disappointing, although I regard it as my responsibility.
E22Hot Pepper牛丼特盛 review ホットペッパーグルメ2026-08; day unknownUnknown: 炭火焼鳥にとん 松本Matsumoto, NaganoD5個人のスマホからの注文形態でしたが、焼き鳥の塩、タレの選択画面がなかったです。Orders were placed from personal smartphones, but there was no screen for choosing salt or sauce for the yakitori.
E23Hot PepperSacky review ホットペッパーグルメ(5/13)2026-04; day unknownUnknown: 酔々屋 難波千日前店Namba, OsakaD11クーポンやポイント利用地は現金払いのみだったのが残念でした。It was disappointing that using coupons or points required cash payment.
E24Hot Pepperいっぺー review ホットペッパーグルメ(5/13)2026-03; day unknownUnknown: 酔々屋 難波千日前店Namba, OsakaD6頼んでいないビールが届いたり履歴をみたら頼んでいない物がのっていて…Beer we had not ordered arrived, and the order history contained items we had not ordered…
E25Hot Pepperジョンカーベル review ホットペッパーグルメ2026-09; day unknown; composite reviewUnknown: 大衆居酒屋 ちから 高田馬場店Takadanobaba, TokyoD9残念なのがトイレットペーパーが切れていた事ですね(スペア含め)The disappointing thing was that the toilet paper had run out, including the spare rolls.
E26notePersonal visit account note.com2025-06-27Unknown: 魚七 天王町店Tennocho; prefecture not explicitly stated in the postD1ほぼ「豚バラとタピオカ入り厚揚げの炒め物」でした。It was practically “a stir-fry of pork belly and thick fried tofu containing tapioca.”
E27Hot Pepperサヴ review ホットペッパーグルメ2026-08; day unknownChain: とりいちず 目黒店Meguro, TokyoD4あまりにもドリンクの提供が遅かったため、料理やサービスを楽しむこともできず、早々に退店しました。Drinks were so slow that we could not enjoy the food or service and left early.
E28TripAdvisorTrail56820365623 review トリップアドバイザー2025-05-31Unknown: 酒肴人 名古屋栄店Sakae, Nagoya, AichiD4厨房に注文が送られてきてないと横柄な態度で言われました。注文履歴も残ってるのに。We were told rudely that the kitchen had not received our order, even though it remained in the order history.
E29TripAdvisorだんごむし review トリップアドバイザー2025-06-15Unknown: 酒肴人 名古屋栄店Sakae, Nagoya, AichiD8下水みたいな臭いでした。It smelled like sewage.
E30TripAdvisor佐藤 梨 review トリップアドバイザー2025-06-16Unknown: 酒肴人 名古屋栄店Sakae, Nagoya, AichiD3しかし責任者はこぼした店員の責任を取るのではなく個人で解決して欲しいと言った。However, the supervisor said we should resolve it privately rather than taking responsibility for the employee who spilled the food.
E31TripAdvisorReview dated October 4 トリップアドバイザー2025-10-04Unknown: まぐろ奉行かに代官 listing; another venue reportedly substitutedShimbashi, TokyoD63階の店舗に行くと地下1階のお店を紹介され、そちらでは、金曜祝日前加算料金等を請求されました。When we went to the third-floor restaurant, we were directed to a basement restaurant, where Friday/pre-holiday surcharges and other fees were charged.
E32TripAdvisorReview dated July 18 トリップアドバイザー2025-07-18Unknown: 出世酒場 大統領Shimbashi, TokyoD23杯以上飲まないとダメYou have to drink at least three drinks.
E33Hot Pepperyogu review ホットペッパーグルメ2026-08; day unknownUnknown: 炭火の一九ChibaD6今回はキャベツの千切りだった…。それで1人780円は高すぎると思った。This time it was shredded cabbage… I thought ¥780 per person was far too expensive for that.
E34TripAdvisorReview dated October 9 トリップアドバイザー2025-10-09Unknown: ザケイブ 新宿店; another venue reportedly substitutedKabukicho, TokyoD10個室で予約しても、全く個室じゃないばかりか、他店に案内され、そこの内装はカーブとは全く似つかないただの居酒屋。Despite reserving a private room, we were taken to another restaurant that was not private and looked nothing like the venue we booked.
E35Tabelogみ〜ぼう review 新宿/居酒屋 [食べログ]Unknown; visit 2025-10Unknown: 魚真 新宿店Shinjuku, TokyoD2期待していた冷たさが全くなく、生温い状態で出てきました。It was nowhere near the cold temperature I expected and arrived lukewarm.
E36Hot Pepper乃 review ホットペッパーグルメ2026-08; day unknownUnknown: 肉ときどきレモンサワー 栄住吉店Sakae, AichiD1ただ、焼き鳥がマズイ…冷凍感がすごくて冷たかった…But the yakitori tasted bad… it had a strong frozen-food impression and was cold…
E37Tabelogreina1524 review 四谷三丁目/居酒屋 [食べログ]Unknown; visit/update 2025-12Unknown: 居酒屋 純ちゃんYotsuya-sanchome, TokyoD1ワンオペの店なので30分に一品は遅いとは言わないですが、食べ物の量が圧倒的に減っているSince one person runs the restaurant, I would not call one dish every 30 minutes slow, but the quantity of food has decreased dramatically.
E38TabelogKyowan review 本厚木/居酒屋 [食べログ]Unknown; visit 2026-05Independent, explicitly described by reviewer: 酒楽 心灯Atsugi, KanagawaD5メニューは手元や黒板にあるので分かるが、スマホのタブを探すのが一苦労。The menu was understandable from the printed menu and blackboard, but finding the corresponding smartphone tab was a struggle.
E39Hot Pepperうさやん review ホットペッパーグルメ2026-09-12Chain: 酔っ手羽 川崎仲見世通り店Kawasaki, KanagawaD8横からタバコの煙がすごすぎて最後までいれず途中で出ました。Smoke from beside us was so intense that we could not stay and left partway through.
E40TripAdvisorStephanie K review Tripadvisor2025-05-09Unknown: 大統領Ueno, TokyoD12He shewed us away but let Japanese speaking people sit once there were tables available.Japanese: 席が空くと、日本語を話す人たちは座らせたのに、私たちは追い払われました。

2. Complaint themes (ranked by number of supporting posts in YOUR sample)

Ties are presented without implying a difference in importance. Confidence refers to the inferred operator struggle, not independent verification of the allegation.

1. Delayed or lost orders / D4

  • Supporting evidence: E01, E02, E03, E07, E15, E27, E28. Count: 7.
  • OBSERVED: Customers describe long periods without food or drinks, and orders that appear not to reach fulfillment. The complaints include both waiting without an estimated completion time and discrepancies between an order history and what the kitchen reportedly received. [E01, E02, E03, E07, E28]
  • Severity signal: Customers explicitly left early or expressed no intention to return; several posted 1/5 ratings. [E01, E02, E03, E15, E27]
  • INFERRED operator struggle: [inference] The order-to-service process lacks reliable tracking, overdue-order detection, or communication about delays. These posts do not establish whether the root cause is staffing, preparation capacity, technology, or task prioritization. [E01, E03, E07, E28]
  • Confidence: High for unreliable fulfillment in the reported incidents; lower for any specific staffing explanation. [E07, E28]

2. Mobile-order friction / D5

  • Supporting evidence: E18, E19, E22, E38. Count: 4.
  • OBSERVED: Customers encounter missing connectivity support, removal of printed menus, unavailable customization choices, and difficulty locating menu items in the interface. One independent-venue reviewer found the printed and blackboard menus understandable but the smartphone navigation difficult. [E18, E19, E22, E38]
  • Severity signal: Outcomes range from mild inconvenience and a 4/5 rating to a 1/5 review with refusal to return; that severe review also includes delayed service and staff attitude, so mobile ordering alone cannot explain the outcome. [E18, E19, E22, E38]
  • INFERRED operator struggle: [inference] Digital ordering has been introduced without fully matching customer capabilities, menu structure, connectivity needs, and fallback service. [E18, E19, E22, E38]
  • Confidence: Medium, because configuration, deliberate menu choices, and customer familiarity are competing explanations. [E18, E22, E38]

3. Advertised items unavailable / D13

D13 explanation: menu availability and stockouts are distinct from food quality or portion size.

  • Supporting evidence: E08, E12, E14. Count: 3.
  • OBSERVED: Customers report extensive stockouts, an unavailable headline item in the most expensive course, and recommended products already unavailable when the menu was presented. The complaint concerns both missing products and insufficient disclosure before ordering. [E08, E12, E14]
  • Severity signal: E08 calls the venue nonfunctional; E14 describes leaving during the visit. Both carry 1/5 ratings. [E08, E14]
  • INFERRED operator struggle: [inference] Ingredient availability, advertised menus, and reservation/course promises are insufficiently synchronized. Demand forecasting or purchasing could contribute, but the posts do not establish why stock ran out. [E08, E12, E14]
  • Confidence: Medium, with direct evidence of availability mismatches but no purchasing or inventory records. [E08, E12, E14]

4. Food composition, temperature and portions / D1

  • Supporting evidence: E26, E36, E37. Count: 3.
  • OBSERVED: Complaints concern a named ingredient barely featuring in a dish, cold and unpleasant yakitori, and reduced portions compared with previous visits. These are different manifestations of food falling short of the customer’s expectation. [E26, E36, E37]
  • Severity signal: E36 gives 2/5 and E37 gives 1.5/5; E26 remains broadly positive about value, so its ingredient complaint is comparatively mild. [E26, E36, E37]
  • INFERRED operator struggle: [inference] Recipe composition, portion standards, or cooking-to-service temperature may be inconsistent with menu descriptions and repeat-customer expectations. Actual frozen sourcing and deliberate cost reduction are not established. [E26, E36, E37]
  • Confidence: Medium, because the posts identify specific shortcomings but cannot distinguish production failure from preference or an intentional menu change. [E26, E36, E37]

5. Dismissive service and poor incident recovery / D3

  • Supporting evidence: E09, E10, E30. Count: 3.
  • OBSERVED: Customers describe unpleasant staff behavior, failure to acknowledge waiting customers, and refusal by a supervisor to take responsibility after a spill. The dissatisfaction concerns interpersonal treatment and resolution, rather than food alone. [E09, E10, E30]
  • Severity signal: E09 explicitly rejects returning; E10 gives 1/5; E30 strongly advises against visiting. [E09, E10, E30]
  • INFERRED operator struggle: [inference] Greeting standards, complaint escalation, and responsibility for service incidents may be unclear or inconsistently followed. [E09, E10, E30]
  • Confidence: Medium, because the reported conduct is specific but management procedures and the other parties’ accounts are unavailable. [E09, E10, E30]

6. Unwanted charges and billing trust / D6

  • Supporting evidence: E24, E31, E33. Count: 3.
  • OBSERVED: Customers report unordered items in their order history, surcharges after being directed to another venue, and an otoshi charge they regard as poor value. Billing accuracy, advance disclosure, and perceived value are separate issues within this domain. [E24, E31, E33]
  • Severity signal: E24 gives 1/5 and E31 uses strong fraud allegations; E33 gives 5/5 overall and identifies otoshi as the only dissatisfaction. The latter does not support a claim that all charge complaints destroy loyalty. [E24, E31, E33]
  • INFERRED operator struggle: [inference] Operators may struggle to maintain trustworthy order records and communicate compulsory charges or their value clearly. Some disputes may reflect an intentional pricing policy rather than a technical mistake. [E24, E31, E33]
  • Confidence: Medium, because no receipts, transaction logs, or contemporaneous disclosures were independently inspected. [E24, E31, E33]

7. Noise and cramped seating / D7

  • Supporting evidence: E06, E11, E13. Count: 3.
  • OBSERVED: Nearby customers’ voices or laughter obstruct conversation, while tight counter seating brings customers into physical contact. A room described as semi-private does not necessarily deliver the quiet experience the customer expected. [E06, E11, E13]
  • Severity signal: Ratings range from 1/5 in E06 to 3/5 in E11 and 5/5 with explicit revisit intent in E13. Space complaints therefore vary considerably in severity. [E06, E11, E13]
  • INFERRED operator struggle: [inference] Table allocation, acoustic separation, and seating density may conflict with customers seeking conversation or personal space. [E06, E11, E13]
  • Confidence: Medium, because the experiences are clear but floor plans, sound measurements, and occupancy economics are unavailable. [E06, E11, E13]

8. Cleaning and restroom upkeep / D9

  • Supporting evidence: E16, E17, E25. Count: 3.
  • OBSERVED: Customers report sticky shared containers and menus, visibly dirty toilets or seating areas, and depleted toilet-paper supplies. E17 says service was acceptable despite the cleanliness problem, separating housekeeping from staff courtesy. [E16, E17, E25]
  • Severity signal: E16 and E17 give 1/5; E25 frames missing supplies as a disappointment while remaining positive about value. [E16, E17, E25]
  • INFERRED operator struggle: [inference] Cleaning coverage, inspection frequency, and consumable replenishment may lack clear ownership or effective checks. [E16, E17, E25]
  • Confidence: Medium, because recurring upkeep tasks are implicated, but inspection logs and actual hygiene conditions are unverified. [E16, E17, E25]

9. Reservation promises not fulfilled / D10

  • Supporting evidence: E05, E20, E34. Count: 3.
  • OBSERVED: Customers report a missing reservation record and unexpectedly early last orders, an unset reserved table, and a private-room booking replaced by another venue without the expected privacy. Each complaint involves a gap between the booked experience and arrival or service conditions. [E05, E20, E34]
  • Severity signal: E05 explicitly says they will not return and left without additional orders; E20 gives 2/5; E34 expresses extreme dissatisfaction. [E05, E20, E34]
  • INFERRED operator struggle: [inference] Reservation records, room allocation, preparation tasks, and time-limit conditions may not be consistently carried through to service. Deliberate substitution remains a competing explanation in E34. [E05, E20, E34]
  • Confidence: Medium, because the mismatches are explicit but internal booking records are unavailable. [E05, E20, E34]

10. Drink-plan and consumption rules / D2

  • Supporting evidence: E04, E21, E32. Count: 3.
  • OBSERVED: Customers object to unwanted self-service drink equipment, extra charges incurred while navigating an inclusive drink plan, and a minimum-drink requirement. These complaints concern the design or explanation of the drinking offer. [E04, E21, E32]
  • Severity signal: E04 explicitly rejects returning; E32 strongly discourages visiting; E21 describes only mild disappointment and accepts personal responsibility. [E04, E21, E32]
  • INFERRED operator struggle: [inference] Revenue-protecting drink rules may be difficult to explain or may conflict with customer expectations of flexibility and an inclusive price. [E04, E21, E32]
  • Confidence: Medium, because communication gaps are plausible, but some dissatisfaction may persist even with perfect disclosure. [E04, E21, E32]

11. Smoke and unpleasant smells / D8

  • Supporting evidence: E29, E39. Count: 2.
  • OBSERVED: One customer reports a sewage-like smell; another left because neighboring tobacco smoke was intolerable. These are distinct odor sources with different potential remedies. [E29, E39]
  • Severity signal: Both accounts describe abandoning the intended visit, and E29 explicitly rejects returning. [E29, E39]
  • INFERRED operator struggle: [inference] Air quality, odor-source maintenance, or smoking-related customer allocation may be inadequate for affected customers. A drainage fault cannot be established from a perceived sewage smell alone. [E29, E39]
  • Confidence: Low, because each odor mechanism has only one supporting post and no technical inspection. [E29, E39]

12. Beer served insufficiently cold / D2

  • Supporting evidence: E35. Count: 1.
  • OBSERVED: The customer describes bottled beer arriving lukewarm despite expecting it to be cold. The same review praises the fish, identifying drink execution as a separate disappointment. [E35]
  • Severity signal: The overall rating is 2/5, and the reviewer says repeat patronage would be difficult without improvement; staff service also contributed. [E35]
  • INFERRED operator struggle: [inference] Beverage chilling, replenishment, or pre-service checks may have failed. [E35]
  • Confidence: Low, because this is one reported incident without temperature readings or equipment evidence. [E35]

13. Cash-only restrictions with benefits / D11

  • Supporting evidence: E23. Count: 1.
  • OBSERVED: The customer liked the affordability and ability to reserve seats but disliked cash-only payment when using coupons or points. The inconvenience relates to a conditional payment rule rather than a reported payment outage. [E23]
  • Severity signal: Mild disappointment with a 3/5 rating; no explicit refusal to return. [E23]
  • INFERRED operator struggle: [inference] Payment and promotional-benefit policies may be difficult to combine or explain conveniently. The reason for the restriction is unknown. [E23]
  • Confidence: Low, because a single customer account cannot establish the commercial or technical reason. [E23]

14. Foreign visitor feels unwelcome / D12

  • Supporting evidence: E40. Count: 1.
  • OBSERVED: An English-language reviewer says they were turned away while Japanese-speaking customers were seated when tables became available. The reviewer interprets this as discriminatory treatment. [E40]
  • Severity signal: A 1/5 rating and advice to choose another izakaya. [E40]
  • INFERRED operator struggle: [inference] Foreign-customer admission or communication may lack a clear, consistently communicated process. Language limitations, reservations, or discriminatory exclusion cannot be distinguished from this account. [E40]
  • Confidence: Low, because only one perspective and no explanation from the venue are available. [E40]

3. Operator struggle map

All struggles below are inferences, not verified diagnoses.

Struggle (inferred)Themes it explainsEvidence IDsConfidence
[inference] Unreliable order tracking, fulfillment, and delay communicationDelayed or lost ordersE01, E02, E03, E07, E15, E27, E28High for the process failure; specific root cause unknown
[inference] Digital ordering poorly matched to customer needs and actual menu choicesMobile-order frictionE18, E19, E22, E38Medium
[inference] Stock availability not synchronized with menus and course promisesAdvertised items unavailableE08, E12, E14Medium
[inference] Food execution or changed portions fail to match expectationsFood composition, temperature and portionsE26, E36, E37Medium
[inference] Inconsistent service standards and unclear incident responsibilityDismissive service and poor incident recoveryE09, E10, E30Medium
[inference] Weak billing transparency, order-record trust, or compulsory-charge valueUnwanted charges and billing trustE24, E31, E33Medium
[inference] Seating and acoustic arrangements conflict with conversation and comfortNoise and cramped seatingE06, E11, E13Medium
[inference] Incomplete cleaning checks and consumable replenishmentCleaning and restroom upkeepE16, E17, E25Medium
[inference] Booking promises do not reliably translate into prepared seats and service conditionsReservation promises not fulfilledE05, E20, E34Medium
[inference] Drink-offer rules conflict with customers’ understanding or preferencesDrink-plan and consumption rulesE04, E21, E32Medium
[inference] Odor control or smoking arrangements fail affected customersSmoke and unpleasant smellsE29, E39Low
[inference] Beverage-temperature control failed on the reported visitBeer served insufficiently coldE35Low
[inference] Promotional benefits and payment rules create frictionCash-only restrictions with benefitsE23Low
[inference] Foreign-customer admission lacks a clear, understandable processForeign visitor feels unwelcomeE40Low

4. Sales opportunity hypotheses

None of these posts establishes that an operator would pay. The proposed purchase motivations are hypotheses to test with operators.

StruggleSolution categoryWhy the complaints suggest the izakaya would pay for itCounter-evidence or risk
[speculation] Unreliable fulfillmentOrder tracking, kitchen/bar dispatch, overdue-order alerts, service-process reviewEarly departures and explicit non-return intentions suggest potential value in preventing lost orders and abandoned visits. [E01, E15, E27, E28]More efficient order capture will not fix insufficient production capacity. Delays also occurred in an apparently quiet venue. [E03]
[speculation] Mobile-order frictionInterface configuration, connectivity support, printed-menu fallback, staff onboardingCould reduce customer assistance needs and make menu options easier to find. [E18, E19, E22, E38]E18 accepts smartphone ordering itself; E38 still gives 4/5. Some issues may justify small configuration changes rather than a replacement system.
[speculation] Menu availability mismatchInventory visibility, stockout alerts, synchronized digital menus, course-availability checksCould prevent selling courses without their headline item and attracting customers for unavailable recommendations. [E08, E12, E14]Genuine supply disruption or deliberate menu decisions require different remedies. Stockout counts and financial losses are unknown.
[speculation] Food inconsistencyRecipe and portion standards, preparation review, hot-holding or serving-process improvementsCould protect repeat-customer expectations and reduce disappointment with cold or poorly composed dishes. [E26, E36, E37]Taste is subjective. Smaller portions may be intentional, and E26 remains positive about value.
[speculation] Poor service recoveryPractical staff coaching, greeting routines, escalation procedures, incident documentationExplicit non-return statements suggest a retention motive; incident handling also consumes management attention. [E09, E10, E30]Training may not change behavior without supervision. E10 reports better treatment at another branch, suggesting a local rather than universal problem.
[speculation] Billing and charge distrustOrder-to-bill reconciliation, itemized running totals, advance charge disclosure; otoshi redesignCould reduce disputes, corrections, and distrust around unordered items or compulsory fees. [E24, E31, E33]E24 says staff removed the disputed items. E33 gives 5/5 overall. Transparent pricing cannot eliminate disagreement about value.
[speculation] Noise and space conflictSeating-allocation review, acoustic treatment, group zoning, accurate room descriptionsCould retain customers choosing the venue for conversation or privacy. [E06, E11, E13]Reducing seating density may reduce revenue. E13 still wants to return; lively surroundings may suit other customers.
[speculation] Cleaning and replenishment gapsCleaning service, task scheduling, inspection checklists, restroom-supply managementCould address visible problems associated with 1/5 reviews and prevent basic supply failures. [E16, E17, E25]A checklist cannot ensure compliance. These posts do not establish food-safety violations or willingness to buy an outside service.
[speculation] Unfulfilled reservation promisesReservation synchronization, room allocation, pre-arrival setup tasks, explicit time-limit confirmationCould protect booked-party revenue and prevent walkouts or disputes over the promised experience. [E05, E20, E34]Intentional venue substitution is not necessarily a software problem. Small venues may solve preparation failures through simple routines.
[speculation] Drink-rule confusionPlain-language plan menus, included-item filtering, confirmation screens, service scriptingCould prevent accidental paid orders and disputes about compulsory drinking formats. [E04, E21, E32]Some customers dislike the underlying policy. Operators may retain it because it supports their revenue model.
[speculation] Smoke and odor problemsOdor-source inspection, ventilation maintenance, smoking-policy and seating reviewCustomers leaving early suggests a possible commercial reason to address intolerable air conditions. [E29, E39]One customer elsewhere explicitly valued being able to smoke. Smoking-related changes could alienate that segment, and ventilation may not remove exposure. [E15]
[speculation] Warm beerChilling and replenishment review, temperature checks, equipment inspectionCould protect the drink experience even where food quality is appreciated. [E35]One incident is insufficient to justify equipment replacement or a major purchase.
[speculation] Conditional cash-only paymentPayment-policy review, benefit reconciliation, pre-visit disclosureCould remove an inconvenience for customers expecting to use promotions and another payment method. [E23]The reason for the restriction is unknown, and the complaint is mild.
[speculation] Foreign-customer admission frictionMultilingual admission information, reservation explanations, staff communication supportCould help venues that want foreign customers avoid rejection-related negative reviews. [E40]Language support will not solve intentional exclusion or actual capacity constraints. This sample contains only one directly relevant foreign-visitor account.

5. Self-audit

  • Claims least certain: Specific causes such as labor shortages, purchasing failures, refrigeration faults, intentional overcharging, or discrimination. Customer accounts establish reported experiences, not those diagnoses. No operator willingness to pay was verified.
  • Date limitations: Five Tabelog posts show visits rather than publication dates. Many Hot Pepper pages explicitly identify only the publication month. E25 and E37 contain multiple visits or updates; each is counted as one post.
  • Platform access: Several Retty and Reddit originals failed to open. Google Maps originals were not successfully verified. Searches of Yahoo!知恵袋 produced little eligible firsthand complaint material. X, Instagram comments, Threads, YouTube comments, 発言小町, ガールズちゃんねる, 5ch, and 一休 were not systematically covered.
  • Sample bias: Hot Pepper dominates. Tokyo and other urban venues are prominent, with repeated posts concerning several venues. Independent ownership is explicitly established for only E38, so chain-versus-independent comparisons would be weak.
  • Time bias: The retained sample is concentrated in 2025–2026; it contains no verified October–December 2024 complaint post.
  • Complaint-search bias: Negative search terms favor dissatisfied customers. Mild complaints in otherwise positive reviews were retained, including E13, E33, and E38, but this is still not a balanced satisfaction sample.
  • Authenticity limits: Individual customer attribution and firsthand wording were checked. Actual patronage, undisclosed incentives, and possible undisclosed AI assistance could not be independently authenticated.
  • Excluded material: News, surveys, vendor and consultancy advice, restaurant responses, operator-authored posts, listicles, review aggregators reproducing Google reviews, and review-site summaries. Older TripAdvisor complaints were excluded even when the same page also contained recent reviews. Search snippets were excluded whenever the original complaint could not be opened and read.
  • Interpretation limits: Ratings and refusal-to-return statements often reflect several complaints together. They cannot isolate the financial effect of the single primary theme assigned here.

6. Machine-readable summary

{
  "model": "GPT-6-based Codex; exact variant unavailable",
  "run_date": "2026-10-04",
  "posts_reviewed": 40,
  "themes": [
    {
      "name": "Delayed or lost orders",
      "domain": "D4",
      "evidence_ids": ["E01", "E02", "E03", "E07", "E15", "E27", "E28"],
      "count": 7,
      "confidence": "High"
    },
    {
      "name": "Mobile-order friction",
      "domain": "D5",
      "evidence_ids": ["E18", "E19", "E22", "E38"],
      "count": 4,
      "confidence": "Medium"
    },
    {
      "name": "Advertised items unavailable",
      "domain": "D13",
      "evidence_ids": ["E08", "E12", "E14"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Food composition, temperature and portions",
      "domain": "D1",
      "evidence_ids": ["E26", "E36", "E37"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Dismissive service and poor incident recovery",
      "domain": "D3",
      "evidence_ids": ["E09", "E10", "E30"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Unwanted charges and billing trust",
      "domain": "D6",
      "evidence_ids": ["E24", "E31", "E33"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Noise and cramped seating",
      "domain": "D7",
      "evidence_ids": ["E06", "E11", "E13"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Cleaning and restroom upkeep",
      "domain": "D9",
      "evidence_ids": ["E16", "E17", "E25"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Reservation promises not fulfilled",
      "domain": "D10",
      "evidence_ids": ["E05", "E20", "E34"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Drink-plan and consumption rules",
      "domain": "D2",
      "evidence_ids": ["E04", "E21", "E32"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Smoke and unpleasant smells",
      "domain": "D8",
      "evidence_ids": ["E29", "E39"],
      "count": 2,
      "confidence": "Low"
    },
    {
      "name": "Beer served insufficiently cold",
      "domain": "D2",
      "evidence_ids": ["E35"],
      "count": 1,
      "confidence": "Low"
    },
    {
      "name": "Cash-only restrictions with benefits",
      "domain": "D11",
      "evidence_ids": ["E23"],
      "count": 1,
      "confidence": "Low"
    },
    {
      "name": "Foreign visitor feels unwelcome",
      "domain": "D12",
      "evidence_ids": ["E40"],
      "count": 1,
      "confidence": "Low"
    }
  ],
  "struggles": [
    {
      "name": "[inference] Unreliable order tracking, fulfillment and delay communication",
      "theme_names": ["Delayed or lost orders"],
      "confidence": "High"
    },
    {
      "name": "[inference] Digital ordering poorly matched to customer needs",
      "theme_names": ["Mobile-order friction"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Stock availability not synchronized with menus and course promises",
      "theme_names": ["Advertised items unavailable"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Food execution or changed portions fail to match expectations",
      "theme_names": ["Food composition, temperature and portions"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Inconsistent service standards and unclear incident responsibility",
      "theme_names": ["Dismissive service and poor incident recovery"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Weak billing transparency, order-record trust or compulsory-charge value",
      "theme_names": ["Unwanted charges and billing trust"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Seating and acoustics conflict with conversation and comfort",
      "theme_names": ["Noise and cramped seating"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Incomplete cleaning checks and consumable replenishment",
      "theme_names": ["Cleaning and restroom upkeep"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Booking promises do not translate reliably into prepared seats and conditions",
      "theme_names": ["Reservation promises not fulfilled"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Drink rules conflict with customer understanding or preferences",
      "theme_names": ["Drink-plan and consumption rules"],
      "confidence": "Medium"
    },
    {
      "name": "[inference] Odor control or smoking arrangements fail affected customers",
      "theme_names": ["Smoke and unpleasant smells"],
      "confidence": "Low"
    },
    {
      "name": "[inference] Beverage-temperature control failed on the reported visit",
      "theme_names": ["Beer served insufficiently cold"],
      "confidence": "Low"
    },
    {
      "name": "[inference] Promotional benefits and payment rules create friction",
      "theme_names": ["Cash-only restrictions with benefits"],
      "confidence": "Low"
    },
    {
      "name": "[inference] Foreign-customer admission lacks a clear understandable process",
      "theme_names": ["Foreign visitor feels unwelcome"],
      "confidence": "Low"
    }
  ]
}