<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: All You Can Eat &amp;amp; Bottomless Menus: Growing Trend, Painful POS Workflow in Industry Trends</title>
    <link>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17756#M206</link>
    <description>&lt;P&gt;Set to print changes only&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jan 2026 19:45:24 GMT</pubDate>
    <dc:creator>josh212</dc:creator>
    <dc:date>2026-01-07T19:45:24Z</dc:date>
    <item>
      <title>All You Can Eat &amp; Bottomless Menus: Growing Trend, Painful POS Workflow</title>
      <link>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17739#M203</link>
      <description>&lt;P&gt;Demand for all-you-can-eat and bottomless drink menus (KBBQ, sushi, hot pot, brunch, etc.) is clearly increasing, but Toast doesn’t seem built for how these programs actually work.&lt;/P&gt;&lt;P&gt;Right now we’re forced to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Use $0 menu items for AYCE food/drinks items&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Create a separate button to charge for AYCE&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This falls apart because AYCE is based on continuous ordering, not one-time ordering.&lt;/P&gt;&lt;P&gt;Common issues we see:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;AYCE items added without charging the AYCE fee&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Free food/drinks accidentally or intentionally added to non-AYCE tables&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;No guardrails to prevent mistakes or abuse&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;As AYCE and unlimited menus become more common and higher-volume, these gaps create real revenue leakage and training problems.&lt;/P&gt;&lt;P&gt;It would be great to see native AYCE support, such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Allowing continuous ordering without $0 item hacks&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Preventing AYCE items from being added to non-AYCE tables&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Curious if others are running into the same problems or if Toast is already exploring a solution here.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2026 22:19:50 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17739#M203</guid>
      <dc:creator>JustAsking</dc:creator>
      <dc:date>2026-01-04T22:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: All You Can Eat &amp; Bottomless Menus: Growing Trend, Painful POS Workflow</title>
      <link>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17743#M204</link>
      <description>&lt;P&gt;So it seems like the best solution would be to build a AYCE menu item and use size and sequence, or just sequence pricing for a modifier group and have all the menu items as modifiers that are included&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 06:11:01 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17743#M204</guid>
      <dc:creator>josh212</dc:creator>
      <dc:date>2026-01-06T06:11:01Z</dc:date>
    </item>
    <item>
      <title>Re: All You Can Eat &amp; Bottomless Menus: Growing Trend, Painful POS Workflow</title>
      <link>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17754#M205</link>
      <description>&lt;P&gt;I might be understanding it wrong but if you do it by modifiers the kitchen receipts won't be smooth as you think. If a customer orders a 2nd round or 3rd using the modifier method the server would have to edit the existing item modifier causing a lot of confusion from the back.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 18:12:00 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17754#M205</guid>
      <dc:creator>JustAsking</dc:creator>
      <dc:date>2026-01-07T18:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: All You Can Eat &amp; Bottomless Menus: Growing Trend, Painful POS Workflow</title>
      <link>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17756#M206</link>
      <description>&lt;P&gt;Set to print changes only&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 19:45:24 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/industry-trends/all-you-can-eat-amp-bottomless-menus-growing-trend-painful-pos/m-p/17756#M206</guid>
      <dc:creator>josh212</dc:creator>
      <dc:date>2026-01-07T19:45:24Z</dc:date>
    </item>
  </channel>
</rss>

