The integration does not create or activate a Klaviyo flow. TValue decides when an enabled wishlist event is ready and sends its data; Klaviyo controls the flow filters, timing, channels, and messages that follow.

What TValue sends to Klaviyo​

The integration provides six metrics. Each represents a different shopper action or product change, so it should have a distinct role in Klaviyo.

TValue can associate events with logged-in customers and with guests who have submitted an email address. An anonymous guest who has not provided an email cannot be connected to a Klaviyo profile.

The event data varies by metric, but can include:

• Customer email, name, and phone when available
• Product title, image, URL, ID, and handle
• Selected variant and variant-specific product URL
• Product price and formatted price
• The time an item was added to the wishlist
• A consolidated array of saved products for Wishlist Reminder
• Previous and current prices for Price Drop
• Inventory changes and the selected threshold for stock events

This data can be used in Klaviyo trigger filters, conditional logic, and dynamic email content.

Built-in automation or Klaviyo?​

TValue provides built-in email automations as well as Klaviyo integration. Choose where you want each customer message to be managed.

Avoid enabling two equivalent customer messages by accident. For example, if the built-in Price drop alert and a Klaviyo flow both send an email for the same price change, the shopper may receive duplicate notifications.

Connect TValue to Klaviyo​

1. Create a Klaviyo Private API Key​

In Klaviyo:

1. Open Settings > API keys.
2. Click Create Private API Key.
3. Give the key a recognizable name, such as TValue Wishlist.
4. Choose Full Access Key, or use custom access and grant at least read/write access to Events.
5. Create the key and copy it.

Klaviyo only displays a newly created private key once, so store it securely while completing the connection. See Klaviyo's current instructions for creating a Private API Key.

2. Connect the integration​

In TValue: Wishlist:

1. Go to Integrations > Klaviyo.
2. Turn on Enable integration.
3. Paste the key into Private API key and click Connect.
4. Confirm that the connection status changes to Connected.
5. Save the integration settings.

The key is used to send events from this store to the connected Klaviyo account. If the key is revoked or becomes invalid, the integration shows a connection error and must be reconnected with a valid key.

Choose and configure the events​

Use Event settings to enable only the metrics you plan to use. The integration has one global switch and a separate switch for each event.

Three events also have their own delivery settings:

Select the currency used to format product prices in the event data. This matters when the Klaviyo email displays prices from TValue's event properties.

Wishlist Reminder timing deserves particular attention. Its delay runs in TValue before the consolidated metric is sent to Klaviyo. Any time delay added to the Klaviyo flow begins after that, so the two delays are cumulative.

For example, a 6-hour reminder delay in TValue followed by a 2-hour Klaviyo flow delay produces an effective wait of about 8 hours. Use the Klaviyo delay only when the additional wait is intentional.

For a detailed explanation of consolidation, see How to Send Automated Wishlist Reminder Emails on Shopify.

Send a test event​

Test one event before building its production flow.

1. In Event settings, click Send test event for the event you want to use.
2. Select a customer and the product data requested by the test form.
3. Review Event data preview.
4. Send the event.
5. Open Klaviyo and find the corresponding TVAW: metric.
6. Confirm that the profile and expected event properties arrived.

The test uses customer and product data from your store and follows the same property structure as a real event. This gives Klaviyo usable preview data before the flow receives live wishlist activity.

Keep the Klaviyo message in draft or manual mode while testing. A test event is sent to Klaviyo as an actual metric and can enter a live metric-triggered flow if its filters allow it.

Build a metric-triggered flow in Klaviyo​

After Klaviyo has received the metric:

1. Create a new flow in Klaviyo.
2. Choose Metric as the flow trigger.
3. Select the relevant TVAW: metric.
4. Add trigger filters or flow filters only when they serve a clear targeting rule.
5. Add the email or SMS messages for that event.
6. Preview the message with the test event data.
7. Keep the flow in draft or manual mode until the content and timing have been verified.

Klaviyo explains that a metric-triggered flow can run every time a profile performs the corresponding action unless its filters or re-entry rules limit qualification. Review Klaviyo's metric-triggered flow documentation before activating the flow.

Use one primary intent per flow:

• Wishlist Item Added can begin an immediate workflow based on a new save.
• Wishlist Reminder is better when TValue should first group several recent saves into one event.
• Price Drop, Back In Stock, and Low Stock should explain the specific product change.
• Wishlist Item Removed can update your downstream logic, but should not automatically be treated as a reason to send a promotional email.

Add wishlist products to the Klaviyo email​

TValue includes prebuilt product blocks for:

• Wishlist reminder and Wishlist Item Added
• Price drop
• Back in stock
• Low stock

To use one:

1. Open Integrations > Klaviyo > Email templates in TValue.
2. Choose the product block that matches the flow event.
3. Click Preview and edit to adjust its visual settings.
4. Copy the generated HTML.
5. Open the corresponding flow email in Klaviyo.
6. Add an HTML block and paste the copied code.
7. Preview the email using the matching TVAW: event data.

The copied code is a dynamic product block, not a complete Klaviyo flow. Its variables are populated from the event that triggered the message, so use the block with its supported metric and test it inside that flow before publishing.

Klaviyo supports custom code through an HTML block and supports arrays of event variables for repeated product data. See Klaviyo's guides to the email template editor and event-data personalization.

Review Event logs in TValue​

Open Integrations > Klaviyo > Event logs to check what TValue attempted to send. Logs can be filtered by event, status, and date range.

Open a log to review:

• Whether the event is pending, sent, skipped, or failed
• The customer profile associated with it
• Product or consolidated wishlist data
• The event properties payload
• The failure or skip reason when available

The two platforms answer different questions:

• TValue Event logs: Did the app prepare and send the expected event data?
• Klaviyo flow activity: Did Klaviyo accept the profile into the flow, and what happened to its messages afterward?

Check TValue first when the metric or product data is missing. Check Klaviyo flow activity when the metric arrived but the profile did not receive the expected message.

Launch checklist​

Before setting a Klaviyo flow live, confirm that:

