When Do You Need a Local Robot Integrator? Direct Purchase vs Distributor vs System Integrator

A robot is a product. A robot deployment is a project. The difference between buying a product and executing a project is where the integration work falls—on the buyer, on the supplier, or on a third party who specializes in connecting the robot to the production environment. Many robot projects struggle not because the robot is wrong but because the buyer underestimated the integration scope and overestimated what the robot supplier would handle. This article explains the difference between a robot seller, a distributor, a system integrator, and a project coordinator—and how to decide which model fits a given project.

Robot Seller, Distributor, Integrator and Project Coordinator Are Different Roles

These four roles are often confused, and the confusion leads to mismatched expectations. Each role has a different scope of responsibility, a different cost structure, and a different point in the project lifecycle where they add value.

A single organization may play multiple roles. A distributor may also be a system integrator for simpler projects. A robot seller may have an in-house integration team for projects in their home market. But the roles are distinct, and the buyer should understand which role each party is playing in their project.

The key question is not “who sells the robot?” but “who does the integration work?” If the answer is “the buyer’s own team,” the buyer needs to have the engineering capability, the time, and the budget to do it. If the answer is “no one,” the project will stall after delivery.

Projects That May Start with Direct Product Supply

Not every robot project requires a full integration team. Some projects may be suitable for direct purchase from the supplier, provided the buyer has the internal capability to handle installation, basic configuration, and the engineering tasks that even a “simple” robot project requires.

Characteristics That May Favor Direct Purchase

• Single robot or small fleet
• Standard product configuration with no custom end-effector or vision system
• No complex building system interfaces (no elevator, no automatic doors, no fire alarm integration)
• Simple or no software integration (standalone operation, no WMS/MES connection)
• Buyer has internal technical staff who can handle installation, programming, and maintenance
• Site infrastructure is ready (power, network, floor, safety perimeter)
• Project timeline is not critical (the buyer can afford to learn and troubleshoot)

What the Buyer Should Still Verify

Even for direct-purchase projects, the buyer should confirm:

• What installation support is included in the purchase price? (Phone support? Remote video? On-site visit?)
• What training is included? (How many sessions? How many people? On-site or at supplier?)
• What is the warranty scope and response time?
• What spare parts are recommended for initial stock?
• What documentation is provided in the buyer’s language?
• Is the robot certified/conform for the destination market? (Identify applicable regulatory, electrical/radio, labeling, and documentation requirements by product, configuration, and market.)

Note: Even a single industrial robot project may require application integration, risk assessment, safeguarding/guarding, end-effector design, PLC interface, or other engineering work. Direct purchase does not mean “buy and plug in”—it means the buyer’s team takes on the integration scope that a supplier or integrator would otherwise handle.

Projects That Usually Need Local Integration

As project complexity increases, the need for local integration engineering grows. The following project characteristics typically require a system integrator:

Project Characteristics That May Require Integration

• Multiple robots or a fleet that requires coordination
• Custom end-effector design (specialized gripper, multi-tool changer, vision-guided pick)
• Machine interface (CNC tending, injection molding, press tending, conveyor tracking)
• Building system interfaces (elevators, automatic doors, fire alarm, building management system)
• Software integration (WMS, MES, ERP, fleet management platform)
• Multi-site deployment with configuration standardization
• Safety system design (area scanners, light curtains, safety PLC, perimeter guarding)
• Site modification (floor preparation, utility installation, layout changes)
• Process engineering (cycle time optimization, quality validation, production ramp-up)

Why These Projects Need Integration

Each of these characteristics involves engineering work that goes beyond unboxing and powering on the robot:

The cost of this work is significant and is typically not included in the robot unit price. Buyers who assume “the robot supplier will handle it” often discover that the supplier’s scope ends at the robot’s shipping crate.

Why CNC, Welding, Elevator, Safety and Building Interfaces Change the Answer

Certain interfaces increase the complexity of a robot project and typically require specialized integration expertise:

CNC and Machine Tending Interfaces

• The robot must communicate with the CNC controller (via Profinet, EtherCAT, or a dedicated I/O interface)
• The robot must synchronize with the machine cycle (open door, load part, close door, start cycle, wait, open door, unload part)
• The robot must handle part presentation (fixture, conveyor, or random bin with vision)
• The robot must handle chip management and coolant (if the machine has internal coolant)

This requires knowledge of both the robot and the machine controller, which is typically beyond the scope of a robot seller’s standard support.

Welding Interfaces

• Welding robot integration involves power supply, wire feeder, torch, gas management, and welding parameter synchronization
• Safety requirements are more stringent (arc flash, fume extraction, fire prevention)
• Weld quality depends on robot path accuracy, torch angle, and travel speed—all of which require process engineering

Elevator Interfaces

• The robot must call the elevator, enter, select the destination floor, wait for arrival, and exit
• This requires integration with the elevator controller, which varies by elevator brand and model
• Some elevator controllers provide a documented API; others require a third-party interface module
• The integration must handle failure modes: elevator occupied, elevator out of service, elevator called but not arriving

Safety System Interfaces

