The cost curve that flips: why remote service fails at scale

For a Chinese robotics manufacturer entering Europe, the decision to invest in a local service network is often framed as a strategic choice. But it is really a math problem. As the installed base grows, the cost of serving it from afar escalates non-linearly, while the cost of a local presence scales more gently. At some point, the two curves cross. That crossing point is the breakeven moment when local stops being optional.

Consider the typical service model for a manufacturer without a local footprint. Every intervention requires either dispatching a technician from China or relying on a third-party contractor. Both options carry hidden costs that grow with the number of machines in the field. The remote model appears cheap at first—no office, no warehouse, no salaries. But each incident incurs travel, logistics, and coordination overhead. As the installed base grows, the frequency of incidents grows, and the cost per incident often rises too, because the technician’s travel time increases as machines are spread across more locations.

In contrast, a local service network—with a spare parts hub and certified technicians—requires upfront investment and fixed operating costs. But the marginal cost of each intervention is lower, and response times are shorter, which can reduce downtime and improve customer satisfaction. The trade-off is not just about cost; it is about capability and reputation.

The anatomy of service costs

To understand the breakeven, we must break down the cost drivers. The main categories are:

• Spare parts logistics: warehousing, inventory holding, shipping, customs clearance, and last-mile delivery.
• Technician deployment: travel time, travel expenses, labor hours, and opportunity cost of idle time.
• Remote support: helpdesk, diagnostics, software updates, and remote troubleshooting tools.
• Coordination and administration: case management, scheduling, invoicing, and compliance reporting.
• Training and certification: initial and ongoing training for local technicians, plus certification fees.
• Quality and compliance: adherence to local regulations, safety standards, and documentation.

In a remote model, many of these costs are variable and escalate with each incident. In a local model, some become fixed (warehouse rent, salaries) while others remain variable but at a lower per-unit rate.

Comparing remote vs. local: a decision table

The table below summarizes the typical cost behavior for each model. The figures are illustrative and will vary by country, machine type, and service contract, but they highlight the structural differences.

This table is a simplification. Real numbers depend on the country, the machine’s reliability, and the service level agreements. But the pattern is consistent: remote service has low fixed costs and high variable costs; local service has high fixed costs and low variable costs.

When does local become cheaper?

The breakeven point is where the total cost of remote service equals the total cost of local service. It depends on the number of machines installed, the failure rate, and the cost per intervention. For a small installed base (say, a few dozen machines), remote service may be cheaper. But as the base grows to hundreds or thousands, the remote model becomes unsustainable.

Consider a scenario where a manufacturer has 100 machines in Europe, each requiring an average of two interventions per year. If each remote intervention costs €5,000 (including travel and logistics), the annual service cost is €1 million. A local network might require an initial investment of €500,000 for a parts hub and technician hiring, plus €300,000 per year in fixed costs, and €1,000 per intervention. For 200 interventions, the local cost is €500,000 + €300,000 + €200,000 = €1 million. That is the breakeven. Beyond that, local is cheaper.

But the breakeven is not just about cost. It is also about revenue. If machines are down for weeks, customers may cancel contracts or switch to competitors. Local service can reduce downtime from weeks to days, which has a direct impact on customer retention and brand reputation.

Why remote service costs escalate

Remote service costs escalate for several reasons:

• Travel time: As the installed base spreads across Europe, a technician from China may need to fly to multiple countries in one trip, but each visit still requires a full day of travel. The cost per intervention rises with distance and frequency.
• Emergency logistics: When a machine fails, the customer expects a quick fix. Shipping a spare part from China by air freight is expensive, and customs clearance can add days. The cost of expedited shipping is often 5-10 times that of standard shipping.
• Coordination complexity: Managing service requests across time zones and languages requires dedicated staff. Miscommunication can lead to repeat visits, increasing costs.
• Compliance burden: Each EU country has its own regulations for machinery safety, electrical compliance, and environmental standards. A remote team may not be aware of local nuances, leading to fines or rework.

These factors make the remote model increasingly inefficient as the installed base grows. The cost per intervention does not stay constant; it tends to rise.

The case for a local network

A local service network addresses these issues by placing spare parts and technicians close to the customer. The benefits are not just cost savings but also:

• Faster response times: Local technicians can often be on-site within 24 hours, reducing downtime.
• Better spare parts availability: A local hub can stock critical parts, eliminating air freight delays.
• Local expertise: Technicians who understand local regulations and customer expectations can provide more effective service.
• Improved customer trust: Knowing that a service team is nearby gives customers confidence in the product.

However, building a local network is not trivial. It requires finding qualified technicians, setting up a parts hub, and navigating local employment laws. The initial investment can be significant, and it may take months to become operational.

What varies by country

The breakeven point varies by country due to differences in labor costs, logistics infrastructure, and regulatory requirements. For example, in Germany, labor costs are high, but the logistics network is excellent, which may reduce the cost of a local hub. In Eastern Europe, labor is cheaper, but infrastructure may be less developed, increasing logistics costs. The manufacturer must analyze each market separately.

It is also important to verify the actual costs in each country. The figures in this article are illustrative and should not be used for budgeting. A detailed cost model should include local salaries, rental rates, and shipping quotes.

Strategic implications for Chinese manufacturers

For Chinese robotics manufacturers, the decision to invest in a local service network is a strategic one. It signals a long-term commitment to the European market, which can be a differentiator in a competitive landscape. But it also requires capital and management attention.

One option is to partner with a local service network being set up, such as Robanchor, which aims to provide after-sales, maintenance, spare parts, and compliance services for Chinese manufacturers. By outsourcing to a certified technician network being assembled, manufacturers can achieve local presence without the full burden of setting up their own entity. This can lower the breakeven point and reduce risk.

However, manufacturers must carefully evaluate the cost and quality of such partnerships. They should also consider the long-term evolution of their installed base and service demand.

Conclusion

The math is clear: as the installed base grows, the cost of remote service escalates, and local service becomes not just cheaper but essential. The breakeven point varies, but it is a threshold that every manufacturer will eventually cross. The question is not whether to go local, but when and how. By understanding the cost drivers and planning ahead, manufacturers can make a smooth transition and turn service from a cost center into a competitive advantage.

Sources

• IndexBox — machinery services — https://www.indexbox.io/ (accessed 2025-11-04)
• IDC — Robotics market — https://www.idc.com/ (accessed 2025-11-04)

Why SLA design is the hidden battleground of robot after-sales

When a Chinese robotics manufacturer signs its first European distribution deal, the conversation quickly turns from unit price to service-level agreements (SLAs). Buyers in Germany, France, or the Netherlands rarely ask about the robot’s payload or cycle time first; they ask: ‘If it breaks, how fast will you respond, and how fast will it run again?’ The answer determines whether the robot is adopted or shelved. Yet most manufacturers treat SLAs as a sales afterthought, copying a template from a competitor or a domestic contract. That is a costly mistake. In Europe, service expectations are not just higher—they are contractual, and they vary sharply by country and industry.

This article explains the core SLA metrics for robot after-sales—response time, time-to-repair, first-time fix rate, and parts availability—and why buyers negotiate them so hard. It also outlines what it actually costs to deliver each tier of service, based on the operational realities of running a service network across Europe. The goal is not to prescribe a one-size-fits-all SLA, but to give manufacturers and service providers a framework for designing SLAs that are both competitive and deliverable.

The four metrics that define robot service quality

SLAs for industrial robots typically revolve around four metrics. Each one addresses a different pain point for the buyer, and each has a distinct cost driver for the service provider.

1. Response time

Response time is the time between the buyer logging a fault and the service provider acknowledging it and starting to work on it. It is often split into two parts: the time to acknowledge the ticket (e.g., within 1 hour) and the time to dispatch a technician or provide remote support (e.g., within 4 hours). Buyers care about response time because it signals how seriously the provider takes their downtime. A slow response can mean hours of lost production even before a technician arrives.

But response time is cheap to promise and expensive to deliver. A call centre can acknowledge a ticket in minutes, but dispatching a technician within 4 hours requires having technicians on call or stationed near the customer. In rural areas, that may be impossible. So response time is often the first metric buyers use to filter providers, but it is not the most important one.

