In This Article:

Ask AI about this article
OpenAI
Claude
Perplexity
Google Gemini

Metrc Oregon Adds Vehicle Registration Number Field

Oregon
February 10, 2026
Link to Metrc Bulletin
TL;DR

• Metrc Oregon now lets transporters add a Registration Number field to vehicle records for better audit readiness.

• The identifier appears on transfer manifests and delivery records, reducing manual reconciliation during compliance reviews.

• Registration Numbers must be unique per active vehicle and support up to 100 alphanumeric characters.

Metrc (Oregon) Bulletin OR_IB_0072 (distributed 02/06/2026; effective 02/10/2026) introduces a new Vehicle Registration Number field for transporter vehicle records, and explains where that identifier will appear across transfers, manifests, and sales deliveries for compliance visibility.

What changed in Metrc Oregon vehicle management

Oregon Metrc vehicle records now include a Registration Number field. Metrc designed this enhancement to help transporters meet state-specific vehicle identification requirements in a single system of record, without relying on external logs or workaround fields.

The new Registration Number field is intended to support multiple state-required identifiers, including vehicle registration numbers, certification numbers, or a VIN, depending on what Oregon requires for a given workflow or what a regulator expects to see during an audit.

Why the Vehicle Registration Number field matters for compliance

This update improves day-to-day compliance operations by making transporter vehicle identification more complete and easier to verify.

• Improves data accuracy and audit readiness by standardizing a key vehicle identifier inside Metrc

• Reduces manual recordkeeping by eliminating the need for external tracking spreadsheets or notes

• Improves regulator transparency by ensuring the vehicle’s identifying number is visible wherever transporter details are captured

Permissions: who can add or edit the registration number

To add or update a vehicle’s Registration Number, a user must have permission to manage transporters in Metrc. If your team cannot see or edit transporter vehicle records, confirm your Metrc user role permissions with your Metrc administrator before attempting updates.

Field rules and validation in Metrc

Optional field: The Registration Number is optional at the vehicle record level, although Oregon or a specific transfer configuration may still make it effectively required in certain workflows.

Character limit: The field allows up to 100 alphanumeric characters, supporting a wide range of formats used by states and fleets.

Uniqueness constraint: A single Registration Number can only be associated with one active vehicle at a time. Operationally, this means you should retire or deactivate old vehicle records before reusing an identifier on a replacement vehicle, where applicable.

Where the registration number appears during transfers

For any transfer type (Licensed or External) that is configured to capture transporter information, Metrc will display the Registration Number alongside the rest of the transporter’s vehicle details in the transfer action window. If Oregon configuration requires this field for a transfer type, Metrc may prompt users accordingly during transfer preparation.

Within the Transfers Hub, the vehicle registration information also displays as part of transporter and vehicle details, improving internal review and making it easier to confirm the correct vehicle identifier before finalizing a transfer.

The transfer manifest will also include the vehicle registration information alongside other vehicle fields. This helps ensure the document that travels with the shipment reflects the same vehicle identification that is stored in Metrc.

Where the registration number appears in sales deliveries

Metrc Sales Deliveries now display the Vehicle Registration Number as part of the vehicle information shown to users during delivery workflows. The Sales Delivery Hub was also updated to include the vehicle registration information within transporter details, helping teams verify vehicle identity during dispatch and reconciliation.

Practical implications for day-to-day cannabis operations

If you operate or manage transportation in Oregon, this change impacts how you maintain fleet records and how you prepare transfer documentation.

• When onboarding a vehicle, capture the identifier Oregon expects your operation to use (registration number, certification number, or VIN) so the right value is available downstream

• When swapping vehicles for a scheduled pickup, confirm the correct vehicle record (and Registration Number) is selected so transfer records, hubs, and manifests remain consistent

• When replacing vehicles or plates, manage record lifecycle carefully to avoid conflicts with the “one Registration Number per active vehicle” rule

How Distru supports compliant operations alongside Metrc

DistruLabels is a 100% free tool for creating compliant packaging and retail labels, helping operators maintain accurate label data and support Metrc Retail ID compliance as products move into retail-ready workflows.

For larger, multi-department operators that need broader operational control, DistruERP is Distru’s comprehensive Cannabis ERP platform for end-to-end supply chain management, designed to complement compliant Metrc tracking with connected inventory, manufacturing, and fulfillment workflows.

