Two equipment offers can name similar physical components while covering different amounts of preparation and support. A goods invoice alone will not tell a buyer whether software configuration, project-specific documentation or coordination work is included. Those activities may sit inside the product price without appearing as separate items.

A September 7 UNCTAD publication examines servicification: the role of services as inputs in production, including manufacturing. For a buyer comparing suppliers, the useful implication is not that every service deserves an extra invoice. It is that the physical item and the work required to deliver it are different things to examine.

Ask what the product price includes

An engineering or configuration activity can contribute to a manufactured product without being sold as a standalone service. Whether the supplier performs it internally or buys it from another provider affects where the expense appears. It does not determine whether the activity exists.

This matters when an offer uses a broad expression such as technical support. One supplier may mean standard product documentation. Another may include a defined configuration task. Neither phrase tells the buyer enough until the expected work is described.

The practical comparison is therefore between scopes, not simply between the number of service lines on the quotation. An offer with no separate service fee may still include substantial work. An offer with several fees may describe work already covered elsewhere. More line items do not, by themselves, make the offer more complete or transparent.

Ask which documents will be supplied, what configuration is included and how additional changes will be handled. These questions produce a clearer comparison than asking a supplier to split every internal activity into a separate price.

Embedded work is different from an additional service

There is a legitimate difference between work promised in the original offer and work requested later. A configuration that the supplier already agreed to provide should not become a new fee simply because someone has now recognized it as a service input.

Equally, a later request for a different interface or a project-specific adaptation should not automatically disappear into unlimited support. The relevant distinction is the agreed scope and the work being requested, not whether the result can be packed in a shipping carton.

For suppliers considering how to describe a service offer, this is an important prior step. Identifying service inputs is not the same as finding new services to sell. The first exercise explains how an existing delivery is produced; the second asks whether a separately defined offer has value for a buyer.

Keeping those exercises apart also avoids an unhelpful discussion in which the supplier lists every effort it has made and the buyer assumes every item is an unexpected charge. Explain what is included before discussing what lies outside it.

Trace one product family before drawing broad conclusions

A supplier can begin with a familiar product family and distinguish recurring work from order-specific work. A standard manual may support many sales. A document explaining a particular buyer's interface may belong to one project. Calling both technical support hides that difference.

Some activities happen once for an order; others grow with the number of units or the number of requested changes. Recognizing the pattern helps explain why orders that look similar on a goods list may need different preparation. It does not require a universal surcharge or a complex pricing model.

Purchased services need similar care. Outsourcing part of a design task may leave internal review and revision work in place. Looking only at the external invoice misses that remaining effort. Counting the entire task both internally and externally introduces the opposite problem. Describe who actually did which part before comparing totals.

For a Chinese exporter, this modest exercise can make quotation discussions more precise. It gives the team a way to explain the scope behind the product price without turning an internal cost map into a customer-facing bill.

Make the offer clearer, not longer

Buyers generally need to understand what they will receive and which requests require a separate agreement. They do not need a full account of every activity inside the factory. A single product price can remain appropriate when its scope is clearly stated.

The UNCTAD publication concerns measurement and analysis. It does not establish a service-cost percentage for an individual supplier or show that adding service fees will improve that supplier's profit. Company-level decisions still need evidence about the actual work.

A useful next quotation can therefore remain short: identify the included deliverables, describe the relevant limits, and explain how changes are agreed. That makes the hidden work easier to discuss while leaving the commercial choice—bundled price or separate service offer—where it belongs, with the parties defining the transaction.

Sources