• The integration and the required event are enabled.
• The Private API Key connection shows Connected.
• A test event appears under the correct TVAW: metric.
• Product, variant, price, and URL data render correctly in the email.
• Reminder and Klaviyo delays do not create an unintended combined wait.
• The same event is not sending duplicate emails from TValue and Klaviyo.
• Klaviyo consent, sending, and re-entry rules match the store's messaging policy.
• TValue Event logs and Klaviyo flow activity can both be checked after launch.

For the complete setting reference and troubleshooting details, see the TValue Klaviyo documentation. To use wishlist events in another workflow system, continue with How to Send Shopify Wishlist Events to Omnisend or How to Use Wishlist Events in Shopify Flow.

Install True Value Wishlist Email on Shopify

TValue determines when an enabled event is ready and sends its contact and wishlist data. Omnisend controls the workflow filters, delays, channels, and messages that run after the custom event arrives.

What TValue sends to Omnisend​

The integration provides six custom events:

Omnisend custom events require an identified contact. TValue can send them for logged-in customers and guests who have submitted an email address. A guest who has not provided an email cannot be associated with an Omnisend contact for these events.

Depending on the event, its properties can include customer identity, product and variant details, storefront URLs, images, formatted prices, added time, price changes, inventory changes, or an array of consolidated wishlist products.

Built-in automation or Omnisend?​

TValue's built-in email automations and Omnisend workflows are separate delivery paths.

Avoid sending the same customer notification through both paths unless the overlap is intentional. An enabled TValue price-drop email and an active Omnisend price-drop workflow can otherwise respond to the same product change with two messages.

Connect TValue to Omnisend​

1. Create an Omnisend API key​

In Omnisend:

1. Open Store Settings > API keys.
2. Click Create API key.
3. Enter a recognizable name, such as TValue Wishlist.
4. Select Events permission.
5. Create the key and copy it.

Omnisend does not display the key again after the creation screen is closed. See Omnisend's current instructions for generating an API key.

2. Connect the integration​

In TValue: Wishlist:

1. Go to Integrations > Omnisend.
2. Turn on Enable integration.
3. Paste the key into API key and click Connect.
4. Confirm that the connection status changes to Connected.
5. Save the integration settings.

If the key is deleted or revoked in Omnisend, TValue can no longer submit events. Create a new key with Events permission and reconnect the store.

Choose and configure events​

Use Event settings to enable only the custom events you intend to use in Omnisend. Three events also require a delivery rule in TValue:

Select the currency code used to format prices in event properties. This ensures that product blocks and personalized fields use the intended display currency.

The Wishlist Reminder delay runs in TValue before Omnisend receives the event. If the Omnisend workflow adds another delay, the two waits are cumulative. For example, a 6-hour TValue reminder delay followed by a 2-hour Omnisend delay creates an effective wait of about 8 hours.

Read How to Send Automated Wishlist Reminder Emails on Shopify for the complete consolidation behavior.

Send the first custom event​

Omnisend only shows a custom event in its automation trigger list after that event has been received at least once. Send a test event from TValue before creating the workflow:

1. Find the event under Event settings.
2. Click Send test event.
3. Select the customer and product data requested by the form.
4. Review Event data preview.
5. Send the event.
6. In Omnisend, confirm that the matching TVAW: custom event now exists.

The test uses controlled data from your store and follows the same property structure as a real event. It also gives Omnisend sample properties that can be selected when configuring workflow conditions and content.

Omnisend documents how API custom events become workflow triggers and provide fields for personalization in Create and Manage Custom Events.

Build the Omnisend automation​

After Omnisend has received the custom event:

1. Go to Automations and create a workflow from scratch.
2. Choose the corresponding TVAW: custom event as the trigger.
3. Add trigger filters when the workflow should respond only to particular event properties.
4. Add audience filters or splits when the next step depends on contact data.
5. Add the email, SMS, or push notification steps required by the workflow.
6. Preview the event fields and test the message before enabling the workflow.

Keep each workflow tied to the meaning of its trigger:

• Wishlist Item Added is an immediate save event and can use an Omnisend delay when follow-up should happen later.
• Wishlist Reminder already waits and groups saved products in TValue before it reaches Omnisend.
• Price Drop, Back In Stock, and Low Stock should explain the product change that triggered the workflow.
• Wishlist Item Removed is useful for downstream logic, but removal alone is not necessarily a reason to send a promotional message.

Omnisend event data is available inside the workflow triggered by that event. It can be used in trigger filters, splits, and personalized message content. See Omnisend's event-data guide.

Add wishlist products to an Omnisend email​

TValue includes editable product blocks for:

• Wishlist reminder and Wishlist Item Added
• Price drop
• Back in stock
• Low stock

To add one to an automation email:

1. Open Integrations > Omnisend > Email templates in TValue.
2. Select the block that matches the custom event.
3. Click Preview and edit and adjust its visual settings.
4. Copy the generated HTML.
5. Open the matching automation email in Omnisend.
6. Drag a Custom HTML block into the Email Builder.
7. Paste the generated code and save the block.
8. Preview the email with data from the corresponding event.

The generated code is a product block, not a complete Omnisend workflow or email. Its variables depend on the event properties supplied by TValue, so use it with its supported custom event and test the rendered products before enabling the automation.

Omnisend's Custom HTML block accepts body content inside an email and should be tested across the inboxes that matter to the store. See Add and Configure a Custom HTML Item.

Review Event logs​

Open Integrations > Omnisend > Event logs to review real and test events. Filter the list by event, status, or date range.

Each log can show:

• Whether the event is pending, sent, skipped, or failed
• The contact associated with the event
• Product or consolidated wishlist data
• The complete event properties payload
• The failure or skip reason when available

Use the two systems together:

• TValue Event logs confirm what the app attempted to submit.
• Omnisend automation activity shows whether the contact entered the workflow and what happened afterward.

If no custom event arrives, start with the connection, event switch, contact identity, and TValue log. If the event arrives but the message does not send, inspect the Omnisend trigger, filters, channel eligibility, and workflow status.

Launch checklist​

Before enabling the Omnisend workflow, confirm that:

