Why I built Vetta: controlling what goes live on Shopify

Where it started

I learned to code as a teenager, for fun, following C++ lessons on an online tutorial site. It was not a career plan. I liked making things work.

Around 2015, when I was somewhere between 18 and 20 and studying management and accounting, I built my first Shopify stores. I was following the trends of the time, like a lot of people my age, and trying things. Whatever else I was studying or doing, e-commerce was always where I felt at home.

Learning the trade with clients

After that I studied digital marketing at ESCEN in Bordeaux. Around 2018 and 2019 I started working professionally for clients, first as a web communication manager, then as a webmaster.

Client work showed me that the technical side is only half the job. The other half is the space between you and the client: who decides, who checks, who is allowed to change what, and how you both know where things stand. Over the years I worked on stores built on custom code with Symfony, on WordPress, and on Shopify. Each has its strengths.

Today I recommend Shopify to clients. Security and hosting are managed for them, and the client can spend their time on what actually brings in revenue: products, content, customers.

Rodhouse and the move to Shopify

In 2020 I joined Rodhouse, a company in the middle of an IT restructuring. There were organisational needs and a fair amount of technical debt. My role was project manager, working with a web agency to improve the customer experience and fix the debt and the bugs that came with it.

From 2023 I led the migration of the whole site to Shopify: the catalogue, customers, orders, a full redesign of the visual identity and new features on top. It went through without incident, which on a project like that is the result you hope for and do not take for granted. Today I am Tech Lead for Rodhouse on all its Shopify apps and maintenance projects.

Building apps for problems I kept seeing

Working on real stores every day, I kept meeting the same gaps, and some of them became apps on the Shopify App Store:

• Stocker handles purchase orders, restock forecasts and ABC analysis. It is an alternative for merchants who relied on Stocky, which Shopify delisted from the App Store in February 2026 and discontinued on August 31, 2026.
• Cost Based Pricing manages B2B and B2C pricing, including prices based on purchase cost.
• Infinite Menu Breadcrumb goes beyond the three levels of menu depth that Shopify menus allow (a top level plus two nested levels).

None of these started as a product idea. They started as something a store needed and did not have. Vetta came from the same place.

The two problems behind Vetta

Rewriting content you are not the expert on

The first one came up while I was reworking product pages and other content for a client. I knew Shopify, SEO and how to structure a page. I did not know their trade the way they did. What I wrote needed someone who actually knew the products to confirm it.

You do not want to update content that is already live without the client checking the facts. But doing that by hand means copying text into documents, going back and forth by email, then pasting the approved version back into the admin and hoping nothing changed in between. I wanted something that linked me and the client smoothly, that was simple enough for them to use without training, and that kept a record of what had been done and what was still waiting.

A bad edit, and no clean way back

The second one came from a client with many employees. One of them had made a bad edit to the store’s content. They needed two things: go back to the previous version of that content, and tell the person who made the mistake so it would not happen again.

Neither was easy without a record of past versions: finding what the content looked like before, and who changed it, meant digging.

Vetta handles both. Every version is kept, including edits made directly in the Shopify admin, which are dated and marked as made in Shopify. Changes that go through Vetta carry the name of their author and reviewer, and any earlier version can be restored. You can read more about how that works on the version history page.

Why now: AI writes faster than anyone can check

Both of those problems existed before AI. What changed is the volume. Today AI writes content faster than anyone can check it. The writing has become cheap. The checking has not, and it is the step that decides whether what goes live is true.

That is why I describe Vetta as the Shopify app that lets you control AI-generated content. Whoever or whatever writes a change, a colleague, a CSV import or an AI agent, it arrives as a proposal. A reviewer sees exactly what changes, field by field and in each language, and it only reaches the storefront once someone approves it. AI agents can propose; they cannot publish.

Who I built it for

Mostly for people in the position I was in: agencies and freelancers who work on their clients’ Shopify stores and need those clients to validate what goes live, without giving everyone admin access or running the process through email. A client can be invited as a reviewer and approve changes without a Shopify staff account. If that is your situation, the agencies page explains how it is set up.

And for stores with several people touching the same content, it is the same idea from the other side: nothing changes without someone checking it, and if something goes wrong anyway, you know what happened and you can go back.

That is really all Vetta is. It is the tool I wanted on those two projects, built by someone who still works on Shopify stores every day.