This update applies to Metrc (Oregon) and is documented in Metrc Support Bulletin OR_IB_0072 (distributed 02/06/2026, effective 02/10/2026). It introduces a new optional “Registration Number” field on transporter vehicle records and surfaces that value in key transfer and delivery workflows, helping licensees meet evolving state vehicle-identification requirements and strengthen audit readiness.
Bulletin summary: new vehicle Registration Number field
Metrc has enhanced vehicle management so transporters can record a vehicle’s registration identifier directly on the vehicle record. The new “Registration Number” field is designed to support different state-required identifiers, including a registration number, certification number, or VIN, depending on how Oregon and related workflows are configured.
Metrc vehicle records already support core vehicle details (such as make and model). Adding a dedicated registration identifier improves data accuracy and reduces the need for off-system spreadsheets or workarounds when regulators expect a specific vehicle identifier to be consistently recorded and reportable.
Why this matters for transporter compliance in Oregon
Transporter details are a common audit touchpoint. When a regulator reviews transfer activity, they often need to confirm that the vehicle used for transport matches what was authorized and recorded at the time of movement. By capturing a standardized identifier in Metrc, operators can present clearer documentation, reduce manual reconciliation, and improve consistency across manifests, transfer records, and delivery records.
How the Registration Number field works in Metrc
Permissions required
To add or edit a vehicle’s Registration Number, a licensed user must have permission to manage transporters in Metrc. If your team members cannot see or update transporter vehicle records, an administrator should review role-based permissions before the effective date.
Field rules (what Metrc will and won’t allow)
- Optional field: The Registration Number can be left blank when creating or updating a vehicle record.
- Length and character set: Up to 100 alphanumeric characters.
- Uniqueness for active vehicles: A Registration Number can only be associated with one active vehicle at a time, preventing the same identifier from being reused across multiple active vehicle records.
Operationally, the “one active vehicle” rule means you should deactivate or update outdated vehicle records before reusing an identifier (for example, if a vehicle is retired and the plate or identifier is reassigned in your internal fleet system).
Where the Registration Number appears during transfers
For Licensed Transfers and External Transfers that use a transfer type configured to capture Transporter Information, Metrc will display the vehicle’s Registration Number alongside the rest of the transporter vehicle information in the transfer action window.
Although the field is optional on the vehicle record, Metrc notes that state requirements may make it required in certain workflows. In practice, this means an Oregon operator may encounter scenarios where a transfer cannot be completed until transporter vehicle details (including this identifier) are provided, depending on configuration and regulatory expectations.
Transfers Hub and manifest visibility
The vehicle Registration Number is also displayed in the Transfers Hub as part of the transporter/vehicle details. In addition, the transfer manifest will show the vehicle registration information alongside other vehicle fields, helping ensure the document matches what is recorded in Metrc at the time of transport.
Where the Registration Number appears in Sales Deliveries
Metrc has also updated Sales Deliveries so the Vehicle Registration Number is visible in delivery workflows where transporter/vehicle details are captured. The Sales Delivery Hub and the transporter details view now include this registration identifier, improving traceability for delivery operations and simplifying internal review when reconciling deliveries against vehicle logs.
Day-to-day operational impact for cannabis licensees
For most teams, this change is straightforward but important:
- Fleet setup and maintenance: When adding new vehicles (or cleaning up existing vehicle records), you can now store the key state-relevant identifier directly in Metrc, reducing reliance on separate fleet documents during an audit.
- Dispatch and manifest prep: Before generating or finalizing transfers and deliveries, confirm the correct vehicle record is selected and the Registration Number reflects the actual vehicle used.
- Fewer last-minute corrections: Because the identifier appears throughout transfer and delivery hubs and on manifests, errors can be spotted earlier—reducing rework and helping avoid compliance friction during transport.
Related compliance tooling: labels and ERP alignment
While this bulletin focuses on vehicle data, transport compliance often intersects with packaging, labeling, and retail readiness. DistruLabels is a 100% free tool for creating compliant packaging and retail labels and can help teams stay aligned with Metrc Retail ID requirements by producing consistent, compliant label outputs tied to the product and retail identifiers you manage in your workflow.
For larger, multi-department operations that need full supply chain control (purchasing, production, inventory, sales, fulfillment, and compliance workflows), DistruERP is Distru’s comprehensive Cannabis ERP platform built to support end-to-end operational management alongside Metrc reporting needs.
Getting help from Metrc resources
If you need assistance updating permissions or understanding how transporter details are configured in your Oregon environment, contact Metrc Support through the Support portal or by phone at 877-566-6506. Metrc also provides training and knowledge resources through Metrc Learn and the in-app Metrc Expert knowledge base. For additional state-specific links and guidance, visit https://www.metrc.com/.