• The integration is enabled and the API key shows Connected.
• The required event is enabled in TValue.
• A test event appears under the correct TVAW: custom event.
• Product, variant, price, image, and URL properties render correctly.
• TValue and Omnisend delays do not create an unintended combined wait.
• The same event is not sending duplicate emails through two systems.
• Omnisend audience, consent, frequency, and channel settings match the store's messaging policy.
• Both TValue Event logs and Omnisend automation activity can be checked after launch.

For the full setting reference, see the TValue Omnisend documentation. To use the same wishlist activity in Shopify's workflow builder instead, continue with How to Use Wishlist Events in Shopify Flow.

Install True Value Wishlist Email on Shopify

TValue sends the trigger and its wishlist data. Shopify Flow then evaluates the conditions and performs the actions defined by the merchant, such as updating customer data, notifying a team, or passing information to another Flow-compatible app.

What Shopify Flow does with wishlist events​

A Flow workflow has one trigger followed by any conditions and actions needed for that use case:

Shopify documents this trigger-condition-action model in Creating workflows in Shopify Flow.

Unlike Klaviyo and Omnisend, Flow does not automatically represent an email-marketing destination. It is a general workflow layer. The action might tag a customer, send an internal notification, add data to another service, or invoke an action supplied by a Flow-compatible app.

Available TValue triggers​

Enable any of these app triggers in TValue:

Shopify Flow events require a Shopify customer reference. For this reason, only wishlist activity associated with logged-in customers can trigger this integration. Guest wishlist activity does not trigger Shopify Flow, even when the guest has left an email address.

When to use Shopify Flow​

Shopify Flow is most useful when wishlist activity should affect a process beyond a single email.

Examples include:

• Add a customer tag after a logged-in shopper saves a product.
• Notify a merchandising team when a wishlisted product reaches a meaningful inventory state.
• Branch based on a product, variant, price, or inventory value supplied by the trigger.
• Record wishlist activity through a Flow connector such as Google Sheets.
• Pass the event to another installed app that provides a compatible Flow action.

Avoid treating every trigger as an instruction to contact the customer. Wishlist Item Removed, for example, describes a change in intent but does not by itself mean the shopper should receive a promotional message.

Enable the integration​

Before setup, install the free Shopify Flow app on the store. Shopify Flow is available on Shopify's Basic, Grow, Advanced, and Plus plans, although some actions have separate plan requirements. Review Shopify Flow availability and limits when a workflow depends on a specific action.

In TValue: Wishlist:

1. Go to Integrations > Shopify Flow.
2. Turn on Enable integration.
3. Enable the events you plan to use.
4. Configure their delay or threshold settings.
5. Select the currency used to format price data.
6. Save the settings.

There is no connection section or API key. The Flow triggers are extensions supplied by the installed TValue app.

Configure event timing and thresholds​

Three Flow triggers have additional settings in TValue:

The Reminder delay finishes before Shopify Flow receives the trigger. If the workflow adds a Wait step, that time begins afterward and extends the total delay.

For the reminder batching model, see How to Send Automated Wishlist Reminder Emails on Shopify. For price and inventory behavior, see How Shopify Wishlist Price Drop and Back-in-Stock Alerts Work.

Create a workflow​

In Shopify Flow:

1. Go to Apps > Flow.
2. Click Create workflow.
3. Select a trigger and choose TValue: Wishlist from the installed apps.
4. Select one of the six wishlist triggers.
5. Add a condition when the workflow should branch based on trigger data.
6. Add the Shopify or app action that should run.
7. Give the workflow a specific name.
8. Test the logic before turning it on.

Flow displays the variables made available by the selected trigger. Product-based events include Shopify customer and product references, allowing conditions and actions to work with the associated Shopify resources. The custom event fields expose wishlist, price, and inventory details that are specific to TValue.

For a reminder containing several saved products, the Wishlist items payload is a list. Use Flow's looping tools only when an action genuinely needs to run once per item; customer-level actions should usually remain outside that loop.

Build useful conditions and actions​

Use conditions to narrow the workflow instead of performing the same action for every event.

Examples:

The exact actions available depend on the store's Shopify plan and installed Flow-compatible apps. Keep the workflow name and notes clear enough that another staff member can understand why each wishlist trigger exists.

Test a TValue Flow trigger safely​

Each event in TValue has a Send test event action. Use it together with Flow's event-recording test mode:

1. Keep the workflow turned off while preparing the test.
2. In the Flow editor, click Test your workflow and start Record events.
3. In TValue, choose the trigger and click Send test event.
4. Select a logged-in Shopify customer and the required product data.
5. Review Event data preview, then send the event.
6. Select the recorded event in Flow and inspect the path, conditions, and variable output.

TValue marks the payload with Is test: true. This is an actual app trigger sent to Shopify Flow. Recording it through Flow's test mode lets you evaluate the workflow without performing actions that change store data. An early Is test condition is also useful when the team expects to send more TValue test events after the workflow is active.

This differs from Flow's own workflow test mode. Shopify states that a Flow test evaluates the workflow path but stops before actions that would make changes. TValue's Send test event is intended to verify the real app-trigger delivery and payload. See Testing a workflow in Shopify Flow for the native test behavior.

A reliable test sequence is:

1. Record the TValue test event and confirm the trigger data is available.
2. Use Flow's test tools to inspect conditions and variable output without performing live changes.
3. Confirm the Is test branch behaves as intended when one is present.
4. Turn on the production workflow only after the actions have been reviewed.

Understand the trigger data​

All TValue triggers provide Is test. The remaining fields depend on the trigger:

• Wishlist item: one saved or removed product with variant, price, image, URL, and related details.
• Wishlist items: a list of products consolidated for Wishlist Reminder.
• Price drop items: product entries with old and new price values.
• Back in stock items: product entries with restored inventory information.
• Low stock items: product entries with previous inventory, current inventory, and the configured threshold.
• Customer reference: supplied for every trigger.
• Product reference: supplied for single-product and product-change triggers, but not the consolidated Wishlist Reminder trigger.

Prefer Shopify customer and product references when an action expects Shopify resources. Use TValue's custom fields when the workflow needs the wishlist-specific snapshot that caused the trigger.

Review delivery and workflow runs​

