BackOfficeBenachrichtigungen
Alle auf dem Laufenden halten — Kunden, Operatoren und Fahrer — mit Push, E-Mail, SMS und WhatsApp.
Channels (Push, Email, SMS)
BackOffice supports five notification channels, each suited to different urgency levels and user contexts. Suppliers configure which channels are active at the organization level, and individual users can further customize their preferences.
| Channel | Best For | Delivery | |
|---|---|---|---|
| notifications_active | Push | Real-time alerts for mobile and desktop users | Instant |
| Order confirmations, invoices, daily summaries | Near-instant | ||
| sms | SMS | Critical alerts, delivery ETAs, OTP verification | Instant |
| chat | Rich delivery updates, order summaries with images | Instant | |
| inbox | In-App | Non-urgent updates, system announcements, task reminders | On next visit |
Supplier-level defaults: As a supplier admin, you set the default channels for each event type. For example, new order notifications can default to Push + Email, while payment reminders default to Email + SMS. Individual users can then opt in or out of specific channels.
Templates
Every notification is based on a template that defines the message content, formatting, and dynamic variables. BackOffice provides default templates for all standard events, and you can customize them to match your brand voice and communication style.
Rich Text Editor
Edit email templates with a visual editor. Add your logo, brand colors, and formatted content.
Dynamic Variables
Insert placeholders like {{client_name}}, {{order_total}}, or {{delivery_date}} that auto-fill at send time.
Multi-Language
Create template variants for each supported language. The system sends in the recipient's preferred language.
Preview & Test
Preview templates with sample data and send test messages to yourself before activating.
Triggers & Events
Notifications are sent automatically when specific events occur in the system. Each event type can be mapped to one or more notification channels, and you can enable or disable triggers independently.
Available event triggers
- shopping_cartNew order placed: — Notify the sales team when a customer submits an order via Supply Now
- check_circleOrder confirmed: — Notify the customer that their order has been accepted and is being prepared
- local_shippingOut for delivery: — Notify the customer with driver name and estimated arrival time
- done_allDelivery completed: — Notify the customer with delivery confirmation and proof of delivery
- receipt_longInvoice generated: — Send the invoice PDF to the client's billing contact
- paymentsPayment received: — Confirm payment receipt to both the supplier and client
- credit_card_offCredit limit warning: — Alert the sales team when a client approaches or exceeds their credit limit
- cancelOrder cancelled: — Notify all relevant parties when an order is cancelled
- assignment_returnReturn requested: — Alert the operations team when a customer initiates a return
Preferences
Every user can customize their notification preferences from their profile settings. They choose which events they want to be notified about and through which channels — without requiring admin intervention.
The preference system works in layers: supplier defaults serve as the baseline, and individual users can override them. Critical notifications (security alerts, system maintenance) are always delivered and cannot be disabled by users.
Quiet hours: Users can set quiet hours (e.g., 20:00 to 07:00) during which non-critical push notifications are held and delivered as a digest the next morning. Critical alerts always come through regardless of quiet hours.
Explore the 8Move Platform