Toast Price Check

Created by Zuppler Level 2 Support, Modified on Fri, 14 Mar at 9:56 AM by Zuppler Level 2 Support

Toast has highly complex tax calculation strategies. A single store can have multiple tax rates—e.g., state tax at 5.5%, county tax at 3.5%, etc. In contrast, our system currently supports only one tax rate, which in this case would be a flat 9%. Additionally, Toast employs two different tax calculation strategies, varying in how they round amounts when discounts are applied. Since any store can use either of these strategies, this sometimes results in minor mismatches in order totals between our system and Toast’s, leading to open orders with due balances on the store's POS.


To address this, we are now leveraging Toast's price check response. When we submit an order to Toast, their system provides a price check step, allowing third-party integrations (like ours) to review the total they have calculated before final submission. Moving forward, we will compare the total calculated by Toast and adjust our order request accordingly, ensuring there is no mismatch or due balance. Important: This adjustment only applies to the order request sent to Toast—customers will not be charged or refunded for the difference.

How it WorksWe’ve introduced a new order action: "NotifyPOS say check prices." This action will determine if there’s a price discrepancy when submitting an order to Toast, leading to one of three possible outcomes:

  • Accept (no or 1 to 5 cent discrepancy):
If there is no discrepancy this action will return accept outcome and the order will be submitted to Toast without any problem.
    image.png
    If the 
    price difference is between 1 and 5 cents, we will adjust the order total accordingly and trigger the NotifyPOS action, submitting the order with the corrected total. These minor discrepancies are rare and stem from Toast’s tax calculation methods mentioned above, which our system does not support.
    image.png
  • Reject (6 to 50 cent discrepancy):
If the discrepancy is between 6 and 50 cents, we have two options: reject the order or proceed by adjusting the total. Currently, we are moving the order to NotifyPOS action, automatically adjusting the total and submitting the order.
    image.png
    However, this behavior can be modified per client from the Order Workflow. Additionally, in this scenario, we are automatically creating a task for the tech support team in Asana, including the order ID of the affected order. This allows them to investigate the root cause of the discrepancy, which typically occurs due to mismatches in tax rates between our system and Toast or varying tax rates applied to specific items in the order. By flagging these discrepancies, we can proactively address and resolve them.
     @Tech Support please let me know if you have any questions regarding the flow or need help debugging these discrepancies.
    image.png
  • Failure (Discrepancy of more than 50 cents):
We already have this logic in place for handling discrepancies greater than 50 cents: the order will fail and not be sent to Toast. This logic remains unchanged. If an order exceeds this threshold, the NotifyPOS say check prices action will fail, moving the order to a missed state in the workflow. This ensures the support team is alerted to investigate and resolve the issue.
    image.png


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article