Skip to content
Interface language: English
Oriens / Signal

MRO in China: a procurement platform also sells a way to handle small needs

Explore how MRO platforms in China describe item identification, company catalogues, approvals and local service, then prepare a product for a procurement discussion.

Article language: English

A hand adjusts a brass-coloured mechanism beside a suspended drop and a pale sphere over a dark bowl.
In this article

A roll of tape was needed. After several messages, five people know it is missing, but none can say whether someone has already ordered it. The product itself does not attract management's attention. The way it is purchased has just started to occupy a whole small team.

In industrial procurement, these small needs can reveal a substantial part of an organisation. MRO covers materials and equipment that support the facility's day-to-day work. For a Polish supplier exploring China, the question is therefore not only where to display a product. It is also how a company chooses and orders that product, and what service surrounds it.

Consider a fictional facility with two workshops. Both order a consumable, but use different names for it. One enters the manufacturer's number; the other uses an internal abbreviation. We will examine platform models and questions to ask partners, without making a purchase or selecting a technical substitute. The same company may use several procurement methods for different needs.

A shop with many products is only the beginning

In its description of MRO solutions, EHSY (in Chinese) includes tools, equipment and other industrial goods that are not production raw materials. It also describes an online procurement model joining product selection, purchasing, payment and delivery. This is the company's account of its own scope, not a uniform definition of every facility's spending.

In our example, a worker needs a specified material for an agreed task. Before choosing a platform, establish how the worker identifies the right item. They may know the manufacturer's number or only the company's own designation. Sometimes a photograph of the old package is the only clue. Each case raises a different question about data quality and the help needed.

A catalogue can contain a great many entries and still fail to explain which one a particular workshop orders. A name resembling the one in a note is not enough to approve a substitute. In the research, record who is to confirm that compatibility. For a product requiring specialist assessment, do not move the decision onto the person operating the search field.

On China's 1688 channel, a starting point may be reading the variant and terms of a visible offer. The guide to prices and terms on 1688 (in Polish) explains how to read them. Here we are also interested in how an organisation makes a repeat purchase. The same person may search for a product on an open site or use a pool selected for the company. Both screens look like shops, but they need not support the same task.

Do not treat a platform's public offer as a list of products approved at any company. A facility may have its own catalogue and agreed terms. A product supplier, in turn, should establish what relationship would even allow a discussion about inclusion in that process. A visible contact form starts a conversation; it does not confirm that a brand has been accepted.

For the two workshops, record whether they use the same item or merely materials with similar names. A shared word may conceal different dimensions or order units. Identifying the data should preserve that distinction instead of immediately merging the records to tidy up a table. Orderliness that removes meaning soon presents its own bill.

A company catalogue has its own roles and decisions

ZKH's Webshop page (in Chinese), read on 30 October 2026, describes a personalised catalogue, separate permissions and configurable purchase approvals. It says searches can use, among other things, a manufacturer's material number and a catalogue item identifier, or SKU. These are one platform's stated functions. Its marketing figures for product counts, savings and delivery times are not results for our example.

In the fictional facility, a user selects an item but is not authorised to order every quantity independently. Someone else checks the need or the cost assigned to the workshop. The team examining the solution should describe these roles in its own words before fitting them to names in a platform presentation.

Show an ordinary case in which the item is known and one in which it is missing from the pool. Does the worker submit a requisition, send an enquiry or look for another channel? Do not fill in the answer merely because a search field exists. This concerns the service model for an exception, not just catalogue size.

Keep a requisition distinct from an order. The first record may still be reviewed or changed. If a report calls both states a purchase, the company loses the ability to identify where the matter actually stalled. It is useful to see what confirmation the person reporting the need receives and whether it tells them what happens next.

Approval does not necessarily answer every fulfilment question either. Someone approving the scope may not be confirming that goods are available. Your own scenario should name what has been agreed at each point. This allows proposals to be compared without assigning another party's commitments to a single button.

For a repeat purchase, ask how it relates to the previous item. Is it the same number, the same sales package and the same number of pieces? When a catalogue changes, a worker may recognise the name without noticing a different unit. Keep an example that reveals that discrepancy before comparing the convenience of two screens.

Suppose a workshop needs twenty rolls, while the listed item is ordered in boxes of ten. The need is described as twenty pieces and the proposal as two boxes. Both numbers can be correct if their units are retained. Do not combine them under a single "quantity" column. The same example helps explain an apparent discrepancy after handover: someone confirmed two packages, while the requester was waiting for twenty pieces. Platform research should establish which data and confirmations the offer covers before the company calls the case a delivery error or chooses another solution.

