Most dispensary buyers do not live in software. They live in their inbox. Vendor reps confirm orders by email. Reps send price sheets by email. The COA always arrives by email. And then the buyer has to context-switch into a procurement portal to log all of it — which is why so much of it never gets logged.
So we built the AP workflow around the inbox instead of the portal. If you run a dispensary on ShelfSpace, your buyers can manage cannabis deliveries by email end to end. Forward a vendor invoice, get a delivery ID back, reply with updates as the situation changes. The portal is still there if you want it. Most days, your buyers won't open it.
The Inbox Is the System of Record
Every ShelfSpace tenant gets a dedicated AP email address — something like ap@yourshop.shelfspace.pro. Behind that inbox is ShelfiQ, our AI that handles invoices, delivery records, and confirmations on your team's behalf.
When a buyer forwards a vendor invoice to that address, three things happen in seconds:
- We parse the PDF — vendor, invoice number, line items, total.
- We match the vendor to your existing partner list.
- We create a delivery record in Ordered status and reply with a permanent DEL-XX ID.
That DEL-XX ID lives in the subject line for the rest of the conversation. Every reply in the same Gmail thread updates the same delivery — no second portal, no second source of truth.
What a Real Buyer Email Looks Like
Here's the kind of message a buyer actually sends. Not a clean form submission. Just the way you'd write it to a coworker.
Attached invoice for Green Leaf Co. ETA is Tuesday 5/6 between 1-3pm.
Delivery DEL-301 has been created for Green Leaf Co — $8,440.00. ETA set to 05/06/2026. I'll let the receiving team know to expect a 1–3pm window.
That's it. Two minutes of work, one email, a delivery now exists in the system with the invoice attached and an ETA on the calendar. No portal login. No copy-pasting line items.
Updating Deliveries Without Leaving the Thread
Stuff changes. The vendor pushes the delivery a day. The driver calls and says they're missing two boxes. The invoice your rep sent had the wrong total. Buyers handle five of these a day, and every one of them used to be a manual portal update.
Now it's a reply.
- "The delivery date is now Wednesday."
- "Updated invoice attached." (with the new PDF)
- "Package count should be 12."
- "New invoice number is INV-228491."
ShelfiQ confirms the change in the same thread. The activity log captures who said what and when. If your finance team or a vendor ever asks how the order amount went from $4,217.50 to $4,103.00, the answer is sitting in the email trail.
Notes for the Receiving Team
This is the one nobody else does well. Buyers know stuff the dock crew needs to know. The vendor mentioned one box was opened in transit. This drop is a $0 sample, don't bill it. The vendor pre-flagged a short on the concentrate lots — don't mark it missing.
Today, that information lives in a Slack message, a Post-it on the receiver's monitor, or — most often — nowhere. Then the receiver flags a "discrepancy" the buyer already knew about, the vendor gets pinged, and now there's an unnecessary cleanup conversation.
With email-driven deliveries, the buyer just types the note into the thread:
Note for receiving: vendor said one of the boxes was opened in transit — count the units inside before signing.
Recorded the note on DEL-301 for the receiving team.
ShelfiQ pins the note to the delivery's procurement-notes panel and tags it with the date and the buyer's name. When the dock crew opens DEL-301 to receive it, the note is the first thing they see.
New Vendors and Vendor Aliases
Sometimes the invoice is from a new brand. Sometimes the vendor's PDF spells the company differently than the partnership record (legal name vs. DBA, parent company vs. brand). When ShelfiQ can't match a vendor confidently, it asks.
The buyer just replies in plain English: "That's Cypress Holdings" — and we link it permanently so the next invoice from the same sender matches without us asking again. Or, if it really is a brand-new vendor: "New vendor, legal name is [Whatever], LLC" — we create the vendor record, the partnership, and the delivery in one move.
The point is the buyer never has to leave the inbox to deal with vendor cleanup. Even non-cannabis vendors — landlords, insurers, accountants — go through the same workflow.
Closing the Loop: Receipt Confirmations
The last piece — and the one that makes the inbox truly the system of record — is what happens when the order actually shows up at the dock. The receiving team confirms the delivery in the dashboard or by scanning a manifest. ShelfiQ then sends a receipt-confirmation email back into the same Gmail thread, addressed to the original buyer and any other buyers on the team.
Vendor name. Date received. Who received it. Invoice number. Order amount. Packages received versus packages ordered. Any discrepancies the dock crew flagged.
That email closes the loop without anyone opening a portal. The whole buyer team has visibility, the original thread is now a complete record from order to receipt, and your accounting team has a paper trail they can actually read.
What This Doesn't Cover
Email is great for the things buyers do every day. It's not great for the things that need extra security. So we deliberately keep some workflows portal-only:
- Banking information changes
- Final payment approvals
- Settlement disputes
- User access and permissions
Those still go through the portal with MFA. Everything else — the day-to-day procurement work that fills a buyer's inbox — runs on email.
Why It Matters
The dispensaries we work with don't have time to retrain a buying team to use a new tool. They have time to forward an email. By meeting buyers where they already work, we get something most procurement systems never get: actual usage. Deliveries that get logged. Notes that get captured. ETAs that stay current. A clean record of every order from "here's the invoice" to "we received 24 of 24."
The best system is the one your team already uses every day. For most dispensary buyers, that's their inbox.
If you want the full step-by-step walkthrough — every command, every example, every edge case — see our doc on how to manage deliveries by email. For the dashboard side of the same workflow, read our case study on how a single dispensary replaced its delivery spreadsheet. And for the inbound side — vendor questions to your AP team — read our case study on how ShelfiQ handled 47 of 52 vendor emails in one week.
Or just talk to us. We'll show you what your buyers' week could look like by next Monday.