Institutional buyers are schools, universities, corporate L&D teams, training companies and professional associations. Their purchase looks nothing like an individual checkout: a procurement contact, a purchase order, invoice terms, a volume price and a seat pool that someone has to manage. The portal has to hold all of that without a spreadsheet on the side.
A working institutional portal has four capabilities. First, a bulk-seat purchase flow where an admin sets a seat count and pays by invoice, purchase order or card. Second, a seat-assignment workflow: the admin uploads a CSV of student emails for immediate enrollment, or keeps a pool of unassigned seats to hand out over the term.
Third, an admin dashboard showing who is enrolled, who has started and who has completed, with completion, time and score totals for the group. Fourth, reporting exports for L&D compliance and training records, because the person who signed the purchase order has to prove the budget was used.
On Shopify, the company account carries that buyer's pricing, payment and shipping methods, and a draft order stands in for the quote. Where a university wants the course to launch inside Canvas or Blackboard, the LTI standard from 1EdTech is the integration to scope, and our API and integration team builds that layer.
design note
The unassigned-seat pool is the renewal lever in an institutional account. Suppose a district buys 200 seats and assigns 60 in the first term. The remaining 140 are a reason for the same procurement contact to come back before the budget year ends, so every dormant seat is worth surfacing.
So build the admin dashboard with unassigned and unstarted seats at the top of the view, and raise a seats-expiring notice at 60 and 30 days. Nothing about that is clever engineering. It is the dashboard answering the one question the buyer's finance team will ask.