General

Who Should Own Your Product Catalog?

Two arrangements

There are two ways to run a store you did not build yourself. In the first, the agency owns everything. You want a product added, you email them. You want a price changed, you email them. Maybe it happens the same week, maybe there is an invoice attached. In the second, you own your catalog and they own the machinery underneath it. Agencies tend to prefer the first. It is more billable and it keeps the client dependent. It also produces worse stores, reliably, and it is worth understanding why.

Why gatekeeping makes stores stale

A catalog is not a website. A website changes a few times a year. A catalog changes constantly: something sells out, a price moves, a seasonal item comes back, a photo is better than the one you rushed at launch. Every one of those is small, and every one of them is urgent in a minor way. Put a vendor between the owner and those changes and something predictable happens. The urgent ones get emailed. The merely useful ones do not, because emailing someone about a slightly better product photo feels like an imposition. So the store drifts. Sold-out items stay listed and customers order them. Prices lag your actual costs. The description you have wanted to rewrite for a month stays as it is. None of that is the agency being slow. It is the friction of asking, and friction always wins.

You know the products

There is also the plain fact that you know your products and nobody else does. You know which two items get confused with each other, which one needs the allergen note, why the large is worth the upcharge, and what customers actually ask before buying. A developer writing your product descriptions is guessing, and the guess is usually a paraphrase of what you already told them, filtered through someone who has never handled the thing. Product copy written by the person who makes the product is better. It is not close.

What you should not be doing

None of this means you should run the whole store. There is a real technical layer and it needs someone competent watching it. Checkout has to work on every device and every browser. The payment connection has to stay authenticated. Tax and shipping rules have to be configured correctly and updated when they change. Order confirmations have to actually arrive rather than landing in spam. The platform needs patching. Backups need to exist and need to have been tested. That work is invisible when it goes well and catastrophic when it does not, and it is nothing like adding a product. It is the part worth paying someone for.

Where the line goes

The line is: anything about what you sell belongs to you, anything about how the store functions belongs to whoever runs it. Products, prices, photos, descriptions, stock, categories, and what is featured this week are yours. Hosting, security, checkout, payments, tax and shipping configuration, the template, monitoring, and backups are theirs. If you are evaluating someone to build or run your store, ask them directly which side of that line they put the catalog on. The answer tells you a lot about the arrangement you are entering, and about whether they are selling you a service or a dependency.

How we do it

Goodform builds the store, sets up your catalog with you at launch, and hands you the keys to it. Adding a product takes a couple of minutes from your phone, costs nothing, and needs nobody's approval. Everything underneath is ours.