What Does a Supply Chain Consultant Actually Do for a Fashion Brand?

I've been asked this question, in various forms, in almost every introductory conversation I have with prospective clients. It's a fair question. The word "consultant" covers an enormous range of activities — from a McKinsey team producing a 200-page strategy document to someone sitting in your warehouse redesigning your pick-and-pack process. These are very different things, and the distinction matters a great deal when you're deciding whether to spend money on one.

Let me try to give you a direct answer — and in doing so, explain clearly how I think about the difference between consulting that produces change and consulting that produces paper.

The Two Models of Consulting — and Why the Difference Matters

There are two fundamentally different ways a supply chain consultant can work with a fashion brand. I'll call them advisory and implementation, though the labels are imprecise.

Advisory consulting — the dominant model in large management consultancies — works like this: the consultant (or a team of them) comes in, conducts interviews and data analysis, and produces a report or a set of recommendations. The deliverable is the document. The client receives a diagnosis, a strategy, and sometimes a prioritised list of initiatives. Then the consultants leave. What happens next is the client's problem.

This model is not without value. For genuinely complex strategic questions — should we enter a new market, how should we structure our multi-brand portfolio, what's the long-term sourcing strategy — an external analytical perspective can be genuinely useful. And the large consultancies have real analytical firepower.

But for operational problems — the kind that most mid-size Indonesian fashion brands are actually dealing with — advisory consulting frequently fails to produce meaningful change. Not because the analysis is wrong. Because the gap between "knowing what to do" and "actually doing it" is enormous, and most advisory engagements end exactly at that gap.

Implementation consulting works differently. The consultant embeds with your team, works through the problems alongside your people, builds the actual systems, trains the actual staff, and stays until the change is operational. The deliverable isn't a document — it's a changed operation.

What a Supply Chain Consultant Should Actually Deliver for a Fashion Brand

Let me make this concrete. Here are the kinds of engagements I run, and what gets delivered at the end of each.

Production planning system build: This starts with mapping the current state — how does the factory or brand currently plan production, what information is used, how is it communicated, where does it break down. Then it moves to designing a better system, which for most SME brands means something relatively simple: a master production schedule template, a capacity utilisation model, weekly reporting cadence, and clear escalation protocols when plans change. Then the implementation work — populating the tools with real data, running the first production cycle through the new system, troubleshooting the problems that always emerge in the first few weeks, adjusting based on what you learn. At the end, there is a working system, documented operating procedures, and a team that has run it through at least one full cycle and knows what to do when things go wrong.

Logistics cost restructuring: This starts with a cost-to-serve analysis — mapping every cost component from production to the buyer's door, by trade lane. It moves to benchmarking and market testing — running an RFQ to alternative freight forwarders, reviewing HS code classifications, checking incoterms alignment. Then the negotiation and restructuring work — renegotiating freight contracts, correcting customs classifications, adjusting incoterms where it makes sense. At the end, there are new freight contracts, documented cost-per-unit models by lane, and vendor scorecards so the ongoing management is straightforward.

Sustainability framework implementation: This starts with mapping what your buyers actually require — not generic sustainability best practice, but the specific documentation standards your specific buyers are asking for. Then a gap analysis against your current documentation. Then building the systems: facility data collection processes, supplier questionnaire and response management, third-party audit preparation and remediation, reporting templates. At the end, there is a repeatable sustainability documentation process, annual reporting ready to deploy, and a team that knows how to maintain it.

Notice that in each case, the deliverable is an operational capability, not a piece of paper. The brand's team is doing the work at the end of the engagement — not the consultant. That's the point. If the only person who can run the system is the consultant, you haven't built anything useful.

How to Tell the Difference Before You Hire

The clearest diagnostic: ask the prospective consultant to describe what a typical engagement looks like, week by week, and specifically what is left in your hands at the end. If the answer is heavy on meetings, analysis, and documents, and light on implementation work and handover — you're looking at an advisory engagement. If the answer describes embedded work, system builds, and a specific handover process, you're looking at an implementation engagement.

Some other useful questions: Have they done this specific type of work in the Indonesian apparel context before? (Industry-agnostic logistics consultants who have never worked with Indonesian manufacturers often miss important local context — customs processes, freight forwarder landscape, cultural dynamics in factory relationships.) Do they have a fixed-scope, fixed-price engagement model? (Open-ended retainers tend to produce indefinite dependency. A consultant who can scope the work at the beginning and commit to a price is demonstrating that they understand what they're actually doing.) What happens when things don't go according to plan — and specifically, do they stay engaged through those problems?

The last question is important. Every implementation engagement encounters unexpected complications. The quality of a consultant is partly visible in how they handle those complications — whether they escalate and stay, or whether the scope suddenly seems to need extending on an hourly basis.

When You Don't Need a Consultant

Not every supply chain problem requires external help. If your team has the capability and bandwidth to implement the change themselves, and the problem is just one of diagnosis — figuring out what to do — an advisory engagement might be the right fit. If the problem is genuinely strategic rather than operational, a different kind of expertise may be more appropriate.

Where implementation consulting is clearly the right choice: when your team knows things are wrong but doesn't know how to fix them; when you've tried to fix something internally and it keeps not getting fixed; when the problem requires cross-functional system changes that nobody in your organisation has the authority to drive; when the cost of ongoing inefficiency significantly exceeds the cost of the engagement; and when you genuinely cannot afford to have this problem persist for another year while you figure it out internally.

In my experience, most mid-size Indonesian fashion brands with persistent operational or supply chain problems fall into one of those categories. The problem isn't usually a lack of intelligence or effort — it's a lack of time, bandwidth, or specific implementation expertise. That's what the right consultant should bring.

If you want to understand whether your specific problems are the kind that can be fixed with implementation support — and what that would look like — that's exactly what the free assessment is for. We'll be direct about whether we can help, what it would take, and what it would cost.