01 · Direct answer
How do you send an abandoned-cart postcard from Shopify?
Use the customer or checkout ID, cart time, postal address, cart value band, and offer version. Add a delay that fits production time. Immediately before release, check for a completed order, duplicate send, suppression, or expired offer.
Shopify Flow HTTP request retries make idempotency necessary. A retry must not create another postcard.
- Choose abandonmentDefine the event and inactivity window.
- Check addressUse only a complete postal address collected for a valid business purpose.
- Delay and recheckStop when the customer buys, unsubscribes, or becomes ineligible.
- MeasureUse an offer code or declared response source without treating tracking as purchase proof.
02 · Direct answer
How do you add postcards to a Klaviyo win-back flow?
Define inactivity from the business's own purchase data. Exclude recent purchasers, suppressed profiles, incomplete addresses, and recent postcard recipients. Save the Klaviyo profile ID and the flow or segment version with the mail record.
A Klaviyo profile entering a flow does not prove that a public Sendvo action exists. Confirm the connection method first.
03 · Direct answer
How do you send a post-purchase thank-you postcard from Shopify?
Use the order ID as the source key. Choose the recipient and address snapshot. Exclude refunds, test orders, canceled orders, and repeated orders inside the thank-you window. Do not use customer creation as proof of payment.
The message should not promise delivery timing that the mail workflow cannot guarantee.
04 · Direct answer
How do you update Mailchimp after direct-mail delivery or response activity?
Use the Mailchimp Marketing API or an approved connector to update a tag, merge field, or event. Save the mailpiece ID and event time. Label mailstream signals as operational. Only record a response when a declared response source, such as a code, call, form, or order, supplies that evidence.
Do not use a mailstream event as proof that a recipient saw the piece or bought something.
Implementation worksheet
Ecommerce event and stop-rule matrix
Each workflow needs an event that starts the clock and a condition that stops the send.
| Workflow | Start event | Stop before release |
|---|---|---|
| Abandoned cart | Checkout inactive for the chosen window | Completed order, missing address, suppression, duplicate, or expired offer. |
| Win-back | Customer crosses the inactivity threshold | New purchase, suppression, missing address, or recent postcard. |
| Post-purchase thank-you | Paid or fulfilled order | Refund, cancellation, test order, or duplicate order window. |
| Mailchimp status | Mail status or declared response event | Do not mix operational status with response evidence. |
Preflight checklist
- Use one stable source-event ID and save it with the mail record.
- Require recipient name, address line 1, city, state, and ZIP Code before release.
- Set a duplicate rule for the person, household, property, order, or job.
- Render a proof with a test record before any funded send.
- Define who can pause the workflow and who can approve release.
- Store the source record ID, campaign ID, and returned mailpiece ID together.
- Treat mailstream events as operational signals, not proof of attention or revenue.
FAQ
Questions to resolve before launch
Does Shopify Flow retry failed HTTP requests?
Shopify documents retry behavior for the Send HTTP request action. Use a stable event key and idempotency to prevent duplicates.
Does customer creation prove payment?
No. Use a paid, successful, or fulfilled event that matches the message and verify the current event semantics.
Does mail tracking prove an ecommerce conversion?
No. Keep mailstream status separate from purchase or response evidence.
Primary sources
Sources and review notes
- Shopify Flow: Send HTTP requestOfficial HTTP request, retry, and plan behavior.
- Shopify Flow: TriggersOfficial Shopify workflow trigger catalog.
- Klaviyo: Webhooks in flowsOfficial outbound webhook action guidance.
- Mailchimp Marketing APIOfficial member, tag, merge-field, and event APIs.
Product plans, trigger names, and connector access can change. Check the linked documentation and your account before production use. Sendvo last reviewed these sources on August 31, 2026.