Metrc resources referenced by the bulletin

Metrc Support: Submit and track a case via the Metrc 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

Metrc Learn: On-demand training available directly or via the Support drop-down in Metrc.

Metrc Expert: In-app knowledge base accessible from the widget icon in the lower right corner of the Metrc interface.

Metrc.com: State partner pages provide training links, state resources, and updates at https://www.metrc.com.

The AI cannabis library

Free skills to put AI to work on your inventory, compliance and costing, and guides on where it actually saves time.

SKILL
Inventory Management

Distru Expiring Inventory

See stock about to expire, who already buys it, and a promo email draft to review.

SKILL
Compliance

Cannabis Inspection Readiness

Turn an upcoming state inspection into a checklist, binder index and gap list.

SKILL
Compliance

Cannabis Transfer Manifest Precheck

Check a B2B transfer before the driver leaves and get GO or HOLD per line.

SKILL
Purchasing

Cannabis Replenishment Planner

Turn sales and on-hand exports into a reorder plan and a draft PO by vendor.

SKILL
Compliance

Cannabis State Rules Lookup

Get a cited, dated answer to a state cannabis rule question.

SKILL
Operations

Cannabis Staff Scheduling Planner

Build a shift schedule that matches demand and stays inside your labor budget.

SKILL
Cultivation

Cannabis Harvest Yield Analysis

See which rooms and strains actually make money, from your own harvest data.

SKILL
Compliance

Cannabis Traceability Reconciliation

Find out why your physical count doesn't match Metrc or BioTrack.

SKILL
Compliance

Cannabis SOP Generator and Trainer

Turn process notes into an inspection-ready SOP and a staff training packet.

SKILL
Finance and COGS

Cannabis Batch COGS Calculator

Find out what a batch really costs per finished unit, line by line.

AI GUIDE
Blog

Why the Harness Matters More Than the AI Model

Two products can use the exact same AI model and perform completely differently. Here's why the harness, not the model, usually explains why.

AI GUIDE
Blog

What Is an Agent Harness? A Plain-English Primer

An AI model alone can't do much. The 'harness' around it is what makes it useful. Here's what that actually means, no jargon required.

AI GUIDE
Blog

Why MSOs Need an AI Strategy Before More Software

Adding another point solution won't fix an MSO's AI readiness problem. Here's why the data foundation has to come first.

AI GUIDE
Blog

The Supply Chain Buyer's Guide to AI Agents and MCP

Evaluating AI agent features in supply chain software? Here's a practical buyer's checklist, including what MCP means for your evaluation.

AI GUIDE
Blog

AI in Supply Chain: What's Hype, What's Working

AI in supply chain gets a lot of hype. Here's an honest look at what's actually delivering results in 2026, and what still needs a person.

AI GUIDE
Blog

Where AI Agents Fit in Cannabis Compliance

Not every step of your compliance workflow is a fit for AI. Here's a clear map of where it helps, and where it should stay hands-off.

AI GUIDE
Blog

The Skills Ops Teams Will Need When AI Agents Arrive

AI agents are coming for repetitive ops tasks in cannabis. Here's what your team needs to get good at instead, starting now.

AI GUIDE
Blog

What Happens When AI Gets Access to Your ERP

Giving an AI tool access to your cannabis ERP isn't all-or-nothing. Here's what real, scoped access looks like, and what to watch for.

AI GUIDE
Blog

AI and 280E: Where Automation Actually Saves Money

280E just got more complicated for mixed medical and adult-use operators. Here's where automated cost tracking actually helps, and its limits.

AI GUIDE
Blog

Can AI Forecast Wholesale Demand Better Than Excel?

Your wholesale forecast spreadsheet has limits. Here's what AI-assisted forecasting can actually add, and where a spreadsheet still wins.

AI GUIDE
Blog

Should Your Cannabis Business Have an AI Strategy?

You don't need to be an AI company to have an AI strategy. Here's a practical starting point for cannabis operators, no hype required.

AI GUIDE
Blog

What Is Claude Cowork? Could It Kill Data Entry?

Claude Cowork lets AI work directly in your files and tools. Here's what that means for the data entry eating your cannabis team's week.