Order API -> diningOption: null

Amiteshwar Mann

February 09, 2023 19:17

For some of the orders, I'm getting diningOption: null. This is weird because we've set up the diningOptions to the concerned vendor. What's interesting is that when I tried to analyze the orders where diningOption: null, all those orders have an amount of 0.00 and have no selection of items. Also, when I try to look up these orders in my Toast account, I don't see them. It's like these orders don't exist. Does anyone else face this? 

0

• 

  John Duggan

  February 10, 2023 19:48

  Thank you for reaching out, Amiteshwar! To help identify what could cause the diningOption to be null, could you provide an example Order JSON? This will help us troubleshoot and identify the issue. Please do not include any sensitive in the Order JSON like customer info, etc.

  0
• 

  Amiteshwar Mann

  April 07, 2023 20:51

  Sure. There you go.

  0
• 

  John Duggan

  April 10, 2023 16:33

  Thanks, Amiteshwar Mann for the example. After testing and investigating how Toast assigns dining options to orders, there are no constraints for in-store orders to require a dining option. If you want all in-store orders to be associated with a dining option, please assign a default dining option either at the device level or in the Toast Backend. More information is in this Toast Article on how to set default modifiers.

  0

Please sign in to leave a comment.