Metrc (District of Columbia) Bulletin DC_IB_0091, distributed 2/13/2026 and effective 2/25/2026, announces a new Metrc Transfers Hub experience that changes how transporters and receiving facilities view and update transfer manifest activity. This article explains where to find the Transfers Hub, what transporters can edit, what each action button records (including layover handling), how rejected packages create return transfers, and what the new grid indicators mean for daily compliance operations.
What’s new: the Metrc Transfers Hub in Washington, DC
The Transfers Hub is a new grid available under the Transfers area in Metrc’s main navigation. Once a transfer is registered, both the designated transporter and the destination licensee can see the transfer details that were entered on the manifest.
For DC operators, the key change is that the designated transporter now has a centralized place (the Transfers Hub) to record key custody and movement events during a route, while the destination licensee retains visibility into the full manifest information.
Who can see and update transfer information
Visibility and actions in the Transfers Hub depend on permissions and on whether your license is assigned as the transporting license for that manifest.
Designated transporter: Can view the transfer in the Transfers Hub and can perform specific action-button updates during the route. The transporter can also edit limited manifest details (described below).
Destination licensee: Can view the manifest information after the transfer is registered, but the action buttons described in this bulletin are specifically presented for users listed as the transporting license.
Transfers Hub action buttons for transporters
Users with Transfers Hub permissions will see selectable buttons on each transfer when they are listed as the transporting license. Each button represents a discrete transfer event that can be reported in Metrc.
Edit: Allows the transporter to update estimated departure time, estimated arrival time, driver information, and vehicle information.
Accept: Intended to be used when the transporter accepts physical custody of the packages for delivery.
Depart: Intended to be used when the transporter departs the originating facility after taking custody.
Check-In: Applicable only when a layover is selected and the transfer will be stored at the transporter’s facility for a period of time. Check-In indicates the transporter arrived at the layover facility.
Check-Out: Applicable only for layovers. Check-Out indicates the transporter is leaving the layover facility to continue the planned route.
Arrive: Indicates the transporter arrived at the destination facility.
How the button sequence affects your compliance record
The buttons are presented in the order they are intended to be used from top to bottom. After selecting a button, all buttons that come before it disappear for that transfer.
Practically, this means the order you click matters for the timestamps Metrc captures. If a transporter selects Arrive before Depart, the Depart option will no longer be visible and no departure date/time will be recorded. Similarly, clicking any button after Edit removes Edit as an option, so teams should confirm driver/vehicle and estimated times before recording downstream events.
Metrc does not require every button to be used
Metrc does not enforce that transporters must select every action button during a route. However, in day-to-day DC operations, using these actions consistently helps create a clearer chain of custody and a stronger internal audit trail for dispatch, driver management, and regulatory inquiries.
Return transfers when packages are rejected
If the destination facility rejects a package on a transfer, the originating facility can access the return manifest from the Rejected tab.
Within the Rejected transfers grid, the originating licensee can use the Transporters option to open an Edit Return Transporters window and confirm or revise return-trip details.
What you can confirm or update for the return: Transport license number, driver, and vehicle information.
Once the return transport details are modified, the return transporter will be able to access the return manifest in their Transfers Hub and use the same set of action buttons described above to record custody and movement events.
Transfers Hub grid indicators: destination icon and direction
Licensees with permission to access the Transfers Hub will see an icon in the Destination column and a Direction column.
Destination icon: Used to identify the point of delivery for each transfer.
Direction: Indicates whether the designated transporter’s movement is Outbound or Inbound for that transfer.
Operationally, these indicators help dispatch teams and compliance staff quickly interpret whether a transfer is headed out for delivery or coming inbound, reducing confusion when the same transporter license manages multiple routes or return activity.
Practical implications for DC cannabis operators
Driver and vehicle accuracy matters more in real time: Because Edit becomes unavailable once later actions are recorded, transport teams should verify driver and vehicle details before logging custody or movement events to avoid mismatches during roadside or facility checks.
Layover workflows must be deliberate: Check-In and Check-Out are only applicable when a layover is selected. If your DC transport model includes overnight storage or staged deliveries at the transporter facility, ensure your SOPs define when layovers are selected and when those timestamps should be recorded.
Return logistics need coordination: When a destination rejects packages, the originating facility controls confirmation or updates to the return transporter details. Tight coordination prevents delays and ensures the correct license, driver, and vehicle are associated to the return manifest.
Buttons are optional, but consistency reduces risk: Even though Metrc doesn’t force every action, consistent use supports clearer documentation of custody transitions, which is valuable for internal controls, incident response, and demonstrating due diligence to regulators.
Supporting tools: labeling and ERP workflows
While this bulletin focuses on transfers, many DC operators pair strong transfer records with strong labeling discipline to reduce downstream compliance issues.
DistruLabels: DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams stay aligned with Metrc Retail ID compliance by producing scannable, standardized labels for retail-facing operations. Learn more at https://www.distru.com/.
DistruERP: For larger, multi-department operations that need end-to-end supply chain management, DistruERP is Distru’s comprehensive Cannabis ERP platform, supporting inventory, production, sales, fulfillment, and compliant operations that complement Metrc-tracked workflows. Learn more at https://www.distru.com/.
Metrc support and training resources
Metrc Support Portal: Visit https://support.metrc.com/ or use the Support link inside the Metrc system to access the portal. First-time access typically requires a username (created when logging in), your state selection, your facility license number, and a valid email to set a password.
Metrc Learn: Metrc Learn provides interactive training on system functionality to build user skills and improve workflow efficiency. In Metrc, navigate to Support and select Sign up for Training to register.
Metrc Expert: Use the Metrc Expert icon within the Metrc system to search topics or enter questions for additional guidance.