Open Integrations > Shopify Flow > Event logs in TValue to inspect real and test trigger deliveries. Filter by event, status, or date range, then open a row to review its customer, product context, payload, and any failure details.

After the trigger reaches Flow, use Recent runs in Shopify Flow to inspect the workflow path, evaluated conditions, actions, and errors. Shopify documents available run filters in Finding and monitoring workflow runs.

Use the two histories for different questions:

• TValue Event logs: Did the app send the expected trigger and wishlist payload?
• Shopify Flow Recent runs: Which workflow received it, which branch ran, and what happened to each action?

If TValue reports a failed delivery, inspect the integration and trigger payload first. If TValue reports the trigger as sent but the expected task did not happen, inspect whether the workflow is active and whether its conditions or actions blocked the result.

Launch checklist​

Before activating a workflow, confirm that:

• Shopify Flow is installed and the TValue integration is enabled.
• The required wishlist trigger is enabled in TValue.
• The workflow uses the intended TValue trigger.
• Customer and product references resolve to the expected Shopify records.
• Custom wishlist, price, and inventory fields are used correctly.
• Reminder and Flow Wait steps do not create an unintended combined delay.
• Test events are separated from production actions.
• The chosen actions are available on the store's plan and through installed apps.
• TValue Event logs and Shopify Flow Recent runs can both be checked after launch.

For the full trigger reference, see the TValue Shopify Flow documentation. For email-first automation platforms, continue with How to Send Shopify Wishlist Events to Klaviyo or How to Send Shopify Wishlist Events to Omnisend.

Install True Value Wishlist Email on Shopify

With TValue: Wishlist, these are separate automations. Each flow has its own trigger and email template, so the message can match the event instead of sending the same generic reminder for every situation.

Wishlist reminder vs product alert​

A wishlist reminder and a product alert both bring shoppers back, but they answer different questions.

• Wishlist reminder: "Do you still want to revisit what you saved?"
• Price-drop alert: "Would the new price change your decision?"
• Back-in-stock alert: "Do you want to return now that the product is available?"
• Low-stock alert: "Do you want to act before the remaining inventory is gone?"

The reminder is time-based. Product alerts are event-based. Keeping these flows separate makes the subject line, product information, and call to action more credible.

Compare the three product alerts​

Shopify tracks inventory at the product variant level when inventory tracking is enabled. Review inventory configuration before relying on inventory-based customer messages, especially when products have sizes, colors, multiple locations, or settings that allow sales beyond available stock. Shopify Help Center: Setting up product inventory

How price-drop alerts work​

The price-drop automation evaluates detected price changes for products shoppers have saved. The email is eligible only when the percentage drop meets or exceeds the threshold configured in the automation.

For example:

A lower threshold responds to smaller changes and can produce more alert activity. A higher threshold limits the flow to more substantial reductions. The right setting depends on normal pricing behavior and how often the catalog changes.

Use the email template to show the old and new price clearly. The shopper should understand the change without decoding a generic sale message.

How back-in-stock alerts work​

The back-in-stock automation watches for a saved product becoming available again. It does not use a configurable percentage or quantity threshold.

This alert is most relevant when the shopper already expressed interest but could not purchase because the desired product or variant was unavailable. The email should make three things clear:

1. Which saved product is available again.
2. That availability has changed.
3. Where the shopper can return to review or buy it.

Avoid adding unsupported urgency such as "selling out now" unless the current inventory actually supports that statement. Back in stock means availability returned; it does not automatically mean stock is already low.

Where low-stock alerts fit​

Low-stock alerts are a separate inventory flow. Instead of waiting for an unavailable product to return, they warn eligible shoppers when stock reaches or falls below the quantity you choose.

If the threshold is 10 units, the event can trigger at 10 units or lower. A smaller threshold moves the message closer to selling out; a larger threshold gives shoppers an earlier warning.

Use low-stock messaging carefully. It should reflect a real inventory threshold rather than manufacture urgency. Inventory tracking must also match how the store actually fulfills products. Shopify provides inventory management at the product and variant level, including available quantities and location-aware inventory states. Shopify Help Center: Managing inventory

Requirements for wishlist product alerts​

Before an alert can become a useful email, the flow needs:

• A product or eligible variant already saved to a wishlist.
• A detected price or inventory event that matches the automation trigger.
• An enabled automation.
• A shopper with an eligible email address and notification preference.
• An active email template and sender configuration.
• A valid product destination for the return click.

This is why product alerts should be configured after the basic wishlist journey works. Start with How to Add a Wishlist to Shopify Without Editing Theme Code if the storefront has not been verified yet.

Set up a price-drop alert in TValue​

1. Open the automation​

Go to Emails > Automations > Price drop alert.

The flow has a Trigger node and a Send email node.

2. Set the percentage threshold​

Open Trigger and set Send event when price drops by.

Choose a threshold from 1% to 100%. Use a value that represents a meaningful price movement for the catalog rather than copying a number from another store.

3. Configure the email​

Open Send email and set the subject, preview text, sender details, and template. Make the saved product and changed price prominent.

4. Enable the flow​

Save the settings and click Enable. Review actual sends under Email history.

For the complete setting reference, see Price drop alert.

Set up a back-in-stock alert in TValue​

1. Open the automation​

Go to Emails > Automations > Back in stock alert.

The trigger is fixed: a wishlisted product is back in stock. There is no threshold to choose.

2. Build an availability-focused email​

Configure the subject, preview text, sender, and template in Send email. Include a direct route to the product so the shopper can verify the current variant and availability.

3. Enable and monitor​

Click Enable, then use Email history to inspect sent, opened, clicked, skipped, or failed activity.

See Back in stock alert for the product documentation.

Coordinate alerts without repeating the same message​

One shopper can be eligible for different events over time. Keep each email specific:

• A reminder should focus on saved interest.
• A price-drop email should focus on the new price.
• A back-in-stock email should focus on restored availability.
• A low-stock email should focus on the configured inventory condition.

Use distinct subjects and templates so the recipient can tell why the email arrived. Product alerts lose value when every automation looks like the same promotion with a different label.