2. Time-to-repair (TTR)

Time-to-repair is the total time from fault report to the robot being back in production. It includes response time, travel time, diagnosis, parts replacement, and testing. TTR is the metric that directly impacts the buyer’s production loss, so it is the one they negotiate hardest. A typical SLA might promise TTR of 8 business hours for a critical breakdown, or 24 hours for a non-critical one. Some buyers demand 4-hour TTR for high-value production lines.

TTR is the most expensive metric to deliver because it depends on many variables: technician availability, travel distance, parts inventory, and the complexity of the fault. A provider can improve TTR by pre-positioning technicians and parts near key customers, but that costs money. It also requires a deep understanding of the robot’s failure modes—something that a new entrant may not have.

3. First-time fix rate (FTFR)

First-time fix rate is the percentage of service calls that are resolved on the first visit, without needing a second trip or a follow-up part. A high FTFR (e.g., 90% or above) means the technician arrives with the right parts and the right knowledge. Buyers value FTFR because a failed first visit doubles the downtime and erodes trust. For the provider, FTFR is a measure of diagnostic accuracy and parts logistics.

Improving FTFR requires investment in training, diagnostic tools, and parts stocking. It also requires a feedback loop between service engineers and the manufacturer’s design team to address recurring issues. For a new service network, achieving a high FTFR is tough because it takes time to build a knowledge base and a parts inventory.

4. Parts availability

Parts availability is the percentage of spare parts that are in stock and can be shipped immediately. It is often expressed as a target, such as 95% of parts available within 24 hours. Buyers care about parts availability because a robot can be down for days if a critical part is not in stock. For the provider, parts availability is a balancing act: too little inventory means longer TTR and lower FTFR; too much inventory ties up capital and risks obsolescence.

Parts availability is particularly challenging for Chinese manufacturers entering Europe because they need to stock parts in multiple countries, each with different import regulations and tax regimes. A central warehouse in, say, the Netherlands can serve much of Western Europe within 24 hours, but Southern or Eastern Europe may need regional hubs.

Why buyers negotiate these metrics so hard

Buyers negotiate SLAs because downtime is expensive. In automotive or electronics manufacturing, a single robot failure can halt an entire line, costing thousands of euros per hour. Buyers use SLAs to transfer some of that risk to the service provider. They also use SLAs to compare providers on a level playing field. A provider that promises a 4-hour response but a 48-hour TTR is less attractive than one that promises a 24-hour TTR, even if the response is slower.

Moreover, European buyers are used to strict contractual terms. In Germany, for example, service contracts often include penalty clauses for missed SLAs—a discount on the service fee or a credit for each hour of overrun. In France, buyers may require a ‘service guarantee’ that includes a temporary replacement robot if the repair takes too long. These clauses are not just legal formalities; they are a way to ensure the provider has skin in the game.

But buyers also know that aggressive SLAs cost money. A provider that promises 4-hour TTR will charge a premium, because it has to maintain a local technician and parts stock. Buyers must decide whether the premium is worth the reduced downtime risk. This is where the negotiation becomes a trade-off between cost and operational security.

What it costs to deliver each SLA tier

The cost of delivering an SLA depends on the tier of service. Below is a comparison table that outlines typical SLA tiers, their operational requirements, and the relative cost impact. The figures are indicative and vary by country, robot type, and customer density.

These tiers are illustrative. The actual cost depends on the density of the customer base. In a country like Germany, where many robot installations are concentrated in industrial clusters, a Silver tier may be achievable at a lower cost than in, say, Spain, where distances are larger. Similarly, a robot that is used in a continuous process (e.g., food and beverage) may require a higher tier than one used in a batch process (e.g., warehousing).

The hidden costs of SLA delivery

Beyond the obvious costs of technicians and parts, there are several hidden costs that can derail an SLA budget:

• Training and certification: European regulations and customer requirements often demand certified technicians. Training a technician on a specific robot model can take weeks and cost thousands of euros. For a new network, this is a significant upfront investment.
• Diagnostic tools and software: Remote diagnostics require secure access to the robot’s control system, which may involve VPNs, cybersecurity compliance, and software licences. These are ongoing costs.
• Parts obsolescence: Robots evolve, and older models may need parts that are no longer manufactured. Providers must either stock them in advance or risk long lead times. This is a particular challenge for Chinese manufacturers that update models frequently.
• Penalty clauses: If an SLA includes penalties for missed targets, the provider must price in the risk. A single missed TTR could wipe out the profit on a contract.
• Country-specific compliance: Each European country has its own rules for service work, including health and safety, data protection, and waste disposal. Compliance adds administrative overhead.

How to design an SLA that is both competitive and deliverable

Given these costs, how should a manufacturer or service provider approach SLA design? Here are some practical steps:

1. Segment your customers: Not every customer needs a Platinum SLA. A small workshop that uses a robot intermittently may be happy with a Bronze tier, while an automotive plant needs Gold. Offer a menu of tiers and let customers choose.
2. Base SLAs on data: If you have historical data on failure rates and repair times, use it to set realistic targets. If you don’t, start with conservative targets and tighten them as you gain experience.
3. Build a partner network: Instead of hiring technicians in every country, partner with local service companies that already have the infrastructure. This is where a local service network like the one being set up by Robanchor can add value—by aggregating demand and coordinating certified technicians across borders.
4. Invest in remote diagnostics: Many faults can be resolved remotely, reducing the need for on-site visits. This can dramatically lower TTR and cost.
5. Stock parts strategically: Use a central warehouse for slow-moving parts and regional hubs for fast-moving ones. Consider drop-shipping from the manufacturer for rare parts.
6. Be transparent about limitations: If you cannot guarantee a 4-hour response in rural Portugal, say so. Honesty builds trust and avoids penalties later.

The role of a local service network

For Chinese robotics manufacturers, building a European service network from scratch is daunting. That is where a local service network being set up—like Robanchor—can help. By aggregating demand from multiple manufacturers, such a network can achieve the scale needed to justify local technicians and parts inventory. It can also provide a single point of contact for customers, simplifying the SLA process. However, it is important to note that Robanchor is not yet a registered entity; it is a concept in development. Manufacturers should verify the legal and operational status of any service partner before signing contracts.

Conclusion

Designing SLAs for robot service is not a paperwork exercise. It is a strategic decision that affects customer trust, operational costs, and the viability of entering the European market. The four metrics—response time, time-to-repair, first-time fix rate, and parts availability—are the levers that buyers pull to control their downtime risk. Each metric has a cost, and the trade-offs are real. By understanding these costs and designing SLAs that are both competitive and deliverable, manufacturers can turn after-sales from a liability into a differentiator.

Sources

• IDC — Robotics market — https://www.idc.com/ (accessed 2025-10-30)
• IndexBox — machinery services — https://www.indexbox.io/ (accessed 2025-10-30)

Warranty versus service contracts: where the real after-sales revenue is

For Chinese robotics manufacturers entering Europe, the after-sales landscape is often misunderstood. Many assume that the legal guarantee, the commercial warranty, and paid service contracts are interchangeable terms for the same thing. They are not. Each has a distinct legal basis, cost profile, and revenue potential. Getting this wrong can turn after-sales into a pure cost centre, while getting it right can create a recurring revenue stream that rivals the initial sale.

The legal guarantee: a statutory cost centre

Under EU Directive 2019/771, every consumer in the EU has a legal guarantee of at least two years from the date of delivery. This is not a marketing tool; it is a statutory right that cannot be waived or limited. The seller is liable for any lack of conformity that becomes apparent within this period, and the consumer can request repair, replacement, price reduction, or a full refund. For a robotics manufacturer, this means that for two years after every sale, you are on the hook for defects that existed at delivery, regardless of what your commercial warranty says.

This legal guarantee is a cost centre. It is an obligation, not a revenue opportunity. You cannot charge for it, and you cannot opt out of it. The only way to mitigate the cost is to build quality products and have an efficient repair process. But even then, the legal guarantee is a baseline liability that every manufacturer must absorb.

Commercial warranty: a differentiator, but still a cost

