The vendor opportunity at Puffy Cotton Candy
Puffy Cotton Candy is a retail food concept with a minimal US footprint. According to the 2025 Franchise Disclosure Document, the system consists of exactly 2 franchised units, with no company-owned locations. The units are split between New Jersey (1) and Florida (1). No multi-unit operators are recorded; both locations appear to be run by single-unit franchisees. Year-over-year unit growth is not disclosed in the FDD, and no average unit volume (AUV) is reported.
For a software vendor, the addressable market here is extremely small. With only 2 locations and no disclosed growth trajectory, the immediate opportunity is limited to two independent operators. There is no parent company on file, and the brand appears to be independently owned. Vendors evaluating whether to allocate sales resources should weigh this micro-footprint against longer-term expansion potential, about which the FDD provides no data.
Who controls software purchasing
The 2025 FDD does not list any executives in Item 1, leaving the decision-making structure opaque. In systems of this size, purchasing authority typically sits with the franchisees themselves, absent a franchisor mandate. No CIO, VP of IT, or operations lead is named, and there is no indication of a centralized technology evaluation process. If you sell software, your buyer is likely the individual operator at each of the two locations. Direct outreach to those units is the only clear path, as no HQ-level gatekeeper is documented.
Mandated and current tech stack
Puffy Cotton Candy’s 2025 FDD contains no mandated or recommended technology systems. There is no mention of a required point-of-sale system, online ordering platform, inventory management tool, payroll provider, or any other operational software. This absence of franchisor-level tech mandates means each operator may be using whatever tools they independently selected. For vendors, this represents a blank slate but also a lack of standardization that can complicate scalable deployment. Any pitch must account for the fact that there is no system-wide stack to integrate with or displace.
Procurement, renewals, and timing
The FDD does not include an Item 8 extract, so the brand’s procurement model—whether designated supplier, approved supplier, or fully open—is not disclosed. Similarly, Item 17 contains no renewal signals, and the initial franchise term and royalty percentage are not stated in the available data. Without these fundamentals, it is impossible to estimate when contract windows might open or whether there is a franchisor-driven refresh cycle. Vendors should approach this as an opportunistic, relationship-based sale rather than one tied to a predictable procurement calendar.
How to read the Puffy Cotton Candy FDD
The full 2025 FDD is embedded below for direct review. This document is the primary source for all facts cited on this page, including unit counts, ownership structure, and the absence of mandated technology. When reading, pay particular attention to Items 1, 8, and 11 for any updates on leadership, procurement rules, or tech requirements that may have changed since this analysis. For software vendors building a ranked target list across franchise systems, FranCloud can help you identify which brands offer the right fit based on real FDD data.