Chick-fil-A is the most productive counter in American fast food and one of the most app-centric, which makes it an unusual data target. It ran 3,287 US restaurants at the end of 2025, and a standalone location averaged just under $9.2 million a year, more per store than McDonald's, Starbucks or Subway (Restaurant Business). Franchise operators run a single location each, so pricing is tightly controlled from the center but still moves by market, and more and more of the ordering happens in the app. Two facts follow for anyone building a dataset: the store menu on the website is the readable price surface, and every store is dark on Sundays, so any time series you build has a hole in it once a week by design.
Chick-fil-A's site passed our request at the door in the atlas run, which makes the real work the store-by-store read behind it. What follows: the target, the jobs, the measured door, and the type, setup, sizing and limits, with the app-and-rewards side ruled out plainly.
Which proxy fits
US residential proxies pinned to the metro of the stores you read, driving a real browser, one session per store. A static ISP proxy per account for any login. Datacenter exits loaded the homepage, as our test showed, and are the first addresses metered once the store menus are read on a sweep.
Chick-fil-A as a target
Store menus and prices, built around a chosen store, centrally set but varying by market. Regional and limited-time items, which appear in some markets before others. Delivery menus on the marketplaces, priced per store. The store locator, at 3,287 US restaurants plus licensed units, growing as sales near $24 billion. And Chick-fil-A One, the rewards and mobile-order layer, which is not a data job.
The site passed our request at the door and loads the store menu and prices around a chosen store from Chick-fil-A's own API calls.
Jobs a proxy is right for
- Store-level and regional price monitoring. How the same order is priced across markets, and when a central change rolls out, read per store on a schedule (six days a week, given Sundays).
- Limited-time and regional item tracking. Which markets get an item first, and at what price.
- Delivery-price monitoring. Chick-fil-A's delivery prices per store on the marketplaces, the method in proxies for DoorDash.
- Location data. The store list with hours and formats, growing steadily, for site selection and competitor mapping. The Sunday-closed hours are themselves a data point.
- Throughput and format research. Which stores have multi-lane drive-thru or mobile-only formats, read from the store pages.
Jobs a proxy is not for
Chick-fil-A One and app-only offers. They attach to a phone or email and the app on a device; farming offers runs against Chick-fil-A's terms.
Mobile ordering. A real pickup location and payment method, not a network property.
The door, measured
On 24 August 2026 a single request to chick-fil-a.com from a datacenter server in Germany, with a normal browser user-agent, returned HTTP 200 and the real homepage, served through Cloudflare, which passed the request rather than challenging it. We sent the same request through twenty elite HTTP proxies from our free proxy list: 15 failed to connect or got another response, five loaded the homepage. So the door passed our client, and what defends the site is the metering behind it on the store menu, which a customer opens a few times and a script opens for every store. We did not measure that limit; log the first rising 403 or 429 rate per exit and treat it as the number. Fixing 429 rate limits through a proxy covers the back-off.
Metro-pinned residential exit
same city as the store
Store chosen
one session
Menu + prices + LTOs
record store and day
Skip Sunday
stores are closed
Type by job
| Chick-fil-A job | Proxy type | Why |
|---|---|---|
| Store-level and regional price monitoring | Rotating US residential, metro-pinned, session per store | Prices vary by market; the sweep is per store |
| Limited-time and regional item tracking | Rotating US residential, region-pinned | Rollouts are staged by market |
| Delivery-price monitoring | Rotating US residential, session per address | Marketplace storefronts are per address |
| Locator and format data | US residential, slow pacing | Paged queries from one address is the metered pattern |
| Any login | US ISP (static residential) | One fixed, trusted location per account |
| One manual look at one store | Datacenter, or a fresh free proxy | The homepage passed; the sweep will not survive |
For why the two address types are treated so differently, datacenter vs residential proxies.
Free proxies here
Five of five connecting proxies loaded the homepage, so Chick-fil-A is friendly to a one-off look and no friendlier to a sweep of thousands of stores. Use a free proxy to test that your parser reads a store menu correctly, verify it in the proxy checker first, and read when free proxies are fine for the line. For the sweep, our US residential proxies start at $0.44/GB, pay as you go, no KYC, pinned to the metro.
Setup
- Metro-pinned residential exit, real browser. An Atlanta store from an Atlanta exit; the store choice does the localizing. Launch flags are in the Playwright proxy guide.
- One session per store, and schedule around Sunday. Read Monday through Saturday; a Sunday read returns closed-store data, which is a fact worth recording once and not worth re-reading. Sticky vs rotating proxy sessions covers the two modes.
- Watch for the central price change. Because pricing is centrally controlled, the signal is a coordinated move across a region; read weekly and diff.
- Back off at the first 429. Avoiding IP bans while scraping has the rest.
Sizing
Regional price index, 400 stores across 15 markets, weekly (6 days):
store sessions per sweep 400
pages per session 2-3 (menu, prices)
sessions per exit per day 4-6
exits in rotation ~30-40 US residential, metro-pinned
You pay for bandwidth, and a menu page with images blocked is tiny, so the store count sets the bill. Our pricing carries no subscription and no expiring balance.
The boundary
A metro address is the proxy's whole part; Chick-fil-A One and mobile ordering stay out of reach, the chain's terms prohibit scraping through any address, and a pickup order needs a real location. Inside them, a metro-pinned residential exit with a real browser reads public store menus and prices the way customers in each city see them: one store per session, six days a week, human pacing, block rate logged.
The chain that runs even more of its business through rewards is in proxies for Chipotle; the test-market chain where city-level reads are the point is in proxies for Taco Bell.
Sources
- Restaurant Business, Chick-fil-A unit volumes (3,287 US restaurants at the end of 2025; standalone average just under $9.2 million; single-location operators): restaurantbusinessonline.com
- HProxy measurement, 24 August 2026: one direct request from a datacenter server (HTTP 200, homepage, Cloudflare passed) and 20 elite HTTP proxies from our free proxy list (15 no connection or other, 5 homepage).