Metrc (Minnesota) Support Bulletin MN_IB_0061 (distributed 04/21/2026, effective ongoing) clarifies how to report off-premise sales as Sales Deliveries (not Sales Receipts) and how to use the Sales Delivery Hub to document delivery chain-of-custody events. This article explains the operational difference between receipts and deliveries, how to record a Sales Delivery Manifest in Metrc, what pricing fields mean, how transporters use the Delivery Hub, and how retail facilities finalize or partially return deliveries.
What the bulletin changes: Sales Receipts vs. Sales Deliveries
Metrc treats an in-store transaction and an off-premise delivery as two separate reporting actions, and they must be recorded differently to stay compliant.
Sales Receipt (in-store sale): Any transaction completed on the licensed premises should be reported as a Sales Receipt.
Sales Delivery (off-premise sale): Any transaction that will be transported to the customer should be reported as a Sales Delivery.
Critical rule: A Sales Receipt and a Sales Delivery should never be reported for the same transaction.
Day-to-day impact: Your POS and compliance workflow should decide at order time whether the sale is on-premise or delivered. If teams “double-report” (receipt plus delivery) or report a delivery as a receipt, inventory, revenue, and audit trails can become inaccurate and may trigger compliance issues during state review.
Sales Delivery Hub: what it is and why it matters
The Sales Delivery Hub is a Metrc feature designed to improve visibility and user experience for license holders transporting sales deliveries. It supports documenting key delivery milestones so the record of transport aligns with what happened in the field.
Enhanced visibility actions supported in the Hub: Acceptance of the product for delivery, departure from the retail facility, arrival at the destination, and verification of recipient ID and payment.
License-type limitation: Not all license types will see both “Deliveries” and “Delivery Hub” options in Metrc; availability depends on license type and statute.
Day-to-day impact: Operators should ensure the correct license is assigned as the transporter and that delivery staff can access the Hub. Otherwise, deliveries can be created but not properly acknowledged, verified, or completed in the intended workflow.
Employee permissions required for Delivery Hub access
Employees who report sales activity need the appropriate Metrc permissions. Only a Metrc Admin (or another user authorized to grant permissions) can assign these permissions.
Required permissions (Sales menu): Sales Delivery.
Required permissions (Sales menu): Hub.
Once granted, users will see the corresponding Deliveries and/or Delivery Hub options under the Sales dropdown, depending on license type.
How to record a Sales Delivery in Metrc (Sales Delivery Manifest)
Metrc requires a Sales Delivery Manifest to be created once a customer places an order for delivery. The bulletin frames this similarly to how a Transfer Manifest is required when transferring product between licensees: it creates necessary visibility while product is being transported off the licensed premises.
Where to start in Metrc: Navigate to the Sales area and open the Deliveries grid, then choose the action to record deliveries to create a Sales Delivery.
Customer identification requirement: Ensure required customer information is entered accurately, such as Consumer ID or patient number (as applicable).
Adult-use vs. medical note: Consumer deliveries are adult-use deliveries and patient deliveries are for authorized patients; a patient ID is not added for a consumer delivery.
Assigning the transporter: During entry, Metrc allows the delivering license to be assigned as the transporter (the license physically delivering the sale).
Day-to-day impact: Because deliveries move off-premise, customer identity fields and transporter assignment are not just “data entry”—they determine whether your delivery record supports who received the product and who transported it.
Pricing fields explained (how to enter delivery pricing correctly)
The bulletin distinguishes between “Total price,” “Price,” and “Discount Amount.” This distinction matters for consistent reporting, especially if your POS displays taxes, fees, and discounts differently than Metrc captures them.
Total price: The amount the consumer pays excluding sales tax and excluding any processing fees (pre-tax only). This should reflect the final price after discounts are applied.
Price: The listed shelf price of the product.
Discount Amount: The total discount applied to the Total price.
Example from the bulletin: If a single pre-roll has a base price of $10 and no discounts, the Total price entered is $10. If a $2 discount applies, the Total price entered is $8. Taxes are not added to the Total price entered into Metrc.
Day-to-day impact: Train staff to avoid entering post-tax totals into Metrc. If your POS shows “total due” including taxes/fees, you may need to reference the pre-tax, post-discount subtotal for accurate Metrc entry.
Using the Sales Delivery Hub as the transporter
Transporters access the Sales Delivery Hub from the Sales dropdown. In the Hub, the transporter license can see deliveries where it is listed as the transporter.
Edit limitation: The transporter license can edit transporter details but cannot edit the contents of the delivery.
Key delivery milestones to record in the Hub
The bulletin describes a practical, event-based workflow in the Hub for documenting delivery progress.
Accept: After the delivery has been physically accepted by the user transporting it, acknowledge acceptance in Metrc.
Depart: After acceptance, acknowledge the transporter’s departure from the retail facility.
Verify ID: During the delivery, verify the recipient’s ID and then record that verification in Metrc.
Payment Type: When verifying ID, the transporting user must select a payment type for the delivery (Cash or Electronic) before completing the verification action.
Day-to-day impact: This workflow creates a defensible timeline showing who took custody, when the delivery left, and that the recipient’s identity (and payment method) was verified before completion—information that is commonly scrutinized in delivery audits.
How to mark a Sales Delivery complete (retail facility step)
After the transporter verifies and completes their Hub steps, the retail facility must finalize the Sales Delivery in Metrc from the Sales Deliveries grid by using the completion action for that delivery.
Complete Delivery action: Finalize the delivery by confirming completion in the Complete Delivery action window.
If a delivery cannot be fully completed: returning product
If the Sales Delivery was unable to be completed as planned, the bulletin instructs users to record returns using the reject/return controls in the completion window.
Reject/return documentation: Use the reject package option to record what is being returned.
Verification field: Confirm the amount of product being returned.
Return Reason: Select a reason for the return from the provided dropdown.
Required Note: Add the additional details required to explain the return circumstances.
Finalization: Complete the Sales Delivery after documenting the return details.
Record status after completion: Once completed, the Sales Delivery is finalized and automatically moves to the Inactive tab in the Sales Deliveries grid.
Day-to-day impact: Returns and partial completions are common in real delivery operations (failed ID check, customer unavailable, changed order). Capturing the returned quantity, reason, and narrative note is essential for inventory accuracy and for explaining discrepancies during inspections.
Operational implications for cannabis operators
Align your POS workflow to Metrc reporting: Decide upfront whether the transaction is on-premise (Sales Receipt) or off-premise (Sales Delivery) and report only one in Metrc.
Assign roles clearly: Retail staff typically create the Sales Delivery Manifest and later complete it; transport staff use the Delivery Hub to document custody and verification events.
Train for the pre-tax pricing requirement: Ensure staff understand that Metrc delivery “Total price” is pre-tax and after discounts, which may differ from a POS “total due.”
Expect license-type differences: If users cannot see Delivery Hub options, confirm license privileges and state allowance rather than assuming a system error.
Tools that support Metrc-ready retail operations
DistruLabels (free): DistruLabels is a 100% free tool for creating compliant packaging and retail labels. For operators managing Metrc Retail ID workflows, consistent, compliant label creation supports day-to-day Retail ID execution by reducing label errors that can lead to inventory confusion at the point of sale and during delivery prep.
DistruERP (for larger operations): DistruERP is Distru’s comprehensive Cannabis ERP platform built for larger operators that need full supply chain management across cultivation, manufacturing, distribution, and retail operations, including tighter coordination between inventory controls, labeling, and compliance workflows.
Metrc support and training resources referenced in the bulletin
Metrc Support Portal: For help, use Support.Metrc.com or access Support from within the Metrc system. First-time portal setup typically requires your state selection, facility license number, username/email, and password creation.
Metrc Learn: Metrc Learn provides interactive training organized by facility-specific programs and courses. Access it via the Metrc Learn site referenced by Metrc.
Bulletin reference: Metrc Support Bulletin MN_IB_0061, “Sales Receipts vs. Sales Deliveries & Sales Delivery Hub,” distribution date 04/21/2026, effective ongoing.
