Liz Jackson

Hi Susann, Just want to keep you posted that our engineering team is working on a fix for this issue. I'll post here after the fix is released. Thanks for bringing the issue to our attention.

Thanks, Kris! I'll pass this along to our product team, that's a valid suggestion. We'll be sure to let you know if there are changes in this area in the future.

Hi Susann, Thanks for bringing this to our attention! I'll notify our engineering team and will let you know what I hear. I just tested a few config API requests and can reproduce this error in the...

Hi Bob, The only quantity-related stock webhook we currently have is the low_quantity event. We designed the webhook this way because it's important for ordering partners to know when an item's qua...

Thanks Jeremy for the feedback! I've brought up your comment with our product team. In your view, what is the ideal way for menu visibility hierarchy to work? Do you think menu visibility should on...

Thanks, Glenn! This is not on our current roadmap but we'll keep you posted if there are changes in this area. We appreciate you sending the feedback.

Hi Meira, Here's the information from our documentation about each of the "fulfillmentStatus" values: NEW - the menu item selection has been added to a check but has not been sent to the KDS for p...

Hi Meira, Here are the values that the "source" value on an order can have: In Store Online OPT API Kiosk Caller Id Google This information is from our Order object specification in our docs. If ...

Hi Jonathan! You've found an example of a time when our loyalty spec is out of sync with our orders spec, which is something we're working on resolving (i.e. allowing the two specs to sync automati...

Hi Steven, Just noticed that we hadn't posted a reply here. In case others find this post, here is a link to the other post about this question. We've let our loyalty product manager know that you'...