The vendor opportunity at Au Za'atar
Au Za'atar is a quick-service restaurant concept headquartered in New York, operating 2 company-owned locations. The 2025 Franchise Disclosure Document reports no franchised units, meaning the entire system is under direct HQ control. For software vendors, this creates a concentrated sales target: a single buying center in New York that manages all technology decisions for locations generating an average unit volume of $5,229,544. The royalty rate is 5%, and the initial franchise term is 10 years.
Year-over-year unit growth is not disclosed in the most recent FDD, so vendors should not assume an expanding footprint. The opportunity here is not scale but depth—each location does significant volume, and the mandated tech stack leaves room for adjacent tools in areas like inventory, labor scheduling, or customer engagement.
Who controls software purchasing
All software purchasing authority rests with Au Za'atar's headquarters in New York. Because the system has no franchised locations, there is no multi-unit operator layer or franchisee autonomy to navigate. The FDD does not list any HQ executives by name, so vendors will need to identify the relevant decision-makers through direct outreach or third-party data sources. The absence of a franchisee base means the sales cycle is shorter and more centralized than in larger, distributed systems.
Mandated and current tech stack
The 2025 FDD mandates two technology platforms: Intuit QuickBooks for accounting and Square for point-of-sale. These are listed as recommended or required systems, giving vendors a clear picture of the operational backbone. QuickBooks handles financial management, while Square covers payment processing and likely some front-of-house functions. This leaves gaps in areas like enterprise resource planning, workforce management, supply chain, and marketing automation—all of which could be pitched as complementary to the existing stack.
No other mandated technology is disclosed. Vendors should note that the brand's small size means any new software adoption would likely be a high-touch, HQ-driven evaluation process rather than a mass deployment.
Procurement, renewals, and timing
The FDD does not extract a procurement model from Item 8, so it is unclear whether Au Za'atar uses designated suppliers, approved suppliers, or an open procurement process. Vendors should approach HQ directly to understand how purchasing decisions are made and whether there are existing vendor relationships that could block or slow new adoption.
On renewal timing, the franchise agreement provides for an initial 10-year term with the option to renew for up to two additional 5-year terms. Renewal conditions include advance notice, compliance with all obligations, renovation to then-current standards, signing the then-current franchise agreement, paying a renewal fee, and signing a general release. These renewal windows could serve as natural inflection points for technology reevaluation, though with only 2 units, the cadence of such events is limited.
How to read the Au Za'atar FDD
The 2025 Au Za'atar Franchise Disclosure Document is embedded below for full review. This document is filed with state franchise regulators and contains the legal and operational disclosures that govern the franchise relationship. For software vendors, the most relevant sections are Item 11 (franchisor's assistance, including technology mandates) and Item 17 (renewal and termination), which outline the contractual framework that shapes technology adoption cycles. Use the viewer below to search for specific terms like "software," "POS," or "technology" to identify additional obligations or recommendations not summarized here.
For a ranked list of franchise systems that match your software's ideal customer profile, FranCloud can help you prioritize targets by unit count, tech stack, and decision-maker structure.