Vendor vs supplier in fashion, understanding supply chain terminology
Manufacturing & Supply Chain

Vendor vs Supplier: What's the Difference?

Clear definitions, how fashion teams actually use the two words, and the moments where getting it wrong costs you money.

Joe LauderJoe Lauder·Founder, Kōbō·Updated Jul 29, 2026

In fashion, vendor and supplier get used as if they mean the same thing, and most days nobody minds. The distinction starts to cost you the moment it hits a contract, a compliance disclosure, or a system that treats the two as different record types.

The Short Answer

The short answer

A supplier provides the inputs a product is built from: fabric, trims, packaging, services. A vendor sells a finished or semi-finished product ready to resell. Suppliers sit upstream in the supply chain, vendors sit downstream, and one company can be both.

That's the definition you'll find in most procurement textbooks, and it holds up well enough as a starting point. What it doesn't tell you is that the words are used far more loosely than the definitions suggest, and that the loose usage is usually fine right up until it isn't. Two teams inside the same brand can use the words in opposite ways without ever noticing, because they never look at each other's spreadsheets.

The rest of this piece is about the parts that aren't in the textbook: who calls whom what in a real fashion supply chain, why an American merchandiser and a European production manager will disagree about the same factory, and the four or five specific situations where the label you attach to a partner changes what happens next.

Supplier

Provides raw materials, components, or services upstream. Suppliers deliver the inputs your products are made from, and their names end up on your bill of materials. Examples: fabric mills, knitters, trim and hardware suppliers, yarn spinners, packaging providers, dye and wash houses.

Vendor

Sells finished or semi-finished goods, positioned closer to the end customer. Vendors take inputs and hand back completed product, and their names end up on your purchase orders. Examples: cut and sew factories, full package (FOB) manufacturers, private label producers, wholesalers.

The one line versionSuppliers provide what you need to make things. Vendors provide things that are already made. A fabric mill is a supplier. The factory that sews your garments from that fabric is a vendor. And the factory that buys the fabric on your behalf is quietly both.

Vendor vs Supplier in Fashion: Who Calls Whom What

Fashion has a longer chain than most industries and almost every link buys from the link above it, which is why the same company gets called different things depending on who's talking. It helps to walk the chain from the fibre end down to the shop floor and note where each word gets used.

Mills, knitters and dye houses: Nobody calls these vendors. They're suppliers, full stop. They sell you fabric by the metre or by the kilo, they have minimums per quality and per colour, and their names sit on bill of materials lines rather than purchase orders

Trim and component suppliers: Buttons, zips, labels, hangtags, elastic, interlining, polybags. Also universally called suppliers, and usually the most fragmented part of the base, which is why brands end up with fifty small accounts and no single view of them

Cut and sew factories: This is where the language splits. A factory that sews garments from fabric you supply is a classic vendor because it hands back finished goods. Plenty of production teams still call it a supplier out of habit, and both are defensible

Full package (FOB) manufacturers: The factory buys the materials and quotes a finished garment price. Commercially it behaves like a vendor. Operationally it has become your supplier manager, running its own mill and trim relationships on your behalf

Sourcing agents and trading houses: An agent introduces and manages factories for a commission, so it isn't really either. Some brands set the agent up as the vendor of record and pay them directly, which keeps accounting simple and makes traceability harder

Brands selling into retailers: Here the brand itself is the vendor. To a department store or marketplace, you are a vendor with a vendor number, a vendor manual, and a vendor scorecard, regardless of what you call your own partners

That last one catches people out. A small brand can spend the morning being a customer chasing its suppliers and the afternoon being a vendor getting chased by a retailer, using the same vocabulary in both directions with different meanings. If you're at the earlier stage of building this base, our guide to finding the right manufacturer covers the vetting side, and the cut and sew manufacturing guide explains where CMT ends and full package begins.

Supplier vs Vendor: Side by Side

The table below breaks down the difference between a supplier and a vendor across the dimensions that actually change how you work with them.