Beyond the legal guarantee, many manufacturers offer a commercial warranty. This is a voluntary commitment that goes above and beyond the statutory minimum. For example, you might offer a three-year warranty on the robot arm, or cover parts that are excluded from the legal guarantee, such as batteries or wear items. A commercial warranty can be a powerful marketing tool, especially in a B2B context where buyers are making large capital investments.

But a commercial warranty is still a cost centre. It is an extension of your liability, and you must price it into the product or absorb it as a marketing expense. The key difference from the legal guarantee is that you have control over the terms. You can define what is covered, what is excluded, and how claims are handled. This allows you to manage risk, but it does not generate revenue. In fact, if you offer a longer warranty than your competitors, you are increasing your costs, not your income.

Service contracts: the revenue engine

Paid service contracts are where the real after-sales revenue lies. Unlike guarantees and warranties, service contracts are not about liability; they are about proactive maintenance, priority support, and guaranteed uptime. A typical service contract might include scheduled inspections, preventive maintenance, software updates, and a guaranteed response time for breakdowns. These are services that the customer pays for separately, either as an upfront fee or as an annual subscription.

Service contracts are a revenue stream because they are priced and sold as a product in their own right. They also have a higher profit margin than hardware sales, because the cost of delivering a service is often lower than the cost of manufacturing a robot. Moreover, service contracts create a recurring revenue model that smooths out the peaks and troughs of hardware sales. A customer who buys a robot once might never buy again, but a customer who signs a five-year service contract is a predictable source of income.

The Right to Repair shifts the economics

The EU’s Right to Repair movement, which is gaining momentum, is changing the after-sales landscape. The directive on common rules promoting the repair of goods (Directive (EU) 2024/1799) requires manufacturers to offer repairs for a longer period and to make spare parts available for up to 10 years for certain products. This means that the legal guarantee period is no longer the only time you must support your product. You will be required to have spare parts and repair capabilities for many years after the sale.

This shift has two implications. First, it increases the cost of compliance, because you must maintain a stock of spare parts and a repair network for longer. Second, it creates an opportunity for service contracts. If customers are entitled to repairs, they will need someone to perform those repairs. A paid service contract can bundle the repair service with preventive maintenance, making it easier for the customer to manage and for you to monetize.

In other words, the Right to Repair turns the legal guarantee from a simple cost centre into a gateway for service revenue. By offering a service contract that covers the entire lifecycle of the product, you can turn a regulatory burden into a business opportunity.

Comparison table: guarantee vs warranty vs service contract

Practical implications for Chinese manufacturers

For a Chinese robotics manufacturer entering Europe, the first step is to understand the legal guarantee requirements in each country. While the EU directive sets a minimum of two years, some member states have longer periods. For example, in some countries, the legal guarantee for B2B transactions may differ. It is essential to verify local rules, as the directive applies to consumers, but B2B sales may be governed by different laws.

Second, design your commercial warranty strategy carefully. A longer warranty can be a competitive advantage, but it must be priced into the product. Be transparent about what is covered and what is not, and ensure that your warranty terms comply with local regulations. Remember that the legal guarantee cannot be overridden by a commercial warranty; you can only add to it, not subtract from it.

Third, build a service contract offering from day one. Even if your initial focus is on hardware sales, having a service contract ready to offer will help you capture recurring revenue. Consider partnering with a local service network, such as a certified technician network being assembled, to provide on-site repairs and maintenance across Europe. This can reduce your capital expenditure while ensuring that customers get timely service.

Finally, keep an eye on the evolving Right to Repair legislation. As of 2026, the new directive is being implemented, and it will require you to provide spare parts for up to 10 years for certain products. This is a long-term commitment that you must plan for. But it also means that customers will expect your product to be repairable, and they will be willing to pay for that repairability through service contracts.

Conclusion

The after-sales market in Europe is not a monolithic cost to be minimized. It is a layered system where the legal guarantee is a mandatory cost, the commercial warranty is a strategic cost, and service contracts are a revenue opportunity. By understanding the differences and aligning your business model accordingly, you can turn after-sales from a burden into a profit centre. The key is to treat service contracts as a product, not an afterthought, and to build the capabilities to deliver them efficiently.

Sources

• Your Europe — consumer guarantees — https://europa.eu/youreurope (accessed 2025-10-25)
• European Commission — Consumer rights — https://commission.europa.eu/ (accessed 2025-10-25)

The ‘reasonable price’ obligation is a legal blank check

Directive (EU) 2024/1799, the EU’s Right to Repair directive, requires manufacturers to offer spare parts at a ‘reasonable price’ for products covered by ecodesign rules. But the directive does not define ‘reasonable’. It leaves the term open to interpretation, creating a compliance grey zone that is already causing headaches for manufacturers and service providers entering the European market. For a Chinese robotics manufacturer setting up after-sales operations in Europe, the practical question is not whether to comply, but how to price parts in a way that satisfies regulators, wins customer trust, and avoids disputes that can escalate into legal or reputational damage.

The directive, adopted in 2024, mandates that spare parts be available for at least 10 years after the last unit of a model is placed on the market, and that they be supplied at a ‘reasonable price’ that does not deter repair. The European Commission’s guidance on repair pricing transparency (available on its website) emphasises that consumers should be able to obtain repair services without excessive cost. Yet neither the directive nor the guidance provides a formula or benchmark. This ambiguity is not an oversight; it is a deliberate flexibility that allows member states to interpret the term within their own legal traditions. But for a manufacturer, this means that a price considered reasonable in Germany might be challenged in Poland, and what is acceptable for a consumer drone may be unreasonable for an industrial robot.

What ‘reasonable’ means in practice: cost-plus, market parity, or something else?

In the absence of a statutory definition, manufacturers and service networks typically adopt one of three pricing strategies:

• Cost-plus pricing: Adding a fixed margin to the manufacturing cost of the part. This is transparent but can be distorted by allocation of overheads, and it may not reflect market value.
• Market-parity pricing: Setting prices in line with comparable parts from other manufacturers or independent suppliers. This requires continuous market monitoring and can be difficult for proprietary parts.
• Value-based pricing: Charging what the market will bear, often justified by the part’s criticality or the cost of downtime. This is the most opaque and the most likely to be challenged as ‘unreasonable’.

Each approach has merits, but the directive’s intent is clear: the price must not deter repair. A part that costs €500 to manufacture but is priced at €2,000 because the robot is down and the customer has no alternative is likely to be seen as unreasonable. Conversely, a part priced below cost might be seen as anti-competitive or as a loss-leader that undermines independent repairers. The ‘reasonable price’ is therefore not a single number but a range that depends on the product category, the part’s complexity, and the competitive landscape.

Opaque pricing creates compliance and trust risks

When manufacturers keep spare parts pricing opaque, they expose themselves to several risks:

• Regulatory risk: National enforcement authorities may investigate complaints about excessive prices, leading to fines or mandatory price reductions. The directive requires member states to establish penalties for non-compliance, and these can be substantial.
• Litigation risk: Consumers or business customers may sue for breach of the directive, especially if the price forces them to scrap a product. Class actions are rare in Europe but not impossible.
• Reputational risk: In an era of social media, a single viral complaint about a €1,000 spare part for a €2,000 robot can damage a brand’s image across the EU.
• Operational risk: Opaque pricing complicates the work of service networks, which need to quote prices quickly. If a technician cannot explain why a part costs what it does, customer trust erodes.

Transparent pricing, on the other hand, builds trust and reduces friction. It also aligns with the directive’s spirit and with the Commission’s push for repair-friendly business models. A manufacturer that publishes a clear price list, with justifications for high-value parts, is less likely to face complaints and more likely to be seen as a responsible market player.

Comparison: opaque vs transparent parts pricing

Practical steps for manufacturers and service networks

For a Chinese robotics manufacturer entering Europe, the ‘reasonable price’ problem is not just a legal issue; it is a business strategy issue. Here are concrete steps to mitigate risk:

1. Conduct a pricing audit: For each spare part, calculate the true cost (materials, labour, logistics, customs) and compare it with market benchmarks. Identify parts where your price exceeds a 100% margin, as these are the most vulnerable to challenge.
2. Publish a price list: Make the list available on your website and to your service network. Update it regularly. This transparency is a strong defence against claims of unfair pricing.
3. Document the rationale: For parts with high prices, prepare a brief justification (e.g., low volume, complex manufacturing, long shelf life). This documentation can be shared with regulators if needed.
4. Offer tiered pricing: For business customers, consider volume discounts or service contracts that include parts. This can make high prices more palatable.
5. Monitor national interpretations: Since the directive is transposed into national law, each member state may define ‘reasonable’ differently. Work with local legal counsel to stay compliant in each market.
6. Leverage a local service network: A certified technician network being assembled in Europe can provide on-the-ground feedback about price sensitivity and help you adjust pricing before problems escalate.

The role of a local service network

For a manufacturer without a European footprint, navigating the ‘reasonable price’ requirement is daunting. A local service network, such as the one being set up by Robanchor, can act as an intermediary. It can help you understand local market expectations, benchmark your prices against competitors, and handle customer complaints before they reach regulators. By partnering with such a network, you gain not only compliance expertise but also a reputation for being a responsive and responsible player in the EU market.

However, it is important to note that Robanchor is not yet a registered entity; it is a local service network being set up. Any claims about its capabilities should be verified. But the concept is sound: a network of certified technicians who understand both the technical and commercial aspects of spare parts can be invaluable.

Conclusion

The ‘reasonable price’ problem is not a puzzle with a single solution. It is a balancing act between profitability and fairness, between legal compliance and customer satisfaction. The directive gives manufacturers flexibility, but with that flexibility comes responsibility. Those who embrace transparency, document their pricing logic, and adapt to national interpretations will thrive. Those who rely on opacity will face regulatory scrutiny, customer backlash, and ultimately a weaker position in the European market. The time to act is now, before the first complaint lands on a regulator’s desk.

Sources

• EUR-Lex — Directive (EU) 2024/1799 — https://eur-lex.europa.eu/eli/dir/2024/1799/oj (accessed 2025-10-20)
• European Commission — Repair of goods — https://commission.europa.eu/ (accessed 2025-10-20)

The hidden ledger of fly-in service

When a Chinese robotics manufacturer receives a service call from a European customer, the default reflex is often to book a flight for a technician from the home base. The logic seems simple: the engineer knows the product, speaks the language of the factory, and the ticket price appears manageable. But the true cost of that single dispatch is a ledger with many lines, and most of them are never written down. This article breaks down the real economics of fly-in service versus a local technician network, using only the categories that any service manager can verify in their own operations.

The visible costs: travel, visa, and per diem

The most obvious line items are travel and accommodation. A round-trip economy ticket from Shanghai to Frankfurt costs around €800–€1,200, depending on booking time and season. Add a hotel for the expected duration—often three to five nights—at €100–€150 per night, plus meals and local transport. That already lands at €1,500–€2,500 per visit. But this is just the tip.

Visa processing is another cost that is frequently underestimated. For Chinese nationals, a Schengen visa requires an appointment, documentation, and often a service fee. The process can take two to four weeks, and if the visa is denied or delayed, the entire service schedule slips. In urgent breakdowns, this delay can be catastrophic for the customer’s production line.

The invisible costs: downtime and lost production

The most expensive line item is not the engineer’s travel—it is the customer’s downtime. Every hour a robot is down, the customer loses output. For a typical manufacturing line, that could be thousands of euros per hour, depending on the industry. A fly-in engineer might take 48 to 72 hours to arrive after the call, even with expedited visa and booking. That means the customer is already facing two to three days of lost production before any diagnosis begins.

Contrast that with a local technician who can be on-site within 24 hours, often within 4–8 hours if the network is dense. The difference in downtime is not a minor detail—it is the core of the value proposition.

The risk of first-time fix failure

Fly-in engineers often arrive with limited information. They may have a remote diagnostic report, but they cannot physically inspect the machine until they land. If they need a spare part that is not in their luggage, they must order it and wait for delivery—another 24–48 hours. If the problem is more complex than expected, they may need to return to China to get the right tools or expertise, leading to a second visit and a doubling of travel costs.

Local technicians, on the other hand, can be dispatched with the right parts from a regional warehouse, and they can return to the site quickly if a follow-up is needed. The first-time fix rate is inherently higher when the engineer has local support and can make multiple trips without incurring international travel costs.

Repeat visits and the multiplier effect

One of the most damaging aspects of fly-in service is the tendency to under-solve the problem. Because the engineer is under pressure to fix the issue in one trip, they may apply a temporary patch or replace a component that is not the root cause. This leads to a repeat failure within weeks, requiring another fly-in visit. The cost of the second visit is not just the ticket—it is the customer’s lost confidence and the potential for contract penalties.

In contrast, a local technician can afford to take a more thorough approach, because a follow-up visit is cheap. They can also build a relationship with the customer’s maintenance team, leading to better preventive care and fewer breakdowns overall.

The compliance and regulatory dimension

European markets have specific compliance requirements for machinery and robotics, including CE marking, safety standards, and documentation. A fly-in engineer may not be familiar with local regulations, and if they perform modifications or repairs that affect compliance, the manufacturer could face legal liability. A local technician network, being set up with European compliance expertise, can ensure that all service work adheres to local standards, reducing risk for both the manufacturer and the customer.

Comparison table: fly-in vs local network

The strategic cost: customer trust and brand reputation

Every time a customer has to wait days for a service visit, the manufacturer’s brand takes a hit. In the competitive robotics market, service response time is a key differentiator. A fly-in model signals that the manufacturer is not committed to the European market. A local network, even if it is being assembled, demonstrates a long-term presence and a willingness to invest in customer success.

Moreover, the fly-in model is not scalable. As the installed base grows, the number of service calls increases, and the cost of flying engineers from China becomes unsustainable. The only viable path is to build a local service infrastructure.

When fly-in might still make sense

There are edge cases where a fly-in engineer is justified: for a complex, rare failure that local technicians are not trained to handle, or for a new product launch where the manufacturer wants to gather field feedback. But these should be exceptions, not the rule. The default should be local.

Conclusion: the math is clear

The fly-in engineer cost model is a losing equation when you factor in travel, visa, downtime, repeat visits, and compliance risk. The visible costs are already high, but the invisible costs—customer downtime and lost trust—are far higher. A local technician network, such as the one being set up by Robanchor, offers faster response, higher first-time fix rates, and lower overall cost. For any Chinese robotics manufacturer serious about the European market, the choice is not about cost—it is about survival.

Sources

• European Commission — Services & trade — https://single-market-economy.ec.europa.eu/ (accessed 2025-10-15)
• IDC — Robotics market — https://www.idc.com/ (accessed 2025-10-15)

The service layer is now a legal boundary

When a European manufacturer deploys a fleet of collaborative robots on a production line, the robots’ connectivity is not just a feature—it is an attack surface. Under the revised Network and Information Security Directive (NIS2, Directive (EU) 2022/2555), that surface is no longer a purely technical concern. For operators classified as essential or important entities, the directive imposes concrete obligations on risk management, incident reporting, and supply chain security. These obligations extend to the maintenance and patching of connected robots, because the service infrastructure that keeps them running is part of the ‘network and information systems’ that NIS2 protects.

The key shift is that cybersecurity is now a service obligation. A maintenance contract that only covers mechanical repairs is insufficient. It must include vulnerability management, timely patching, and incident response—because a compromised robot can disrupt production, exfiltrate data, or serve as a pivot to other systems. This article explains how NIS2 applies to connected robot fleets, what it means for maintenance and patching, and how it interacts with the Cyber Resilience Act (CRA).

NIS2: who is in scope and what is required

NIS2 entered into force on 16 January 2023, and EU member states had until 17 October 2024 to transpose it into national law. It replaces the original NIS Directive and expands the sectors and entities covered. The directive applies to ‘essential’ and ‘important’ entities across sectors such as energy, transport, banking, health, digital infrastructure, and manufacturing. For manufacturing, the directive covers ‘manufacture of basic metals’, ‘manufacture of electrical equipment’, ‘manufacture of machinery and equipment n.e.c.’, and ‘manufacture of motor vehicles, trailers and semi-trailers’, among others. If your company operates in these sectors and has 50 or more employees or an annual turnover exceeding €10 million, you are likely in scope as an important entity. Smaller companies may also be captured if they are the sole provider of a service that is critical for an essential entity.

