This Metrc (Nevada) support bulletin (NV_IB_0110) announces an enhancement to transporter vehicle records: you can now store a Vehicle Registration Number directly in Metrc. This article explains what the new field is, where it appears across transfers and sales deliveries, and what Nevada operators should do to keep daily transportation workflows audit-ready.
Metrc bulletin details (Nevada)
Bulletin Number: NV_IB_0110
Distribution Date: 02/06/2026
Effective Date: 02/10/2026
Subject: Addition of Vehicle Registration Number
Reason: Provide the ability to add a vehicle’s registration number to vehicle records to better support transporter compliance and state-specific vehicle identification requirements.
What changed in Metrc: Vehicle Registration Number field
Metrc has added a Registration Number field to transporter vehicle records. This field is designed to capture the vehicle identifier your state requires, which may be described as a registration number, certification number, or VIN, depending on the regulator and program rules.
Metrc continues to store core vehicle descriptors (such as make and model), and this new identifier helps align what’s in Metrc with what an inspector expects to see on paperwork and in vehicle documentation.
Field rules and data validation you should know
Optional field: The Registration Number is optional in the vehicle record itself, but it may become required in certain workflows depending on how Nevada (or a specific transfer type) is configured.
Character limit: Up to 100 alphanumeric characters.
Uniqueness constraint: A Registration Number can only be associated with one active vehicle at a time in Metrc, which helps prevent duplicate identifiers across active vehicle records.
Required permission to edit transporter vehicles
To add or update a vehicle’s Registration Number, a licensed user must be granted the permission to manage transporters (i.e., the ability to manage transporter-related records in Metrc). If your staff cannot see or edit transporter vehicle details, it is typically a role/permission issue rather than a system error.
Where the Registration Number appears in transfers
For any transfer type (Licensed or External) that is configured to capture transporter information, Metrc will display the vehicle’s Registration Number alongside the rest of the transporter vehicle details during the transfer workflow.
This matters because some state configurations can make transporter/vehicle fields conditionally required at the time of creating or completing a transfer. If Nevada requires an identifier for the vehicle used in transport, the Registration Number field is the place to store it so it can surface consistently in transfer actions and documentation.
Transfers Hub and transfer manifest visibility
The Registration Number also displays in the Transfers Hub as part of the vehicle information shown for transporter details.
The transfer manifest includes the vehicle registration information alongside other vehicle fields, improving consistency between what is dispatched, what is received, and what is presented during inspections.
Where the Registration Number appears in sales deliveries
Metrc has also extended this field into Sales Deliveries, so the Vehicle Registration Number appears with the delivery’s vehicle/transporter information.
The Sales Delivery Hub reflects the same vehicle registration information in delivery listings and transporter detail views, supporting clearer audit trails for delivery activity.
Practical operational impact for Nevada operators
Better audit readiness: Capturing the state-required vehicle identifier in Metrc reduces gaps between operational records and what regulators verify during a compliance review.
Less reliance on external workarounds: Operators no longer need to maintain separate spreadsheets or internal notes to track vehicle identifiers that don’t fit cleanly into make/model fields.
Cleaner transportation records: The “one Registration Number per active vehicle” rule encourages more disciplined vehicle record management, especially when vehicles are retired, replaced, or temporarily removed from service.
Fewer delays at transfer time: If a transfer workflow requires transporter details, having vehicle records fully populated ahead of time helps prevent last-minute edits that can slow dispatch, acceptance, or manifest generation.
Related compliance tooling: DistruLabels and DistruERP
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels. It helps operators generate labels that support Metrc Retail ID compliance by keeping key label data organized and ready for printing as products move through inventory and retail workflows.
DistruERP: For larger multi-license or high-volume operations, DistruERP is Distru’s comprehensive Cannabis ERP platform designed for complete supply chain management, helping teams coordinate inventory, production, transfers, and compliance processes across facilities.
Metrc support and training resources
Metrc Support: Submit and track a case in the Support portal or call 877-566-6506.
Support hours: Monday–Friday, 8 a.m. ET–10 p.m. ET.
• Saturday 10 a.m.–8 p.m. ET
• Sunday voicemail or portal only
Support portal access note: First-time portal access typically requires a username (established when logging in), the state, facility license number, and a valid email to set a password.
Metrc Learn: Metrc’s on-demand training platform provides interactive education on system functionality and workflow efficiency. Access it directly or via the Support drop-down in Metrc.
Metrc Expert: Use the widget icon in the lower right of Metrc to open the knowledge base for step-by-step guides and searchable help content.
Metrc.com: Visit your state’s partner page for training links and program resources at https://www.metrc.com/.
