Yogen Früz

The vendor opportunity at Yogen Früz

Yogen Früz is a quick-service restaurant concept headquartered in Ontario, Canada, with a small US footprint of 23 franchised locations. The brand does not disclose any company-owned units. Year-over-year unit growth stands at -17.9%, signaling a contracting rather than expanding target market for software vendors. The total addressable market is limited to these 23 units, concentrated primarily in Wisconsin, where the single mapped operator runs approximately one location. No multi-unit operators are recorded in the operator footprint.

The franchise system operates on a 10-year initial term with a 6.0% royalty rate. Average unit volume (AUV) is not disclosed in the most recent FDD. For a software vendor, the opportunity here is narrow: a small, declining base of franchisees with no visible technology mandates and a centralized purchasing structure.

Who controls software purchasing

Purchasing authority at Yogen Früz sits at the headquarters level. The FDD lists Aaron Serruya as CEO, President, and Director, with Simon Serruya serving as Vice President and Director, and Josh Serruya as Vice President. Irena Rakhamimov is the point of contact for franchise sales and development. Weny Wu holds the title of VP of International Operations & Marketing.

Because the system is entirely franchised and lacks a disclosed field operations or IT executive, any software pitch must navigate this small executive team. The absence of multi-unit operators means there is no alternative path to adoption through a franchisee buying group. Vendors should direct outreach to Aaron or Josh Serruya for operational or technology-related decisions.

Mandated and current tech stack

The 2026 FDD does not capture any mandated or recommended technology systems. No POS provider, back-office platform, online ordering vendor, or loyalty program is named. This absence of disclosed tech mandates can mean one of two things for a vendor: either the franchisor leaves technology decisions entirely to franchisees, or the franchisor has not formalized a technology program in its disclosure document. In either case, a vendor must validate the actual tech stack in use through direct discovery with the franchisees or HQ.

Without a mandated stack, the sales motion becomes a unit-by-unit or HQ-relationship play rather than a system-wide rollout. Given the small unit count, a vendor could feasibly map the installed base manually.

Procurement, renewals, and timing

Item 8 of the FDD, which would describe procurement restrictions and designated suppliers, was not captured in the available extract. This means the procurement model is unknown from the public filing. Vendors should assume that any sale will require HQ approval or at least HQ influence, given the centralized management structure.

Renewal terms, drawn from Item 17, provide a narrow window for engagement. Franchisees must notify the franchisor in writing within the last six months of their 10-year term if they wish to renew. The renewal term is five years, and the franchisor may present materially different contract terms, though territory boundaries remain unchanged and fees will not exceed those charged to similarly situated renewing franchisees. If a franchisee does not wish to renew, they must provide notice no later than 60 days before expiration.

With only 23 units and a 10-year initial term, the number of renewal events in any given year is small. A vendor looking for a trigger to engage will find few natural openings. The declining unit count further reduces the likelihood of new store openings that would create fresh technology buying events.

How to read the Yogen Früz FDD

The full Franchise Disclosure Document for Yogen Früz, filed in 2026, is available below. The FDD is the primary source for understanding the legal and operational constraints that shape software purchasing in this franchise system. Key items for a vendor to review include Item 8 (procurement restrictions), Item 11 (franchisor assistance and mandated systems), and Item 17 (renewal and transfer conditions). Because the captured data lacks specifics on Items 8 and 11, a direct reading of the PDF is essential to confirm whether any technology mandates or preferred vendor relationships exist. For a ranked target list of franchise systems with stronger technology adoption signals and growth trajectories, FranCloud can help.