The core obligations under NIS2 are set out in Article 21, which requires entities to take ‘appropriate and proportionate technical, operational and organisational measures’ to manage risks to their network and information systems. These measures must include:

• Policies on risk analysis and information system security
• Incident handling, including prevention, detection, and response
• Business continuity, such as backup management and disaster recovery
• Supply chain security, including security aspects of relationships with suppliers and service providers
• Security in network and information systems acquisition, development, and maintenance, including vulnerability handling and disclosure
• Policies and procedures to assess the effectiveness of cybersecurity risk-management measures
• Basic cyber hygiene practices and cybersecurity training
• Cryptography and encryption where relevant
• Human resources security, access control, and asset management
• Use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications, and secured emergency communication systems

These are not optional. The directive requires that measures be ‘appropriate and proportionate’—meaning they must be tailored to the risk profile, size, and sector of the entity. But the baseline is high. For a robot fleet operator, this means that the entire lifecycle of the robots—from procurement to decommissioning—must be considered from a cybersecurity perspective.

Connected robots: a concrete example of NIS2 in practice

Consider a mid-sized automotive parts manufacturer that uses a fleet of 40 collaborative robots (cobots) for assembly and welding. The cobots are connected to a local network, which also links to the company’s ERP system and to a cloud-based monitoring platform provided by the robot manufacturer. Under NIS2, this manufacturer is likely an important entity in the manufacturing sector. The cobots are part of its ‘network and information systems’, and the monitoring platform is a supply chain service.

What does NIS2 require in this scenario?

1. Risk assessment: The manufacturer must conduct a risk analysis that includes the robots and their connectivity. This means identifying threats such as malware, unauthorized access, and denial-of-service attacks that could disrupt production.
2. Incident response: The manufacturer must have a plan to detect, report, and respond to incidents. If a robot is compromised, the incident must be reported to the relevant national authority (CSIRT) within 24 hours of becoming aware, with an initial notification, and a final report within 72 hours.
3. Supply chain security: The manufacturer must ensure that its robot supplier and maintenance provider also meet cybersecurity standards. This includes contractual clauses on security, and regular audits of the provider’s practices.
4. Patching and maintenance: The manufacturer must have a process for applying security patches to the robots’ software and firmware. This is not just an IT task—it is a maintenance task that must be coordinated with production schedules.

The maintenance provider, whether internal or external, becomes a critical part of the cybersecurity chain. If the provider does not have a robust patching process, the manufacturer is non-compliant. This is why cybersecurity is now a service obligation: it must be embedded in the service level agreements (SLAs) for maintenance and support.

NIS2 vs. CRA: complementary but distinct

The Cyber Resilience Act (CRA) is a separate regulation that imposes cybersecurity requirements on products with digital elements, including robots. While NIS2 targets operators (the users of the technology), the CRA targets manufacturers (the producers of the technology). The CRA requires that products be designed and developed with security in mind, that they be free of known vulnerabilities, and that manufacturers provide security updates for a defined period. The CRA also introduces a ‘CE’ marking for cybersecurity, similar to other CE markings.

For a robot fleet operator, the CRA means that the robots they buy should be secure by design. But NIS2 means that the operator must also manage the risks associated with using those robots. The two regulations are complementary: the CRA ensures that the product has a baseline of security, while NIS2 ensures that the operator uses it securely.

For a service provider like a maintenance network, both regulations matter. The provider must ensure that the robots it services are patched and maintained in a way that meets NIS2 requirements for the operator, and it must also be aware of the CRA’s requirements on the manufacturer, because the provider may be involved in applying updates.

Maintenance and patching: the new frontline

Under NIS2, patching is not just a best practice—it is a legal obligation. Article 21 specifically mentions ‘vulnerability handling and disclosure’ as part of the required measures. This means that operators must have a process for identifying, assessing, and remediating vulnerabilities in their robots. For a fleet of robots, this is a significant operational challenge.

Robots are often deployed for years, and their software may become outdated. The manufacturer may release patches, but applying them requires downtime, which conflicts with production targets. NIS2 forces operators to balance these priorities. The directive does not prescribe a specific patching frequency, but it requires that measures be ‘appropriate and proportionate’ to the risk. A robot that is exposed to the internet or to a wide network will need more frequent patching than one that is isolated.

Maintenance contracts must now include:

• Regular vulnerability scanning and assessment
• Defined service windows for patching, with minimal production disruption
• Clear escalation paths for critical vulnerabilities
• Documentation of all patching activities, for compliance audits
• Coordination with the robot manufacturer to ensure patches are available and validated

For a service network like Robanchor—a local service network being set up to support Chinese robotics manufacturers in Europe—this is a core value proposition. The network can provide certified technicians who are trained not only in mechanical repair but also in cybersecurity hygiene. They can ensure that patches are applied correctly and that the robot’s configuration is secure. This is a differentiator in a market where many maintenance providers are still focused on hardware.

Incident reporting: a new operational reality

NIS2 introduces strict incident reporting requirements. Article 23 requires essential and important entities to notify their CSIRT (Computer Security Incident Response Team) of any incident that has a significant impact on the provision of their services. The notification must be made without undue delay, and in any case within 24 hours of becoming aware of the incident, with an initial notification. A final report is due within 72 hours, and a detailed final report within one month.

For a robot fleet operator, this means that a cyber incident that disrupts production must be reported to the national authority. This is a significant change from the past, where such incidents might have been handled internally. It also means that the operator must have the ability to detect incidents quickly, which requires monitoring and logging on the robots and their network.

Service providers must be prepared to support this reporting process. They need to have incident response plans that include notifying the operator’s designated contact, and they must be able to provide forensic data to help with the investigation. The service contract should specify the roles and responsibilities of each party in the event of an incident.

Practical steps for operators and service providers

To comply with NIS2, operators of connected robot fleets should take the following steps:

1. Identify your status: Determine if you are an essential or important entity under NIS2. This depends on your sector and size. If you are in scope, you must comply.
2. Conduct a risk assessment: Map your robot fleet, its connectivity, and its dependencies. Identify potential threats and vulnerabilities.
3. Implement security measures: Based on the risk assessment, put in place the technical and organizational measures required by Article 21. This includes access control, network segmentation, and patching processes.
4. Review your supply chain: Ensure that your robot manufacturer and maintenance providers meet cybersecurity standards. Include security requirements in your contracts.
5. Develop an incident response plan: Define how you will detect, report, and respond to incidents. Ensure that your service providers are integrated into this plan.
6. Train your staff: Cybersecurity awareness is not just for IT. Operators, maintenance technicians, and managers should all understand the risks and their roles.

For service providers, the opportunity is to become a trusted cybersecurity partner. This requires investing in training, tools, and processes. It also requires a deep understanding of the regulatory landscape, which is still evolving. The NIS2 directive is being transposed into national laws, and there may be differences in how member states implement it. Service providers should monitor these developments and adapt their offerings accordingly.

Conclusion

NIS2 has turned cybersecurity from an IT footnote into a board-level obligation. For operators of connected robot fleets, this means that maintenance and patching are no longer optional extras—they are legal requirements. The service layer is now a critical part of the security posture. A service network that can provide not only mechanical expertise but also cybersecurity support will be invaluable in this new landscape. As the European market for robotics grows, the demand for such services will only increase. The time to prepare is now.

Sources

• EUR-Lex — Directive (EU) 2022/2555 (NIS2) — https://eur-lex.europa.eu/eli/dir/2022/2555/oj (accessed 2025-10-10)
• European Commission — Cybersecurity policies — https://digital-strategy.ec.europa.eu/ (accessed 2025-10-10)

The Data Act and robot telemetry: who owns the service data, and what that means for after-sales

