How a Custom Klaviyo Data Feed Shopify Setup Made $84k
Most eCom brands run standard product recommendation blocks in their emails. I did this too when I first started out. We all trust the default settings to do the heavy lifting.
Then we tested a custom dynamic Shopify data sync Klaviyo catalogue feed for a client with over 4,500 SKUs. The default blocks were failing them. We stripped out the standard setup and built a custom data feed from scratch.
That single change generated $84,000 in additional revenue in 90 days.
High-SKU stores experience massive friction when using default product recommendations. The standard algorithms push irrelevant items. They recommend products that are out of stock. They promote low-margin accessories when you need to move high-margin hero products.
The numbers show why that default setup is expensive. You pay for the traffic. You capture the email. You send the campaign. Then you lose the sale because the email suggests a product the customer has zero interest in buying.
Here is exactly how we fixed it.
Native recommendation limits in high-SKU stores
Native recommendation blocks rely on broad algorithms. These static rules ignore granular buyer history. They are designed for stores with twenty products, not two thousand.
Klaviyo offers standard options like most viewed products or top selling items. This works fine for a simple apparel brand. It breaks down completely for a complex catalogue.
Imagine you sell automotive parts. A customer buys a specific air filter for a 2018 Toyota Hilux. A week later, your post-purchase flow triggers. The default recommendation block looks at your store data. It sees that Ford Ranger floor mats are your top selling item this week.
Your email recommends Ford Ranger parts to a Toyota owner. The customer ignores the email. Your click-through rate drops.
High-SKU catalogues often show irrelevant items through these default blocks. They also push low-margin items. If a $5 sticker is your most viewed product, the algorithm will put that sticker in every email. You waste valuable email real estate on products that do not move the needle on your revenue.
Standard product blocks cannot read custom Shopify metafields. This is their biggest flaw. They only see the basic product title, price, and image. They cannot see your custom data fields for reorder cycles, formulation variations, or profit margins.
Solving these technical catalogue constraints consistently drives measurable growth in our results at Elite Brands. We see it across dozens of accounts. You need a system that reads your custom data and serves exact matches to your customers.
Custom JSON feed creation for a Klaviyo data feed Shopify setup
To fix this problem, we build custom web feeds. This involves exposing Liquid templates as raw JSON endpoints within the Shopify theme layer.
Instead of relying on an API bridge, you create a specific URL on your Shopify store. This URL outputs pure data. Klaviyo reads this data URL every few hours.
We start by injecting custom metafields into the feed payload. We map out profit tiers. We map out replenishment timing. We include specific variant sizes. If a product has a 65 percent profit margin, we tag it in the JSON feed. This allows us to tell Klaviyo to only recommend high-margin items in specific emails.
Optimising these JSON output structures is critical. You must ensure fast server execution and minimal latency. If your JSON feed takes twenty seconds to load, the sync will time out. We limit the feed to specific collections to keep the file size small and the load time under two seconds.
Liquid template architecture for JSON rendering
Structuring theme files to render valid JSON format takes precision. You cannot have any HTML wrapper pollution.
We create a new template in Shopify called collection.json.liquid. The very first line of code must be {% layout none %}. This strips away your website header, footer, and styling. It leaves only the raw code.
We then use Liquid tags to filter collection handles. We output targeted product subsets. We loop through the products in a specific collection and format them into a JSON array. Every comma and bracket must be perfect. A single missing comma will break the entire feed.
Metafield extraction for hyper-targeted product logic
Extracting metafields gives you total control. We map customer buying intervals directly into product attributes.
If you sell a 30ml face serum, we create a metafield stating a 45-day supply. If you sell a 50ml version, we state a 75-day supply. We pull this exact number into the JSON feed.
We also pass margin thresholds to ensure high-value items are prioritised. We create a metafield for margin categories like tier one, tier two, and tier three. The JSON feed sends this tier data directly to Klaviyo.
Building these feeds requires technical knowledge. We recommend having an experienced developer or a dedicated Klaviyo expert team handle this setup. One syntax error can stop your emails from sending entirely. If you’re looking to review your store’s setup before going live, our free Klaviyo audit covers the same structural checks we run during custom integrations.
Catalog feed configuration for Shopify data sync in Klaviyo
Once the Shopify endpoint is live, you must connect it to your email platform. Connecting custom web feeds inside Klaviyo catalogue settings takes only a few clicks, but the configuration requires attention to detail.
You navigate to the data feeds section in your account. You add a new web feed. You paste the Shopify JSON URL you just created.
Then comes the important part. You must map the custom JSON parameters to usable Django-style email variables.
Klaviyo uses the Django syntax language to display data. If your JSON feed outputs a product title as item_name, you must write the correct Django tag to display it in the email. It usually looks something like {{ feeds.ShopifyFeed.products.0.item_name }}.
You have to map the image URL, the product link, the price, and your custom metafields.
Setting automated sync frequency is the final configuration step. This guarantees stock and price accuracy. We set our custom feeds to sync every hour. If a product sells out on your website at 2:00 PM, the feed updates by 3:00 PM.
This prevents the nightmare scenario of sending an email blast to 50,000 people featuring an out-of-stock item.
You can read the exact technical requirements for these custom endpoints in the Klaviyo developer documentation for custom web feeds.
We use these feeds across multiple automated sequences. Dynamic product feeds integrate perfectly into The Elite Brands Framework for Your Klaviyo Welcome Flow. You can show new subscribers exactly what they need to see based on the specific form they filled out.
Dynamic replenishment flows using a Klaviyo data feed Shopify strategy
We applied this custom data feed to automated replenishment campaigns for a client in the consumable health space. The results were immediate.
We built predictive reorder triggers based on real consumption cycles. We stopped guessing when customers might run out of product. We used the exact data from our custom JSON feed to trigger the emails.
This strategy yielded $84,000 in new sales over a 90-day period.
We rendered tailored product recommendations into flow templates dynamically. We A/B tested these feed-driven personalised flows against static baseline recommendation blocks. The custom feed outperformed the default blocks by a massive margin.
Replenishment trigger logic and customer consumption timing
Calculating individualised repurchase windows based on order history changes the game entirely.
Before the custom feed, the brand sent a generic replenishment email 30 days after every purchase. It did not matter if the customer bought a two-week supply or a three-month supply. Everyone received the same email on day 30.
With the custom feed, we automated post-purchase timing delays tied to product size variants.
The JSON feed told Klaviyo exactly how many days of supply the customer purchased. If they bought the small tub of protein powder, the flow waited 14 days. If they bought the large tub, the flow waited 45 days.
The email arrived exactly when the customer was scooping the last serving out of the tub.
Dynamic template blocks and cross-sell pairing
We also used the feed to pull complement SKUs into the email body without manual design updates.
If a customer bought a specific brand of coffee beans, the JSON feed identified the exact paper filters that matched their purchase history. The email recommended those specific filters.
This eliminates manually updated catalogue images across evergreen flows. You never have to log into Klaviyo to swap out a product image when packaging changes. The JSON feed updates the image URL automatically.
These dynamic email feeds work across all your retention channels. You can apply similar logic when Integrating SMS with Your Klaviyo Abandoned Cart Flow for Better Recovery. Multi-channel recovery tactics complement dynamic email feeds perfectly.
Revenue measurement and results for Klaviyo data feed Shopify integration
The financial impact of this integration is clear. The $84,000 in incremental revenue generated across our flow triggers broke down into three distinct categories.
Predictive replenishment flows drove $42,000 of the total. Dynamic cross-sell blocks in post-purchase emails contributed $25,000. Upgraded abandoned cart blocks brought in the remaining $17,000.
Analysing click-through rate and conversion rate improvements over the default setup proved the value of the custom feed.
Our click-through rate moved from 1.2 percent to 3.8 percent in the first month. Open rates held steady at 34 percent, but the revenue per recipient tripled. When you show people the exact product they need at the exact moment they need it, they click and they buy.
eCommerce brands must evaluate their current email product catalogue strategy.
Open your Klaviyo account. Look at your automated flows. Click on the product recommendation blocks in your emails. If you are using the default “viewed product” or “popular products” settings, you are leaving money on the table.
Check your high-margin items. Are they getting enough visibility in your automated emails? Look at your consumable products. Are you sending replenishment emails based on exact variant sizes or just guessing with a flat 30-day delay?
Most brands have the data they need sitting in Shopify. They just lack the technical bridge to push that data into Klaviyo effectively.
Building a custom JSON endpoint solves the problem. It requires some initial development work. You have to write the Liquid code, map the Django variables, and test the outputs. Once it is running, it operates completely in the background. It updates your stock levels, your prices, and your product images every hour without manual intervention.
Want a Klaviyo expert to look at your account?
We’re Klaviyo Master Gold partners. Our free Klaviyo Audit flags the 24 things that most often kill email revenue on Shopify stores.
If you want a hand identifying the missing revenue opportunities in your current email infrastructure, you can request a free Klaviyo audit from our team.
