If you sell POS, payments, payroll, or marketing software into franchising, "what's already installed" is usually the first qualifying question on any account, and the hardest one to answer at scale. A franchisee won't tell a cold caller their POS vendor before a discovery call, and a franchisor's website never lists it. But the FDD does, because franchisors are legally required to disclose the technology they mandate. Read enough of them and a market map appears. For how those clauses shape a sales motion, see what FDDs reveal about franchise tech stacks.
Where franchise tech stack data actually comes from
It comes from Item 11 of the FDD, "Franchisor's Assistance, Advertising, Computer Systems, and Training." Every FDD filed under the FTC Franchise Rule has to describe the computer systems and software a franchisee is required to buy or lease, usually down to the approved vendor, the hardware specs, and the cost range. This isn't marketing copy or a vendor's self-reported install base; it's a legal disclosure the franchisor drafted and updated for its own protection, which makes it one of the more reliable primary sources on franchise technology in existence.
The catch is that Item 11 is prose, not a spreadsheet. A single filing might spend two or three pages describing POS hardware requirements, back-office software, credit card processing, and required internet connectivity, in whatever order and level of detail that brand's counsel chose. Reading one brand's Item 11 takes a few minutes. Reading it across every active US franchise brand to see which POS vendor actually dominates franchising doesn't scale by hand, which is the specific gap a structured franchise database is built to close.
What Item 11 actually discloses
Across the systems FranCloud has extracted from FDD filings, the disclosures cluster into a handful of categories:
- Point of sale: the register, kitchen display, and payment processing stack. Toast, Square, and Clover are the most commonly named POS platforms in the corpus.
- Accounting and back office: QuickBooks and QuickBooks Online appear across hundreds of franchisor requirements, often as the mandated bookkeeping system franchisees must give the franchisor visibility into.
- Productivity and communication: Microsoft Office, Windows, and Google Workspace show up as baseline requirements far more often than any category-specific software, simply because most franchisors still specify a minimum office computing standard.
- Marketing and social: a growing number of FDDs now name specific platforms (Facebook, Instagram, LinkedIn) directly in Item 11 or Item 6, reflecting franchisor-mandated local marketing programs.
- Industry-specific ordering and delivery: restaurant-oriented platforms like Olo show up specifically in quick-service and fast-casual filings, tied to required online ordering integrations.
- Distribution and inventory: food-service brands frequently name an approved distributor, such as Sysco, as part of the required supply chain and inventory system.
What the most commonly named systems look like
A sample of the systems that show up most often across FranCloud's corpus, by category:
| System | Category |
|---|---|
| Microsoft Office | Productivity |
| QuickBooks / QuickBooks Online | Accounting |
| Marketing | |
| Toast | POS |
| Marketing | |
| Marketing | |
| Square | POS |
| Sysco | Inventory/distribution |
| Olo | Restaurant ordering |
| Clover | POS |
A few things stand out. Toast is named more often than Square or Clover, a lead wide enough to matter for anyone targeting restaurant franchisors specifically. And the productivity and accounting categories are dominated by two vendors, Microsoft and Intuit, because most franchisors mandate a baseline standard rather than picking a niche alternative.
What the actual disclosure language looks like
Item 11's tech language tends to follow a pattern: the franchisor names a required or approved system, reserves the right to change it, and states its own access rights to the data that system generates. A typical clause requires a franchisee to purchase point-of-sale hardware and software from an approved vendor, grant the franchisor independent remote access to the resulting sales and customer data, and absorb the cost of future upgrades the franchisor decides to mandate. That combination (vendor lock plus data access plus franchisee-borne upgrade cost) repeats across concepts as different as quick-service restaurants, fitness studios, and home services, which is part of why POS and back-office software sit near the top of franchisor priorities. Brand-level examples of locked stacks show up in posts like the McDonald's FDD breakdown and Domino's Pizza FDD.
How this data gets used
A tech stack database built from FDDs supports a few concrete workflows:
- Displacement targeting. If you sell a POS system, filtering for every restaurant brand that currently mandates a specific competitor tells you exactly where a rip-and-replace pitch is viable, and where it isn't, because the incumbent is locked in contractually.
- Whitespace sizing. Counting brands with no named POS system in Item 11 (or an outdated one) surfaces a genuine greenfield list, distinct from displacement targets.
- Franchisor prioritization. A vendor selling at the franchisor level, not the franchisee level, can rank brands by how prescriptive their Item 11 language is. Some franchisors mandate a single approved vendor down to the model number, others leave more room, and that difference predicts how a sales conversation will go.
- Market-level franchise data analytics. Aggregated across categories, the same disclosures answer broader questions: which POS vendors dominate quick-service versus full-service, or how fast a given platform's franchise footprint is growing filing over filing.
Those motions sit inside the broader GTM frame in selling to franchise systems and the pre-call scan in Turn the FDD Into Your Sales Compass.
What this kind of database can't tell you
Item 11 discloses what's required, not everything a franchisee actually runs. Optional add-ons, franchisee-side workarounds, and systems adopted after a franchise agreement was signed won't show up in the filing. Disclosures also age at the pace of FDD renewals. Most franchisors refile annually, but a brand's Item 11 can be nine to fifteen months stale depending on filing timing, so a tech stack database is a strong directional map, not a live inventory feed. Treat it the way you'd treat any regulatory filing: authoritative on what the franchisor is contractually requiring, silent on everything outside that requirement. For why generic B2B tools miss this layer entirely, see restaurant and franchise data accuracy.
Go deeper
FranCloud's franchise database extracts Item 11 technology requirements across every active US franchise brand's FDD filings, searchable by system, vendor, and category, alongside unit counts and ownership data, so you can go from "who requires Toast" to a qualified target list in one search. For the fundamentals of what's in an FDD and how Item 11 fits alongside the other 22 items, see the FDD guide and key FDD sections. Vendors ready to move from research to a working target list can see current pricing.