WebstaurantStore Scraper

Extract structured product data from WebstaurantStore search results, category/listing pages, and product URLs. It is useful for restaurant-supply catalog research, price monitoring, assortment analysis, and procurement workflows.

Extracted fields

Each dataset item contains the product name and URL, SKU/product ID, brand, category, description, price and currency, availability, rating, review count, primary image, source URL, scrape timestamp, and extraction warnings.

Input examples

Search:

{ "searchQueries": ["disposable gloves", "commercial blender"], "maxResults": 50 }

Product or listing URL:

{ "startUrls": [{ "url": "https://www.webstaurantstore.com/" }], "maxPages": 2, "maxResults": 25 }

Reliability and limits

WebstaurantStore can present Cloudflare challenges, especially to datacenter IPs. For production runs, configure an authorized Apify residential proxy, preferably with US geography. If all pages are challenged or fail, the actor exits with an error diagnostic and does not emit fabricated products. The actor does not log in, place orders, access customer data, or bypass authentication.

maxResults caps both returned product records and product-record billing events. The default result-event price is intended to be configured in the Actor's private monetization settings before Store publication.

Legal note

Use this actor only for information you are permitted to access. Respect WebstaurantStore's terms, robots guidance, applicable law, rate limits, and any access controls. You are responsible for your use of the extracted data.

Use cases

• Monitor public products, prices, availability, sellers, and catalog changes.
• Schedule repeatable collection and export results to downstream workflows.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Output example

{
  "recordType": "Example Record type",
  "productId": "Example Product ID",
  "name": "Example Product name",
  "url": "Example Product URL",
  "sku": "Example SKU",
  "brand": "Example Brand",
  "category": "Example Category",
  "description": "Example Description",
  "price": 1,
  "currency": "Example Currency",
  "availability": "Example Availability",
  "rating": 1
}

The exact fields depend on the selected input and what the public source exposes. Use the dataset schema as the machine-readable contract and retain source URLs for verification.

Run WebstaurantStore Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/webstaurantstore-scraper').call({
  "startUrls": [],
  "searchQueries": [],
  "maxResults": 25,
  "maxPages": 3,
  "enrichDetails": true,
  "includeDescription": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Pricing and cost control

This Actor uses pay-per-event pricing. Charges follow the live event definitions shown below.

Event	Price (USD)	When it is charged
product-record	$0.005	One charge for each schema-valid WebstaurantStore product record stored in the dataset.
apify-actor-start	$0.00005	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).

For example, 100 product-record events cost $0.5, plus any enabled Actor-start event. Empty or failed work should be checked in the run log and dataset before reuse.

Support

When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

Frequently asked questions

Can I schedule WebstaurantStore Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/webstaurantstore-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.