Shell

The vendor opportunity at Shell

Shell operates in the automotive services sector with its headquarters in Ohio. For software vendors evaluating this account, the immediate challenge is the opacity of the franchise system’s structure. The 2026 Franchise Disclosure Document (FDD) does not disclose the total number of units, nor does it break out the split between franchised and company-owned locations. This lack of public unit count makes it difficult to size the addressable market without proprietary data. Similarly, the average unit volume (AUV) is not reported, leaving vendors without a standard revenue-based proxy for a location’s technology budget. The royalty rate and initial franchise term are also not disclosed in the most recent filing, which means the typical economic levers that influence software adoption and renewal cycles are hidden from public view.

Despite these gaps, Shell remains a significant brand. The absence of mandated technology in the FDD can be interpreted as a greenfield or a black box, depending on your perspective. If the system truly lacks mandated tools, there is no incumbent to displace. If mandates exist but are simply not captured in the FDD, the sales cycle will require deep discovery. Year-over-year unit growth is not available, so vendors cannot gauge whether the system is in an expansionary phase that typically accelerates software procurement.

Who controls software purchasing

The 2026 FDD does not list any executives in Item 1, which is where franchisors typically disclose the officers and directors responsible for the brand. This means the software buying center at Shell’s headquarters is not publicly mapped. Without named individuals, vendors cannot immediately identify a CIO, VP of Technology, or Operations lead who would champion a new platform. The decision-maker level is therefore classified as unknown. In practice, this requires a top-down prospecting approach, starting with the main corporate line in Ohio to map the organizational chart. It is not clear from the FDD whether purchasing authority rests entirely at the corporate level, is delegated to multi-unit operators (MUOs), or is left to individual franchisees.

Mandated and current tech stack

The FDD contains no captured data on mandated or recommended technology systems. This means there are no named POS vendors, operational platforms, or back-office tools that franchisees are required to use. For a vendor, this is a critical piece of intelligence. If the system is truly open, you are not competing against a franchisor-endorsed standard. However, it is equally possible that the franchisor has internal standards not published in the FDD. The tech landscape, as far as public compliance documents are concerned, is a blank slate. Vendors should approach initial conversations prepared to educate the prospect on category best practices, as there is no documented legacy stack to integrate with or displace.

Procurement, renewals, and timing

Item 8 of the FDD, which typically outlines whether the franchisor designates approved suppliers or requires purchases from specific vendors, yielded no extract in the 2026 filing. This leaves the procurement model undefined. It is not known whether Shell operates a closed, designated-supplier model or an open market where franchisees choose their own vendors. Similarly, Item 17, which covers renewal, termination, and transfer, provided no signal. Without the initial term length or renewal windows, vendors cannot build a timeline for when franchisees are likely to re-evaluate their technology contracts. The absence of these data points means that outbound timing cannot be data-driven from public filings alone.

How to read the Shell FDD

The Shell 2026 FDD is a legal document filed with state franchise regulators. It is the foundational disclosure that governs the relationship between the franchisor and its franchisees. For software vendors, the FDD is a primary source of truth for understanding unit counts, mandated suppliers, and the legal constraints on franchisee operations. The embedded PDF viewer below contains the full text of the filing. When reading it, focus on Item 11 for any mention of required technology, Item 8 for procurement restrictions, and Item 20 for a table of outlet locations that can help you build a geographic map of the system. For a ranked target list of franchise brands with clearer technology entry points, FranCloud can help you prioritize accounts based on real FDD data.