Wishlist saves processed
A FieldsRaven processing count, not a count of unique customers or saved lists.
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
Illustration: four saved favorites: Everyday backpack, Weekend sneakers, Tortoiseshell shades and Linen throw.
Illustrative storefront · Your design, your brand · Built by you or your developer
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.
Historical implementation results from the existing FieldsRaven use-case story.
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.
A FieldsRaven processing count, not a count of unique customers or saved lists.
The merchant controls the product experience and can reuse the customer-owned JSON shape.
For you and your developer. Start with the recipe, adapt it to your theme, then test the full journey before day 14.
Choose the customer resource and the data your experience needs to save.
Use your field’s Get Code output and the recipe to connect your custom interface.
Confirm the saved value in Shopify and test returning to it as a signed-in customer.
Using an AI coding tool? Connect it to FieldsRaven MCP for field setup and starter code. Connect your coding tool
Standard resource-ID submissions use the field’s generated Get Code configuration, including a signature tied to the field and resource. FieldsRaven accepting the request confirms receipt; the Shopify save runs afterward in the background.
Submit the save from your add or remove handler, with the complete updated list. Do not submit 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.
No. Your theme controls the buttons and wishlist page; FieldsRaven accepts the verified write to the customer value.
Yes. FieldsRaven supports product and product-list reference fields as well as JSON. The linked wishlist recipe uses JSON because the list is easy to inspect and adapt.
This customer pattern needs the shopper to sign in before the generated configuration can identify the customer resource.
When you turn on Klaviyo sync for this field, a successful Shopify save queues an update to the shopper’s existing Klaviyo profile, matched by email. A JSON list of product handles becomes numbered properties, such as product_handle_1 and product_handle_2. An empty list is not sent.
Build a wishlist that fits your store. Use the recipe as a starting point, then test saving and reopening favorites.
START 14-DAY FREE TRIAL (opens in a new tab)Installs from the Shopify App Store · US$29.99/month per store after the 14-day trial · Billed through Shopify · Developer setup required