Communication

Notifications are a personal inbox for system messages for the logged-in user — they serve to ensure that the administrator does not have to constantly monitor several modules simultaneously, but receives information the moment something relevant to their work happens. This typically involves a completed long-running background task, an integration error, or an event that requires the operator's attention. Unlike email messages, notifications function within the context of administration and complement it — they should therefore not serve as the primary channel for critical information, but as a quick overview during regular work in the system.

A newsletter is a typical gateway to a long-term customer relationship — the customer voluntarily requests regular information and in return receives offers, news, and useful content. The `/newsletter` module therefore manages a list of all subscribers, regardless of whether they signed up from the web, came via import, or were manually entered by an operator. It separates the signup phase from the confirmation phase, tracks the source of each subscription, and connects with the **Contacts** module as a unified recipient database, as well as with **Newsletter Campaigns**, which execute the mailings themselves. A clean and verified list of subscribers is p...

A newsletter campaign is a planned mass mailing of specific content to a defined group of subscribers. The `/newsletter-job` module serves to allow the operator to prepare, launch, monitor its progress in real-time, and subsequently evaluate how it performed. The campaign differs from a one-time transactional email primarily in that it runs in batches with speed limits — only a certain number of messages are sent each minute — to prevent blocking by mail servers and to ensure that the deliverability of other messages from the given domain does not decrease. The module builds upon **Newsletter** as a source of subscribers and **Emails...**

How BizKitHub queues, dispatches, retries, and audits every outgoing e-mail — from the platform's own transactional messages to admin-triggered marketing sends.

The `/emailer-template` page is used to manage email templates that the system uses for automatically sending messages. Typical examples include order confirmation, password reset, new customer welcome email, or a notification about a complaint status change.

The `/emailer-layout` page is used to set the general appearance — i.e., the layout — of all sent emails. A layout is a framework into which the content of individual messages is inserted. It typically contains a header with a logo, body border, and a footer with contact and legal information.