Edge case, we’re a jan/san <em>service</em> company, not a distributor. Does Magento still fit?

Yes, with a different angle. Jan/san service companies (the firms that send cleaning crews to office buildings, hotels, hospitals) typically buy chemicals and supplies in bulk and re-stock crew kits weekly. The Magento use-case is internal procurement + crew-kit fulfilment, not external sales.

The architecture:

• Per-crew or per-account ordering portals: each cleaning crew (or each client building) has a Magento customer account with a curated SKU list of approved chemicals + supplies. Crew lead orders weekly from their tablet; warehouse picks + delivers to the site.
• Per-account budget enforcement: cleaning service contracts typically have a per-month chemical budget per building. Magento customer-group budget rules block orders that would exceed the budget without supervisor approval.
• CribMaster / AutoCrib at the cleaning service warehouse: rather than at the customer site, vending machines control crew access to chemicals + PPE. Reduces shrinkage ~20-30% in the data I see.
• Subscription auto-ship on the high-velocity SKUs: paper towels, can liners, all-purpose cleaner ship automatically to each crew on a weekly cadence. Cuts crew-lead admin time ~75%.
• Reporting: per-account chemical-spend dashboards roll up to the operations team. Profitable buildings vs underwater ones become visible in real-time.

This is a smaller-scope Magento build (typically $15k, $35k) but with high operational ROI. ServiceMaster, ABM Janitorial Services, Coverall Health-Based Cleaning, and Jani-King all run variants of this internally; the independent service company can ship the same playbook on Magento + Hyvä for a fraction of enterprise software cost.

If you’re a hybrid service-company-plus-distributor (you clean buildings AND sell supplies to other cleaners), the Magento store supports both use-cases in a single instance with separate customer groups + storefronts.