Chipotle is a rarity among big US chains: it owns and operates its restaurants rather than franchising them, so its prices are set centrally, which makes the ways they still vary the interesting part. At 4,056 restaurants as of 31 December 2025, after a record 334 openings that year with 257 Chipotlane drive-thrus attached (Chipotle, 3 February 2026), regional pricing, market-by-market menu differences and limited-time items are what analysts, competitors and journalists track, and they track them per store. That is the job proxies do here.
The other half of Chipotle is behind a wall no proxy touches. Digital sales were 36.7 percent of food and beverage revenue in 2025, and nearly 90 percent of digital transactions are tied to Rewards, so the app, the deals and the free-item offers live in an account on a device. This page covers what a proxy can read (the store menus and prices), the door as measured on 24 August 2026, and the type, setup, sizing and limits, with the account 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.
Chipotle as a target
Store menus and prices, built around a chosen store. Because Chipotle is company-operated, the price is set centrally, but it still moves by region and market, so the dataset is the spread across 4,000 stores rather than franchisee-by-franchisee variation. Limited-time items, which appear in some markets before others. Delivery menus on the marketplaces, priced per store. The store locator, at 4,056 locations with 334 added in a year. And the app and Rewards, which is not a data job.
Chipotle runs a JavaScript application that passed our request at the door. The store menu and prices load around a chosen store from Chipotle's own API calls.
Jobs a proxy is right for
- Store-level and regional price monitoring. How Chipotle prices the same order across markets, and when a central price change rolls out, read per store on a schedule.
- Limited-time-item tracking. Which markets get a new item first, and at what price, read across regions.
- Menu-difference mapping. What a store in one market offers that another does not, read per store.
- Delivery-price monitoring. Chipotle's delivery prices per store on the marketplaces, the method in proxies for DoorDash.
- Location data. The store list with Chipotlane presence and hours, growing by hundreds a year, for site selection and competitor mapping.
Jobs a proxy is not for
Rewards and app-only deals. They attach to a phone or email and the app on a device; farming offers runs against Chipotle's terms.
Free-item offers. Tied to accounts and devices, not addresses.
Ordering. A real pickup or delivery address and a payment method, not a network property.
The door, measured
On 24 August 2026 a single request to chipotle.com from a datacenter server in Germany, with a normal browser user-agent, returned HTTP 200 and the real homepage, with no challenge page and no bot-vendor marker we could name. Of twenty elite HTTP proxies from our free proxy list, one request apiece, 16 never connected and all four that did 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 time
Rotate
next store, fresh exit
Type by job
| Chipotle job | Proxy type | Why |
|---|---|---|
| Store-level and regional price monitoring | Rotating US residential, metro-pinned, session per store | Prices move by region; the sweep is per store |
| Limited-time-item tracking | Rotating US residential, region-pinned | Rollouts are staged by market |
| Menu-difference mapping | Rotating US residential, session per store | Differences are per store |
| Delivery-price monitoring | Rotating US residential, session per address | Marketplace storefronts are per address |
| Locator and location 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
Four of four connecting proxies loaded the homepage, so Chipotle is friendly to a one-off look and no friendlier to a sweep of 4,000 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. A Chicago store from a Chicago exit; the store choice does the localizing. Launch flags are in the Playwright proxy guide.
- One session per store. Choose the store, read the menu, prices and any limited-time items, record store and timestamp, rotate. Sticky vs rotating proxy sessions covers the two modes.
- Watch for the central price change, not daily noise. Because pricing is central, the signal is a coordinated move across a region; read weekly and diff, and read more often only where a rollout is expected.
- Back off at the first 429. Avoiding IP bans while scraping has the rest.
Sizing
Regional price index, 500 stores across 20 markets, weekly:
store sessions per sweep 500
pages per session 2-3 (menu, prices)
sessions per exit per day 4-6
exits in rotation ~30-40 US residential, metro-pinned
Residential meters bandwidth; menu pages with images blocked are small, so the store count sets the bill. Pricing is pay as you go with no expiring balance.
The boundary
A metro address is the proxy's whole part; the app and Rewards stay out of reach, Chipotle's terms prohibit scraping through any address, and an order needs a real pickup address. Within those lines, a metro-pinned residential exit with a real browser lets a legitimate data job read public store menus and prices the way customers in each city see them, one store per session, at a human pace, watching the block rate.
The chain whose menu resets every week instead of holding steady is in proxies for Crumbl; the test-market chain where city-level reads are the point is in proxies for Taco Bell.
Sources
- Chipotle Mexican Grill, fourth quarter and full year 2025 results, 3 February 2026 (4,056 restaurants as of 31 December 2025; 334 company-owned openings, 257 with a Chipotlane; digital sales 36.7 percent of food and beverage revenue): newsroom.chipotle.com
- Chipotle, 21 million active Rewards members and nearly 90 percent of digital transactions tied to Rewards, per the company's 2025 reporting.
- HProxy measurement, 24 August 2026: one direct request from a datacenter server (HTTP 200, homepage) and 20 elite HTTP proxies from our free proxy list (16 no connection, 4 homepage).