Skip to main content

Order & payment messages

Each order or payment event sends one message to one side: the supplier or the customer.

Who uses it​

Nobody sends these by hand; they follow what staff do on an order or payment.

How it works​

EventToEmailSMSPush
A customer places, or staff record, an orderSupplierYesNoYes (New Order Received)
Order confirmed (Packing)CustomerYesYesYes (Order Confirmed)
Ready for Delivery, with the invoiceCustomerYesNoYes (Order Ready for Delivery)
DeliveredCustomerYesNoYes (Order Delivered)
CanceledCustomerYesOnly if it refundedYes (Order Canceled or Refund Issued)
Returns recordedCustomerYesNoYes
Payment recordedCustomer, and supplier for online paymentsYesYes (customer)Yes
Payment corrected or removedCustomerYesYesYes
Invoice due or overdue (reminder)CustomerYesYesYes (Invoice due)

SMS is kept to what a customer is waiting on, because it costs per text. A message is frozen as of the event: a confirmation quotes the total at confirmation even if the order changes later. A cancellation with a refund reads as a refund message; the supplier gets its own refund wording.

Muting a channel​

Clipp can switch email, SMS or push off for a supplier. A muted message is skipped, not failed, and is not retried. Suppliers cannot do this themselves.

Where it shows up​

Emails (with the invoice PDF on Ready for Delivery and Delivered), texts, and push in the apps. The supplier's order list shows new orders without any message.

Permissions​

No one configures these per user.

Known limitations​

  • A message is dropped if it is no longer relevant when sent, for example a reminder for an invoice that was just paid.

FAQ​

Why did the customer get an email but no text? Only confirmation, refund, payment and reminder events send texts.

Can I stop emails to customers? Not from the app. Ask Clipp to mute the channel.