Drip Campaigns for Physical Products: A Playbook
Key Takeaways
- The first QR code scan at unboxing is the highest-intent signal a physical product manufacturer can receive from a customer — every post-purchase sequence should be built around that event, not email open rates.
- Apple's iOS 15 Mail Privacy Protection broke open-rate-triggered automation for a significant share of audiences; scan events are entirely unaffected and represent a strategically superior trigger.
- Customer.io's event-driven API architecture handles scan-triggered personalised sequences that Klaviyo and Mailchimp were not designed to support.
- A five-email post-registration sequence covering confirmation, setup, accessories, maintenance, and warranty renewal captures the full post-purchase relationship — and the spare parts and renewal revenue that goes with it.
Search for "drip campaign playbook" and you will find hundreds of guides. Almost all of them assume you are selling software subscriptions or e-commerce baskets. The triggers are page views, trial sign-ups, abandoned carts. The metrics are open rates and MRR expansion.
Physical product manufacturers are largely invisible in this conversation — which means there is a genuine competitive advantage waiting for any brand that gets this right.
The core insight is simple: when a customer buys a physical product, the moment of deepest engagement is not a page view. It is a scan. The first scan of a QR code at unboxing is the most high-intent signal a physical product manufacturer will ever receive from a customer. Every drip campaign for hardware, appliances, tools, or consumer goods should be built around that moment.
| Platform | Primary model | Physical product fit | iOS 15 open-tracking impact |
|---|---|---|---|
| Customer.io | Event-driven API | Excellent | Low — scan events unaffected |
| Klaviyo | E-commerce transactions | Moderate | High — email-open triggers break |
| HubSpot | CRM / marketing ops | Moderate | High — workflow triggers email-based |
| Braze | Mobile event streams | Good | Low — event-driven |
| Mailchimp | Broadcast lists | Poor | High — open-rate dependent |
Why Physical Product Drip Is Different
In SaaS, every customer interaction happens inside a system you control. Logins, feature usage, support tickets — all of it is instrumented. You know exactly what users do and when.
Physical products have the opposite problem. Once the box ships, you lose visibility entirely. You do not know if the customer set the product up, whether they are using it correctly, whether they have a problem, or whether they are even aware of the accessories that would make their purchase more valuable. Without a connected identity layer, the product disappears into a black hole the moment it leaves your warehouse.
The scan event changes this. When a customer registers via QR code — at unboxing, on first use, or during setup — they hand you something precious: a timestamped signal of intent, tied to an email address, attached to a specific serialised product. That event is your trigger.
This is fundamentally different from an e-commerce open rate or a website session. Klaviyo is brilliant at tracking whether someone opened a Black Friday email. It was not designed to receive "unit SN-4821 scanned in Manchester on 14 May" and fire a personalised sequence from that event. Customer.io, with its event-driven API architecture, was.
The Five-Email Post-Registration Sequence
A well-structured sequence does five jobs: confirms the relationship, guides setup, extends the basket, protects the product long-term, and creates a renewal touchpoint. Here is how each email earns its place.
Email 1 — Registration confirmation (immediate)
Sent the moment the scan event fires. This email does one thing: confirms the customer is registered, gives them their warranty reference number, and sets expectations for what comes next. Keep it short. The customer is mid-unboxing. A single CTA linking to a setup guide is enough.
Subject line: "Your [Product Name] is registered. Here's your warranty reference."
Email 2 — Setup and first use (Day 2)
Forty-eight hours after registration, the customer has had time to set up the product — or has stalled. This email provides the three most common setup questions, links to a video walkthrough, and offers a direct route to support. It deflects inbound support tickets before they are raised. Measure this email by support contact rate, not open rate.
Email 3 — Accessories and complementary products (Day 7–10)
A week in, the customer has formed an opinion of the product. This is the right moment to surface accessories, spare parts, or compatible products — not as an aggressive upsell, but as a genuinely useful recommendation. "Customers who registered [Product Name] also found these useful" performs better than a promotional banner. Conversion rate on spare parts and accessories is the metric that matters.
Email 4 — Maintenance reminder (Day 30–60)
Physical products need care. Filters need replacing. Blades need sharpening. Batteries need conditioning. An email timed to the realistic first maintenance window — for a product you know by serial number — is far more useful than a generic newsletter. This email builds long-term trust and drives repeat parts revenue. It also separates brands that understand their products from brands that just sell them.
Email 5 — Warranty renewal prompt (90 days before expiry)
If the customer's statutory or manufacturer warranty is approaching expiry, now is the time to offer an extended plan — either your own or via a partner like Domestic & General or Upsafe. You know the exact expiry date because you have the registration timestamp. A targeted, timely offer converts at multiples of a blanket promotional email (Epsilon Email Marketing Research, 2023). This is where the digital registration investment pays back most visibly.
Why Customer.io Beats Klaviyo for This Use Case
Klaviyo is excellent at what it was built for: e-commerce brands on Shopify or WooCommerce, where the transaction record drives everything. If you are sending post-purchase sequences triggered by Shopify order events, Klaviyo is hard to beat.
Physical product manufacturers typically sit outside that model. Their sales go through distributors, retailers, or direct B2B channels — not Shopify storefronts. Their trigger is not a transaction; it is a scan event fired from a connected product platform.
Customer.io's architecture is event-first. You send an event to their API — product_registered, serial_number: SN-4821, postcode: M1, product_sku: PRD-220 — and Customer.io fires the appropriate sequence, personalised by the data attributes you passed. There is no dependency on an e-commerce plugin or a transaction record. Any system that can make an HTTP POST request can trigger a Customer.io workflow.
Braze offers comparable event-driven capability and is worth evaluating for manufacturers with a mobile app component. For most mid-market manufacturers without a dedicated mobile engineering team, Customer.io's API-first model is the more accessible starting point.
The iOS 15 Problem and Why Scan Events Are the Solution
Apple's Mail Privacy Protection, introduced in iOS 15, broke open-rate tracking for a significant portion of email audiences (Litmus Email Analytics Report, 2022). When Apple pre-fetches emails on behalf of users, every email shows as "opened" regardless of whether the recipient actually read it. For brands that built automation triggers on open-rate signals — "if opened in 3 days, send follow-up; if not opened, send variant" — the data became unreliable overnight.
Physical product scan events are entirely unaffected. A scan happens when a customer physically picks up the product and points their camera at a QR code. It cannot be spoofed by a mail proxy. It is as close to ground-truth intent data as you will find anywhere in the marketing stack.
This makes scan events not just a convenient trigger, but a strategically superior one. As email open-rate reliability continues to erode, brands with scan-driven automation have a durable signal that competitors relying on email engagement metrics do not.
For a deeper look at how scan data shapes post-registration communication, see our guide to product scan data and customer communication. And for the mechanics of what happens in the first email after a scan, our post-scan email after registration article covers the technical setup in detail.
Measuring What Actually Matters
Drip campaigns for physical products should be measured on different KPIs than their SaaS or e-commerce equivalents. Open rate tells you almost nothing. Here is what to track instead.
Spare parts and accessories conversion rate. What percentage of registered customers purchase a complementary product within 90 days? This is the most direct revenue signal from your Email 3.
Support deflection rate. Do customers who receive the setup email (Email 2) contact support at a lower rate than those who do not? Reduced inbound contact volume is a direct cost saving.
Warranty renewal rate. What percentage of customers with expiring cover take up a renewal offer? This metric captures the long-term value of the registration relationship.
Scan-to-registration rate. Before any of the above matters, you need to know what proportion of shipped units are generating a scan event. Low scan rates indicate a packaging or placement problem — the QR code may not be visible, or the value exchange is not clear. This is the top-of-funnel metric for the entire programme.
FAQ
Do I need a Shopify store to use Customer.io for physical product drip?
No. Customer.io is platform-agnostic. It receives events via a REST API — you send a JSON payload when a product is registered, and Customer.io handles sequencing, personalisation, and delivery. It integrates cleanly with connected product platforms like Branded Mark, which fire registration events automatically when a customer scans. No e-commerce platform required.
How do we handle customers who never scan the QR code?
Some customers will not scan, and that is a recoverable situation. If you have an order email address from a retail partner or your own store, you can send a lightweight registration prompt at 48 hours post-purchase. Keep it simple: one CTA, the benefit stated plainly ("register to activate your warranty"), no form beyond email and product serial. For retail-distributed products where you have no email at all, the packaging QR remains the primary capture mechanism — invest in making the scan prompt visible and the value exchange unmistakable.
Is this approach viable for B2B or trade customers?
Yes, with adjustments. B2B drip sequences tend to be longer, slower-paced, and more focused on compliance documentation, maintenance scheduling, and renewal conversations than consumer upsell. The trigger architecture is identical — a scan or registration event fires the sequence — but the content and cadence differ. A contractor scanning a hired tool into their site register has different needs from a consumer unboxing a coffee machine. Segment by customer type at registration and serve each a purpose-built sequence.