Order-notification texts communicate a verified change to an existing order. Start with a supported POS or ecommerce event, an eligible recipient and one clear pickup or service instruction. An order submitted, an order ready and an order collected are separate events. For a completed sale, the paperless receipt guide explains how to check the transaction record and receipt destination.
You can use Blackleaf Texting with supported existing POS systems without switching to Blackleaf POS. Confirm the exact order events, fields and sending setup for your store before activation.
Choose the event and next step
- Received: acknowledge only what the order source has confirmed. A submission is not necessarily store acceptance.
- Ready for pickup: use a staff-confirmed or supported source status, with the correct location and next step. If pickup will take longer than first estimated, confirm a revised window with the store. If the store cannot give a reliable time, tell the customer when staff will check again. Send the ready notice once the order is actually ready.
- Changed or canceled: recheck the latest status and stop queued alerts that no longer apply.
Check the recipient before texting
Blackleaf requires explicit recipient consent and age confirmation before order texts, including pickup updates. In the message flow, the intended recipient selects the birthday on file; never disclose the saved birthday. These are Blackleaf requirements, alongside the separate sending-route and content review.
Keep the update focused on the existing order. Adding a coupon or product recommendation changes its purpose and needs a separate eligibility review. An order or phone number is not blanket marketing permission.
Bring a clear setup brief
- Your order source, locations, event definitions and expected update timing.
- Which system already sends each notice, who handles replies and how cancellations or uncertain sends are reviewed.
- The proposed wording, required fields and pickup destination. If a customer opts out of SMS, record the separately permitted service fallback, such as email, and who checks the current order before using it. Review the order alert exception checklist before deciding whether another update is needed.
Read the detailed order-alert workflow for source checks and exceptions, review supported integrations, or discuss your proposed setup.
Treat fewer status calls or faster pickup as goals to measure. Define a comparable baseline and review actual order outcomes. A reported delivery status does not establish a read, completed pickup or extra revenue.