Aeneia conceptual photography

If the company wants to assign the expense to a workshop, establish where that information comes from and who checks it. Do not assume that the platform will reconstruct the company's internal structure from a delivery address. An address helps deliver an item; by itself it does not explain which team reported the need or which budget should cover it.

When organising company and CRM data (in Polish), the organisation, its branch and a particular relationship are distinguished. Similarly, retain the place of use, purchaser and recipient here if they differ. This is not an invitation to move arbitrary data between systems. First establish its meaning and the agreed scope needed for the discussion.

A choice on one site can return to the customer's system

EHSY's public description of EIS (in Chinese) distinguishes E-Mall from PunchOut. It presents the former as a company shop for customers without a connection to an ERP, a system for managing the enterprise. In the second model, the selection from the supplier's site returns to the customer's internal purchasing system for approval, and a formal order is then transmitted through the system connection. This reading covers the public description before login; we did not make such a purchase or test the connection.

The distinction helps identify the right question for the implementer. Where does the worker select the item, where is approval obtained and where is the formal order sent to the supplier? Your own process may differ from the marketing diagram. Relate the description to the tools and organisational rules actually used instead of treating a familiar name as a ready-made fit.

An example with invented data is enough to prepare for the conversation. Name the item, quantity, unit and place of use. Also show what happens after a refusal or a change of need. Do not send real access credentials to prove that a system exists. Assessing whether a connection is possible and implementing it are a separate agreed technical scope.

Our workshops may have different approval routes. In one, a requisition requires approval before searching for goods; in the other, approval follows a prepared proposal. We do not judge these rules by which has fewer arrows on a slide. We ask what decision they support and whether the solution's description actually accommodates the chosen process.

An urgent need deserves its own example too. Who recognises its urgency, and what can follow from that? It should not automatically bypass agreed rules simply because a worker marked it with an exclamation point. Research needs to establish whether the supplier describes a special service route and, if so, what limits of that route it can explain.

After the conversation, record which elements are the platform's standard offer and which need work for the company. The name of an existing feature does not automatically define what the customer must prepare. When comparing proposals, retain that contribution alongside the supplier's claims. Otherwise, two different tasks can easily be mistaken for the same product.

For a supplier, what surrounds the product matters too

A Polish consumables manufacturer can prepare a good product sheet and still not know who will reach for it when reordering. The manufacturer needs to identify the partner, the rules for presenting the item and the expected service scope. Simply counting products visible on a site will not answer all of that.

Choosing a distributor or direct sales in Asia (in Polish) separates the channel's tasks. In MRO, ask who answers product questions, who maintains catalogue data and who handles the facility's particular need. One organisation may do several of these jobs. Confirm its own scope instead of assembling it from claims made by several different parties.

Prepare product material so that a partner can identify the right variant without guessing. Manufacturer name, designation, sales unit and information needed for the stated application should form a coherent whole. When data is missing, name the question. A description found beside a similar item does not automatically complete your documentation.

The example of Chinese aluminium profiles (in Polish) shows why the cross-section itself should be distinguished from a product prepared for further work. Procurement also needs a clear boundary around the item. Is the purchase for material, a prepared component or a set with an additional service? This affects whom to speak to and what materials are needed for a comparison.

Check whether the proposed model also suits the facility in our scenario. A broad catalogue and approval tools may make sense for recurring procurement, but do not yet explain how an unusual one-off need will be handled. Choose a channel for the work it needs to make easier, instead of sending every purchase to it automatically.

For warehouse robots from China (in Polish), describing the unit carried helps explain the solution's scope. MRO poses an earlier question: how did the company identify and order the item that must reach the right place? A procurement platform and internal logistics can meet, but neither description substitutes for the other.

Finish the research with material that can be handed to the person responsible for the next decision. Mark the platform model, a potential partner's role and questions that remain unanswered. If it is not known who will confirm the variant or handle an exception, keep that gap visible. A useful report need not pretend that purchasing is fully ready.

At Aeneia Oriens, we can examine local sources and procurement models for a particular product and the customer's way of working. This helps frame discussions with relevant parties around a defined scope. Tape will remain a small purchase. At last, however, it will be clear who is handling it and what stage it has reached.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear