Genuine Check belongs at the start of the arrival workflow because it gives the user a device-state reference before other setup notes accumulate. This should be written as a neutral first-step process, not as a channel concern or a sales argument.
Arrival workflow starts with visible records
Before connecting the device, record the visible arrival context: date, device model, package observation, and accessory state. Keep this separate from device confirmation. The first app-led step can then focus on Ledger entry and device state.
The authenticity checking guide gives a structured way to compare entry, package observation, device state, and local record.
Genuine Check should be read through Ledger Wallet
Use the known Ledger Wallet entry before starting the check. The app gives the workflow context, while the device state gives the hardware-side reference. If the app path is unclear, stop and confirm the app entry rather than switching to another route.
- Record package observations before device-state checks.
- Use Ledger Wallet as the entry path for Genuine Check.
- Keep recovery phrase and PIN out of arrival notes.
Device state and service context are separate
Genuine Check can support later service conversations, but it is not the same as a service promise. Keep the result as a device-state record. The entry verification checklist helps keep the check focused on source path, device screen, and local record.
The first-step record keeps later work clean
End with a short first-step record: date, model, Ledger Wallet entry, device-state result, and next setup step. This keeps the future-scheduled article useful without creating anxiety about purchase or delivery channels.
