Product Messaging

Per-product emails and checkout messaging for Magento 2

Every SKU you sell has something worth saying after the sale - a warranty to register, a manual to open, an accessory that ships separately. OCM Labs Product Messaging lets you say it automatically. Define a rule once, match it to specific SKUs, and the module handles the rest: a native Magento email at the order-lifecycle point you choose, a CMS block on the checkout success page, or both.

One rule, two moments

A rule matches a list of SKUs - exact or * wildcard - and drives two independent actions: send an email, and show a block on the checkout success page. Turn on one, the other, or both. A drill's warranty rule can email a registration reminder three days after shipment and still show "register your warranty now" the moment the order is placed. One order can trigger multiple emails and multiple success-page blocks, one per matched rule.

Built on Magento's own templates and blocks - no lock-in

There is no proprietary template language to learn. Emails are ordinary Magento email templates, edited in Marketing > Communications > Email Templates with the same var, trans, if and for directives you already use for order confirmations. Success-page content is an ordinary CMS static block, authored in Content > Blocks. Two sample templates - a warranty email and an instruction-manual email - install automatically so you have a working example on day one.

Never slows down checkout

Matching a rule against an order is a cheap database write, not a template render or an HTTP call. When an order is placed, invoiced or shipped, an observer checks the SKUs, inserts a queue row and returns. A background cron job does the actual sending a minute later. If a rule is misconfigured, the failure is logged and swallowed; it never breaks checkout, invoicing or shipping.

Every order gets exactly one email per rule

A unique constraint on the rule-and-order pair means a rule can never email the same order twice - not on a double save, not across a re-invoice, not across two partial shipments of the same order. A shipment-triggered rule only fires when a matched SKU is actually in that shipment, so split orders don't produce duplicate or premature sends.

Attach the manual, not just a link

Rules carry PDF attachments that go out on every email they send. Uploads are checked against both file extension and actual file content, so a renamed non-PDF is rejected before it is ever stored. If an attached file goes missing by the time an email sends, the email still goes out without that attachment, with a warning in the log.

Meet buyers on the success page, while they're still paying attention

The checkout success page is the highest-attention moment in the order. A rule's success-page block shows up right there, only to buyers of the matching product: warranty registration, a manual download link, a note that the battery ships separately. It is evaluated fresh on every page view against the live order, works identically on Luma and Hyva, and leaves no empty markup behind for orders that don't match.

Technical details

• Magento Open Source / Adobe Commerce 2.4.7 - 2.4.9, PHP 8.2 / 8.3 / 8.4 / 8.5
• Magento Open Source: composer require ocmlabs/module-product-messaging
• Adobe Commerce: composer require ocmlabs/module-product-messaging-commerce (pulls in the module automatically)
• SKU matching with exact and * wildcard patterns, with optional child-SKU matching for configurable, bundle and grouped products
• Order-lifecycle triggers: Order Placed, Invoice Created, Shipment Created, each with an optional per-rule send delay
• PDF attachments per rule, MIME-verified at upload and size-capped
• Cron-driven send queue with automatic retry and exponential backoff, plus a full Email Log with Resend
• ACL-controlled admin access for rules, deletion, the Email Log and configuration