You can also send these events through supported integrations. Follow the complete workflow guides for Klaviyo, Omnisend, or Shopify Flow when you want another platform to handle the downstream automation.

Product-alert launch checklist​

Before enabling all alert flows, verify:

• Shopify price and inventory data reflect the storefront accurately.
• The price-drop threshold matches normal promotion behavior.
• Back-in-stock and low-stock templates use different messages.
• Saved variants link shoppers back to the correct product context.
• Email sender and unsubscribe behavior have been reviewed.
• Test events and real sends can be distinguished in reporting.
• Email history is checked after the first live product changes.

Product alerts work best when the event itself is useful. Send fewer, more specific messages tied to changes the shopper is likely to care about.

Install True Value Wishlist Email on Shopify

This is different from sending one message for every click. The delay creates one useful summary of recent wishlist interest instead of a stream of repetitive emails.

What is a wishlist reminder email?​

A wishlist reminder is an automated message based on an explicit save action. The shopper chose a product strongly enough to keep it, but the product did not necessarily belong in the cart yet.

That makes wishlist reminders different from broader promotional campaigns:

A store can use more than one flow because each one responds to a different reason for returning.

What needs to be in place before sending​

An effective reminder flow needs more than an enabled toggle.

Before setup, confirm that:

• Wishlist buttons and the wishlist page or popup work on the storefront.
• The shopper can be resolved to an eligible email address.
• The email template clearly shows saved products and links back to the store.
• Sender and reply-to details are appropriate for the brand.
• Unsubscribe and notification preferences are respected.

If visitors can save without signing in, use the guest wishlist guide to decide when to ask them to sign in or leave an email.

How TValue groups wishlist items​

TValue uses the delay as a consolidation window.

The first qualifying wishlist addition creates the scheduled reminder. If the same shopper saves more products before that reminder is sent, TValue adds those products to the existing batch. The later additions do not create separate reminders and do not restart the original timer.

At send time, TValue checks the captured wishlist items again. A product that the shopper removed is not included. Products that are no longer available to the automation can also be omitted.

Here is a simplified example with a 2-hour delay:

This behavior gives the shopper time to build a list while keeping the number of sends controlled.

Choose a reminder delay​

There is no universal delay that fits every catalog. Choose it based on how customers shop.

• Shorter delay: useful when product consideration is quick and shoppers commonly finish in one session.
• Longer delay: useful when visitors compare several products, sizes, styles, or higher-consideration purchases.
• Specific send time: useful when you want reminders to arrive at a consistent hour rather than immediately when the raw delay ends.
• Selected weekdays: useful when the store intentionally limits automation sends to particular days.

TValue lets you configure the delay in minutes, hours, or days. You can also delay until a specific time of day and choose the recipient's local timezone, the shop timezone, or another timezone. Selected weekday rules can further constrain when the reminder is delivered.

For stores with customers in multiple regions, choose Recipient's local timezone. A reminder scheduled for 7:00 PM then follows 7:00 PM for each recipient instead of arriving at the same global moment, which could be late at night or early in the morning elsewhere. If a valid recipient timezone is unavailable, TValue falls back to the shop timezone and then UTC.

Treat the first delay as a testable starting point. Review email engagement and adjust it when the data shows that shoppers respond better sooner or later.

Set up wishlist reminder emails in TValue​

1. Open the automation​

In the app, go to Emails > Automations > Wishlist reminder.

The flow has three nodes:

1. Trigger: someone adds a product to their wishlist.
2. Time delay: TValue waits and consolidates saved items.
3. Send email: the grouped reminder is delivered.

The trigger is fixed, so configuration begins with timing.

2. Configure the delay​

Open Time delay and set Wait before sending and consolidate wishlist items for.

Then decide whether to enable:

• Delay until a specific time of day
• A timezone rule for that time
• Delay until specific days of the week

Save the delay settings before moving to the email node.

3. Configure the email envelope​

Open Send email and review:

• Subject line
• Preview text
• Sender name
• Reply-to address
• Optional Cc and Bcc addresses
• Email template

The subject should describe the reason for the message without pretending that the product changed when it did not. A reminder can be direct: the saved products are still waiting, the list is ready to revisit, or the shopper can continue where they left off.

4. Build the reminder template​

Use the email editor to keep the saved products central to the message. Product image, title, price, and a clear return action should be easy to scan.

You can add a Discount block when an incentive is part of the campaign. The reminder restores product context; the discount can give an undecided shopper an additional reason to act. Do not add a discount by default if it conflicts with margin or promotion strategy.

See Email templates for template library, saved template, and editor behavior.

5. Enable and monitor the automation​

After the delay, sender, subject, and template are ready, click Enable.

Use Email history to review each email and its event timeline. Sent, opened, and clicked events help distinguish delivery volume from actual engagement. Email detail also shows the automation, recipient, content, and events associated with a send.

What to measure​

Start with a small set of questions:

• Are reminder emails being delivered to the expected contacts?
• Do shoppers open the message?
• Do they click a product or wishlist link?
• Which delay produces useful engagement without sending too early?
• Does adding a discount improve action enough to justify the incentive?

Avoid judging the flow only by the number of emails sent. The objective is to recover useful shopping intent, not maximize automation volume.

Common reminder mistakes​

Sending too many separate messages​

One email per saved product can quickly become repetitive. Use the consolidation delay so a browsing session becomes one grouped reminder.

Hiding the saved products below generic content​

The shopper should recognize why they received the email. Put the relevant wishlist products before unrelated promotions.

Treating every guest as reachable​

A guest save does not automatically provide an email address. The shopper must have an eligible contact identity before an email can be delivered.

Enabling the flow before testing the storefront​

The email cannot repair a wishlist button, product link, or wishlist page that does not work. Complete the wishlist setup verification checklist first.

What to automate next​

Wishlist reminders are based on elapsed time. Product alerts respond to a new reason to return, such as a lower price or restored inventory.

Continue with How Wishlist Price-Drop and Back-in-Stock Alerts Work on Shopify to add event-driven follow-up without turning every saved product into the same message.

If your store manages downstream workflows elsewhere, continue with the integration guide for Klaviyo, Omnisend, or Shopify Flow.

