OEM / private label · Multi-factory sourcing · Export project coordination
sales@moxasourcing.comCall UsChat on WhatsApp

Map a mugwort supply route: activities, entities and flows

Three views of a proposed supply route: physical flow, information flow and commercial links.
Original explanatory diagram; read the distinctions separately.

Activities, entities and roles

Begin with the route for one proposed product configuration, rather than the supplier’s entire catalogue. A route map answers which activities are needed, which organizations perform them, where work moves between them and which information connects the steps. UNIDO’s published value-chain method separates an initial structural map from later quantification and recognizes that several connected maps may communicate the chain more clearly than one crowded diagram. For a purchasing project, this means understanding the proposed arrangement before attaching capacity numbers or assuming that all displayed products come from one site.

Separate an activity from an organization. Mixing, filling, decorating a bottle and assembling a gift set are activities; an organization might perform several, or several organizations might share them. The diagram should therefore identify an activity first and attach the proposed performing entity and location as separate fields. A box labelled only with a city or a sales brand conceals this distinction. If the counterparty has not identified the operator, leave the operator field open. A nearby industrial cluster is a place to investigate a route, not the missing operator’s identity.

Next distinguish a seller, an owner of goods and a provider of processing services. UNIDO’s mapping questions explicitly distinguish product owners from businesses carrying out outsourced operations. Applied to a buyer’s file, a filling workshop should not automatically be labelled as the seller of the finished product, and the company issuing a quotation should not automatically be labelled as the owner of every machine involved. Record the role stated in the proposed arrangement and the document that supports it. The map does not itself decide legal ownership, risk transfer or contractual liability; those points need their appropriate agreements and responsible reviewers.

Three connected route views

Build a physical-flow view that follows the selected configuration through its main activities. In a hypothetical liquid-product project, bulk preparation, bottle supply, filling, decoration and set assembly might be separate activities. They could be performed at one location or at several; neither arrangement should be assumed from a catalogue photograph. Show the actual proposed handoff between activities and distinguish movement of components from movement of finished goods. If the supplier proposes a different assembly route for a second pack size, show that branch rather than silently applying the first map to both versions.

Keep the information-flow view separate enough to expose missing handoffs. Identify who supplies the configuration details to the next operator, who communicates an approved change and who receives an unresolved question. For example, an assembly provider may need the agreed pack configuration without receiving the buyer’s confidential formula. The authorized technical reviewer may need formula information that does not belong in a public route diagram. This view is concerned with the right information reaching the right role; it does not replace the detailed sample, specification or inspection records maintained for the product.

A third view can identify commercial relationships without displaying confidential amounts. Record which proposed entity quotes to the buyer, which party coordinates another operator and which link is still a proposed introduction rather than an established arrangement. Keep the original offers and exact identities in the authorized private file. A public illustration can show own reference codes and neutral role labels. Do not infer that a payment link proves manufacturing control, or that a supplier’s introduction establishes an exclusive relationship. Where a relationship remains unconfirmed, make the open link explicit in the working map.

Evidence and changes

Use different evidence states for different links. An operator named in a proposal, an operator supported by current project documents and an activity actually observed are different states. A useful map connects each significant statement to a source, date and owner of the next verification action. This is an editorial application of the source’s iterative mapping process, not a universal audit certification scheme. Do not fill empty links simply to make the diagram symmetrical. An incomplete but correctly labelled map is more useful for allocating the next question than a complete-looking diagram assembled from assumptions.

Review the map against the purchasing decision it is meant to support. If the buyer is choosing between a single-site route and coordinated specialists, identify which activity or interface differs and what evidence is still needed to compare them. Avoid scoring the number of boxes as a measure of quality. More operators can create additional interfaces; fewer named operators can conceal outsourced work. The relevant question is whether the proposed route is sufficiently identified and coordinated for the selected brief, with remaining questions assigned before the affected commitment.

Quantify only after the structure is clear, and only with values whose scope is known. A regional production figure cannot populate a selected operator’s capacity field. A company-wide output statement cannot automatically populate the capacity of a particular filling or assembly operation. Record whether a number describes a site, process, product family or proposed order, together with its date and source. Where comparable quantities are unavailable, compare the identified activities and unresolved evidence first. The purpose of the map is to expose what must be learned, not to manufacture numerical certainty.

Treat the map as a versioned project record. Revisit the affected link when the proposed operator, location, processing step, component route or assembly arrangement changes. Preserve the earlier version so that a later reader can distinguish the original proposal from the route subsequently agreed. Ask the relevant participants to correct the parts they know, while retaining differences that have not been resolved. A route diagram is ready to support the next decision when its roles, interfaces and open questions are understandable; it does not become proof of completed production merely because the drawing is tidy.

FAQ

Is an activity the same as a company?

Separate an activity from an organization. Mixing, filling, decorating a bottle and assembling a gift set are activities; an organization might perform several, or several organizations might share them. The diagram should therefore identify an activity first and attach the proposed performing entity and location as separate fields. A box labelled only with a city or a sales brand conceals this distinction. If the counterparty has not identified the operator, leave the operator field open. A nearby industrial cluster is a place to investigate a route, not the missing operator’s identity.

Does a route map determine legal ownership?

Next distinguish a seller, an owner of goods and a provider of processing services. UNIDO’s mapping questions explicitly distinguish product owners from businesses carrying out outsourced operations. Applied to a buyer’s file, a filling workshop should not automatically be labelled as the seller of the finished product, and the company issuing a quotation should not automatically be labelled as the owner of every machine involved. Record the role stated in the proposed arrangement and the document that supports it. The map does not itself decide legal ownership, risk transfer or contractual liability; those points need their appropriate agreements and responsible reviewers.

Sources and scope

UNIDO: Agro-Value Chain Analysis and Development (2009) — section 2.2, printed pages 16–20. Buyer-oriented editorial adaptation of the published mapping method. Product and coordination examples are hypothetical; they do not describe inspected suppliers or completed Moxa projects.

Chat on WhatsApp+852 5725 4301