1. Scan the carrier
A service card stays with the vehicle. An industrial sticker stays on the system. The customer scans that carrier. Object access opens for that object only — not for the whole business.
The visible PINNEX ID labels the object. It is not a secret. Each object has its own PIN, which is not printed on the public-facing card. No protected content appears without the PIN.
2. Enter the 6-digit PIN
After every scan PINNEX requires the 6-digit PIN. This applies to every public object. The PIN does not replace a business account or an internal note.
No customer account is required for the basic flow. After a successful PIN, an optional account can — depending on pilot scope — save several objects. The account never replaces the PIN.
When a card is replaced, the old carrier, its token and dependent sessions are revoked and a new carrier is assigned to the same vehicle. The Asset PIN remains a separate credential and is renewed in a controlled process when security or handover requires it. The previous PIN and access are invalidated; the new owner receives a new Asset PIN. The vehicle retains its technical history, completed work and dates, and the professional service provider. Currently permitted, sanitised document copies are intended to form part of the transfer; the seller can exclude them. Confirmed repair costs transfer only with separate seller consent that is off by default. Both parties see and confirm the exact transfer manifest. Personal data, private messages, AI chats, consents, internal garage notes and unsanitised originals do not transfer. This handover model is in pilot; full production implementation and acceptance remain open.
3. Choose the next action
The preview shows six typical actions. In the pilot, available actions are configured by package, vehicle and permission: for example appointment, fault, callback, history, approved documents and released invoice information.
Technical history and approved invoice metadata stay separate. Original invoices, personal data and internal notes are not released automatically.
An asset-specific data assistant is in development for the Garage pilot. It uses only current, approved and versioned sources for that vehicle, cites the source or refuses an unsupported answer. Manufacturer manuals and general internet sources are not currently approved as active knowledge sources. The assistant does not make an autonomous diagnosis or submit a request, booking or payment without explicit confirmation. No production AI service is active on this marketing site.
What the business sees
Businesses work in the company portal with email and password. Access is set up during onboarding, not as a public login on this website. In an active pilot the request arrives object-linked.
PINNEX does not collect workshop payments or issue workshop invoices. TWINT is planned; a future payment is intended to go directly to the garage. RechNex is only a possible, separate integration candidate. The payment provider, invoice source and reconciliation are not activated.
Garage is first (vehicles). Anlagenpass is second (heat pump, PV, installation). See Garage, Anlagenpass, Glossary, FAQ.