LCS franchise / multi-location pull-list portability, how does it work on Magento?

Larger LCS chains (think Mile High Comics, Galaxy of Comics, Big Bang Comics franchise model) operate 3-15 physical locations and need pull-list portability: a subscriber who moves from the Denver store to the Boulder store keeps their pull-list, history, and tier-pricing intact.

The Magento implementation:

• Store-view-per-location, one Magento store, multiple store views, each tied to a physical location. Customer accounts are shared across store views.
• Customer attribute: home_store, identifies the customer’s primary location for pickup-hold logic and local-event invites. Editable by the customer.
• Stock per location, Magento Multi-Source Inventory (MSI) with one source per location. Pull-list cron reserves stock from the home_store source first, falls back to other locations.
• Tier-pricing globally shared, customer groups (Tier 1/2/3) apply across all locations. A 25-title subscriber gets Tier 3 discount whether they pick up in Denver or Boulder.
• Per-location reporting, Magento order reports filtered by store view feed the franchise-level operations dashboard.

This is the architecture that lets a 15-location chain run one Magento install instead of 15 separate ones. The operational savings (one PIM, one customer database, one pull-list cron, one pre-order ingest) are the reason LCS chains migrate from Lightspeed Retail / ComicHub to Magento.