Блог EN
2026-11-14 14:55 Email Marketing

Order-ready email arrives too early: test automation triggers and status mapping

A customer receives “Your order is ready for pickup”, goes to the store and learns that staff are still assembling it. The trigger may use the wrong event, incorrectly map shop and CRM statuses, process delayed synchronisation or handle the same incoming webhook twice. The entire event path—from real fulfilment state to email delivery—must be checked, not just the message text.

Define the actual business event

“Paid”, “accepted”, “assembling”, “ready” and “collected” mean different things. A purchase trigger cannot legitimately send an email headed “Ready” if packing is unfinished. Confirm the exact readiness event with operations. It should come from the system responsible for the physical process, not an indirect marketing tag.

The RU article points to a separate analysis of service notifications and payment milestones; there is no reason to assume its language-specific blog URL exists without checking.

Check what the integration can genuinely deliver

MailerLite documents e-commerce purchase triggers, but a purchase event is not automatically a warehouse readiness signal. Physical status may require a separate event from CMS, ERP, CRM or fulfilment software, if the selected integration supports it. Confirm store platform, connected service, version and account permissions.

Email marketing and automation may include scenario design, but the source of fulfilment status needs independent verification. Sometimes technical integration changes are required between the shop and email system.

Protect against duplicate and late events

A webhook can be delivered again, a server can process a request late and staff may revoke readiness because a package is incomplete. Decide which events must never send a message, whether retries are safe and how a cancellation is handled. Logs should connect order ID, original status, event, automation decision and message ID without leaking unnecessary personal information.

Worked hypothetical TASK-091: order status sequence

Test order ORD-091 follows paid → assembling → ready → collected. A readiness message may be sent only in ready, once per order. Events arrive as paid at 09:00, assembling at 09:10, ready at 09:40 and duplicate ready at 09:41.

  1. Map source statuses to the rule: paid and assembling must never trigger “ready”.
  2. Bind sending to the confirmed transition to ready, not to order creation.
  3. Use an agreed idempotency key combining the order and notification type.
  4. Replay the second ready event: no second email is allowed.
  5. Simulate a revoked-ready state and an email-provider failure, then agree safe retry logic.

Positive test: one correct email after 09:40. Negative test: one email at 09:00 or a duplicate at 09:41. If the underlying issue is a warehouse sync error, change the event pipeline instead of rewriting the subject line.

Separate email automation from event development

The published email marketing commercial offer describes automated sequences, CRM integrations and technical error monitoring. It does not make a real-world ready-for-collection event appear by itself. First identify the source system, status owner, cancellation and redelivery conditions. Scope the email workflow and any custom integration work separately.

How to accept the repair

Request a state diagram, integration map, event logs and tests for successful, duplicate and cancelled orders. Service messages and promotional messages may have different legal requirements; classify them with qualified advice where needed. Send the agency a description of the shop, CRM, current messages and one anonymised failure. The deliverable is testable logic and a safe event path, not a guarantee against every future platform fault.

Order states and the precise sending point

Fictional shop ORDER-91 uses new, paid, assembling, ready and handed_over. “Your order is ready” must require an operations-confirmed transition to ready, not payment or start of assembly. A custom intermediary state such as “almost ready” must not silently count as ready. Specify the source, owner and meaning of each status before building the automation.

  1. Create O91-A in the test system and move new → paid → assembling. Expect no readiness email.
  2. After an operator confirms assembling → ready, expect exactly one send event.
  3. Deliver the same ready event a second time; prevent duplicate sends with an event identifier or equivalent agreed logic.
  4. Cancel an order before ready. No collection notice may be generated.

Logs and negative checks for TASK-091

For each case log the order ID, former/new status, event time, origin, selection rule, send ID, provider response and outcome. If the integration polls statuses, account for delays. If it uses webhooks, test duplicates and out-of-order delivery. Positive test: O91-A receives exactly one email after ready. Negative test: the mail is sent at paid, and a later manual return to assembling cannot undo the misleading message.

Determine whether CMS, ERP or warehouse is authoritative and who may mark ready. Email delivery alone is not proof of physical readiness. Include a state map, event contract, test orders and monitoring in the estimate; this is substantially more than writing one email template.

Order notifications should follow the actual fulfilment stage; the post-purchase email flow guide distinguishes dispatch, delivery and other order events, which can inform the trigger matrix without proving a particular shop integration.

The five email automation flows also require stop conditions and a reliable source of events; an order-ready notice must be checked against operational status rather than a generic sales sequence.