Shopify vendor field: what 181 stores actually put in it
There is a column in your product admin called Vendor. If you have never deliberately filled it in, it is still not empty.
We read the public product catalogue of 181 Shopify storefronts on 23 September 2026 (6,473 products) and checked what was in that field. Not one product came back with it blank. That is the finding, and it is not the good news it sounds like.
This piece does not tell you what to put in the field. It tells you what is in it on 181 storefronts that asked strangers for a review of their shop, which is a particular kind of store and not a sample of Shopify.
A field that is never empty is not a field that is filled in
| Share of 6,473 products | |
|---|---|
| Vendor blank | 0.0% |
| Vendor identical to the store's own domain name | 43.2% |
The second row is a match against the store's own hostname, which is a rough test and we say how rough in the method section. Read it as a floor for "this is the shop's name, not a supplier's".
And read it next to the other version of itself. We could only read 50 products per store, and 107 of the 181 stores hold more than that. On the 74 stores whose catalogue we saw in full, the same match rises to 60.6%. The stores we could only see one page of are the ones doing more with the field, so the 43.2% is the friendlier of the two numbers, not the harsher one.
So on close to half the products we read, the answer to "who is the vendor" is "us". That is a legitimate answer for a store that makes what it sells. It is also exactly what you would see if nobody had ever touched the field.
See what Arvio does with product data
More than half of stores use one value for the whole catalogue
Counting stores instead of products changes what the number means. The median storefront uses exactly 1 distinct vendor value across everything it lists. 97 of the 181 stores are on a single value, and for 66 of those 97 that value is the store's own name.
At the other end, 37 stores use five or more, and one store had 31 distinct vendors in the 50 products we read from it. Those are catalogues where the field is doing real work: a shop that resells across brands has something to put there.
The distribution is the point. This is not a field that most stores fill in badly. It is a field that most stores never engage with at all, and a minority use properly.
What the field actually is
Shopify's Liquid documentation describes product.vendor in one line — the vendor of the product — and types it as a string rather than a list, so a product has one vendor and cannot have two. Buy from a distributor who carries several brands and the field will not hold both facts.
It is also not required. Shopify's own product documentation says a product needs only two things: a title and a price. Everything else, vendor included, is optional structure you add for your own benefit — filtering and sorting in the admin, and whatever your theme chooses to display.
That is worth stating plainly because it changes what a full column means. Nothing checks it. Whatever is in it is what somebody or something typed.
Something else is filling it in
The single most common vendor value across everything we read was Printify, on 258 products. Those products were spread across 9 stores.
We cannot see who typed it, and we say so at the bottom of this page. What we can see is that the same value sits on products in 9 unrelated shops, which is not how a name somebody chose for their own brand behaves. If you import products from an app, whatever the app writes becomes your vendor column. That is fine until you try to use the column for something.
How Arvio works across a whole catalogue
What to check on your own store
Open https://your-store.com/products.json in a browser. That is the endpoint we read — no login, and it is what any crawler already sees. It pages: ?limit=250&page=2 gets the next 250, and you keep going until a page comes back empty.
Count how many distinct vendor values you have. One value across a catalogue of five hundred products tells you the field is decorative on your store. Thirty tells you somebody has been maintaining it.
Check whether that one value is your own store name. If it is, you have not lost anything — but you also do not have supplier data, so anything you were planning to build on top of it has no input.
Look at what your apps wrote. Sort by vendor and look for names you did not type. Those came from an import, and they will keep coming.
When this is not worth your time
You make what you sell. Then your own name is the correct answer and the field is done. Nothing below applies.
You have no workflow that reads it. The field costs nothing while it sits there. It only matters when you start filtering by it, feeding it somewhere, or displaying it on the product page — and if you are not doing any of those, a tidy vendor column buys you nothing.
You already know the answer. If you can name your suppliers from memory because there are four of them, a report telling you there are four is not useful. The number gets interesting on catalogues nobody can hold in their head — which, in our sample, is most of them: 107 of the 181 stores hit the 50-product ceiling we read to, so we saw only part of what they list.
Arvio reads the same fields and flags the products where the organising data is missing or was written by something other than you. You choose the scope — one product, a batch, or the whole catalogue — and every change waits for you to approve or reject it, with any edit reversible in a click. What it will not do is decide whether your vendor column should hold the brand or the distributor. This article just spent a section explaining that the platform has no answer to that; neither does a tool that reads the same field.
What we cannot tell you is whether any of this moves your revenue. We counted what is in the field. Whether filling it in properly sells anything is a different question, and reading public catalogues once does not answer it.
Check your own catalogue with Arvio
FAQ
What is a vendor in Shopify?
A text field on the product, described in Shopify's Liquid reference simply as the vendor of the product. It is meant for the brand, manufacturer or supplier, it is optional, and it is not validated against anything. In our sample it was never blank and 43.2% of the time it matched the store's own name.
How do I add or change a vendor in Shopify?
It is a field in the Product organization section of the product page in your admin, with a dropdown of values you have used before. What we can say from the data rather than from the interface is that whatever ends up in there tends to stay: the median store in our sample has been using exactly one value across its whole catalogue.
How do I find which products have which vendor?
The product list in your admin filters by vendor. For a catalogue-wide view without clicking through filters, read products.json as described above and count the distinct values — that is exactly what we did, and it takes a minute.
Vendor, brand or supplier — which one is it?
Shopify gives you one string, so you have to pick. If you resell several brands bought through one distributor, the field cannot hold both and you will have to decide which one your workflows need. Merchants have been asking this question in the community for years and there is no platform answer, only a convention you choose and then apply consistently.
Can a product have more than one vendor?
No. product.vendor is a single string in Shopify's Liquid object, not a list. Anything beyond one value has to live somewhere else — tags, metafields, or an app.
Does the vendor field affect SEO?
We did not measure that and this read cannot tell you. What we can say is what the field is: an organising attribute that your theme may or may not print on the page. If you want to know what we did measure about product pages, the Shopify product page audit covers eleven checks across a different sample.
Should I clear it if it is just my store name?
There is nothing to clear — the field will hold whatever you leave in it, and your own name is a valid value. The question worth asking is the opposite one: if you have suppliers and the column says your name on every product, the data you thought you had is not there.
How we measured this
The sample frame is the Shopify Community "Store Feedback" board, where merchants post their own store URL and ask strangers for a review. We read the first post of 600 threads, posted between March 2025 and September 2026, and took every linked hostname, dropping the community's own domain, Shopify's, image hosts, social networks and link shorteners. That left 406 candidate domains. On 22 September we requested /products.json?limit=1 from each and kept the 185 that answered with valid Shopify product JSON. The 221 that did not are this frame's largest bias: 114 did not resolve at all, 53 returned HTTP 404, 26 returned HTTP 402 — the code Shopify serves for a frozen unpaid store — 10 returned 401, 11 answered with something that was not JSON, and 7 failed in other ways. What survives is the set of shops still trading that week.
The catalogue read itself happened the next day, 23 September: one pass per store, from the same public endpoint, up to 50 products each. Two of the 185 that had answered the day before did not answer this time — one HTTP 402, one HTTP 500 — and of the 183 that did, two carried no products at all. That leaves the 181 storefronts and 6,473 products here.
This is the same read as the Default Title variant piece, which used the same 181 storefronts to count variants rather than vendors.
How we decided a vendor "is the store's own name". We reduced the store's domain to its main label — dropping www., shop. and similar prefixes and the suffix — kept only letters and digits, lowercased both sides, and required an exact match. No fuzzy matching, so anyone can reproduce the same number from the same data.
What this doesn't show
- That match test is a floor, not a measurement. It undercounts every store whose brand name differs from its domain, and overcounts every store whose real brand happens to equal its domain — which is correct data, not an empty field. Both errors are in the sample and we cannot separate them.
- This is not a random sample of Shopify. It is a public, reproducible convenience frame. Merchants who post asking for feedback skew newer, smaller, and more likely to be struggling. Anyone can rebuild the same list from the same board, over the same date range, with the same rule.
- We read up to 50 products per store, and 107 of the 181 hit that ceiling. Excluding those stores moves every number here and moves them a long way: on the 74 stores we saw in full, the share of products whose vendor matches the store name rises from 43.2% to 60.6%, stores on a single vendor value go from 97 of 181 to 55 of 74, and the largest number of distinct vendors on one store drops from 31 to 15. The direction holds; the size does not. The stores we could only see one page of are the ones doing more with the field.
- We cannot tell an empty field from one the platform filled for you. The 0.0% blank figure is what the public endpoint returned; we did not establish whether a merchant who never touched the field would show up as blank there at all. If Shopify or an import always writes something, then "never empty" is a property of the plumbing and not a fact about merchants — which is exactly why the rest of this piece is about what is in the field rather than whether it is.
- We did not check whether the value is correct. A vendor reading
Acmetells us a string is there, not that Acme made the product. - The public endpoint does not expose everything. We can report what is in the vendor field and nothing about where it came from, except where the value names an app.