Metrc (District of Columbia) Support Bulletin DC_IB_0090 announces new “Sales Delivery” functionality that lets DC-licensed transporters participate in retail delivery workflows inside Metrc, with enhancements going live February 25, 2026. This article explains what changed, how retailers and transporters should use the new Sales Delivery Hub, and what the update means for day-to-day delivery operations and compliance documentation.
Bulletin snapshot: what Metrc changed in Washington, DC
Bulletin number: DC_IB_0090
Distribution date: February 13, 2026
Effective date: February 25, 2026
Subject: New Sales Delivery Functionality
Reason: Sales delivery functionality now allows retail deliveries to be completed by transporters when the transporter (not the retailer) is physically delivering the order.
This update was released by Metrc in conjunction with the District’s Alcoholic Beverage and Cannabis Administration (ABCA).
What “Sales Delivery Hub” means in Metrc
In DC, when a license type is permitted to report patient sales deliveries, Metrc now supports assigning a separate transporter license to handle the physical delivery of a retail sale. The retailer still records the sales delivery in Metrc, but the transporter can now log key delivery-chain events in their own Metrc license using the new Sales Delivery Hub.
Practically, this creates a clearer division of responsibilities in Metrc between the license that sold the product (retailer) and the license that physically delivered it (transporter), while keeping the final completion/rejection decision with the retailer.
When to assign a transporter license to a sales delivery
You should use this workflow when the physical delivery is performed under a license other than the retailer’s license. In other words, if a transporter is doing the driving and handoff, the retailer should associate that transporter license to the sales delivery during creation.
Retailer workflow: recording a sales delivery with a transporter
1) Start the sales delivery from the Sales area
In Metrc, the retailer begins in the Sales area by opening the Sales Deliveries grid (found under Sales > Deliveries) and selecting the action to record deliveries.
Permission note: If a user cannot see the Deliveries option, a Metrc Administrator must grant the required permission before the user can create or manage sales deliveries.
2) Record the delivery details and assign the delivering license
When recording the sales delivery, the retailer enters the required delivery details and uses the new option to select an alternate license (the transporter) that will physically deliver the sale when it differs from the retailer’s license.
After required fields are completed, the retailer records the sales delivery, which creates the delivery record and makes it visible to the assigned transporter license in the Sales Delivery Hub.
Transporter workflow: using the Metrc Sales Delivery Hub
Accessing the Sales Delivery Hub
Transporters navigate to the Sales Delivery Hub from the Sales area (Sales > Delivery Hub). The hub displays deliveries where that transporter license was assigned as the delivering license.
Editing limitations: The transporter can update transporter-side details (for example, drivers and vehicles) but cannot change the delivery’s content that was recorded by the retailer.
Key delivery events the transporter records in Metrc
Once the retailer creates the sales delivery and the transporter begins the job, the transporter records the delivery lifecycle actions in Metrc:
• Acceptance of the delivery
• Departure from the retailer
• Arrival at the destination
• Verification of both recipient I.D. and payment
These actions create a structured, time-sequenced compliance record inside Metrc that supports ABCA oversight and internal auditing.
I.D. verification and payment type capture
During handoff, the transporter must verify the recipient’s I.D. In Metrc, the transporter uses the I.D. verification action and records the payment type using the provided selection.
Payment types captured in Metrc: Cash or Electronic
Operationally, this means transport teams should be trained not only on I.D. checking requirements, but also on consistently recording the correct payment type at the time verification is performed, since it becomes part of the delivery record.
Finalization: retailer completes (or rejects) the delivery
Even after the transporter finishes their steps in the Sales Delivery Hub, the retailer is responsible for closing out the sales delivery record in Metrc.
Completing a successful delivery
In the retailer’s Sales Deliveries grid, the retailer selects the completion action to finalize the sales delivery in Metrc.
Rejecting a delivery that cannot be completed
If the delivery cannot be completed, the retailer marks the delivery as rejected in Metrc and documents the reason.
How Metrc captures a rejection: The retailer uses the reject option, selects a return reason, and can add additional details in an optional note field.
Where completed deliveries go in Metrc
After completion or rejection, the delivery is finalized and appears under the “Inactive” view in the Sales Deliveries grid, supporting record retention and audit review.
Day-to-day operational implications for DC cannabis operators
Retailers: clearer accountability without losing control of the record
This change allows retailers to outsource the physical delivery to a transporter license while still keeping the retailer as the license responsible for creating and closing the sales delivery record. That structure helps reduce confusion about who should record what in Metrc, especially when deliveries are handled by a third party.
Transporters: Metrc becomes part of the delivery workflow
For transporters, this update makes Metrc a real-time operational system (not just a back-office system). Drivers or dispatch staff will need reliable access and internal procedures to ensure acceptance, departure, arrival, and I.D./payment verification are recorded consistently.
Compliance documentation improves, but only if teams use it correctly
Because the delivery record is split across two licenses, operators should align on handoffs: the retailer must create the delivery early enough for the transporter to see it in the hub, and the retailer must close the delivery after transporter steps are finished. If either party delays their part, deliveries can remain open longer than intended and create reconciliation work later.
Metrc data quality: why accurate retail identification still matters
While this bulletin focuses on delivery events, DC operators still need strong data hygiene around retail sale records and product identification. Clean labeling and accurate identifiers reduce delivery exceptions, returns, and post-delivery corrections.
DistruLabels is a 100% free tool for creating compliant packaging and retail labels, and it can help teams stay consistent with Metrc Retail ID-related workflows by producing clear, standardized labels for day-to-day operations.
For larger, multi-license operators that need end-to-end inventory, manufacturing, purchasing, and distribution visibility alongside compliance execution, DistruERP is Distru’s comprehensive Cannabis ERP platform built for complete supply chain management.
Where to get help and training
Metrc Support: Operators can access Metrc Support through the portal at Support.Metrc.com (and via the Support link inside Metrc). First-time portal access typically requires a username, the state and facility license number, and a valid email to set a password.
Metrc Learn and Metrc Expert: Metrc Learn offers interactive training accessible from within Metrc (via the Support area and training registration). Metrc Expert can be used inside the system to search help content, including “What’s New in Metrc” for Sales Delivery Hub updates.