DimensionSupplierVendor
DefinitionProvides raw materials, components, or servicesSells a finished or semi-finished product
Position in supply chainUpstream, early in the production processDownstream, closer to the end customer
What they provideFabrics, yarns, trims, threads, zips, labels, packaging, wash and dye servicesCut and sewn garments, full package production, finished goods
Where the name sits in your dataOn the bill of materials, against each component lineOn the purchase order and the invoice
Relationship typeLong term, development led, often shared across factoriesOrder led, ranging from transactional to strategic
Order patternBulk materials with mill minimums per colour and per qualityPer style MOQs and seasonal production runs
Examples in fashionFabric mill, knitter, button maker, dye house, interlining supplierCMT factory, FOB manufacturer, private label producer, wholesaler
Negotiation focusQuality consistency, lead time, MOQ, exclusivity, colour continuityUnit price, delivery date, payment terms, quality standards
How performance is judgedLab dip and bulk approval rates, shade consistency, on time material deliveryOn time in full, measurement and quality pass rate, cost accuracy
Compliance languageTier 2 and beyond, material traceability, mill certificationsTier 1, code of conduct, factory audits, disclosure lists
Key takeawayThe difference between supplier and vendor comes down to where they sit in the value chain and, practically, where their name lands in your data. Suppliers feed inputs into the process and appear on bills of materials. Vendors deliver outputs from it and appear on purchase orders.

How the Terms Shift by Region and Context

Most arguments about vendor versus supplier are really arguments about which industry dialect someone learned first. The words carry different defaults depending on the market you sell into and the function you sit in.

US retail: vendor is the default

In American retail, vendor means whoever sells goods into the retailer. That's why the vocabulary around it is so developed: vendor numbers, vendor manuals, vendor portals, vendor compliance, vendor chargebacks, vendor scorecards. If you sell wholesale into a US department store, you'll be issued a vendor guide that runs to dozens of pages covering labelling, carton marking, routing, and EDI, and the penalties for missing any of it.

Sourcing and manufacturing: supplier is the default

Move into sourcing, production, and sustainability teams and the default flips. Everything is a supplier: approved supplier lists, supplier codes of conduct, supplier audits, supplier development, supplier risk. The reason is that these functions think in tiers rather than transactions, and tier language only works if every level of the chain shares one noun.

UK and Europe: supplier for almost everything

British and European teams tend to say supplier for anyone they buy from, whether it's fabric or finished garments. Vendor sounds slightly imported and is more often heard in software procurement or in a legal context, where a vendor is simply the party selling something. Neither usage is wrong, but if your team spans both sides of the Atlantic you should expect the mismatch and write it down somewhere.

Finance and ERP: everyone is a vendor

Accounts payable has the bluntest definition of all. Anyone you pay goes into the vendor master, so your fabric mill, your freight forwarder, your sample courier, and your accountant are all vendors as far as the ledger is concerned. This is where confusion usually enters a growing business: finance imports its vendor list into a new system, production expects to find suppliers there, and the two lists never quite reconcile.

Watch out: the same factory can be a vendor in your accounting system, a tier 1 supplier in your compliance disclosure, and a manufacturer in your product data. That's not a problem in itself. It becomes a problem when nobody has agreed which of those records is the master, and three departments start maintaining three versions of the same address, contact, and certificate.

Vendor Management vs Supplier Management

Beyond the definitions, vendor management and supplier management are genuinely different disciplines with different rhythms. Vendor management is mostly about performance against something already agreed. Supplier management is mostly about capability and risk before anything is agreed at all.

What supplier management involves

Supplier work is front loaded. The value is created before the order exists, in development, qualification, and capacity planning. You're not buying a product so much as securing the ability to make one to a standard your customers recognise.

Qualification and approval: Assess capability, minimums, certifications, and testing before a supplier ever appears on a bill of materials, then keep an approved list that buyers actually work from

Development collaboration: Work with mills on custom qualities, exclusive prints, and proprietary blends, which is slow work that pays back over several seasons rather than one

Forecasting and capacity: Share seasonal forecasts early so mills can reserve yarn and loom time, because material lead times, not sewing time, are what usually break a critical path

Colour and quality continuity: Track lab dip and bulk approval history so a carryover fabric matches season to season, and so you know which supplier drifts

