What Is the Difference Between a Sourcing Partner and a Factory When You Import?

The question is usually asked as a pricing question — can a buyer go direct and remove a margin — and it is better asked as a risk question. Going direct is entirely possible and sometimes right. What changes is not only the price but who absorbs the things that go wrong: a specification that has to be rewritten, a line that is full in the needed window, a test report that a customer will not accept, a second colourway that has to be sourced from a different base.

A production base optimises for its own utilisation. That is not a criticism, it is what a line is for: a base wants a long run of a construction it knows, on equipment it has, with materials it holds. A buyer with a stable high-volume repeat of one construction is a good match for that, and a buyer with four categories, three colourways and a seasonal calendar is not, however attractive the unit price looks.

This piece sets out what each side actually owns, where the difference costs or saves money, and how to decide. It uses the phrase sourcing partner throughout to mean a company that coordinates production and manages the programme on the buyer behalf, which is the role this desk performs.

What Does a Production Base Actually Own?

The line, the operators, the equipment, the material store and the production schedule. It converts an approved specification into goods, and it is judged on whether it does that to the agreed window and the agreed standard. What it does not own is the specification itself, the compliance file for the destination market, or the consequence of a delivery date that was set before anyone asked whether the line was free.

Who Owns the Specification in Each Arrangement?

In a direct relationship the buyer owns it alone, which is fine if the buyer has someone who can write and hold a tech pack, and expensive if not. The failure is rarely dramatic: the specification is written once in an email, never given a revision number, and quietly reinterpreted on both sides over two runs. By the third reorder nobody can say what was agreed, and the argument is settled by whoever has the strongest commercial position rather than by the document.

With a programme manager the specification is the central artefact of the relationship rather than an attachment to a purchase order. It carries a revision number, it is referenced by the quotation, the sample and the inspection, and a change to it is a decision with a visible cost in calendar. That discipline is worth more than any difference in unit price on a range that is going to be reordered.

What Changes When Capacity Is Short?

This is the moment the two arrangements diverge most sharply. A single base that is full in the needed window either asks the buyer to wait or declines, and the buyer discovers the constraint at the point of ordering rather than at the point of planning. A coordinated programme has already asked the capacity question across more than one base, and it can move the work or split it.

The seasonal version of this is the one that costs the most. In the months running up to an autumn selling season, capacity across the whole production region tightens, and a buyer with one base and no plan B discovers that at the worst possible moment. The development calendar from tech pack to bulk note sets out the calendar view of that squeeze.

How Is a Change Handled Differently?

Step 1

The change is described against the current revision

Step 2

The effect on materials is established

Step 3

The effect on the sampling window is stated in days

Step 4

The effect on the bulk window is stated in days

Step 5

The cost is quoted, including any material already bought

Step 6

The buyer decides, against a stated date

Step 7

The tech pack is re-issued at a new revision

Step 8

The new revision is acknowledged in writing

Step 9

Any compliance document affected is re-opened

Step 10

The reference sample is updated after approval

Those ten steps are the same in both arrangements; the difference is who does them and how long they take. A buyer working direct does all ten alone, usually while also running the rest of the business. A programme manager does them as routine work, which is why a change that costs a direct buyer two weeks of email frequently costs a managed programme two days.

What Does the Arrangement Cost?

A coordinated programme carries a margin that a direct relationship does not, and the question is what that margin buys. It buys the capacity search, the specification discipline, the inspection planning, the compliance file assembly, the change handling and someone whose job is to notice that a gate has slipped. Whether those are worth more or less than the margin depends entirely on whether the buyer has those capabilities in house.

The comparison that matters is not margin against zero, it is margin against the cost of getting it wrong once. A single failed run on a 500-piece order — rejected at inspection, reworked, reshipped — costs more than the margin on several successful ones. Buyers who have never had a run fail tend to price the margin and not the failure; buyers who have had one tend to do the opposite.

When Is Going Direct the Right Call?

