> ## Documentation Index
> Fetch the complete documentation index at: https://help.tapp.shop/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand notification types

> Recognize messages about orders, bookings, ratings, and other shop activity.

Notifications tell you about activity that may need your attention. Read the title and message to understand what happened, then check the related area of Tapp if you need to take action. The icon helps you recognize the subject, but does not tell you everything about the event.

## Who can do this?

Owners, Managers, and Staff can read the notifications delivered to their account. Some events notify particular roles or people, so colleagues in the same shop may see different messages. For example, menu-import results go to Owners and Managers. Not receiving a notification is not proof that nothing happened.

## Where

Open **Notifications** in the web app or use the header bell for recent unread messages. Check the selected shop and the time shown on the entry before acting.

## Recognize common messages

* **Orders:** new orders, payment updates, pay later orders, cancellations, and completed orders.
* **Bookings:** requests, new bookings, confirmations, cancellations, or changes to an existing booking.
* **Ratings:** feedback about an order or a staff member.
* **Messages and shop updates:** other information, such as a menu change or the result of importing a file.

Read the full message even when the icon looks familiar. A booking request may still need a decision; a confirmation describes a different stage. A file import message may ask you to check the imported menu or try again.

## Open the details

1. Read the title, message, and time.
2. Select the row to mark the entry as read.
3. If Tapp opens a related screen, check its current details before making changes.
4. If no screen opens, go to the appropriate area using the navigation.

Reading or dismissing a notification does not perform the task described in it. Check an order directly before assuming it is paid or completed.

## Temporary payment alerts

While you use the web app, a brief alert may report a payment received or failed for an order paid by QR code, payment link, or text message. It can concern an order started by a colleague in the selected shop. An order already open for payment, or sent to another device, uses its own payment flow instead.

These alerts are not a payment history. Opening the app or switching shops does not replay earlier payments. If no alert appears, open the order and check its current payment status before trying to collect payment again.

## Platform and market notes

These instructions cover the web app in both supported markets. The mobile app separately lets you choose certain order alerts for the device you are using. Those switches do not remove messages from the web notification list.

## Troubleshooting

If the wording is unclear, keep the message and contact Tapp support with its title, time, and shop. Use the actual order or booking details to resolve a time-sensitive question rather than relying on an older notification.

## Related articles

* [View and filter notifications](/en/notifications/view-and-filter-notifications)
* [Choose device notifications](/en/notifications/choose-device-notifications)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.