When a European manufacturer’s production line grinds to a halt because a Chinese-made robot arm is throwing an error code, the first question is usually about spare parts. The second, increasingly, is about data. Under the EU Data Act (Regulation (EU) 2023/2854), the telemetry generated by that robot — its operational logs, error codes, maintenance alerts, and performance metrics — is no longer a grey area. The regulation, which applies from 12 September 2025, establishes clear rights for users to access and share data generated by connected products. For robot manufacturers and independent service providers, this changes the after-sales landscape fundamentally.

The Data Act is not about ownership in the traditional sense. It does not grant exclusive property rights over data. Instead, it creates a framework of access and use rights. The key concept is the ‘user’ — the entity that owns, rents, or leases a connected product. In the context of industrial robots, the user is typically the factory operator, not the manufacturer. The regulation gives users the right to access, in a timely manner, the data generated by their use of the product, and to share that data with third parties. This includes telemetry data that is essential for maintenance and repair.

For a Chinese robot manufacturer entering Europe, this means that the factory owner can demand access to the raw telemetry data from the robot’s sensors and controllers. The manufacturer cannot hide behind proprietary formats or claim that the data is trade secret. The Data Act requires that data be provided in a structured, machine-readable format, with metadata, and free of charge. This is a significant shift from the traditional model where manufacturers controlled all service data and used it to lock customers into their own maintenance contracts.

Independent service providers, such as the network being assembled by Robanchor, a local service network being set up in Europe, stand to benefit directly. Under the Data Act, a third-party service provider can be designated by the user to receive the data. The manufacturer must comply with the user’s request to share data with that third party. This opens the door for independent maintenance, repair, and diagnostics, without the manufacturer’s involvement or approval. The only condition is that the third party must protect the data and not use it for competing purposes, such as developing a competing product.

However, the Data Act is not without its nuances. It distinguishes between ‘product data’ and ‘related service data’. Product data is generated by the product itself, while related service data is generated by the manufacturer’s own services, such as cloud-based monitoring. The user has rights to product data, but related service data is more restricted. For example, if a robot manufacturer offers a remote monitoring service that processes telemetry to provide predictive maintenance, the data generated by that service (e.g., the predictive alerts) may not be automatically accessible to the user. This distinction is critical for after-sales: a user can demand the raw error logs, but may not get the manufacturer’s proprietary analysis.

Another key aspect is the protection of trade secrets. The Data Act includes provisions to protect trade secrets and confidential business information. A manufacturer can refuse to share data if it would undermine a trade secret, but the burden of proof is on the manufacturer. They must demonstrate that the data constitutes a trade secret and that sharing it would cause serious harm. In practice, this is a high bar. For robot telemetry, most operational data is unlikely to qualify as a trade secret, as it is generated by the user’s own operations. The manufacturer’s algorithms and software code are protected, but the raw data is not.

For the after-sales ecosystem, the Data Act also introduces rules on switching between cloud service providers. While this is more relevant for software, it has implications for robots that rely on cloud-based fleet management. Users can switch providers without penalty, and the provider must facilitate the transfer of data. This reduces the lock-in effect and allows users to choose the most cost-effective service provider.

Compliance with the Data Act is not optional. The regulation applies to all connected products placed on the EU market, regardless of where the manufacturer is based. Non-compliance can result in fines of up to €20 million or 4% of global turnover, whichever is higher. For Chinese manufacturers, this means that their European subsidiaries or importers must ensure that their products and contracts comply with the Data Act. This includes providing clear information to users about the data generated and their rights.

For independent service providers, the Data Act is a powerful tool. It allows them to offer maintenance services without needing a partnership with the manufacturer. They can access the telemetry data directly from the user, diagnose issues, and even provide remote support. This is particularly valuable for a network like Robanchor, which aims to provide after-sales support for Chinese robots across Europe. By leveraging the Data Act, the network can offer services that were previously the exclusive domain of the manufacturer.

However, there are practical challenges. The Data Act requires that data be provided in a ‘readily usable’ format, but it does not specify the exact format. Manufacturers may choose to provide data in a proprietary format that is difficult to parse. The regulation also requires that data be provided ‘without undue delay’, but the definition of ‘timely’ is vague. Service providers may need to negotiate with manufacturers or rely on the user to enforce their rights. In some cases, the manufacturer may argue that the data is not ‘generated by the use of the product’ but rather by the manufacturer’s own systems, which could limit access.

Another challenge is the interaction with other regulations, such as the GDPR. Telemetry data may include personal data if the robot is used in a way that involves individuals, such as collaborative robots that work alongside humans. The Data Act does not override GDPR; it requires that data sharing comply with data protection rules. This means that users and third parties must have a legal basis for processing personal data, which could complicate access to certain datasets.

Despite these challenges, the Data Act represents a fundamental shift in the balance of power. It empowers users and independent service providers, and it forces manufacturers to be more transparent. For the after-sales market, this means more competition, potentially lower costs, and better service. For Chinese manufacturers, it means that they must adapt their business models to a more open data environment. They can no longer rely on data lock-in to maintain their service revenue.

To illustrate the rights of different parties under the Data Act, consider the following comparison:

This table is a simplification; the actual rights and obligations are detailed in the regulation. For instance, the Data Act also includes provisions on data sharing between businesses and governments in exceptional circumstances, but that is less relevant for after-sales.

In practice, the Data Act will likely lead to the emergence of new business models. Independent service providers can offer diagnostics and maintenance based on data that they obtain from users. They can also aggregate anonymized data across multiple users to provide benchmarking and predictive insights. This could create a data-driven after-sales ecosystem that is more efficient and responsive.

For Robanchor, as a local service network being set up, the Data Act provides a legal foundation for its operations. The network can advise its clients on how to exercise their data rights, and it can use the data to provide better services. However, it must also ensure that its own practices comply with the regulation, particularly regarding data protection and trade secrets.

In conclusion, the Data Act is a game-changer for robot after-sales in Europe. It gives users control over their data, enables independent service providers, and forces manufacturers to be more open. While there are challenges in implementation, the overall direction is clear: data is no longer a proprietary asset of the manufacturer, but a shared resource that can be used to improve service and innovation. For Chinese robot manufacturers, embracing this shift is not just a legal requirement but a competitive opportunity to build trust and long-term relationships with European customers.

Sources

• EUR-Lex — Regulation (EU) 2023/2854 (Data Act) — https://eur-lex.europa.eu/eli/reg/2023/2854/oj (accessed 2025-10-05)
• European Commission — Data Act — https://digital-strategy.ec.europa.eu/ (accessed 2025-10-05)

Robots are not just machines—they are a compliance stack

A mobile robot sold in the EU is simultaneously a piece of electrical and electronic equipment (EEE), a carrier of one or more batteries, and a product whose components—from steel to rare earths—will soon be traced through a digital product passport (DPP). For a Chinese robotics manufacturer, the first instinct is to treat these as separate paperwork burdens. They are not. They form a single, layered compliance stack that determines whether a robot can be placed on the market, serviced, and eventually taken back. This article unpacks each layer—WEEE, the Batteries Regulation, and the DPP—and shows how they interact, using only the legal texts as reference.

Layer 1: WEEE—the waste electrical and electronic equipment regime

The WEEE Directive (Directive 2012/19/EU) is the oldest and most established layer. It applies to any product that is dependent on electric currents or electromagnetic fields to work properly, and that falls under one of the six categories listed in Annex III. Robots, with their motors, sensors, and control units, clearly fall under category 6 (large equipment) or category 5 (small equipment), depending on size. The directive sets collection, recovery, and recycling targets, and it obliges producers to finance the collection and treatment of waste EEE.

For a robot manufacturer, the immediate obligations are:

• Registration in each EU member state where you place products on the market. There is no single EU-wide register; you must register with national authorities or their appointed compliance schemes.
• Marking with the crossed-out wheeled bin symbol, and in most cases a producer identification mark.
• Financing the collection, treatment, and recycling of waste EEE. This is usually done by joining a producer responsibility organisation (PRO) that handles the logistics and reporting.
• Reporting annually on the quantities of EEE placed on the market and the waste collected.

