Proxies for Overstock read a home-goods catalog behind a layered door, on a site in the middle of a rebrand. On 24 August 2026 we sent overstock.com a plain request from a home connection and from a datacenter server. Both returned the homepage, HTTP 200, with Akamai's _abck and bm_sz sensor cookies, Forter, and F5 Shape telemetry, served through a modern hosting layer (Vercel). The homepage loading is not the catalog opening; Akamai gates the product data, Shape scores the session, and Forter scores orders.
Overstock is a home and furniture retailer that took on the Bed Bath & Beyond brand after acquiring the name, so it presents that identity over its discount-marketplace roots. Its data is home-goods pricing, fast-moving furniture stock, and clearance, which makes the proxy job a store-priced read behind an Akamai-and-Shape defense, close to Wayfair in category.
What proxies work best for Overstock?
US rotating residential proxies behind a real browser, one consistent exit per session because Shape scores behavior. A static ISP proxy for a logged-in account. Datacenter proxies are for testing only.
Akamai gates the request, Shape scores the session
The homepage returning 200 is Akamai admitting a first look, not opening the catalog. Akamai's sensor sets _abck only after its data validates and reads the TLS fingerprint before any HTTP, so a bare client fails the request-level check (how the _abck cookie works, what is JA3/JA4 fingerprinting). F5 Shape then scores the session over time (how to handle F5 Shape), so one consistent exit per session beats rotation, and Forter scores orders at checkout. The combination is a residential IP for reputation, a real browser for the sensor and Shape, and consistency across the session, the same Akamai-plus-Shape pattern as Uniqlo and PetSmart.
A broad catalog under a new name
The rebrand is context for the data, not a technical change: the site carries a broad home and furniture catalog with the discount and clearance dynamics Overstock was known for, now under the Bed Bath & Beyond identity. Furniture stock moves and clearance rotates, so a dataset reads on a schedule and records the price and stock over time, treating the catalog as a fast-turning home-goods feed rather than a static price list.
Homepage loads
200, looks open
Akamai sensor
product data gated
F5 Shape score
session behavior
Price and stock
fast-turning home goods
Which proxy type fits which job
| Overstock job | Proxy type | Why |
|---|---|---|
| Price and clearance monitoring | US rotating residential, one exit per session | Akamai gates the request, Shape scores the session |
| Furniture stock and back-order reads | Sticky residential per session | Stock moves; delivery timelines matter |
| Category and catalog collection | Rotating residential | Volume across a pool |
| Review and rating data | Rotating residential | Separate endpoints, own limits |
| Account, cart, checkout | Static ISP | Session and Forter order scoring need one address |
| Parser tests against saved HTML | Datacenter or free | The homepage allows the read; only proves plumbing |
Rotating residential IPs pass Akamai and start clean with Shape, and ISP proxies hold one address for an account. The two are compared in rotating vs static residential proxies.
Setup
Drive a real browser so the sensor sets _abck, keep the cookies, and behave, because Shape is watching (proxies for Playwright). Hold one residential exit per session, read on a schedule to catch clearance, and record price and stock over time. For accounts, use a static ISP address because Forter scores the order. Pace like a shopper.
Sizing
Size by sessions, because Shape scores the session, and by request rate for Akamai. Decide how many pages one session reads before the score tips, and add exits. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Accounts are one static ISP address each, and our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for Overstock
A free datacenter IP loads an Overstock page, so it is fine for testing your parser, but Shape scores a shared datacenter address down and Akamai's limits cut it off. Our free proxy list and proxy checker cover the parser test; the monitoring wants residential from $0.44/GB pay-as-you-go with no KYC behind a real browser. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not rotate mid-session. Against Shape, an IP swap inside a session is a bot tell.
- Keep the sensor cookies. Discarding
_abckrestarts the Akamai layer. - Read clearance on a schedule. Home-goods stock and markdowns move.
- Isolate accounts. One address per account, because Forter scores the order.
- Watch where the session turns. Note when challenges begin; that is your per-session budget. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy gives a browser session a clean, consistent residential address and keeps accounts apart. It does not run Akamai's sensor, does not make a headless client behave for Shape, and does not clear Forter on a suspicious order. Scraping overstock.com runs against its terms of use, a risk that stays with you regardless of the IPs. What a residential exit does is let a well-behaved session start trusted and stay consistent, which is what an Akamai-and-Shape defense rewards. Test with the free proxy list, then read price and stock with residential from $0.44/GB, one exit per session.
Sources
- Akamai, Bot Manager: the request-level layer on Overstock.
- F5, Shape / Distributed Cloud Bot Defense: the session-scoring layer whose telemetry we observed.
- Forter, order fraud prevention: the order-scoring layer present.
- HProxy test on 24 August 2026: plain GET requests to overstock.com from a residential connection and a datacenter server, both returning HTTP 200 with Akamai sensor cookies (
_abck,bm_sz), Forter and F5 Shape telemetry.