Select your location:

Location

Select your language:

  • English

Creator Extension Certification

The certification by the KUKA Creator Portal is designed to ensure that the customer experience is as good as possible.


Build Trust. Deliver Quality. Get Certified.

Achieving certification through the KUKA Creator Portal ensures your product meets the highest standards of compatibility, reliability, and usability – core drivers of customer satisfaction. Our structured certification process is designed to identify and address potential issues early, safeguarding every critical point of the customer journey. Once certified, your product earns a visible mark of quality in the KUKA Marketplace, enhancing both its credibility and exposure to end customers.

Certification Drives Trust and Market Reach. Your adds values.

  • Identify Problems Early

    The certification process helps identify problems before the customer does, ensuring a smoother experience
  • Improved Customer Journey

    KUKA and Creators work together to offer an improved customer journey
  • Testing Opportunities

    It offers testing possibilities to KUKA Creators, allowing them to refine their products before they reach the market

Show off your certified products in the KUKA Marketplace

Only certified products are featured in the Marketplace, giving them increased visibility and credibility with potential users. Certification applies to individual products – whether hardware or software on the KUKA system, so-called KUKA Option Packages (KOP) – not to entire companies or groups. This rigorous certification process ensures high quality, fosters trust among end customers, and clearly distinguishes product types.

  • Mandatory for KOPs: Certification is mandatory for KOPs written with the help of the the iiQWorks.App Builder. A KOP can only be used in developer mode on the controller without appropriate signing
  • Optional for Hardware: Certification is optional for hardware products, where a minimal technical test is sufficient.

Certification process

A structured path to validate your product and showcase it in the KUKA Marketplace

Certify your KOP written with the help of the iiQWorks.App Builder

  1. Requirement communication: KUKA and Creators align on certification goals and benefits during joint meetings.
  2. Development: In the development stage Creators writes their KOP using the iiQWorks.App Builder.
  3. System test: The system test verifies that the toolbox basic system tasks can be performed. These tasks include installation, drag and drop nodes, and using capabilities.
  4. Function test: A functional test must be performed. Depending on the complexity of the product and toolbox, the function test may be performed either at a KUKA facility or through the Creator. If the Creator performs the final function test, a verification must be done.
  5. Proof of certification: Creators receive official proof, and a badge appears in the Marketplace. Certification is version-specific and must be renewed after major changes.

KOP submission requirements

All requirements for hardware-only extensions also apply. For software toolboxes, please provide the following:

  • Installation file (KOP)
  • End User License Agreement (EULA) in .txt format
  • Complete list and short description of toolbox functions (.txt, .pdf, .docx, etc.)
  • Customer-facing documentation
  • If applicable, complete hardware required for functional testing
  • Contact person for technical or process-related inquiries

Certify your hardware extensions

  1. Requirement communication: In meetings between KUKA and Creators, the requirements and benefits of certification will be discussed.
  2. Development: In the development stage the Creator can adjust their product, so it will fit to the desired KUKA Robots.
  3. Pre-Stage: The pre-stage is for testing and evaluating what needs to be adjusted The Feedback Loop ensures that the Creator gets the necessary information to go through with the certification. The pre-stage can start also during the development to speed up the process.
  4. Certification: The certification Phase makes sure no critical point along the customer journey is open. If this is the case a certificate can be granted.
  5. Proof of certification: Proof of certification is handed to the Creator. The certification badge is also displayed in the Marketplace. Certification depends on the product and version. It must be renewed if critical changes are made to the product.

Hardware extensions submission requirements

  • Feasibility clarification
  • Marketplace information
  • Contacts (technical, commercial, service)
  • Service Concept
  • Sales Concept
  • Release plan
  • Hardware and documentation available for certification