Install True Value Wishlist Email on Shopify

With TValue: Wishlist, the selected Type controls what happens when a shopper opens the wishlist. The same header button, floating button, or other wishlist entry point can open either the popup or the page. You can switch between both formats without rebuilding those entry points.

Wishlist page vs popup at a glance​

The choice changes the result of opening the wishlist, not which storefront controls can open it. Header buttons, floating buttons, and other supported entry points follow the selected type.

When a wishlist popup works best​

Choose popup mode when the wishlist is primarily a quick utility inside the current shopping session.

It is a good fit when:

• Shoppers usually save only a few products at a time.
• Comparing the wishlist with the current product or collection page is useful.
• You want a header button, floating button, or another entry point to reveal the wishlist without navigating away.
• The list and its actions fit comfortably inside an overlay on desktop and mobile.

Popup mode can reduce unnecessary page transitions, but it still needs clear controls. The shopper should be able to close it, search or scan saved products, remove items, choose variants when needed, and move eligible products to cart.

TValue also provides Hide sidebar for popup mode. Use it when the sidebar does not add enough value for the available width and a simpler overlay is easier to scan.

When a dedicated wishlist page works best​

Choose page mode when the wishlist benefits from a full-page browsing context.

It is a good fit when:

• Shoppers may build longer wishlists.
• The theme layout gives a full page more usable room than an overlay.
• Wishlist management is important enough to deserve its own browsing context.
• You want the option to link directly to the wishlist from email, navigation, or other store content.

A shopper does not need a navigation-menu link to use page mode. When Type is set to Page, existing wishlist entry points such as the header button and floating button navigate to the wishlist page automatically.

The dedicated URL is an additional option. You can place it in Shopify navigation, an email, or other store content when that return path is useful, but this is entirely up to the merchant. Shopify Help Center: Online store pages

Default page or existing Shopify page?​

When Type is set to Page, TValue provides two page options.

Default page​

The default option uses TValue's built-in wishlist page and provides a wishlist URL for the store.

Choose Default page to use the built-in wishlist page provided by TValue. You do not need to create or select a Shopify page.

Select existing page​

This option renders the wishlist through a Shopify page selected from the store.

Choose it when you want the wishlist to use a Shopify page and page handle that you manage. From the TValue setting, you can select an existing page or enter a title and create a new page for the wishlist.

After selecting or creating a page, verify the public URL and confirm that the wishlist content appears in the theme you plan to publish.

How the selected type controls entry points​

Storefront entry points are not limited to one wishlist type. They follow the Type selected in Display > Widgets > Wishlist page:

• With Popup, clicking an entry point opens the wishlist overlay.
• With Page, clicking the same entry point navigates to the wishlist page.

This applies to supported entry points such as the wishlist header button, floating button, and View wishlist actions. The merchant can therefore choose popup or page mode independently of where those controls appear.

A direct navigation-menu link is different because it points to a URL. It is available for page mode, but adding it to the store navigation is optional and does not replace the header button, floating button, or other entry points.

Set up popup mode in TValue​

1. Open Display > Widgets > Wishlist page.
2. Set Type to Popup.
3. Decide whether to enable Hide sidebar.
4. Set the primary color, text color, and primary button text color.
5. Decide whether Remove item after adding to cart matches the store's workflow.
6. Save and test the popup from every active wishlist entry point.

On mobile, test more than whether the overlay opens. Confirm that long product names, variant actions, the close control, footer actions, and the on-screen keyboard do not block important content.

Set up page mode in TValue​

1. Open Display > Widgets > Wishlist page.
2. Set Type to Page.
3. Choose Default page or Select existing page.
4. If using a Shopify page, select one or create it from the setting.
5. Apply the wishlist colors and cart-removal preference.
6. Test the header button, floating button, and every other active entry point to confirm that each one navigates to the page.
7. Open the public URL directly and test it as both a guest and a signed-in shopper.
8. Optionally add the URL to store navigation, email, or other content when you want another direct route to the wishlist.

See Wishlist page and popup for the exact setting reference.

Keep or remove an item after adding to cart?​

Both formats include the Remove item after adding to cart setting.

Enable it when adding to cart means the shopper has finished using the wishlist for that product. Leave it disabled when the list should continue acting as a reference, even after the product is placed in the cart.

This choice is independent of popup or page mode. Test it based on how customers use saved products, not on the size of the interface.

How guest access affects the choice​

Guest shoppers can use either format when login is not required.

Popup mode can keep the entire guest interaction in one browsing context. Page mode gives the guest a clearer destination to revisit. In both cases, decide separately whether TValue should show the Save wishlist contact popup after wishlist activity.

Read How to Add a Guest Wishlist to Shopify Without Login before enabling a login barrier simply to support page mode.

Questions to answer before choosing​

Use these questions during review:

1. How many products do shoppers commonly save?
2. Do shoppers need to compare the list with the page underneath it?
3. Do you need the option to link directly to the wishlist from email, navigation, or other content?
4. Does the popup remain comfortable on the smallest supported mobile viewport?
5. Does the page inherit the intended theme layout and spacing?
6. Can guests and signed-in customers both return to their saved products as expected?
7. Should adding to cart remove the item from the list?

If most answers concern quick in-session access, start with popup mode. If they concern return visits, direct links, or longer list management, start with page mode.

Test before launch​

Whichever format you choose, verify:

• Header, floating, toast, and other wishlist entry points follow the selected type.
• Any optional direct link to the wishlist page opens the correct URL.
• Saved products, prices, variants, and stock states render correctly.
• Search and list controls remain usable with several items.
• Remove and add-to-cart actions behave as configured.
• Guest and signed-in access match the store's policy.
• Desktop and mobile layouts have no blocked controls or overlapping text.
• Reminder email links return to a useful storefront destination.

You can change the format later, but the shopper should always have one consistent and visible route back to saved products.

Install True Value Wishlist Email on Shopify

For most direct-to-consumer stores, the least disruptive starting point is to let the shopper save first. You can then offer a clear choice to sign in or leave an email address when you want to connect that wishlist with a reachable contact.

What is a guest wishlist?​

