Edge cases, rural mobile vet vs 30-clinic regional group?

Two ends of the vet-supply customer spectrum, both worth designing for.

Rural mobile vet (1-2 vets, no fixed clinic):

• Orders smaller volume, 1-3x per month, AOV $150-$400.
• No practice-management system (or paper-based / Excel). Won’t integrate. Order entry is the e-com store directly.
• Mobile-first UI critical, they place orders from a truck between calls.
• Cold-chain is harder: no clinic fridge at the destination. Solution: ship to a partner clinic or pharmacy with cold-chain capability + scheduled pickup.
• DEA registration usually present (Schedule III-V common for sedation in equine practice), but state edge cases matter (Texas mobile-vet rules differ from CA).
• Customer-group: “mobile-vet” with small-pack SKU visibility + tiered shipping that favors ship-to-partner-clinic.

30-clinic regional group:

• Centralised purchasing (one buyer for all 30 locations) or decentralised (each clinic orders independently). Both patterns common, Magento needs to handle both.
• Adobe Commerce B2B Companies module is the clean fit: parent company → 30 child clinics → shared catalog → multi-step approval (clinic-manager approves over $500, regional-director over $5k).
• Practice-management integration matters: regional groups often standardise on one PIMS (often Cornerstone in US) across all locations. One PIMS connector reaches all 30 clinics.
• Net-30 invoicing via TreviPay or Resolve. Centralised AR.
• DEA: each clinic has its own DEA registration; the parent account routes orders to the right registration based on ship-to location. Magento needs to validate per ship-to, not per account.
• Quarterly business review with the regional purchasing manager; this is where the relationship deepens.

Both ends matter, both can run on the same Magento with customer-segment-based UX. Don’t over-build for one end; the spectrum in between is where the volume sits.