Continuity and risk: Know which materials have a single source, where the second source would come from, and how long a switch would take if the first one stops

What vendor management involves

Vendor work is back loaded. The specification is settled, so the job is measuring execution against it and reacting fast when the numbers move. Good vendor management is boring, repetitive, and worth a lot of margin.

Price and terms: Compare unit costing across vendors, understand what drives the difference, and watch for surcharges on sub-minimum orders that quietly erase a margin

On time in full: Track promised versus actual ship dates and quantities by order, and flag slippage at the fabric stage rather than at the shipping stage

Quality pass rates: Score inspection results and measurement conformity by vendor, so pattern and grading problems get separated from workmanship problems

Scorecards and reviews: Give each vendor the same handful of numbers every season, in the same format, and review them together rather than only when something has gone wrong

Capacity planning: Know each vendor's production calendar and peak weeks, and avoid booking your most complex style into their busiest month

Brands that do this well tend to run one shared set of measures across both groups rather than two disconnected processes. Our guide to supplier management best practices goes deeper on the scorecard side, including what to measure when you're too small to have leverage.

When the Distinction Actually Matters

Ninety percent of the time you can use either word and nothing bad happens. Here are the situations where precision earns its keep.

Contracts and liability

Buying materials and buying finished goods are different transactions in law and in practice. A materials agreement needs to cover shade and quality tolerances, testing standards, batch consistency, and what happens to fabric that fails after cutting has started. A finished goods agreement needs inspection and acceptance criteria, delivery terms and Incoterms, defect liability, and who owns the patterns, blocks, graded specs, and artwork when the relationship ends.

The costly grey area is fabric liability under full package. If the vendor sourced the fabric and it fails a rub test after production, that's the vendor's problem. If you nominated the mill, it usually isn't, and the argument you have then depends entirely on how the agreement described the relationship in the first place.

Compliance and traceability

Due diligence and disclosure expectations are written in supplier and tier language, not vendor language. Tier 1 is where your product is assembled, tier 2 is fabric and materials processing, and tiers beyond that reach into yarn and raw fibre. A vendor list tells you who you paid. A supplier map tells you where the product came from, and the two are not interchangeable when a customer, a retailer, or a regulator asks.

If you only track vendors, everything below your cut and sew factory is invisible, which is precisely the part of the chain that questions get asked about.

Costing and product data

In your product data the distinction is structural rather than semantic. Supplier names belong on bill of materials lines, next to the component, the consumption, and the price per unit. Vendor names belong on the purchase order, next to the style, the quantity, and the delivery date. Mix those up and you can't answer either of the two questions that matter: what does this garment cost to make, and who owes me what next week.

Onboarding and system access

The two roles need different things from you and should see different things from you. A mill needs colour standards, lab dip requests, and material specs. A factory needs tech packs, size charts, comments on fit samples, and delivery schedules. If you invite both into the same portal with the same permissions, you'll either overshare commercial data or make people ask you for files by email, which defeats the point of having a portal.

Where the Two Roles Overlap

In fashion manufacturing the line is rarely clean, and pretending otherwise is how data models end up fighting reality. Several common arrangements put one company on both sides at once.

A vertically integrated mill that knits its own fabric and sews its own garments is a supplier and a vendor inside one legal entity, one contract, and one invoice. A full package manufacturer sells you finished goods (vendor) while running fabric and trim procurement on your behalf (supplier management, delegated). An agent sits outside both definitions and can appear in your books as the vendor of record while none of the actual production happens under their roof.

Nominated suppliers are the sharpest version of the overlap. You choose the mill, agree the price and the quality with them directly, then instruct your factory to buy from them and bill it through the garment price. The mill is your supplier by relationship and the factory's supplier by transaction. That works well until something fails, at which point everyone points at the other party, and the only thing that resolves it is having written down who approved what and when.

Practical tipDon't try to force every partner into one box. Model the role instead: one company record, with roles it can hold (material supplier, production vendor, agent, service provider) and a tier tag for compliance. A company can hold more than one role, and the same record still reconciles with finance.

Setting It Up in Your Systems

