Instructions for Push Notifications

The add-on sends browser push notifications and SMS to CS-Cart administrators and customers. It is suitable for automatic alerts about orders, products, and users, as well as for manual messages and delayed sending through cron.

What the add-on does

• sends browser push notifications through Firebase;
• sends SMS through several providers;
• reacts to store events related to users, products, and orders;
• supports separate rules for administrators and customers;
• allows manual sending and scheduled delivery;
• keeps a notification history in the log.

The add-on is useful when you need to quickly notify people about new orders, status changes, new customers, and stock problems.

Where to find it

The add-on is configured on its settings page in the CS-Cart admin panel. Inside you will find separate sections for general settings, push notifications, SMS, feedback, and help.

• General — SMS service selection, service credentials, Firebase parameters, cron password, and notification icon.
• Push Admin Notifications — admin tokens and phone numbers, plus sending conditions.
• Push Customer Notifications — customer push conditions and manual push sending.
• SMS Admin Notifications — admin phone numbers and SMS conditions.
• SMS Customer Notifications — customer phone selection and SMS conditions.
• Feedback and Help — built-in service blocks.

To check the result, use the message sending section and the notification log available in the add-on admin area.

General settings

First choose the SMS channel you will use. After that, fill in only the fields for that provider.

• SMS Service — SMS.ru, TurboSMS, TargetSMS, OsonSMS, SMS Xabar, Imobis, MTS, or SMS Center Kazakhstan.
• SMS.ru — API key.
• TurboSMS — login, password, and sender.
• TargetSMS — login, password, and sender.
• OsonSMS — login, hash, and sender.
• SMS Xabar — login, password, and originator.
• Imobis — token and sender.
• MTS — token and sender.
• SMS Center Kazakhstan — login, password, and sender.
• Firebase — Server Key, Web API Key, Project ID, and Sender ID for browser push notifications.
• Cron Password — protects the delayed sending command.
• Notification Icon — the image URL shown inside push notifications.

Firebase keys are required for push notifications. If they are missing, browser push delivery will not work.

Administrator push notifications

This section defines who receives administrator push notifications and under which conditions.

• Admin firebase tokens by comma — device tokens that should receive push notifications.
• Admin phones by comma — phone numbers used for SMS.
• New user registered — send a notification when a customer account is created.
• Product amount is zero or less — notify when stock drops to zero or below.
• New order is placed — notify about a new order.
• Order has been updated — notify when an order changes.
• Send just if order total exceeds — order total threshold.
• Send just if one of the following shipping methods is selected — shipping method filter.
• Send just if order status is one of the following — order status filter.

If several conditions are enabled, the add-on sends the message only when the current event matches them.

Customer push notifications

This section controls push messages that are delivered to the customer.

• Order has been updated — send push when the order changes.
• Shipping restriction — limit sending to selected shipping methods.
• Status restriction — limit sending to selected order statuses.
• Order total threshold — send only when the order total is above the configured value.
• Send manual pushes — allows manual customer push campaigns from the message section.

To deliver a customer push, the add-on needs a saved device token. It can appear when the customer works with the profile or updates their data.

Administrator SMS notifications

This section uses the same event logic as administrator push notifications, but sends SMS instead.

• Admin phones by comma — recipient phone numbers.
• New user registered — SMS on registration.
• Product amount is zero or less — SMS when stock runs out.
• New order is placed — SMS about a new order.
• Order has been updated — SMS when the order changes.
• Send just if order total exceeds — minimum amount required.
• Send just if one of the following shipping methods is selected — shipping filter.
• Send just if order status is one of the following — status filter.

Customer SMS notifications

Here you select the customer phone number and the conditions under which SMS is sent.

• Customer phone field — billing or shipping.
• Order has been updated — SMS on order changes.
• Send just if one of the following shipping methods is selected — shipping filter.
• Send just if order status is one of the following — status filter.
• Send just if order total exceeds — minimum amount required.
• Send manual SMS — allows manual SMS sending to customers.

Message templates

Order statuses can contain a message template that is used when the order status changes. The template supports these placeholders:

• %ORDER_ID% — order number;
• %AMOUNT% — order total;
• %NAME% — customer first name;
• %LAST_NAME% — customer last name;
• %USER_EMAIL% — customer e-mail;
• %COUNTRY% — shipping country;
• %ADDRESS% — shipping address;
• %CITY% — shipping city;
• %STATE% — shipping region or state;
• %TRACKING% — tracking number, if it is already available for the order.

For manual sending, you enter your own message text in the sending form.

Manual and delayed sending

The admin panel includes a separate message sending section. There you can select recipients by several criteria:

• user groups;
• individual users;
• phone numbers;
• customers by order date range.

The message can be sent immediately or delayed. For delayed delivery, set the date and time, then add the cron command from the settings hint to your server scheduler. The cron password is taken from the add-on settings.

The notification log shows the message text, event, send time, order ID, and delivery result.

How to test the add-on

1. Fill in the credentials for the selected SMS service and the Firebase parameters.
2. Add administrator tokens or phone numbers.
3. Enable at least one push or SMS event.
4. For a test, create a new customer, place an order, or change its status.
5. Check that the message reaches the device or phone and appears in the log.
6. Test manual sending from the message section.
7. If you use delayed sending, run cron and make sure the message is processed.

If a push does not arrive, first check browser notification permission and whether the customer has a token saved.