• The robot must integrate with the site’s safety system: E-stop circuits, light curtains, area scanners, safety doors
• Safety requirements are determined by the robot type, application, installed configuration, and applicable standards—not by the sourcing model
• For industrial robot applications, applicable standards include ISO 10218-1:2025 and ISO 10218-2:2025 (internationally) and ANSI/A3 R15.06-2025 (United States). For collaborative industrial applications, ISO/TS 15066:2016 applies within its scope. For driverless industrial trucks / many AMR applications, ISO 3691-4:2023 may apply. These standards must not be generalized to robot types or applications outside their scope.
• A risk assessment must be conducted for the installed configuration by a qualified person
• Safety circuit architecture (e.g., dual-channel monitored) must be designed and validated by a qualified integrator or safety professional per applicable functional-safety requirements—not assumed as a universal default

These interfaces require engineering expertise that a robot seller typically does not provide as part of the standard product package. A system integrator who has experience with the specific interface type can significantly reduce the risk and timeline of the project.

What a Distributor Can Coordinate Without Being the Local Integrator

A distributor occupies a middle ground between direct purchase and full integration. The distributor can coordinate several aspects of the project without performing the engineering work:

The distributor’s value is in local presence: they can receive the shipment, handle customs, provide a local point of contact, and coordinate with the supplier for support. But they are not a substitute for a system integrator when the project requires engineering work.

When a Distributor May Be Sufficient

• The buyer has an internal engineering team that can handle integration
• The project is at a single site with no complex interfaces
• The robot is a standard configuration with no custom engineering
• The buyer needs local logistics and warranty support but not engineering

When a Distributor May Not Be Sufficient

• The project requires custom end-effector design, PLC programming, or software integration
• The project involves elevator, door, or building system interfaces
• The buyer does not have internal engineering capability
• The project is multi-site and requires configuration standardization

How to Split Responsibilities Before Purchase

For projects that involve multiple parties (supplier, distributor, integrator, buyer’s team), the responsibilities should be split explicitly before the purchase order is issued. A responsibility matrix ensures that every task has an owner and that no task falls into the gap between parties.

R = Responsible (does the work) / A = Accountable (approves the work) / C = Consulted / I = Informed

This matrix should be agreed by all parties before the project starts. It prevents the most common source of project delay: “I thought you were going to do that.”

Questions to Ask a Local Integrator

When evaluating a system integrator for a robot project, the following questions help assess their capability and fit:

Technical Capability

• What robot brands have you integrated? (If they only work with one brand, they may not be the right choice for a multi-vendor fleet.)
• What machine interfaces have you completed? (CNC, injection molding, conveyor, press—specific experience matters.)
• What building system integrations have you done? (Elevator brands, door controllers, fire alarm systems.)
• What software integrations have you completed? (WMS, MES, ERP—specific platforms and versions.)
• Do you have in-house mechanical design capability for custom end-effectors?
• Do you have in-house PLC programming capability?
• Do you have in-house safety system design capability?

Project Experience

• How many robot projects have you completed in the past 2 years?
• What is the largest fleet you have deployed?
• Do you have experience with multi-site rollouts?
• Can you provide references from projects with similar scope?
• What is your typical project timeline for a project of this scope?

Support Model

• Do you offer ongoing maintenance contracts?
• What is your response time for on-site support?
• Do you have remote diagnostics capability?
• Do you stock spare parts, or do you order on demand?
• Do you provide training for our operators and technicians?

Commercial Terms

• Do you work on a fixed-price or time-and-materials basis?
• What is included in your integration quote, and what is excluded?
• Do you offer a warranty on your integration work?
• How do you handle change orders if the project scope changes?

Decision Matrix: Direct Supply vs Distributor Support vs Full Integration

How to Use This Matrix

Score the project against each row. If most rows point to “Direct Supply,” the project may proceed without an integrator. If most rows point to “Full Integration,” an integrator is likely needed. Mixed results indicate a distributor-supported model, where the distributor handles logistics and basic support while the buyer or a third party handles specific integration tasks.

Note: Safety requirements are not determined by the sourcing model. Whether the project uses direct supply, distributor support, or full integration, safety measures must be determined by a risk assessment conducted for the installed configuration, per applicable standards. A “simple” project does not mean “basic safety”—it means the safety scope may be simpler, not that it can be skipped.

The matrix is a guide, not a formula. A project with a small fleet but complex elevator integration may still need an integrator. A project with a larger fleet but standard configuration and a strong internal team may proceed with direct supply. The decision depends on the specific project characteristics.

Research Sources Used

1. Source / organization: RobotCompany (OEM-neutral fleet operations model, per-task/per-uptime-hour pricing) | URL: as cited in report_batch_d | Version/date: as cited
2. Source / organization: ISO (ISO 10218-1:2025, ISO 10218-2:2025, ISO/TS 15066:2016, ISO 3691-4:2023) | URL: https://www.iso.org/ | Version/date: as applicable
3. Source / organization: ANSI/A3 (R15.06-2025) | URL: https://www.a3automate.org/ | Version/date: 2025

Internal product/material source: report_batch_d (batch D research report) [TO VERIFY]: none