A guest wishlist is a saved-products experience that does not require the shopper to authenticate before using the wishlist button.

This matters because a visitor can show interest much earlier than they are ready to create an account or buy. The wishlist gives that visitor a low-commitment action: save the product now and decide what to do next later.

A customer account still has an important role. Shopify customer accounts give shoppers a persistent sign-in experience and access to account features such as profile and order information. But account access and wishlist access do not have to begin at the same moment. Shopify Help Center: Customer accounts

Choose the right wishlist access model​

There are three practical ways to handle visitors who are not signed in.

These models are not merely visual choices. They determine where you place friction in the customer journey.

If browsing is open to everyone, requiring an account for the first wishlist action can feel disproportionate. If prices, products, or buying privileges are account-restricted, requiring login may be consistent with the rest of the store. Shopify B2B, for example, relies on signed-in customers to access company-specific products and pricing. Shopify Help Center: B2B customer accounts

Guest saving and email capture are different decisions​

It is useful to separate two questions:

1. Can this visitor save a product?
2. Can the store contact this visitor later?

A guest can use the wishlist without being a reachable email contact. That keeps the first interaction simple, but an automated reminder cannot be delivered until TValue has an eligible email address for that shopper.

TValue provides contact actions inside the main wishlist experience as well as an optional prompt after wishlist activity. A guest can:

• Use Sign in to save your wishlist in the header of the wishlist popup or page. This is the only contact action shown when the guest wishlist is empty.
• After saving at least one item, use the contact area in the wishlist sidebar to Sign in or Leave email. Choosing Leave email reveals the email field and Save action.
• Respond to the optional Save wishlist contact popup shown after wishlist activity.

These contact points preserve the quick guest save action while giving the shopper more than one opportunity to connect the wishlist with an eligible email address. The sidebar form is available only when the guest has at least one wishlist item and the wishlist sidebar is visible; popup mode can hide that sidebar through the Hide sidebar setting.

Set up a guest wishlist with TValue​

Before changing guest behavior, complete the standard installation in How to Add a Wishlist to Shopify Without Editing Theme Code.

1. Allow wishlist actions without login​

Open Display > Widgets > Require login for wishlist.

Keep Require login for wishlist disabled. A visitor who is not signed in can then use wishlist actions without first seeing the login requirement.

If the setting is enabled, TValue shows a sign-in prompt when the guest tries to add a product.

See Require login for wishlist for the setting and prompt customization options.

2. Decide whether to show the additional contact popup​

Open Display > Widgets > Save wishlist contact popup.

Enable Show login or leave email popup when you want to proactively invite guest shoppers to identify themselves after wishlist activity. TValue can show this prompt after the first saved item and again after later wishlist activity when the guest is still signed out and has not left an email.

Keep it disabled when you do not want the additional prompt interrupting the storefront journey. Disabling it does not remove every contact option: guest shoppers can still use Sign in to save your wishlist in the wishlist header. After the guest saves at least one item, the Sign in / Leave email controls also appear in the wishlist sidebar when that sidebar is visible.

The three contact surfaces serve different moments:

You can customize the popup title, description, field placeholder, buttons, and success message under Translation.

3. Give shoppers a way back to the wishlist​

Saving is only useful if the shopper can find the products again.

Provide at least one visible wishlist entry point:

• A wishlist button in the store header
• A floating wishlist button
• A View wishlist action in the confirmation toast
• A navigation link to a dedicated wishlist page

You can use a popup for a quick overlay or a page for a dedicated URL. The detailed tradeoffs are covered in Shopify Wishlist Page vs Popup: Which Should You Use?.

4. Test the complete guest journey​

Use a private or incognito browser window so an existing Shopify login does not affect the test.

Verify that a guest can:

1. Open an empty wishlist and see Sign in to save your wishlist without the sidebar email form.
2. Add a product from a product page.
3. Add a product from the main collection page.
4. See the correct additional contact popup behavior.
5. Close the prompt without losing the save action.
6. Reopen the non-empty wishlist and find Sign in to save your wishlist.
7. Use Leave email in the wishlist sidebar when the sidebar is visible.
8. Remove an item and add an eligible item to cart.

Then repeat the test as a signed-in customer. The storefront should make sense in both states.

When should you require login?​

Requiring login is reasonable when account identity is part of the store experience, not simply because a wishlist exists.

Consider it when:

• The storefront is designed for B2B or approved customers.
• Product access or pricing depends on account identity.
• The wishlist is part of a private member experience.
• Your operational process requires every saved list to belong to an authenticated customer.

For a public consumer storefront, start by testing guest access. You can still invite the shopper to identify themselves after they have received value from the save action.

Connect guest intent with reminder emails​

Once a shopper has provided an eligible email address, the wishlist can become more than a passive list.

TValue can use saved-product intent for:

• Wishlist reminder emails
• Price-drop alerts
• Back-in-stock alerts
• Low-stock alerts

These emails should follow the shopper's notification eligibility and unsubscribe preferences. Guest access itself does not mean every guest can automatically receive email.

Continue with How to Send Automated Wishlist Reminder Emails on Shopify when your guest and signed-in wishlist journeys are working correctly.

Guest wishlist checklist​

Before launch, confirm:

• Guests can save without an unexpected sign-in barrier.
• The additional contact popup appears only when you intend it to.
• The wishlist header provides the guest sign-in action even when the wishlist is empty.
• The sidebar sign-in and email form appear after a guest saves at least one item and work when the sidebar is visible.
• Closing the popup does not make the wishlist journey confusing.
• Shoppers have a visible way to reopen the wishlist.
• Guest and signed-in behavior have both been tested.
• Email automation is sent only to eligible, reachable contacts.
• Wishlist text is translated for the storefront locales you support.

The best guest wishlist is not the one that collects the most information at the first click. It is the one that lets shoppers save with confidence and gives them a clear next step when they are ready.

Install True Value Wishlist Email on Shopify

With True Value: Wishlist Email, the standard setup is to install the app, follow its onboarding link to the theme editor, save the enabled TValue: Wishlist Core app embed, and test the wishlist on your storefront.