What varies by country is the fee structure, the registration deadlines, and the enforcement intensity. Some member states require a bank guarantee for future waste, others do not. The directive sets minimum requirements, but national transposition laws differ. A manufacturer must verify the specifics in each country of sale.

Layer 2: The Batteries Regulation—beyond simple waste

Batteries are not just another component; they have their own regulation, Regulation (EU) 2023/1542, which replaces the old Battery Directive and introduces a comprehensive lifecycle approach. It covers all batteries, including those in robots, and it sets requirements for sustainability, safety, labelling, and end-of-life management.

Key obligations for robot batteries include:

• Carbon footprint declaration for electric vehicle batteries and rechargeable industrial batteries with a capacity above 2 kWh—this includes many robot batteries. From 2025, a declaration is required; later, a performance class and a maximum threshold will be added.
• Recycled content requirements for industrial batteries with a capacity above 2 kWh, starting from 2031, with mandatory percentages of cobalt, lead, lithium, and nickel.
• Durability and performance requirements, including documentation on expected lifetime and capacity.
• Removability and replaceability: by 2027, portable batteries in appliances must be removable and replaceable by the end-user. For robot batteries, which are often industrial, the requirement is that they be easily removable by professionals, but the regulation pushes for design that facilitates repair.
• Collection and recycling targets: the regulation sets collection targets for portable batteries (63% by 2027, 73% by 2030) and for industrial batteries, a requirement to ensure they are collected at end-of-life. Producers must finance the collection and treatment.

The regulation also introduces the battery passport, a digital record for each battery with a capacity above 2 kWh. This is not just a label; it is a data set that must be accessible via a QR code and that accompanies the battery through its life. The passport will include information on the battery’s manufacturer, composition, carbon footprint, recycled content, and status (e.g., health, state of charge). For robot fleets, this means each battery will have a unique identifier and a live data record.

Layer 3: The digital product passport—the umbrella

The DPP is a broader concept introduced by the Ecodesign for Sustainable Products Regulation (ESPR), which is not yet in force but is being phased in. The DPP will apply to many product categories, including electronics and possibly robots, and it will require a digital record that contains information on the product’s origin, composition, repair instructions, and end-of-life handling. The battery passport is, in effect, a specific DPP for batteries.

For a robot, the DPP will likely integrate the battery passport data, along with data on the robot’s own components, such as plastics, metals, and rare earths. The goal is to create a single source of truth that supports circular economy practices: repair, refurbishment, and recycling. The DPP will be accessible via a data carrier (e.g., QR code) on the product, and it will be mandatory for certain categories starting in 2027–2030, with a phased approach.

How the layers interact

The three regimes are not isolated. WEEE focuses on the whole product at end-of-life; the Batteries Regulation focuses on the battery as a distinct entity; and the DPP aims to connect product and component data. For a robot, the practical consequence is that you must track both the robot and its battery separately, and report on both. The battery passport will feed into the DPP, but the DPP will also contain WEEE-related data, such as the waste category and recycling instructions.

One point of interaction is the removability requirement. Under the Batteries Regulation, batteries must be removable to facilitate repair and recycling. This affects the design of the robot and the WEEE treatment process. If a battery is embedded, the entire robot may be treated as hazardous waste, increasing costs.

Comparison table: WEEE vs Batteries Regulation vs DPP

Practical implications for Chinese robot manufacturers

For a manufacturer entering Europe, the compliance stack means you cannot treat WEEE, batteries, and DPP as separate projects. You need a unified data strategy. The battery passport, for instance, will require you to collect data from your battery supplier and update it throughout the battery’s life. That data will also be needed for WEEE reporting and for the DPP.

Here are the steps to take:

1. Map your products to the WEEE categories and the battery capacity thresholds. Determine which obligations apply.
2. Register in each member state where you sell, or join a compliance scheme that handles registration and reporting.
3. Design for compliance: ensure batteries are removable, and that you can provide the data required for the battery passport.
4. Set up data collection from your supply chain, including battery suppliers, to feed the passport and DPP.
5. Plan for end-of-life: work with recycling partners who can handle both the robot and its battery, and who can provide the documentation you need for WEEE and battery reporting.

What varies by country is the fee structure, the registration deadlines, and the enforcement intensity. Some member states require a bank guarantee for future waste, others do not. The directive sets minimum requirements, but national transposition laws differ. A manufacturer must verify the specifics in each country of sale.

What to verify before you rely on this article

This article is based solely on the two EUR-Lex sources cited. It does not cover national transposition details, which change over time. For example, the WEEE Directive has been amended by Directive (EU) 2018/849, but the consolidated text on EUR-Lex includes those amendments. The Batteries Regulation is directly applicable, but some provisions require implementing acts that are still being drafted. Always check the latest consolidated versions and consult a local compliance expert.

Sources

• EUR-Lex — Directive 2012/19/EU (WEEE) — https://eur-lex.europa.eu/eli/dir/2012/19/eu/oj (accessed 2025-09-30)
• EUR-Lex — Regulation (EU) 2023/1542 (Batteries) — https://eur-lex.europa.eu/eli/reg/2023/1542/oj (accessed 2025-09-30)

Introduction: A regulatory shift with direct consequences for service providers

When the Machinery Regulation (EU) 2023/1230 replaced the Machinery Directive 2006/42/EC, most attention focused on new product requirements such as cybersecurity and AI. But for companies that maintain, repair, or retrofit machinery, the regulation quietly rewrote the rules on documentation. The most immediate change: the legal status of the ‘EC Declaration of Conformity’ and the technical file. Under the Directive, these documents were required for placing machinery on the market. Under the Regulation, they remain required, but the obligations for keeping them available and updating them after modifications have been sharpened. Service providers who ignore these changes risk performing work that legally invalidates the machinery’s conformity, exposing both themselves and the machinery owner to liability.

What the Machinery Regulation actually changes

The Regulation (EU) 2023/1230, applicable from 20 January 2027, is not a mere renumbering. It introduces new definitions, expands the scope to include certain ‘safety components’ and ‘partly completed machinery’, and adds requirements for cybersecurity and AI-based safety functions. But for after-sales, the key changes are in the documentation and instruction requirements. The Regulation clarifies that the technical documentation must demonstrate conformity with the essential health and safety requirements (EHSRs) as they apply at the time of placing on the market. It also strengthens the obligation to provide instructions in a language that can be easily understood by end-users, and it requires that instructions be updated when the machinery is modified.

Technical documentation: more than a paper trail

Under the Directive, the technical file had to be compiled before placing on the market and kept for at least 10 years after the last unit was produced. The Regulation keeps that 10-year retention period but adds a crucial nuance: the technical documentation must be kept available for the national authorities for that period, and it must be updated if the machinery is modified in a way that affects conformity. This is a direct hook for service providers. Any modification that changes the safety characteristics of the machinery—whether a software update, a replacement of a safety component, or a structural change—triggers an obligation to update the technical documentation. The Regulation does not say who must do this, but in practice it falls on the person who makes the modification, which is often the service company.

Instructions: from ‘accompanying’ to ‘continuously updated’

The Directive required that instructions accompany the machinery. The Regulation goes further: it requires that instructions be provided in a language easily understood by operators, and that they be updated when the machinery is modified. This means that after-sales service providers must not only perform the physical work but also ensure that the operator’s manual reflects the new state of the machinery. If a service provider replaces a safety relay with a different model, the instructions must be amended to describe the new component, its maintenance, and any changes in safety functions. This is a significant operational burden, but it is also an opportunity for service providers to offer documentation updates as a value-added service.

Comparison: Machinery Directive vs. Machinery Regulation on documentation

What service providers must know when maintaining machinery

For a service network like Robanchor—a local service network being set up to support Chinese robotics manufacturers in Europe—the Regulation creates both compliance duties and business opportunities. Here are the practical implications.

1. Modifications trigger a conformity reassessment

Any modification that changes the safety functions, performance, or intended use of the machinery may require a new conformity assessment. The Regulation does not define ‘modification’ precisely, but it is clear that a change that affects conformity must be documented. Service providers should establish a protocol to evaluate whether a repair or upgrade affects conformity. If it does, the provider must either restore the machinery to its original state or conduct a new risk assessment and update the technical file. This is a legal requirement, not a best practice.

