Give every customer a wishlist that follows them
Let signed-in shoppers save favorite products and return to their list on another visit or device. You control how the wishlist looks and works in your store.
Installs from the Shopify App Store · Then US$29.99/month per store, billed through Shopify
A custom experience, built by you or your developer.
Illustration: a wishlist with three saved favorites: a backpack, sneakers, and sunglasses.
Illustrative storefront · Your design, your brand
A saved product is useful customer data
The fashion store wanted the wishlist to do more than hold products on a page. Each save showed interest in a specific item, so the data needed to survive the next session and device.
They stored the wishlist on the Shopify customer, with the option to send it to Klaviyo.
The storefront could load the list when the shopper returned. With the integration on, the marketing team could use the same signal for follow-up about saved products.
Purchase intent, saved on the customer record and available to Klaviyo when you enable it.
Wishlist saves processed
A FieldsRaven processing count, not a count of unique customers or saved lists.
Favorites and reorder lists
The merchant controls the product experience and can reuse the customer-owned JSON shape.
30,000+ wishlist saves processed. The wishlist lives on the customer record, supporting the storefront experience and, when configured, later customer follow-up without claiming that every downstream sync has already completed.
Historical implementation results from the existing FieldsRaven use-case story.
Make it feel like
part of your store.
Start with the recipe and code generated for your field. Adapt the interface, connect it, then test the full experience.
Configure your field
Choose the customer resource and the data your experience needs to save.
Connect your storefront
Use your field’s Get Code output and the recipe to connect your custom interface.
Test the complete journey
Confirm the saved value in Shopify and test returning to it as a signed-in customer.
Connect Codex, Claude Code, or Cursor through FieldsRaven MCP to configure fields, retrieve starter code, and check saved submissions.
Connect your coding tool ↗View starter code
Scroll sideways to see more code
const cfg = window.FR_CUSTOM__CUSTOMER_WISHLIST;
const payload = [
{ product_handle: "linen-shirt" },
{ product_handle: "oak-side-table" }
];
await fetch("/apps/raven/create_metafield", {
method: "PUT",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
raven: {
raven_id: cfg.ravenId,
resource_id: cfg.resourceId,
raven_mac: cfg.ravenMac,
value: JSON.stringify(payload)
}
})
});Run this request from your add or remove handler, with the complete updated list. Do not run it on page load.
A JSON save replaces the full metafield value. Read the current list, prevent duplicates, apply the change, then send the complete next array.
Get Code supplies the configuration and inline HMAC. Change local wishlist state only after FieldsRaven accepts the request.
Custom storefront design, integration, and testing are still required.
Does FieldsRaven render the wishlist page?
No. Your theme controls the buttons and wishlist page; FieldsRaven accepts the verified write to the customer value.
Can I store product references instead of JSON?
Yes. FieldsRaven supports product and product-list reference fields as well as JSON. This starter uses JSON because the list is easy to inspect and adapt.
Can a guest use the wishlist?
This customer pattern needs the shopper to sign in before the generated configuration can identify the customer resource.
How does Klaviyo receive the list?
When you turn on Klaviyo sync for this field, each successful Shopify save updates the shopper’s existing Klaviyo profile, matched by email. A list like this example arrives as numbered properties, such as product_handle_1 and product_handle_2, not as one list property. An empty list is not sent.