When a customer submits a product registration, a dozen things should happen next. Their warranty should start counting. Their serial number should land in the right spreadsheet. High-value purchases should flow into your VIP email segment. Anything that looks off should ping the right person on your team.
None of that happens while the data sits in an app. It happens when the data can act — and on Shopify, the engine for that is Shopify Flow, the free automation tool that connects your apps to the rest of your store.
The My Product Cares “Product registration submitted” trigger has always been able to start a Flow workflow. What’s new is what the workflow can see: the complete submission — every field, including the custom ones you designed yourself.
The Gap We Closed
Flow triggers work with a fixed list of variables, and ours used to be a short one: the product, the email, the serial number, a few basics. Perfectly workable — until your form asks a question that isn’t a basic.
And that’s exactly what custom fields are for. “Where did you purchase this?” “What’s your bike’s frame number?” “Which store handled the sale?” A dropdown for the product’s color, a checkbox for marketing consent, a text field for the retailer’s name — the questions that make a form yours.
Until now, a Flow workflow couldn’t see any of it. The answer was safely stored on the registration, but your automations were blind to it. If you wanted “customers who bought at a physical store get a different welcome email,” that was a manual export job.
Not anymore.
What the Trigger Exposes Now
Every workflow you build on the trigger gets the full picture:
| Variable | What it gives you |
|---|---|
| Product | The registered product, as a Shopify product reference |
| Product name, Email, Phone | The essentials, ready to drop into any action |
| Serial number | Registered serial number(s), comma-separated |
| Purchase date | When the product was bought |
| Order ID | The Shopify order, if collected on the form |
| First name, Last name, Street address, City, State, Zip code, Country | The complete customer record |
| Form slug | Which form the submission came from |
| Form fields | Every field the customer submitted — including your custom fields |
That last line is the big one. Form fields is a complete list of the submission as name-and-value pairs: every standard field and every custom field, exactly as the customer filled it in. Inside Flow, you can loop over it with a For each step to act on each answer, or pass the whole thing to an HTTP request step as JSON — straight into your ERP, a Google Sheet, Slack, or anything with an endpoint.
One detail we’re proud of: for dropdowns, radio buttons and checkboxes, the values arrive as their readable labels — “Matte Black”, not matte-black — so what your workflow sees is what a human submitted.
Workflows That Were Impossible Last Month
A few examples of what this unlocks:
Segment by purchase channel. Your form asks where the product was bought. Flow checks the answer: retail-store buyers join your “in-store experience” Klaviyo flow; online buyers get the standard welcome series. One field, two journeys, zero manual sorting.
Route high-value registrations. Purchase date within the last 30 days and the right product? Trigger a white-glove onboarding email, or create a task for your support team to reach out personally.
Sync every registration to a metaobject. Loop over the Form fields list and write each answer into a metaobject — suddenly your registrations are first-class Shopify data you can display on the storefront or use anywhere in the admin.
Flag what needs a human. A registration with no order ID, an unusual serial number pattern, or a warranty claim on a product line you’ve had issues with — send it to Slack for review before it quietly becomes tomorrow’s support ticket.
Feed the tools you already use. Because the full submission can travel as JSON, integrations that Flow doesn’t have native actions for are suddenly reachable — no custom development, no waiting on an integration roadmap.
Getting Started
- In the My Product Cares admin, go to App settings → General → Shopify Flow trigger and make sure it’s enabled.
- In your Shopify admin, open Apps → Shopify Flow and create a new workflow.
- Choose My Product Cares → Product registration submitted as the trigger.
- Add your conditions and actions — the variables above are available everywhere in the workflow. For custom fields, add a For each loop over Form fields.
Two small things worth knowing: for multi-product registrations the trigger fires with the first product (use the Form slug and Serial number to correlate with the full submission in the app), and very long field values are trimmed to 2,000 characters so payloads stay within Shopify’s limits.
The Bottom Line
Product registration was never meant to end at a database entry. It’s the opening move of your after-sales relationship — the moment a customer tells you who they are, what they bought, and what they need. Every field you collect is a signal, and now every signal can drive automation across your whole store: emails, segments, tasks, data syncs, alerts.
This is also what being built for Shopify means in practice. Your registration data doesn’t live in a walled garden — it flows (literally) into the tools you already run your business on.
Ready to wire it up? Enable the Flow trigger in App settings → General, open Shopify Flow, and build your first workflow on the full submission. New to My Product Cares? Install it from the Shopify App Store — and if you’re syncing registrations into Klaviyo, see how automated flows and registration data work together.
Every field is a signal. Now every signal can act.
