Two different jobs inside “ecommerce”
Teams often buy one proxy product for both “running a store” and “watching the market.” Those are different rhythms:
- Store operations: backends for stores / brand sites / content-commerce you are authorized to operate—need the same exit for the term → prefer static residential.
- Market research / assortment / competitor page checks: publicly reachable listings, details, landing pages, multi-region storefront previews → prefer rotating residential (traffic / GB).
Forcing one product across both jobs is how teams buy the wrong line or lose bill control. If you still need the rotating-vs-static frame, read Rotating vs static residential first. This page is an ecommerce scene map: which side store work goes to, which side research goes to, and how to split when you need both. On-site scene name: Global commerce. Lawful, authorized use only; stores mean authorized operations; research means publicly reachable pages and data.
Store operations: why static first
Static residential provides a fixed exit for the term—aligned with store operations and persistent business environments. Shared or dedicated.
Fit:
- Long login on an authorized store backend
- Brand / content-commerce sites that need a stable exit
- Pinning region to a target market (US / JP / SG / UK, etc.—inventory in console)
Billing mindset: mainly IP × month, not how many GB you browsed that month (unit frame: Billing GB vs IP).
Shared vs dedicated (pointer only; deep guide zt-02):
- Single-store validation / start → try shared static first (about $1.50/IP/month, confirm in console)
- Multi-store / reduce cross-store exit bleed → lean dedicated static or a mix (about $5/IP/month, confirm in console)
Detail: Shared vs dedicated static. Regions: Locations.
Market research and assortment: why rotating first
Rotating residential aligns with public data and market insight: pick country/region and rotate exits.
Fit:
- Public listing / detail spot checks
- Competitor landing pages and public price / stock observation
- Multi-country UI, currency, and checkout previews on public surfaces
Billing mindset: GB; published about $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only)—deeper cost math in Billing GB vs IP. Price-monitoring deep dive: Price monitoring.
Do not rent monthly static IPs just to “rotate through public pages”—you want traffic and rotatable exits, not a month-long identity. Entry: Rotating + Pricing.
One table: choose by ecommerce task
Task-type contrast
| Dimension | Store ops (static lean) | Research / assortment (rotating lean) |
|---|---|---|
| What you buy | Fixed exit for the term | Rotatable residential exits + traffic |
| Billing | Per IP / month (shared or dedicated) | Per GB (optional large bundle) |
| Typical use | Authorized store backends, persistent environments | Public page checks, multi-region sampling |
| ZTProxy entry | Static; shared/dedicated → zt-02 | Rotating; billing → zt-03 |
| Common miss | Using static to bulk-scrape public pages | Using rotating GB to hold long login identity |
Prices and capabilities: console. This table is not a success-rate or platform-risk promise.
Choose by ecommerce task
| Task | Prefer | Why | ZTProxy |
|---|---|---|---|
| Authorized single-store long backend login | Shared static (validate first) | Fixed identity + lower start cost | Shared ~$1.50/IP/month (console) |
| Multi-store; reduce exit bleed across shops | Dedicated static or mix | Clearer exclusive fixed exits | Dedicated ~$5/IP/month; zt-02 |
| Weekly public product/price checks in target countries | Rotating | No long login identity required | Rotating ~$0.40/GB (console) |
| Same project runs stores and assortment research | Split: static + rotating | Different exit behavior and bill units | Static + Rotating |
| New-market UI / currency / checkout preview | Rotating + geo | Short, multi-region sampling | Rotating + Locations |
| Still unsure rotating vs static class | Read selection guide | Avoid replaying the whole comparison here | Rotating vs static |
Short cases (illustrative, not promises)
Authorized single-store backend. Term-long same exit → static; start shared (~$1.50/IP/month, console), then decide dedicated after a real backend smoke test.
Multi-store isolation. Plan fixed exits per store (or stable environment); dedicated or mix when isolation matters. Do not jam unrelated accounts onto one exit “to see.”
Weekly public assortment / price checks. Public data, no long login → rotating by GB. No need to month-rent piles of static IPs for this.
Same team runs stores and research. Split configs: static monthly for stores + rotating GB for research. Do not force one product.
New-market storefront / currency / language preview. Short multi-region sampling → rotating + geo; add static only after an authorized store exists for that market.
“I only need the same IP for a few minutes.” That is rotating sticky session territory—not monthly static, and not a substitute for store identity. See Sticky vs static and the selection guide.
Multi-store and target markets
One store (or one stable environment) → clear exit plan; unrelated accounts should not share an exit by luck. Shared/dedicated trade-offs: zt-02.
Target markets (US / JP / SG / UK, …): Locations. City-level inventory changes—confirm in console or with sales; this page invents no stock numbers. Smoke-test one real store flow before scaling IPs.
How to read price
- Store side (static): shared about $1.50/IP/month; dedicated about $5/IP/month (USD, console).
- Research side (rotating): about $0.40/GB; large-bundle rules on Pricing and zt-03.
Different bill units—do not pick by “which unit price looks lower.” Confirm plans on Pricing. Payment context site-wide: USDT/USDC available; Visa/Mastercard applying / pending.
Pre-order checklist
- Job: store ops, public research, or both (split if both)?
- Product: rotating / shared static / dedicated static; quantity or traffic tier.
- Region: confirmable on Locations + console?
- Protocol: HTTP or SOCKS5 from console credentials.
- Scope: authorized business vs public data—clear?
- Pace: small traffic / single store first. Connect: Docs EN quickstart.
FAQ
For cross-border store ops, static or rotating?
Authorized store backends that need the same exit for the term → static first. Public assortment / competitor / multi-region checks → rotating first. Need both → split. Frame: Rotating vs static. Products: static, rotating.
I only do assortment and competitor page checks—do I need static?
Usually no. Public pages + rotatable exits fit rotating by GB. Selection: zt-01.
How should multi-store ops plan fixed connections?
Plan fixed exits per store (or stable environment); start shared for one store, lean dedicated or mix for multi-store isolation. Do not invent “N IPs per store”—scale after a real smoke test. Detail: Shared vs dedicated.
What proxy for Amazon / DTC cross-border ops?
Split by task, not by platform name: authorized long backend login → static; public listing / landing checks → rotating. No promise of any platform’s rules or “never blocked” outcomes—authorized use + console smoke test.
Can store and research share one proxy setup?
Hard-sharing is a bad default. Exit behavior and bill units differ—split: static for stores, rotating for public research. Billing: GB vs IP.
How is ecommerce billed?
Static IP / month (shared ~$1.50, dedicated ~$5); rotating GB (~$0.40/GB; bundles on pricing). USD; console + Pricing win. Do not cross-compare unit prices across job types.
Are HTTP and SOCKS5 supported?
Depends on product. After order, use console-returned protocol, host, port, and auth. Docs EN quickstart.
How do I confirm country/city inventory? Mainland China?
Start with Locations, then console or sales; stock changes. All proxy services on this site are not supported for use in mainland China.
Next steps
- Mark the tables: stores → static; research → rotating; both → split.
- Store side: Static (shared/dedicated → zt-02); research: Rotating (bill → zt-03).
- Confirm plan, region, and quantity on Pricing; scene hub: Solutions.
- Connect via Docs EN quickstart: one real authorized backend path and/or a small rotating sample before scale.
Stores → static · research → rotating · confirm on Pricing →
Unsure? On-site support or [email protected]. Split by job first; unit price second.