<?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 Simplify Splitting a ticket in a table in Toast in Restaurant Operations</title>
    <link>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13813#M5764</link>
    <description>&lt;DIV&gt;When we split a table say 4 ways when accepting a payment, Toast&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For e.g.… say the total is $20&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;20/4 = 5 each&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The system gives this number; then after we charge for one person, it shows $15 remaining, which is correct, but ODD.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Instead, it should actually show five buttons for payment, with $5 as payment. When we swipe the card, the total should be prepopulated.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Currently, it’s expecting the waiter to fill in the number, and there can always be mistakes with human input.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Both my previous POSs before migration to Toast 2 years ago, this is how they worked and more natural instead of the waiter doing all the matches or remembering to populate it every single time for each payment.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Folks, if you know how to move this up the queue or you have similar thoughts, please help raise this feature request for development teams to consider.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Cheers,&lt;/DIV&gt;&lt;DIV&gt;Ashok&lt;/DIV&gt;</description>
    <pubDate>Sun, 02 Feb 2025 21:19:52 GMT</pubDate>
    <dc:creator>ashokr</dc:creator>
    <dc:date>2025-02-02T21:19:52Z</dc:date>
    <item>
      <title>Simplify Splitting a ticket in a table in Toast</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13813#M5764</link>
      <description>&lt;DIV&gt;When we split a table say 4 ways when accepting a payment, Toast&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;For e.g.… say the total is $20&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;20/4 = 5 each&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;The system gives this number; then after we charge for one person, it shows $15 remaining, which is correct, but ODD.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Instead, it should actually show five buttons for payment, with $5 as payment. When we swipe the card, the total should be prepopulated.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Currently, it’s expecting the waiter to fill in the number, and there can always be mistakes with human input.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Both my previous POSs before migration to Toast 2 years ago, this is how they worked and more natural instead of the waiter doing all the matches or remembering to populate it every single time for each payment.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Folks, if you know how to move this up the queue or you have similar thoughts, please help raise this feature request for development teams to consider.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Cheers,&lt;/DIV&gt;&lt;DIV&gt;Ashok&lt;/DIV&gt;</description>
      <pubDate>Sun, 02 Feb 2025 21:19:52 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13813#M5764</guid>
      <dc:creator>ashokr</dc:creator>
      <dc:date>2025-02-02T21:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: Simplify Splitting a ticket in a table in Toast</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13814#M5765</link>
      <description>&lt;P&gt;Err.. not sure how I can make 2 labels? I wanted to edit and add a label "Payments" but there is no way to edit/update this post?&lt;/P&gt;</description>
      <pubDate>Sun, 02 Feb 2025 21:27:17 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13814#M5765</guid>
      <dc:creator>ashokr</dc:creator>
      <dc:date>2025-02-02T21:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: Simplify Splitting a ticket in a table in Toast</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13819#M5769</link>
      <description>&lt;P&gt;This one has always confused me,&amp;nbsp; I'm surprised it hasn't been improved. Split by 4, then split by 3, then split by 2, at least you don't have to do anything for the last payment!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 02 Feb 2025 22:22:04 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13819#M5769</guid>
      <dc:creator>rcmck</dc:creator>
      <dc:date>2025-02-02T22:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: Simplify Splitting a ticket in a table in Toast</title>
      <link>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13821#M5770</link>
      <description>&lt;P&gt;Absolutely.. if there is a little odd number, the. last guy is the unlucky winner :-).. This is how age old POS's worked, but somehow Toast is yet to catchup!&lt;/P&gt;</description>
      <pubDate>Sun, 02 Feb 2025 23:02:37 GMT</pubDate>
      <guid>https://community.toasttab.com/t5/restaurant-operations/simplify-splitting-a-ticket-in-a-table-in-toast/m-p/13821#M5770</guid>
      <dc:creator>ashokr</dc:creator>
      <dc:date>2025-02-02T23:02:37Z</dc:date>
    </item>
  </channel>
</rss>