Where all four hold, direct is sensible and the savings are real. Where two of the four hold, the usual outcome is that the buyer saves the margin and spends it on a delay, a re-work or a compliance gap, and the spend is larger than the saving because it lands late in the calendar when it costs the most.

When Is a Programme Manager the Better Answer?

How Is Accountability Written Down?

One party, one commitment. In a direct relationship accountability is split: the base is accountable for making the goods to the specification and the buyer is accountable for everything else, including the things the buyer did not know were theirs. In a coordinated programme there is one party accountable for the outcome, which is the difference that matters when something goes wrong and two parties each have a reasonable explanation.

The written expression of that is the order file: a single document that names the specification revision, the windows, the inspection plan, the payment trigger and the change rule. Whether the arrangement is direct or coordinated, that file is what turns a commercial relationship into a programme, and it is worth insisting on in both cases.

How Do the Quality Arrangements Differ?

Less than buyers expect, because the standard is the same either way: ISO 2859-1 at General Inspection Level II, AQL 2.5 for major defects and 4.0 for minor, with critical defects at zero acceptance. What differs is who writes the class list and who is in the room when a lot fails. A buyer working direct has to define the classes and argue them; a coordinated programme has already defined them and applies them.

The class list is the whole game. "Workmanship" is not a defect class; a list that names the defect, the class and the acceptance number for each is. A buyer who writes that list once, in either arrangement, has done more for the outcome than any amount of inspection after the fact.

How Does the Communication Load Differ?

In a direct relationship the buyer carries all of it: the specification questions, the material questions, the scheduling questions and the compliance questions, each with a party in another time zone and usually in another first language. That is a real workload and it is routinely underestimated, because each individual exchange is short. What accumulates is not the length of the messages but the number of decisions waiting on them.

A coordinated programme concentrates that load. The buyer makes the product decisions and the programme manager carries the rest, which is the practical meaning of the margin: it is buying back the hours and, more importantly, the latency. The turning a tech pack into a production specification note covers the document that removes most of the questions before they are asked.

What Happens at the Third Reorder?

By the third run the differences between the two arrangements are visible in the artefacts rather than in the relationship. A direct buyer either has three tech packs at three revisions, three retained samples and a written defect history, or has none of those and is re-deciding everything from memory. A coordinated programme has them as a matter of routine, because producing them is part of the work.

The measurable effect is on the calendar. A reorder that starts from documents is quoted, sampled and scheduled in a fraction of the time a reorder that starts from a conversation takes, and it is more likely to match the run before it. Over three or four years that difference is worth more than the accumulated margin, which is why buyers who have run both tend to stay with coordination.

One more dimension deserves its own answer because it decides several relationships every year: what happens when the buyer wants a construction the base has never made. A production base quotes optimistically on unfamiliar work, because it wants the booking, and the optimism lands as a longer sampling window and a higher defect rate at inspection. A coordinated programme can say no to the match, or can qualify a second base for that construction, or can stage the first run as a pilot with a smaller commitment and a defined decision at the end of it.

What Should a Buyer Ask Before Choosing?

Three questions, answerable in an email. Who holds the tech pack and its revisions? What happens if the line is full in the needed window? And who produces the compliance file when a customer or an authority asks for it? The answers tell a buyer which arrangement they are actually in, regardless of what the relationship is called, and they tell the buyer what a margin is or is not buying.

A fifth question belongs on the list for any buyer with a retail customer: who answers when the customer audits. An audit request arrives with a deadline and asks for a site, a date and a document set, and the buyer either produces them or loses the listing. Establishing which party holds those artefacts, before any request arrives, is the most economical insurance in the relationship.

The fourth question is the honest one: what happens when something goes wrong. Asked early it is a hypothetical; asked after a failed lot it is a negotiation. A relationship that answers it well in advance is worth more than a small difference in unit price, because the unit price is known and the failure cost is not.

Frequently Asked Questions

People Also Ask