Flying Biscuit

The vendor opportunity at Flying Biscuit

Flying Biscuit operates 35 quick-service restaurants, with 27 franchised and 8 company-owned locations. The brand posted an average unit volume of $1,901,798.75 in its 2025 Franchise Disclosure Document and grew units by 3.846% year-over-year. For software vendors, the total addressable footprint is 35 units—small by chain standards but tightly controlled from headquarters, which simplifies a top-down sale.

The royalty rate sits at 5.0% of gross sales, and the initial franchise term runs 10 years. These economics matter to vendors because they shape the franchisee’s operating margin and the franchisor’s appetite for system-wide technology investments. A $1.9 million AUV in quick service means operators are sensitive to tools that reduce labor, streamline ordering, or improve throughput without adding meaningful overhead.

Who controls software purchasing

The 2025 FDD lists three executives in Item 1: Daryl Dollinger (President), Sohail Khizer (Director of Operations), and Andrew Scherzer (Director of Franchise Development). In a 35-unit system with mandated technology, purchasing authority almost certainly sits with the President and Director of Operations. Vendors should direct initial outreach to Dollinger and Khizer, as they oversee the operational and financial decisions that drive software adoption. Scherzer may serve as a gatekeeper for franchisee-facing tools but is less likely to control back-of-house or enterprise procurement.

No parent company is disclosed in the FDD; Flying Biscuit appears independently owned. This means there is no larger corporate procurement layer to navigate—the decision-making path is short and concentrated in the Georgia headquarters.

Mandated and current tech stack

Flying Biscuit mandates three Oracle MICROS products across its system: Micros by Oracle Corporation, MICROS Systems, Inc. (MICROS) by Oracle Corporation, and the MyMicros.net Enterprise Information Portal. This is a fully Oracle-aligned POS and enterprise reporting environment. Any vendor selling adjacent software—labor scheduling, inventory management, catering, loyalty, or delivery integration—must integrate with Oracle MICROS or demonstrate a clean data handoff.

The mandate is absolute; franchisees do not have discretion to choose an alternative POS. This centralization creates a single integration point and a single buyer for any tool that touches the transaction flow or operational reporting. Vendors who already support Oracle MICROS integrations have a technical advantage here.

Procurement, renewals, and timing

The 2025 FDD does not include an Item 8 extract describing a designated or approved supplier program. In the absence of that disclosure, vendors should assume an open procurement model where the franchisor evaluates tools on a case-by-case basis. There is no published list of preferred vendors to join, but there is also no formal barrier to entry beyond the franchisor’s approval.

Renewal terms in Item 17 require franchisees to provide written notice, sign the then-current Franchise Agreement, pay a renewal fee, potentially refurbish the restaurant, complete retraining, and sign a general release. The renewal term is 10 years. These conditions create natural evaluation windows: a franchisee approaching renewal may be more open to new systems if a refurbishment or retraining is already required. For vendors, tracking the initial sale dates of franchised units can surface clusters of locations nearing their 10-year mark.

How to read the Flying Biscuit FDD

The 2025 Flying Biscuit Franchise Disclosure Document is the authoritative source for unit counts, executive names, mandated technology, fees, and contractual terms. Item 1 identifies the franchisor and its officers. Item 11 details the franchisor’s obligations, including any mandated technology systems—here, the Oracle MICROS suite. Item 17 governs renewal and transfer, which signal when franchisees must re-commit to the system. Item 19, if present, provides financial performance representations; the AUV cited here comes from that section.

For software vendors, the FDD is a due-diligence document, not a sales deck. It tells you who controls purchasing, what technology is already locked in, how many units are in play, and when contractual churn is likely. Use the embedded viewer below to search for the specific items relevant to your product category. If you need a ranked list of franchise targets matched to your software category, FranCloud can build that list from the underlying FDD data.