Two items of the Franchise Disclosure Document — Item 8 and Item 11 — disclose the technology a franchisor mandates or approves for its franchisees: point of sale, payroll, scheduling, marketing, back office. Because every US franchisor must file an FDD and refresh it annually under the FTC Franchise Rule, that makes franchise tech stacks public record. A software vendor can know, before the first call, whether a system already runs a competitor, keeps an approved list, or leaves the choice to each franchisee — instead of learning mid-sequence that the account’s technology decisions were never the location’s to make.
Where do FDDs disclose technology requirements?
Technology requirements live in two places. Item 11 — “Franchisor’s Assistance, Advertising, Computer Systems, and Training” — requires the franchisor to describe the computer systems, cash registers, and software the franchisee must buy or use, including costs, upgrade obligations, and whether the franchisee is contractually required to keep the systems current. Item 8 — “Restrictions on Sources of Products and Services” — discloses which purchases must come from the franchisor or its designated or approved suppliers, and whether the franchisor earns revenue on those purchases. POS terminals, payment processing, and required software subscriptions routinely appear in both.
The two items answer different questions. Item 11 answers what must run in the unit — the named systems, what they cost to buy and maintain, and whether the franchisee must take upgrades on the franchisor’s schedule. Item 8 answers who profits from the requirement — whether purchases route through designated suppliers, whether the franchisor or its affiliates take a margin, and what share of a franchisee’s purchases the restrictions cover. A vendor reading both learns not just the incumbent’s name but the commercial structure holding it in place.
What is the difference between mandated, approved-supplier, and open clauses?
Filings sort each technology category into one of three states, and the state determines who the buyer is.
- Mandated — the FDD names one required system (“Franchisees must use the XYZ point-of-sale system”). The decision already happened at HQ; individual franchisees cannot switch while the mandate stands.
- Approved-supplier — the franchisor maintains a list of vetted vendors and franchisees choose among them. Getting listed is a corporate conversation; selling is then unit-by-unit or operator-by-operator.
- Open — the FDD is silent on the category or leaves it to the franchisee, sometimes subject to general brand standards. Franchisees and multi-unit operators buy like independent businesses.
The distinction is usually visible in the filing’s own language. Mandates read as named requirements: “Franchisees must purchase and use the designated point-of-sale system.” Approved-supplier clauses read as process: “Franchisees may purchase from suppliers we have approved in writing,” often with a described approval procedure and fees. Open categories read as standards without names — “equipment meeting our specifications” — or simply do not appear. The same brand routinely holds different postures in different categories, which is why the useful unit of analysis is the category-brand pair, not the brand.
Which categories do franchisors tend to mandate?
Mandates concentrate where the franchisor needs uniform data or earns revenue on the choice. Across the corpus, three layers behave differently:
- The transaction layer — POS and payments — is the most locked. Royalties are computed from unit sales, so franchisors want one reporting pipe, and payment economics often give them a direct stake in the pick.
- The operations layer — scheduling, inventory, accounting, HR and payroll — tends to sit in approved or open territory. The franchisor cares that it works, not which logo is on it.
- The corporate layer — CRM, franchise-development, and marketing platforms the franchisor itself runs — is not mandated on franchisees at all; it is HQ’s own purchase, and it shows up in filings mostly through fees and program descriptions.
For a vendor, the layer you sell into predicts the deal shape before you read a single clause: transaction-layer products fight for mandates, operations-layer products win operators and approved lists, corporate-layer products sell to the franchisor like any other B2B account. Reading a single brand’s clauses takes minutes; reading a whole market’s is the part that used to be impractical.
What patterns show up across filings?
Read enough filings and vendor footprints stop looking random — they cluster by operating archetype. Toast clusters in full-service and fast-casual restaurant systems, where kitchen workflow and table management drive the POS choice. Square shows up in service brands and mobile-first concepts — units that need payments to travel with the operator. Mindbody concentrates in boutique fitness and wellness studios, where scheduling and class booking are the core workflow. On the corporate side, Salesforce tends to appear in systems running field-sales-driven development, while HubSpot maps to marketing-led service brands managing lead flow to local units. These are archetypes read from disclosure language, not market-share claims — the filings tell you where a vendor’s model fits a system’s operating reality.
The pattern is the point: a vendor’s existing franchise footprint predicts which other systems fit it. If your product wins in boutique fitness, the brands disclosing Mindbody-style stacks are your look-alike market. The who-uses-what hub indexes disclosed vendor relationships across the corpus, one page per vendor, built from the filings rather than from marketing claims.
The same patterns work in reverse for displacement mapping. Systems that disclose a competitor’s archetype but not the competitor itself — a fast-casual brand with an approved list where the usual restaurant POS names are absent, a fitness concept whose Item 11 describes scheduling requirements generically — are the accounts where the category is contested rather than settled. Filing-to-filing changes sharpen the read further: a vendor appearing in a brand’s new FDD that was absent from the last one marks a fresh rollout, and a vendor quietly dropped marks a contract that ended.
What does a mandate mean for a vendor?
A mandate means the system-level decision is taken — the question is whether you sell with it or against it. Selling with a mandate means integrating or partnering: if the required POS is not yours but your product rides alongside it, the mandate is distribution, and the disclosed stack tells you exactly which integration to lead with. Selling against a mandate is displacement, and displacement is a timing game: franchise technology contracts turn over at renewal, and systems signal restlessness before they switch — pilot language in a new filing, an approved list where a single mandate used to be, a competitor dropped from Item 8. A locked account is not a dead account; it is an account with a known clock.
The displacement math favors patience over volume. A system that mandated its POS four years ago is closer to a decision than one that mandated it last year; a brand whose new filing moves a category from a single mandate to an approved list has already started the conversation internally. Vendors who maintain a dated watchlist of locked systems — what is mandated, since when, and what changed in the latest filing — enter those windows with context instead of cold. The door-by-door mechanics of who to call when a window opens are covered in the franchise GTM playbook.
Where can you look up a franchise tech stack?
The primary source is the FDD itself — Items 8 and 11 of the brand’s current filing. FranCloud structures that source at scale: technology and supplier clauses are extracted from thousands of FDD filings, linked to vendors, and verified against the documents, with the methodology published. The vendor pages show the disclosed footprint per vendor; brand profiles show the disclosed stack per system. For the market-level view — which categories are locking up, where approved lists are replacing single mandates — the franchise tech-stack report pulls the corpus into one document.
Franchising is one of the few markets where the install base is disclosed by law, brand by brand, every year. Nothing in these documents is secret — every clause quoted above sits in a filing any competitor could download today. The difference is operational: reading one FDD is diligence, reading thousands is a dataset. The vendors who treat the disclosures as pipeline data are working from the same public record as everyone else — earlier, and across the whole market at once.