Build vs Buy:
Why In-House Shoppable Video Rarely Works

There might be instances when brands think of building shoppable videos in-house. These are brands who don't fully understand the complexities they would get into — they think of it like another small plugin they can knock out in a sprint or two.

The reality is different. Shoppable video is a technically demanding product that touches performance, infrastructure, content management, and conversion analytics all at once. The brands that try to build it themselves almost always end up with a solution that is slower, harder to manage, and delivers a fraction of the ROI compared to a purpose-built platform.

Here are the five problems they consistently run into — in the order they tend to discover them.

Page speed issues

Page speed is the first wall brands hit — and it's a genuinely difficult engineering problem. Video is heavy. If it's not handled correctly, it will tank your Core Web Vitals and cost you organic traffic before it ever converts a single customer.

Getting this right requires several layers of work that most product teams underestimate:

Each of these is a solved problem — but only if you've solved it before. Most ecommerce engineering teams haven't. They end up shipping something that works in a test environment and then quietly drags down page speed scores in production.

No dashboard to manage videos

The second problem hits the marketing team, not engineering. When you build in-house, video links typically get hard-coded in the frontend. There is no dashboard. There is no CMS layer. There is no way to swap a video without opening a pull request.

Every time you want to add, remove, or reorder videos — whether that's to align with a new campaign, pull down an out-of-season product, or test a different piece of UGC — it requires a developer, a code change, a deployment, and however long your release cycle takes.

A purpose-built platform gives the marketing team a visual editor to manage every video, every placement, and every product tag — without touching code. That operational independence compounds over time.

Limited templates & customizations

When brands build in-house, they almost always start with the simplest possible implementation: a horizontal carousel of 4–5 videos on the homepage. That's it.

There's nothing wrong with starting simple — the problem is they rarely get further than that. The full set of formats and touchpoints that actually drive conversions never gets built:

Each format that doesn't get built is a customer touchpoint that doesn't exist. And the brands that hit top-quartile results are the ones with video present at every stage of the buyer journey — homepage, collection, PDP — not just one placement on one page.

Zero or low ROI

The previous three problems combine to produce this one. When shoppable video is only present in one or two places, only a small fraction of visitors ever encounter it. When they do encounter it, the engagement is low because the format is basic. When engagement is low, the revenue impact is low — or zero.

This creates a vicious cycle. The marketing team sees low numbers from the in-house implementation and concludes that "shoppable video doesn't work for our store." The real conclusion is that a minimal implementation delivered minimal results.

Not having videos at multiple touchpoints — and not covering the full customer buyer journey with videos — means the sessions that actually engage with video stay very, very low. And when engagement is that low, it doesn't add anything to the overall conversion rate. The investment in building the system returns nothing because the system was never deployed at scale. For what proper deployment actually delivers, see our 2026 shoppable video benchmarks.

No personalization

The final gap is personalization — and it's the one that is almost never on the roadmap when brands start building in-house, but becomes obvious once you have a working system.

Showing every visitor the same videos regardless of who they are leaves conversion on the table. The two key attributes for personalizing the video experience:

Understanding user behaviour and personalizing the video experience based on these attributes requires a data layer, a rules engine, and an A/B testing framework that sits on top of the video delivery system. This is rarely something an in-house team builds. It's usually something they put on the roadmap and never get to.

So — build or buy?

If you are a large enterprise with a dedicated platform engineering team, months of runway to invest, and the ability to maintain a custom system long-term, building in-house is a defensible choice. You'll own the infrastructure and you can tailor it precisely.

For the vast majority of D2C and ecommerce brands, the math doesn't work. The engineering cost of getting page speed right, the operational overhead of managing without a dashboard, the missed conversion from limited formats, and the absence of personalization all combine to produce a system that costs more to build than it ever returns.

A purpose-built platform ships all of this on day one — video optimisation, a content management layer, every format type, and personalization rules — at a fraction of the cost of building and maintaining it yourself.

The question isn't whether you can build it. It's whether building it is the best use of your engineering team's time — and whether a half-built version serves your customers better than a fully-featured one they could have from a platform. If you're evaluating what the setup actually involves, our guide on how to add shoppable videos to your ecommerce website is a useful reference.