The important part is not only placing a heart icon. A complete wishlist also needs somewhere to view saved products, support for the shoppers you want to serve, and a reliable way to keep working with your theme.

What a Shopify wishlist needs​

A wishlist normally combines several storefront behaviors:

• A wishlist button on product pages
• Wishlist buttons on collection product cards
• A wishlist page or popup where shoppers can review saved products
• An entry point such as a header icon or floating button
• Support for guests, logged-in customers, or both
• Actions to remove products or move them to cart

Depending on your goals, you may also want to capture a guest shopper's email and follow up when saved products change in price or inventory.

Before installing anything, decide whether you only need a temporary browser-based favorites list or a wishlist system that can connect saved products with customers, reports, and email automation.

Choose how to add a wishlist​

There are three practical ways to add a wishlist to a Shopify store. The right choice depends on what your current theme already provides and how much you need the wishlist to do beyond saving products.

Start by checking whether your theme already includes a wishlist and what it supports. A built-in theme feature may be enough when shoppers only need a simple way to save and revisit products.

If you also need guest and customer wishlists, cross-device access, reporting, email capture, or automated price and inventory alerts, compare those requirements with the theme's capabilities before choosing an app.

Custom development is the least common path. It is usually reserved for stores with a development team and behavior that cannot be delivered reliably through an existing theme feature or wishlist app.

For merchants who need more than the theme provides but do not want to maintain custom code, a wishlist app is the practical next step.

Add TValue: Wishlist to Shopify​

1. Install the app​

Open the True Value: Wishlist Email listing, click Install, and approve the installation in Shopify.

The app opens automatically after installation and starts a short onboarding flow. Select the language used inside the app, then continue to the app embed step.

For the installation flow in product documentation, see Install True Value Wishlist Email.

2. Enable the core app embed​

In onboarding, choose the theme where you want the wishlist to run and click Enable.

TValue opens a new theme editor tab with TValue: Wishlist Core already enabled. You do not need to find the toggle or paste code into the theme. Click Save in the theme editor, then return to the app.

When TValue detects the saved embed, the status changes to TValue: Wishlist Core is ready. Click Finish to complete onboarding.

Shopify supports activating and deactivating app embeds through the theme editor. This avoids manually changing Liquid templates and makes the integration easier to manage when the app changes. Shopify Help Center: Extend your theme with apps

3. Let TValue check your theme​

After installation, TValue checks whether the selected theme already has a complete placement preset.

When the theme is fully supported, the main wishlist placements can work automatically, including product page, collection, and header buttons.

If the theme needs additional support:

• The wishlist header button may not appear automatically.
• Collection page wishlist buttons may not appear automatically.
• The product page button may appear in a position or style that does not fully match the theme.

Other wishlist features can still load, but the main entry points should be placed correctly before launch.

TValue detects unsupported themes without waiting for you to submit a request. Our team can prepare the missing theme preset, usually in about 5–10 minutes after detection.

Read Check theme compatibility for the exact behavior of fully supported themes and themes waiting for a preset.

4. Test the storefront​

Open the same theme where you saved the app embed and test the customer journey.

At minimum, confirm that you can:

1. Add a product from a product page.
2. Add a product from a main collection page.
3. Open the wishlist from the entry point you plan to use.
4. Remove a saved product.
5. Move a wishlist item to cart.
6. Save a product as a guest.
7. Save a product as a logged-in customer if your store uses customer accounts.

Use the complete wishlist setup verification checklist before launching the feature to all shoppers.

Choose how shoppers open the wishlist​

Adding products is only half of the experience. Shoppers also need an obvious way to return to what they saved.

TValue can present the wishlist as:

• Popup mode for a quick overlay without leaving the current page
• Page mode for a dedicated wishlist URL and a larger browsing surface

You can expose that experience through a header button, floating button, toast action, or another supported entry point.

There is no universal best option. Popup mode keeps the shopper in context, while page mode gives a longer wishlist more space. The right choice depends on your theme, catalog, and expected wishlist size.

Use Shopify Wishlist Page vs Popup: Which Should You Use? to compare the two experiences, then see Wishlist page and popup for the available settings.

Decide how guest wishlists should work​

Requiring an account before a shopper can save a product adds friction. A guest wishlist allows first-time visitors to save products immediately.

With TValue, you can keep the save action open to guests and use the Save wishlist contact popup when you want to collect an email address. That gives the shopper a way to preserve their wishlist while giving your store an identity that can be used for eligible follow-up.

Read How to Add a Guest Wishlist to Shopify Without Login for the complete access strategy, then configure the behavior in Save wishlist contact popup.

When manual placement is actually needed​

The standard setup does not require custom placement or theme code editing.

Manual placement is intended for special areas such as custom sections, unusual product grids, search results, featured products, or heavily modified theme layouts that a preset does not yet cover.

Contact TValue support first when an important placement is missing. Adding support to the theme preset is usually cleaner than maintaining selectors yourself. Developers who need direct control can follow the Custom placement guide.

What to configure after the wishlist works​

Once the core journey is stable, continue in this order:

1. Adjust automatic product and collection button placement.
2. Choose button styles and icons that match the theme.
3. Decide between wishlist popup and page mode.
4. Configure guest contact capture if needed.
5. Translate shopper-facing wishlist text.
6. Enable the email automations that fit your store.

The storefront should work correctly before you start changing every visual detail. Test one complete save-and-return journey first, then customize from a stable baseline.

When the storefront journey is ready, continue with How to Send Automated Wishlist Reminder Emails on Shopify and How Shopify Wishlist Price Drop and Back-in-Stock Alerts Work.

Launch checklist​

Before considering the wishlist ready, verify:

• TValue: Wishlist Core is enabled and saved on the correct theme.
• The product page wishlist button is visible and usable.
• Main collection product cards show the expected wishlist button.
• Shoppers can find and open the wishlist again.
• Guest and logged-in behavior match your store's account strategy.
• Saved variants display correctly.
• Remove and add-to-cart actions work.
• The experience has been checked on desktop and mobile.
• Any missing theme placements have been reported or detected for support.

After these checks, your Shopify store has a working wishlist without a manual theme code installation.

Install True Value: Wishlist Email on Shopify