Commerce intelligence
Track prices across the markets you serve
Check storefronts from the markets that drive your pricing decisions, then send observations into the dashboards you already run.
Who this is for
Pricing, ecommerce, and intelligence teams who compare public prices and availability across countries or storefronts.
See the price the local shopper sees
Location-aware access plus sticky or rotating sessions so scheduled monitors collect comparable price and stock fields.
Monitoring outcomes
Local prices and promotions
Capture currency, discounts, and banners that change by country.
Stock and assortment
Record in-stock flags and listing presence, not only the numeric price.
Fits existing pricing tools
Your scheduler and warehouse stay in place. The proxy is an access setting.
Built for scheduled storefront checks
Market-level access
Select the dashboard location that matches each storefront market.
Repeatable sessions
Sticky sessions help a product-page journey stay consistent during one check.
Script-friendly credentials
Pass HOST, PORT, USERNAME, and PASSWORD into any HTTP client.
What teams monitor
Competitor prices
Track the same SKU in several countries on a fixed interval.
Stock status
Detect public sold-out or limited-availability states.
Promotion changes
Note landing-page and listing changes over time.
Recommended setup
Residential or mobile
Storefronts often vary by consumer network. Start with mobile or residential for the markets you sell in. Use datacenter only when the target remains accurate on that product.
Sessions
Sticky for browse → product page in one check. Rotate between scheduled cycles if you want a new IP each run.
Location
One location per market you price against. Tag every stored observation with that location.
Before you start
- A SKU or URL list per storefront, plus the countries you care about.
- Fields to extract: price, currency, stock, and promotion text.
- A Premip plan covering those locations.
- A schedule and a table or warehouse for results.
How to set up price monitoring
Prove one SKU in one market, then clone the job across the catalog.
Step 1
Freeze the SKU list
Export canonical product URLs or search queries. Decide the check interval (hourly, daily) and which fields are required for a valid row.
Step 2
Create the proxy
Sign up, choose a plan, and open the proxy detail page for credentials.
Step 3
Assign a location per market
For each country you monitor, use a matching dashboard location. Do not mix markets in one run if prices are geo-specific.
Step 4
Configure the monitor client
Set the HTTP proxy to http://USERNAME:PASSWORD@HOST:PORT. Send a realistic User-Agent and respect the site’s public access patterns.
Step 5
Validate a single product page
Confirm currency, price, and stock match what you expect for that location. Save a sample HTML or JSON for parsers to lock against.
Step 6
Pick session behavior
Use a sticky session if the check follows search → PDP. Rotate after the batch if the next cycle should use a new IP.
Step 7
Parse and store with location tags
Write timestamp, market, URL, price, currency, and stock. Alert on parse failures, not only on price deltas.
Step 8
Roll out the catalog
Increase SKUs and markets once the parser stays stable. Add concurrency gradually.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://example.comPrice monitoring questions
- Can I monitor more than one market?
- Yes. Run the job once per dashboard location and store the market on each row.
- Can I monitor stock as well as price?
- Yes. Public listing and availability fields can be collected with the same proxy setup as price.
- Is Premip a pricing dashboard?
- No. It provides access. Charts, rules, and alerts live in your commerce or BI tools.
- What if a storefront blocks datacenter IPs?
- Switch the proxy product to residential or mobile for that market and re-run the validation URL.
Message us
Reach support on Telegram, email, phone, or the contact form. Include your account email and, if you have one, your order ID.