B&M Stores Scraper API
B&M Stores is a UK discount retailer whose online catalogue covers groceries, home goods and lifestyle products.
Collecting that catalogue at scale means dealing with JavaScript-rendered pages, bot defences and changing markup. A managed scraping API handles those layers for you and returns the page content or structured data your team can parse. This guide explains what you can collect, how the credit model affects cost, and which controls to set before running a B&M Stores job.
What you can collect from B&M Stores
The useful targets on bmstores.co.uk fall into four groups. Product pages carry names, specifications and category placement. Listing and product pages carry prices and availability signals. Review sections carry ratings and customer comments. Delivery information may appear alongside price and stock. Which of these you can reach depends on the page layout and on whether the content is rendered by JavaScript; a managed API returns the rendered HTML or extracted fields, and your parser or extraction rules decide what becomes a row in your dataset.
A practical field map looks like this:
- Product identity: name, SKU or product URL, category breadcrumb.
- Commercial data: current price, any promotional price, shipping cost, estimated delivery window.
- Availability: in-stock or out-of-stock status, and store-level availability where the page exposes it.
- Specifications: size, colour, material, pack quantity and other attributes shown on the product page.
- Reviews: rating, review count and review text where present.
Treat each field as optional until you have confirmed it on a sample of pages. B&M Stores pages vary by category, and a selector that works on one product type may return nothing on another.
How a managed B&M Stores scraping job works
The workflow has three stages. First, create an account and obtain an API key; the supplied plan information includes a free starting allowance. Second, send a request containing the target URL and any options you need, such as JavaScript rendering, premium proxies or extraction rules. Third, receive the rendered page or extracted data and parse it into your own schema.
The API layer is responsible for proxy rotation, headless browser rendering and retry handling. Your code is responsible for choosing URLs, defining selectors or extraction rules, and validating the output. That division matters when a job fails: a request that returns an error status is an API or network problem, while a request that succeeds but returns empty fields is usually a selector or page-layout problem. Check the response status before you debug your parser, and check your parser before you blame the proxy.
Worked example: estimating credit cost
Credits are consumed per successful request, and the number depends on which features you enable. The supplied rules are: a standard request starts at 1 credit; JavaScript rendering costs 5 credits per successful request; premium proxies cost 10 credits without JavaScript rendering or 25 credits with it. Credits are valid for one month and do not roll over.
Suppose you want to refresh 2,000 product pages each month and each page needs JavaScript rendering plus premium proxies. At 25 credits per request, that is 50,000 credits per monthly run. A plan with 75,000 credits covers that run with headroom for retries and ad-hoc checks. If you can drop premium proxies and keep only rendering, the same run costs 10,000 credits. Run the arithmetic against your own page count before choosing a plan, and budget for retries on top of your successful-request total.
Choosing the right controls for a B&M Stores job
Not every job needs every feature. Use this checklist to decide what to enable before your first production run.
- Does the product data appear only after JavaScript runs? If yes, enable rendering. If the HTML already contains the price and stock text, leave rendering off and save credits.
- Is the site returning challenge pages or empty shells from your usual location? Try premium proxies. If the pages load cleanly without them, skip the extra cost.
- Do you need a specific country view of the catalogue? Geotargeting routes requests through a chosen country or territory.
- Do you need exact elements rather than the whole page? CSS or XPath extraction rules return only the fields you name.
- Do you need a visual record of a page? Full-page screenshots capture the rendered layout.
- Will several people run jobs? Team management assigns credit and concurrency quotas per user.
Start with the smallest set of features that returns correct data on a sample of ten pages, then scale up. Enabling premium proxies and rendering together multiplies the credit cost per request, so confirm that each feature is actually needed before you commit to a monthly volume.
Legality and compliance
Scraping B&M Stores can be lawful when it respects the site's terms of service and applicable law. That is a general statement, not legal advice for your jurisdiction or use case. Before you collect, review the site's terms, the robots directives and any contractual limits that apply to you. Avoid collecting personal data unless you have a lawful basis, and keep request rates modest enough that you do not degrade the service for other users.
A managed API can help with compliance mechanics such as request pacing and proxy rotation, but it does not transfer legal responsibility to the provider. Your team remains responsible for what you collect and how you store it.
Plan and pricing context
The supplied plan table lists monthly prices and credit allowances across standard and enterprise tiers. Prices are exclusive of VAT. Credit allowances reset monthly and do not roll over, so size your plan to your busiest expected month rather than your average. Concurrency limits determine how many requests can run at once; a job that needs many parallel requests will hit the concurrency ceiling before it hits the credit ceiling.
Use the plan table as a dated reference and confirm current prices and allowances with the provider before purchase. The table rows are preserved exactly in the accompanying pricing module.
| Plan | Monthly price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
All prices are exclusive of VAT. Credit allowances are valid for one month and do not roll over. Requests start at 1 credit each; JavaScript rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits depending on rendering. Confirm current prices and allowances with the provider before purchase.
Frequently asked questions
What is B&M Stores?
B&M Stores is a UK discount retailer selling groceries, home goods and lifestyle products, often at lower prices than mainstream retailers. Its online catalogue is the target for most scraping jobs.
What does scraping B&M Stores involve?
It means extracting data from the B&M retail website, usually for price comparison, inventory tracking or product research. A managed API handles proxy rotation and JavaScript rendering so your code can focus on parsing the returned content.
Is scraping B&M Stores legal?
It can be lawful when you follow the site's terms of service and applicable law. Review those terms and your own obligations before collecting, and keep request rates reasonable. This is general information, not legal advice.
What data can I extract from B&M Stores?
Product names, prices, shipping costs, estimated delivery times, specifications and reviews are the common targets. Custom extraction rules let you pull only the fields you need rather than the whole page.
How can I scrape B&M Stores data quickly?
Send the target URL to the API with your key and enable premium proxies and JavaScript rendering where the page needs them. Those features reduce blocking and incomplete renders, which are the usual causes of slow or failed jobs.
Do I need an API to scrape B&M Stores?
No, but an API removes much of the operational work: proxy management, browser rendering and retries. A self-built scraper can work, but you take on those layers yourself and must maintain them as the site changes.