Skip to main content

Nomni Console fixes, October 2026: Donation report and menu product search

The Donation report no longer times out, and menu product search finds non-English names.

L
Written by Lucien Hopkinson

Quick answer: The Donation report in Nomni Console no longer times out, and searching for a product with non-English characters in its name now works when you add it to a menu. These fixes went live on 21 October 2026. You don't need to do anything.


Donation report loads without timing out

The Donation report could time out and show no results. It now loads faster.

  1. In the top bar click BI, then in the left menu go to Sales > Donations.

  2. Set Created From, To and the Company (store).

  3. Click Export if you need a file.

What you should see: the donations for your dates show in the table, with Total Donation Amount at the bottom.

Good to know: Created From can't be set earlier than 1 January 2026. If you need donations from before then, contact us.


Product search in the menu editor finds non-English names

When you added a product to a menu, searching for a product whose name uses non-English characters (for example Korean, Chinese, Japanese or Thai) could fail to find or load it. Search now matches these names.

  1. Open your online ordering menu in Nomni Console and add a product.

  2. In Search Product, type at least 2 characters of the product name.

  3. Pick the product from the list.

What you should see: the product shows in the list and its details load the first time you pick it.


If something goes wrong

The Donation report is empty

Check the dates and the Company you picked, and that your POS has synced recently.

A product still doesn't show in the search

  1. Check the product is published and not archived. Only published products show.

  2. Try typing a different part of the name.

  3. If it still doesn't show, contact us with the product name and a screenshot.


Need help?

Message us from the chat in Nomni Console, email support@nomni.ai or call 1300 445 483.

Did this answer your question?