2. Documentation updates are a service deliverable

When a service provider performs a modification, they should deliver an updated set of instructions and a revised Declaration of Conformity if the modification affects conformity. This is not optional. The Regulation requires that the machinery be accompanied by the Declaration of Conformity, and that instructions be updated. Service providers should include documentation updates in their service contracts, clearly stating what will be updated and who is responsible for the technical file.

3. Language requirements are stricter

The Regulation requires instructions to be in a language easily understood by operators. This is a shift from the Directive, which left language choice to member states. In practice, this means that instructions for machinery used in Germany must be in German, in France in French, and so on. Service providers working across borders must be prepared to provide documentation in multiple languages, or at least to coordinate with the manufacturer to ensure compliance.

4. The 10-year retention period starts at the last unit produced

This is a subtle but important point. The 10-year period for keeping technical documentation is counted from the date of manufacture of the last unit of the model, not from the date of sale or installation. For service providers, this means that documentation for older machinery may still be legally required. If a service provider modifies a machine that is 9 years old, they may need to ensure that the technical file is still available and updated.

5. Cooperation with the manufacturer is essential

In many cases, the original manufacturer holds the technical file. Service providers should establish clear agreements with manufacturers about who updates the documentation after a modification. The Regulation does not specify who is responsible, but it is logical that the entity that makes the modification is responsible for ensuring conformity. For a network like Robanchor, this means building relationships with manufacturers to access technical documentation and to agree on update procedures.

Practical steps for service providers

1. Audit your current service processes to identify where modifications occur.
2. Develop a checklist to assess whether a modification affects conformity.
3. Include documentation update services in your contracts, with clear deliverables.
4. Establish a system for tracking the 10-year retention period for each machine you service.
5. Work with manufacturers to obtain technical documentation and to agree on update responsibilities.
6. Train technicians on the new regulatory requirements, especially the language and update obligations.

Risks of non-compliance

Failure to update documentation after a modification can have serious consequences. The machinery may be considered non-conforming, and the person who made the modification could be held liable. National market surveillance authorities can require corrective actions, including withdrawing the machinery from use. In the event of an accident, the lack of updated documentation could be used as evidence of negligence. For service providers, this is a professional liability risk that should be managed through clear contracts and rigorous procedures.

Conclusion: Documentation is a service, not a burden

The Machinery Regulation (EU) 2023/1230 elevates documentation from a bureaucratic requirement to a core element of machinery safety. For after-sales service providers, this is an opportunity to differentiate themselves by offering compliance-focused services. By understanding the new obligations and integrating them into service workflows, providers can help their clients maintain conformity and avoid legal pitfalls. As the Regulation applies from 20 January 2027, there is still time to prepare. But the time to start is now.

Sources

• EUR-Lex — Regulation (EU) 2023/1230 (Machinery) — https://eur-lex.europa.eu/eli/reg/2023/1230/oj (accessed 2025-09-25)
• European Commission — Machinery — https://single-market-economy.ec.europa.eu/ (accessed 2025-09-25)

Spare parts carry firmware, and firmware carries risk

A replacement sensor board for a collaborative robot arm looks like a commodity: a PCB, a connector, a housing. But if that board contains a microcontroller with embedded software, it is a ‘product with digital elements’ under Regulation (EU) 2024/2847, the Cyber Resilience Act (CRA). The regulation applies from 11 December 2027, and it does not exempt spare parts that are placed on the market separately. For a service network assembling after-sales support for Chinese robotics manufacturers entering Europe, this changes how spare parts must be documented, updated, and traced.

The CRA defines a ‘product with digital elements’ as any software or hardware product and its remote data processing solutions, including software or hardware components that are placed on the market separately. A motor controller that ships with firmware is such a product. A sensor board that runs calibration routines is such a product. Even a simple I/O module with a bootloader qualifies. The only parts that fall outside are those that contain no programmable logic and no software that can be updated or exploited.

Why a replacement board is not just a component

In the after-sales context, a spare part is often treated as a repair item, not a new product. But the CRA looks at the moment of placing on the market, not at the end use. When a distributor or a service network stocks a replacement motor controller and sells it to a maintenance provider, that controller is placed on the market as a standalone product. It must meet the same essential cybersecurity requirements as the original equipment.

That means the spare part must be designed, developed, and produced so that it is free from known exploitable vulnerabilities, comes with a secure default configuration, and is supported with security updates for the expected product lifetime. The manufacturer must also provide a Software Bill of Materials (SBOM) and report actively exploited vulnerabilities to the EU Agency for Cybersecurity (ENISA). These obligations are not optional for spare parts.

Hardware-only vs. firmware-bearing parts

The distinction is practical. A metal bracket, a cable, a passive filter, or a mechanical seal has no digital elements. It cannot be updated, cannot be exploited, and does not need a security update policy. But a replacement sensor board with a microcontroller, a motor controller with a CAN stack, or a vision module with embedded image processing is a different category. The table below summarises the key differences.

What this means for service networks and manufacturers

For a service network being set up to support Chinese robotics manufacturers, the practical consequence is that spare parts logistics must be treated as product compliance logistics. Every firmware-bearing part must be traceable to a CE marking that includes the CRA requirements. The manufacturer must have a single point of contact for security issues, and the service network must be able to identify which software version is installed on each part.

This is not just a paperwork burden. The CRA requires that vulnerabilities are handled according to the regulation’s Annex I, which includes obligations to inform users and ENISA. A service network that replaces a motor controller must know whether the new part has the latest firmware and whether any known vulnerabilities are patched. If the network installs an outdated part, it could be held liable for introducing a vulnerability into the robot system.

Practical steps for spare parts compliance

1. Classify every spare part: determine whether it contains any programmable logic or firmware.
2. For firmware-bearing parts, obtain the EU declaration of conformity and the SBOM from the manufacturer.
3. Ensure that the part’s security update period is clearly stated and that the service network has access to update files.
4. Keep records of which software version is installed in each part, and when it was updated.
5. Verify that the manufacturer has a process for reporting vulnerabilities to ENISA and for notifying users.

Deadlines and transition periods

The CRA entered into force on 10 December 2024. Most obligations apply from 11 December 2027, which is the date by which products placed on the market must comply. There is a shorter transition for the reporting obligations, which apply from 11 September 2026. For spare parts, the key date is the same: from 11 December 2027, any firmware-bearing spare part placed on the market must be CRA-compliant.

It is worth noting that the regulation does not have a separate category for spare parts. They are treated like any other product with digital elements. This means that a manufacturer cannot argue that a spare part is ‘only for repair’ and therefore exempt. The European Commission’s guidance on the CRA, available on its digital strategy page, confirms that the regulation applies to products placed on the market, regardless of their intended use.

What varies by country and what to verify

While the CRA is a regulation and directly applicable in all EU member states, market surveillance and enforcement are carried out by national authorities. This means that the level of scrutiny may vary from one country to another. Some authorities may focus on high-risk products, while others may conduct random checks. Service networks should verify with the national market surveillance authority in each country where they operate to understand local enforcement priorities.

Additionally, the CRA is aligned with the harmonised standards that are still being developed. Until those standards are published, manufacturers can use other technical specifications to demonstrate compliance. Service networks should ask for the technical documentation that supports the CE marking, including the risk assessment and the security requirements that were applied.

Conclusion: spare parts are a compliance frontier

The Cyber Resilience Act is not just about new robots or smart devices. It reaches into the after-sales ecosystem, where spare parts with firmware are placed on the market every day. For a local service network being set up to support Chinese robotics manufacturers, the message is clear: treat every firmware-bearing spare part as a product that must meet the same cybersecurity standards as the original equipment. That means asking for the right documentation, keeping track of software versions, and being ready to support security updates. The deadline is 11 December 2027, and it will arrive faster than many expect.

Sources

• EUR-Lex — Regulation (EU) 2024/2847 (CRA) — https://eur-lex.europa.eu/eli/reg/2024/2847/oj (accessed 2025-09-20)
• European Commission — Cyber Resilience Act — https://digital-strategy.ec.europa.eu/ (accessed 2025-09-20)