1
Upload PDFs
Drop one COA PDF or a batch into PDF Intake. The app reads each certificate, extracts the target METRC package ID, and places ready files into the Upload Queue.
2
Review the queue
Rows marked Ready can be sent. Use Details to inspect the parsed package ID, parent package context, client/license, sample type, and any parser warnings.
3
Upload All
Upload All sends every ready row directly. A centered progress modal shows the current PDF plus a live upload console while the batch runs. Only one METRC upload run is allowed at a time across all users; if another user is already uploading, the app will say another METRC upload is running and ask you to try again shortly. The app spaces METRC communication, attaches each PDF to the lab result row, verifies the document, and marks rows SENT!, FAILED, or SKIPPED.
4
Retry failed PDFs
If a PDF fails, its server-stored copy appears in Past Failed Uploads. This is especially useful for retrying R&D samples while waiting for their lab result rows to appear in METRC, which is the usual reason these uploads fail. Use Attempt reload of past failed uploads to load those PDFs back into the queue and try them again.
5
Use the console
The METRC Console explains what the app is doing in plain language. It is the first place to check if a file is blocked, skipped, or fails because METRC has no lab result row.
6
Check history
History shows upload attempts with client, status, file, METRC ID, and product. Click any history row to see full upload details, including failure reasons, lab result IDs, document IDs, and the stored workflow log. Successful METRC IDs are excluded from the failed retry list.
7
Email summary
Email summary is optional and can be turned off under Upload All. Email Recipients controls who receives the Upload All completion summary when that option is enabled. The email includes counts, package IDs, clients, products, documents, and failure reasons.