Single-store consignment is one set of operational problems. Multi-location consignment is a different set, but it's not the operational nightmare most multi-store operators assume it will be. The trap is to imagine that bringing consignment to a second, third, or fifth store means doing all the vendor onboarding work N times. It doesn't have to. The platform was designed around multi-location retailers from day one, and the rollout work scales with the number of vendor relationships you have, not with the number of stores you have.
Here's how rolling out consignment across multiple cannabis dispensary locations actually works on ShelfSpace, the three patterns that work in practice, and what changes operationally when you go from one store to many.
The retailer group: one business, multiple stores
If you run more than one cannabis dispensary under common ownership, your business sits on the platform as one retailer group — a parent that holds multiple store records. Each store has its own retailer ID, its own Metrc license, its own POS connection, its own bank account, and almost always its own legal entity for tax purposes. But the platform knows they're part of one group, and operations that should reach across stores — user permissions, vendor partnerships, group-level reporting — are aware of the group relationship.
One vendor onboarding, every store covered
The mechanics: when you add a new consignment vendor at any one store in your group, the platform looks up the retailer group ID, finds every sibling store in the group, and creates the same partnership at each one. Stores that already have an active partnership with that vendor are skipped — no duplicates, no overwrites. Defaults like payment terms, return policy, and co-marketing discount carry through from each store's own configured defaults so the propagation respects per-store customization where it already exists.
What this means for the rollout: you do the vendor conversation once. You negotiate the splits and discount cap with the vendor once. You configure the partnership at one store once. Two minutes later, every other store in your group has the same vendor ready to ship — same splits, same discount cap, same defaults — without you logging into each store separately.
Onboarding effort scales with the number of vendor relationships, not the number of stores. One vendor conversation covers your whole group.
Per-store vs uniform terms — when each makes sense
The default behavior is uniform: when a partnership propagates, every store gets the same starting terms. That's the right answer most of the time. Your vendor expects to be paid the same way at every one of your locations, and your accounting is easier when the settlement math is consistent across stores.
But the platform doesn't lock you into uniformity. Each store-vendor partnership is its own record with its own settings — Master Vendor Split, Operational Discount Budget, per-category splits. You can adjust any of them at any store independently. Two reasons this matters in practice:
- Local economics differ. A vendor whose product moves at premium pricing at your downtown flagship may not move the same at a suburban location. Different sell-through velocity can justify different splits without renegotiating the whole relationship — the downtown store keeps the original split, the suburban store gets a vendor-favorable adjustment to keep the product on shelf.
- One store needs aging-discount latitude the others don't. If your downtown store turns inventory faster than your slower-velocity locations, the aging-discount tiers on slower stores might need to kick in earlier. Per-store aging tiers handle this without affecting how the same vendor's product is settled at the faster store.
For details on the splits + tiers + caps mechanics, see Category Splits and Profit Sharing and Aging Discounts and Inventory Markdowns. The takeaway for multi-location: configure once, adjust per-store only where the economics genuinely differ.
Three rollout patterns that work in practice
Sequential — store by store, learning compounds
Roll out consignment at one store completely — first vendor, first settlements, first month of operational rhythm — before bringing the next store online. The first store absorbs the learning curve. By the time the second store goes live, your team has worked through the vendor conversations, the receiving SOP, and the payday flow at scale.
Synchronized — every store goes live at once
The vendor record propagates to all stores in the group at the moment of partnership creation. If you want all stores to start receiving consignment from a vendor on the same day, you don't have to do anything special — the propagation is already automatic. Just coordinate the vendor's first deliveries to land at every store within the same window.
Pilot then expand — one store fully tested, then group-wide
A hybrid. Configure the vendor only at the pilot store first (decline the auto-propagation prompt, or manually scope the initial onboarding). Run the full cycle — receipt, settlement, payday — for a month at that one store. When the rhythm is proven, propagate to the other stores in the group.
The vendor conversation at scale
The conversation with a vendor about consignment changes when you're bringing them onto multiple stores at once. You're not negotiating shelf space at one store — you're negotiating across two, five, or fifteen. That shifts the leverage. Vendors care about distribution. A single-store consignment ask is a "let's test this together" conversation; a multi-store ask is a "this is meaningful distribution for your brand" conversation.
A few things to lead with when the conversation is at the group level:
- Total shelf space being offered. Three stores carrying their flagship pre-roll is a different deal than one store carrying it. Lead with the aggregate distribution number, not the per-store one.
- Settlement consistency. Vendors hate per-retailer custom payment terms. Telling a vendor that all three of your stores will pay them on the same weekly settlement cycle, through the same Check 21 instrument, is a serious selling point compared to chasing three separate AP teams.
- Reporting they get back. Each store sends them its own settlement report and sell-through data. The vendor gets a real-time view of which of your locations moves their product fastest — useful intel for them, evidence for you that the relationship is transparent.
For the broader negotiation playbook (whether to ask vendors to add consignment vs convert their wholesale to it), see Don't ask your vendor to convert. Ask them to add.
Reporting and accounting at the group level
Multi-store accounting in cannabis is its own discipline. Each store typically has its own legal entity (one LLC per license, often), its own bank account, its own QuickBooks file, and its own state tax filings. The platform respects that boundary — each store's consignment settlements post to that store's QBO file separately. No automatic cross-entity rollup, because the entities don't share a chart of accounts and shouldn't for compliance reasons.
What does happen at the group level: your bookkeeper or accounting firm consolidates the per-location settlement data at the parent for ownership-level reporting, the same way they'd handle any other multi-entity consolidation. The platform makes their job easier because the source data is already structured, the Bills and Bill Payments are already posted to each store's QBO, and the bank-feed match works on every store independently. See how consignment settlements hit QuickBooks for the per-store QBO sync mechanics that compound across multi-location groups.
For the broader bookkeeper partnership model that multi-store retailers usually run through, For Bookkeepers covers how the accounting firm stays in the loop on every location.
The cleanest multi-store consignment rollouts I've seen weren't the ones with the most ambitious vendor lists. They were the ones with the clearest first-store playbook. Once it runs at one store, the propagation does the work everywhere else.
What the first 30 days look like
For most multi-store retailers, the first 30 days of consignment go something like this. Week one: pick the pilot store and the first vendor or two. Configure the partnerships, the splits, the aging tiers. Week two: first deliveries land at the pilot store; the receiving team runs through the SOP for the first time, and you absorb the learning. Week three: first weekly settlement runs at the pilot store; the vendor gets their first payout; the vendor portal lights up with their sell-through data. Week four: review the rhythm, decide if you're ready to propagate. If yes, propagation is one click on the partnership record — and now your other stores are live too.
Forty-five days in, you have real settlement data from multiple stores on multiple vendors, your QBO is reconciled, your vendors have a track record with you, and you've stopped tying up working capital on inventory you used to pre-purchase. The mechanics aren't the hard part. The conversations are. The platform handles the mechanics.
Ready to roll out consignment across your retail group? Get in touch for an evaluation — we'll look at your store-by-store vendor activity over the last 90 days and identify the candidates that benefit most from a group-level rollout.