Billing and notifications

Notifications

What the platform tells you, what it tells your customers, and how to get told about the things it does not mention.

Three different things get called notifications, and they have nothing to do with each other. Sorting them out is most of this page.

What the Cockpit tells you

The bell in the top bar opens the Notifications panel. It draws on your tenant's event stream, what the apps and integrations in your platform did, and shows the most recent entries with an unread count. Mark all read clears the count; View all events opens the full Event stream in Integration Studio, where you can search and filter. When there is nothing new, the panel says so.

Two honest limits:

  • It is a feed, not an alerting system. Nothing here watches a number and warns you when it crosses a line.
  • Everyone sees the same feed. There is no per-person choice of which events reach the bell.

Do not use the unread count as a work queue.

Notification rules: planned. A screen where you pick the events that matter to you and route them to email is not yet on your tenant. Until it lands, the way to get told about something specific is the workflow described below, and it is the better tool for anything that has to reach someone who is not looking at the Cockpit.

What your customers are told

Order confirmations, dispatch notes, password resets, the mails your buyers receive: that is transactional messaging, and it is a different system entirely. It is configured with your storefront, not here. See Forms and email.

The distinction matters because the two are often confused in the same sentence: "turn on order notifications" can mean tell my Innendienst or tell the customer, and they are configured in different places by different people.

Getting told about things that matter

For anything you need to know about, a failing nightly ERP sync, an order stuck for two days, a customer whose orders stopped, build the alert rather than wait for it.

Events and webhooks let a workflow react to what happens on the platform, and a workflow can send mail, post to a channel, or call another system. That is where alerting lives today:

Start with one. The most valuable alert in most B2B setups is "the nightly sync failed". It fails on a Sunday, nobody notices until Tuesday, and by then three days of prices are wrong. Build that one first and add others only when somebody asks.

What to check

Ask the person who would need to act at 07:00 on a Monday how they would find out. If the answer is "I would open the Cockpit and look", you have no alerting and should build the workflow.

Next

Subscription and billing

Your plan, your add-ons, your invoices, and the two changes that cost money immediately.

Security and data protection

Access hygiene, and the data-protection paperwork a German company cannot avoid.