This is where the vocabulary stops being academic. Once you're running more than a handful of partners across spreadsheets and email threads, the vendor and supplier question becomes a data modelling question, and getting it slightly wrong creates work every season. A PLM system is where most brands eventually settle it, because it's the one place where materials, styles, and orders all meet.

One record per company, with a role field. Two directories for the same factory means two addresses, two contact lists, and two sets of expiring certificates
Tier tagging on every partner, so a compliance disclosure is a filter rather than a fortnight of chasing
Supplier names linked to bill of materials lines, so costing rolls up from real component prices instead of estimates
Vendor names linked to purchase orders and delivery dates, so the critical path reflects who actually owes you what
Performance history on the partner record: on time delivery, quality pass rate, lab dip approval rounds, cost variance
Documents stored against the company, not in someone's inbox: certifications, audit reports, quality agreements, signed terms, with expiry dates visible
Portal access scoped by role, so mills see materials and colour work while factories see tech packs, samples, and schedules

The pattern worth copying is simple. Model companies once, model roles separately, and let the words vendor and supplier describe what a partner is doing on a given order rather than what they are forever. That way finance, production, and compliance can each use their own dialect and still be looking at the same underlying record.

Understanding the difference between vendors and suppliers is the easy part. Building a system where both are visible, measured, and traceable is what separates brands that scale from brands that stall.

If you're weighing up whether it's worth moving this out of spreadsheets, the practical test isn't how many partners you have. It's whether you can answer, right now and without asking anyone, which supplier provides a given trim, what the last three deliveries from a given factory looked like, and which certificates expire this quarter. If any of those take more than a minute, the structure is the problem rather than the effort. Kōbō is built around exactly this model, and the pricing page shows what it costs at your size.

Frequently Asked Questions

What is the difference between a vendor and a supplier?

A supplier provides the raw materials, components, or services that go into a product, such as fabric, trims, and packaging. A vendor sells a finished or semi-finished product ready to resell, such as a garment factory or a wholesaler. Suppliers sit upstream, vendors sit downstream, and one company can be both.

Can a company be both a vendor and a supplier?

Yes, and in fashion it is the norm rather than the exception. A full package factory buys fabric and trims (acting as a buyer of suppliers) and sells you finished garments (acting as your vendor). A vertical mill that knits its own fabric and sews its own garments is a supplier and a vendor in a single legal entity.

Is a manufacturer a vendor or a supplier?

It depends on what you buy from them. If a factory sews garments from fabric you own, most brands call it a vendor because it delivers finished goods. If that same factory sources the fabric and quotes you a full package price, plenty of teams call it a supplier because it now owns material development too. Compliance frameworks sidestep the argument and call it a tier 1 supplier either way.

Why do American and European teams use the terms differently?

In US retail, vendor is the standard word for whoever sells goods into the retailer, which is why you see vendor manuals, vendor portals, and vendor chargebacks. In the UK and Europe, supplier is the default word for almost anyone you buy from, and vendor sounds like software procurement. Finance systems complicate it further by calling every payee a vendor in the vendor master.

Does the vendor versus supplier distinction matter for contracts?

It does. Buying materials and buying finished goods carry different obligations around title and risk transfer, Incoterms, inspection and acceptance criteria, defect liability, and ownership of patterns, blocks, and artwork. Naming the relationship accurately in the agreement makes it much easier to argue who pays when something goes wrong.

How should I organise vendors and suppliers in a PLM system?

Keep one partner record per company and add a role field rather than maintaining two separate directories. Tag each partner by tier and capability, link material suppliers to bill of materials lines, link production vendors to purchase orders, and scope portal access to what each role actually needs to see.

Joe Lauder, Founder of Kōbō Labs
About the Author
Joe Lauder
Founder · Kōbō Labs

Joe's the founder of Kōbō Labs. Before this, he founded Satta, a fashion brand he scaled to sell internationally at Mr Porter, SSENSE, and Beams Japan. A decade of running his own brand, design, suppliers, production, the lot, is what Kōbō is built on.

Ready to manage every vendor and supplier relationship in one place?

Kōbō centralises your partner directory, performance data, and communication history, so nothing gets lost between seasons.

Book a Discovery Call