Skip to content
Resilic Docs

Custom products & projects

Many manufacturers do not ship in series: they deliver one or a few units per order — a palletiser for customer X, a test cell for customer Y. Resilic records such deliveries as custom products — in the same register as series products, with the same versions, SBOMs and deployments, but with the facts you think in: order number, customer, handover date and the platform the unit derives from.

Series product or custom product?

Section titled “Series product or custom product?”
  • Series product: built repeatedly to one specification (“VL-500 packaging line”). Versions are your software/configuration releases, deployments the installations in the field.
  • Custom product: built to one customer’s specification, one or a few units (“VL-500 for customer X, order 2026-0471”). A custom product is one delivered unit: product, as-built version and deployment are created in one step.

The distinction is product vocabulary, not a legal consequence. The CRA has no series threshold: a product with digital elements built to a customer’s specification is placed on the market on handover and carries the full manufacturer duties — its own technical documentation, SBOM, conformity route, support period and Article 14 reporting path. The Machinery Regulation likewise applies per machine. Resilic derives no relief from the kind and shows none.

Registering a custom product

Section titled “Registering a custom product”

In the product register choose New product and set the product kind to Custom product. Besides name and manufacturer you record:

  • Order number — your commercial reference; it also names the as-built version unless you give another one.
  • Customer and site — pick an existing customer and one of its sites, so the same customer and site records are reused across products and deployments. A name that does not exist yet is only created when you choose Create new customer (or Create new site) in the list; an unconfirmed name holds the form, so a typo never creates a second customer. With a site, the deployment is created at the same time.
  • Handover date — the day you hand the product to the customer. That is its placing on the market (CRA Art. 3(22)): the reference date for the support period and for whether a later retrofit is a substantial modification. Resilic does not set the support period automatically — you determine and justify it as for any product.
  • Platform — the series product the unit derives from. Role, product family, CRA classification and the support-period inputs are copied as unsigned drafts; you review and sign them for this product. The platform’s current SBOM can be taken over as the starting bill of materials (on by default, can be unticked): it is copied and marked taken over from the platform — vulnerabilities are correlated through it at once, but it is not an as-built SBOM. The delivered unit’s as-built SBOM remains the authoritative bill of materials: upload it or assemble it from components; it replaces the copy.

The kind can be changed later on the product page under Product kind; switching back to a series product clears the project facts.

A custom product with a platform does not count towards your plan’s product limit — it is one delivered unit of that platform. Custom products without a platform count like series products; see Plans and trial.

The Projects view

Section titled “The Projects view”

Projects (Monitor menu) lists every custom product grouped by customer: order, product, platform, handover and support status. It is a view over the product register, not a second set of records — a click opens the product, where SBOM, vulnerabilities, documentation and reports live. Custom products without a customer sit in their own group at the end.

What does not change

Section titled “What does not change”
  • Vulnerabilities are correlated per product through its own SBOM. A vulnerability in a platform component shows on every unit whose as-built SBOM contains that component. The platform’s page says how many custom products it is the platform for; with open findings, a hint reminds you to review the derived custom products. Nothing propagates automatically — you decide per unit.
  • Technical documentation, security passport, evidence pack and Article 14 reports belong to the product — that is, to the delivered unit.
  • The CRA Copilot knows the product kind and answers questions about custom products as guidance; the assessment remains part of your conformity process.

Practice case: Grandfathering for old machines? What the CRA requires for machines already shipped — the handover date as placing on the market, Article 69, and what is contested about retrofits.