Edge cases, single food truck vs 200-property hotel chain procurement?

Magento + Hyvä scales both directions, but the right scope is different.

Single food truck / small independent restaurant ($100, $5k/yr per buyer):

• You probably don’t need a custom build. Shopify or BigCommerce is enough at this end of the market, light catalog (1k, 5k SKUs), card-on-checkout, parcel-only freight, no Net-30, no NSF flagging report.
• If you’re the distributor selling to food trucks, you might still run Magento because your aggregate business has the catalog + drop-ship + LTL needs. Just don’t over-build for single-buyer features at this tier.
• Lead-magnet content + Klaviyo / Mailchimp for repeat orders + a Stripe-only checkout with no Net-30 is the right shape for the bottom of the market.

200-property hotel chain procurement (Marriott, Hilton, IHG):

• Custom enterprise build. Parent / child account architecture (corporate parent → 200 property children → ~6 buyer roles per property).
• PunchOut catalog integrated with their procurement platform (Coupa, SAP Ariba, Oracle iProcurement, Jaggaer).
• Custom Marriott-approved-catalog customer-group; per-property pricing tier (full-service vs select-service); per-property tax exemption certificates.
• Net-45 or Net-60 underwritten through TreviPay (longer terms = higher underwriter fee but still cheaper than self-AR).
• EDI integration if their AP runs through an enterprise system (most do above 50 properties).
• Cost: $50k, $200k initial build + $5k, $15k/mo ongoing for new-property onboarding + carrier-mix optimisation + procurement-platform updates.
• Timeline: 16-28 weeks.

Mid-market sweet spot ($1M, $25M GMV): the foodservice distributor with 200-2,000 active restaurant accounts, 3-8 drop-ship manufacturer relationships, and 20k, 40k SKUs. That’s the customer Magento + Hyvä is built for, and where the $4,999 build → custom-enterprise progression makes economic sense.