For arlanix/notification 1.0.0
Rule examples
Rules for what stores most often want to hear about. Make each as Rules says: Add rule, a Name, the Event and the Topic, then the conditions and the subject below. Leave Body empty for the event's own text, unless a body is given. Make the topic and subscribe its people first: see Topics.
A subject or a body that names personal data, such as a customer's name, sends it to everyone subscribed to the topic: send those to people who may see it.
Sales
Big refunds to accounting
- Event: Refund
- Condition: Refunded total equals or greater than 200
- Topic: Accounting
- Subject:
Refund of {creditmemo.grand_total_formatted} on order #{order.increment_id}
A refund is a Warning already, so a subscription that takes only warnings and errors gets it.
Orders paid by bank transfer
- Event: New order
- Condition: Payment method code is banktransfer
- Topic: Accounting
- Subject:
Bank transfer to expect: #{order.increment_id}, {order.grand_total_formatted}
checkmo is Check / Money order; another payment method has a code of its own, which your developer can tell you.
Wholesale orders
- Event: New order
- Condition: Customer group is Wholesale
- Topic: Wholesale
- Subject:
Wholesale order #{order.increment_id} from {customer.name||customer.email}: {order.grand_total_formatted}
The subject names the customer, which is personal data.
Orders on hold
- Event: Order status changed
- Condition: Status is On Hold
- Topic: Customer service
- Subject:
Order #{order.increment_id} is on hold, was {order.status_from_label}
Customers and catalog
Customers moved to wholesale
- Event: Customer group changed
- Condition: Customer group is Wholesale
- Topic: Wholesale
- Subject:
{customer.name} moved from {customer.group_from_label} to {customer.group_label}
Reviews to moderate
- Event: Review to moderate
- Topic: Catalog
- Subject:
Review of {product.name} to moderate - Body:
{review.nickname}: {review.title}
The nickname and the title are personal data: the body sends them.
The contact form to support
- Event: Contact form
- Topic: Support, delivered by email
- Subject:
Contact form: {contact.name}, {contact.email} - Body:
{contact.comment}
Everything in it is personal data. Replying to the email answers the store's sender, not the customer: write to the customer from your own mailbox.
Security and the system
Failed sign-ins as admin
- Event: Admin login failed
- Condition: Username is admin
- Severity: Error
- Topic: Store health
- Subject:
Failed admin sign-in as {admin.username}: {admin.reason}
Many stores have no user called admin: whoever tries it is guessing.
Sign-ins from a new device
- Event: Admin logged in
- Condition: From a new device is Yes
- Topic: Store health
- Subject:
{admin.username} signed in from a new device - Body:
From {admin.ip}, {admin.user_agent}.
The address and the browser are personal data. Each admin's first sign-in after the installation is from a new device: see Admin sign-ins.
Imports that left rows out
- Event: Import finished
- Condition: Errors greater than 0
- Severity: Warning
- Topic: Store health
- Subject:
{import.entity_label} import left {import.errors} rows out
Product feeds
A feed that fails, to the team
- Event: Feed failed
- Condition: State is Problem
- Topic: Feed alerts
The event's own text names the feed and why it failed. Without the condition, the team also hears, as Info, when the feed delivers again. More rules for feeds are in Get told when a feed fails.