Faire Product & Brand Details Scraper

Turn public Faire product pages into structured wholesale sourcing records.

Paste one or many faire.com/product/p_... URLs and receive one normalized row per product with retail price, stock, MOQ, case-pack rules, images, option state, brand minimums, lead time, rating, and review count.

This Actor is designed for retailers, sourcing teams, catalog operators, and analysts who already have product-detail URLs and need repeatable data instead of manual copying.

• 🛍️ Extract product and every public option, with CSV-friendly primary columns
• 📦 Compare minimums, multipliers, pre-packs, and orderability
• 🏬 Enrich records with brand economics and reputation
• 🔁 Schedule recurring stock, price, and lead-time checks
• 📤 Export to JSON, CSV, Excel, Google Sheets, or your API workflow

What does Faire Product & Brand Details Scraper do?

The scraper visits each supplied public Faire product-detail page and reads the server-rendered product and brand state.

It creates one product record for every successfully processed unique product token.

The output combines product identity, merchandising content, wholesale order rules, every supplied public option, stock availability, and brand-level details. Familiar flat columns still describe the primary active, non-deleted option (or first option if none qualifies).

It does not require a Faire buyer account, Faire API key, or browser automation for the supported public pages.

This version intentionally accepts product-detail URLs only.

It does not claim Faire search, category, brand-page, account-dashboard, or sitemap discovery.

Who is it for?

Independent retailers

Compare suggested retail prices, minimum quantities, brand order minimums, and lead times before adding products to a buying shortlist.

Wholesale sourcing teams

Turn supplier research into consistent rows that can be sorted by availability, MOQ, rating, review count, or shipping origin.

PIM and catalog operators

Enrich internal product records with canonical Faire tokens, descriptions, image URLs, option identifiers, SKU values, measurements, and lifecycle state.

Market and assortment analysts

Build recurring snapshots of products already under review and detect changes in stock, orderability, price, or brand terms.

Automation developers

Call the Actor through the Apify API, webhooks, integrations, or MCP without maintaining Cloudflare-aware request and parsing logic.

Why use this Faire scraper?

Manual sourcing reviews are slow and inconsistent.

Product pages mix consumer-facing content with wholesale economics, option state, and brand-level terms.

This Actor places those values in stable columns.

• ✅ Strict URL validation prevents unrelated Faire pages from producing misleading rows
• ✅ Duplicate product tokens are processed once
• ✅ Proxy sessions rotate after a challenge or incomplete response
• ✅ Total extraction failure exits non-zero instead of reporting false success
• ✅ One row per product makes monitoring and catalog joins predictable
• ✅ Numeric values remain numbers for filtering and calculations

What Faire data can you extract?

Group	Example fields	Why it matters
Identity	canonicalUrl, productToken, title, category	Join and deduplicate products
Content	description, imageUrls, badges	Enrich catalogs and merchandising reviews
Availability	availableUnits, productState, brandAvailability	Track whether a product can be ordered
Retail price	retailPriceCents, currency	Compare suggested retail economics
Product terms	minOrderQuantity, unitMultiplier, perStyleMinOrderQuantity	Estimate opening inventory
Pack rules	hasPrePacksAvailable, soldInPrePacks	Understand case and pre-pack handling
Option	optionToken, optionName, optionSku, optionGtin	Map the primary active option
Measurements	weight, massUnit	Support shipping and catalog workflows
Brand	brandToken, brandName, brandPublishedProductsCount	Group products by supplier
Brand minimum	brandMinimumOrderCents, brandMinimumOrderCurrency	Model supplier opening orders
Lead time	brandLeadTimeDays, lower and upper bounds	Plan replenishment timing
Reputation	brandAverageRating, brandReviewCount	Add supplier quality signals
Pricing flags	hasVolumePricing	Identify products with quantity pricing
Freshness	scrapedAt	Compare scheduled snapshots

Optional source values are omitted when Faire does not publish them for that product.

How much does it cost to scrape Faire product details?

This Actor uses pay-per-event pricing.

A $0.005 start event covers run setup, and an item event is charged only for each complete Faire product record saved to the dataset.

Apify tier	Price per Faire product	1,000 products plus start
Free	$0.00074073	about $0.75
Bronze	$0.00064411	about $0.65
Silver	$0.00050241	about $0.51
Gold	$0.00038647	about $0.39
Platinum	$0.00025765	about $0.26
Diamond	$0.00018035	about $0.19

Proxy and compute usage are included in the Actor charge; you do not need to calculate separate infrastructure fees.

For the cheapest first test, keep the prefilled input at one product: about $0.00575 on the Free tier.

Before a larger monitoring job, estimate the maximum charge in Console using the number of supplied unique product tokens.

How to scrape Faire products

1. Open the Actor input page.
2. Add one or more public URLs matching https://www.faire.com/product/p_....
3. Set Maximum products to control the run size.
4. Keep the recommended SHADER US proxy unless you have a tested alternative.
5. Start the run.
6. Preview the Faire products dataset view.
7. Export the records or connect them to your downstream workflow.

A one-product run normally finishes well within the five-minute Actor timeout.

Input parameters

Parameter	Type	Required	Description
startUrls	array	Yes	Public Faire product-detail URLs
maxItems	integer	No	Maximum unique products to save, from 1 to 1,000
maxRequestRetries	integer	No	Proxy-session attempts per product, from 1 to 5
proxyConfiguration	object	No	Apify Proxy or custom proxy configuration
failOnPartialFailure	boolean	No	Default false; fail incomplete selected snapshots after retaining rows and summary

The recommended default proxy is Apify SHADER in the United States.

maxItems limits the selected unique URLs, not replacement successes. Explicit limits must be integers within the listed ranges. maxRequestRetries counts total attempts including the first; confirmed 404/410 pages receive one attempt. Transient failures use fresh proxy sessions within the same bounded limit.

Do not paste search, category, brand, sitemap, login, or account URLs.

Unsupported URLs fail early with an actionable validation message.

Input example

{
  "startUrls": [
    { "url": "https://www.faire.com/product/p_8x9adp4dzv" }
  ],
  "maxItems": 1,
  "maxRequestRetries": 3,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["SHADER"],
    "apifyProxyCountry": "US"
  }
}

You may also provide a URL as a plain string when calling the Actor through the API.

Output example

{
  "canonicalUrl": "https://www.faire.com/product/p_8x9adp4dzv",
  "productToken": "p_8x9adp4dzv",
  "title": "BIG sticker Suncatcher \"ex-voto flower\"",
  "category": "Suncatcher",
  "imageCount": 2,
  "shipsFrom": "Ships from France",
  "minOrderQuantity": 5,
  "unitMultiplier": 1,
  "availableUnits": 30,
  "retailPriceCents": 1500,
  "currency": "USD",
  "brandName": "Poulette Magique",
  "brandMinimumOrderCents": 10286,
  "brandLeadTimeDays": 15,
  "brandAverageRating": 5,
  "brandReviewCount": 7,
  "hasVolumePricing": false,
  "scrapedAt": "2026-07-18T04:58:09.317Z"
}

The complete record also contains description, image URLs, badges, option state, orderability, measurements, and lead-time bounds when available.

Understanding prices and quantities

retailPriceCents is the public suggested retail amount in the accompanying currency.

For example, 1500 with USD means a retail price of USD 15.00.

brandMinimumOrderCents is the brand-level minimum in brandMinimumOrderCurrency.

minOrderQuantity is the product-level MOQ.

optionMinOrderQuantity applies to the primary active option.

unitMultiplier and optionUnitMultiplier help model how many units are added per cart quantity.

Wholesale buyer-only prices or private deal terms are not claimed by this Actor.

Understanding options and availability

A Faire product can contain multiple options.

The Actor reports optionCount and an ordered options array containing every supplied public option, including inactive/deleted options with their source flags. Missing source options produce []. Each option includes token, name, SKU, GTIN, state/lifecycle, availability, units, retail cents/currency, MOQ, multiplier, pre-pack flag and weight/unit when published.

The first active, non-deleted option is still flattened into stable columns; if none qualifies, the first supplied option is used. JSON exports and the Product options view expose the nested array. This keeps one row and one item event per product, with no extra charge per variant, and preserves familiar CSV columns.

Use optionToken, optionSku, and optionGtin to map the primary option.

Use optionState, optionLifecycleState, brandAvailability, and orderabilityType together when evaluating availability.

availableUnits reflects the public option value at scrape time and may change between runs.

Run completeness and retry lists

Download Run completeness and failed-product retry list from the Output tab, or fetch RUN_SUMMARY from the run's default key-value store. Its schema is faire-run-summary/v1.

It reports submitted (including duplicates), unique, selected, attempted (unique products visited), saved, failed, skippedByLimit, complete, and failures. Each failure contains canonical url, sanitized category, optional httpStatus, and attempts. complete refers only to selected URLs; capped-out URLs are not failures. Diagnostics never appear as product rows.

By default, partial runs succeed with valid rows and an explicit warning. Set failOnPartialFailure: true for monitoring that must signal incomplete snapshots; the run fails only after retaining useful rows and summary. Zero saved products always fails. Invalid inputs fail before network access and do not produce a summary. A setup or storage failure also fails; an ambiguous failed dataset write is not retried. In that case counts describe confirmed writes, and attempted may exceed saved + failed.

For example, two unique valid products, a duplicate and a missing product yield submitted: 4, unique: 3, selected: 3, saved: 2, failed: 1, and complete: false. Submit the URLs in failures to retry only the missing subset.

Tips for reliable recurring monitoring

• 🔁 Use the same canonical product URL set on every scheduled run
• 🕒 Store scrapedAt with each snapshot before comparing changes
• 🧮 Compare integer cent fields rather than formatted currency text
• 📦 Watch MOQ and multiplier changes alongside price changes
• 🏬 Group by brandToken, not only the display name
• ⚠️ Treat missing optional fields as unpublished source data, not zero
• 🎯 Keep concurrency conservative by using this URL-detail workflow
• 🌐 Retain the recommended proxy unless another route has been verified

Integrations and workflow patterns

Google Sheets sourcing tracker

Schedule the Actor, send dataset rows to Google Sheets, and add buyer-review columns for margin, fit, and reorder priority.

Airtable product intake

Use productToken as an external identifier and update image, MOQ, stock, and brand fields after each run.

PIM enrichment

Join canonicalUrl or productToken to candidate products, then map descriptions, images, option SKU, and measurements into your PIM.

Stock and term monitoring

Store each run in a warehouse and alert when availableUnits, retailPriceCents, minOrderQuantity, or brandLeadTimeDays changes.

Supplier scorecard

Aggregate products by brandToken and combine minimum order, lead time, rating, review count, and catalog size.

Webhooks

Attach an Apify webhook to trigger your ETL or notification service when a scheduled run succeeds or fails.

API usage with JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/faire-product-brand-details-scraper').call({
  startUrls: [{ url: 'https://www.faire.com/product/p_8x9adp4dzv' }],
  maxItems: 1,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Use environment variables or a secret manager for your Apify token.

API usage with Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/faire-product-brand-details-scraper').call(run_input={
    'startUrls': [{'url': 'https://www.faire.com/product/p_8x9adp4dzv'}],
    'maxItems': 1,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

The returned dataset can be loaded into pandas or written directly to your catalog pipeline.

API usage with cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~faire-product-brand-details-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "startUrls": [{"url":"https://www.faire.com/product/p_8x9adp4dzv"}],
    "maxItems": 1
  }'

After the run finishes, fetch items from its defaultDatasetId.

Use with Apify MCP

Apify MCP lets Claude Code, Claude Desktop, Cursor, or VS Code call this Actor as a tool.

For Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/faire-product-brand-details-scraper"

For Claude Desktop, Cursor, or VS Code, add an HTTP MCP server:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/faire-product-brand-details-scraper"
    }
  }
}

Example prompts:

• “Extract the wholesale order terms from these Faire product URLs.”
• “Compare stock, MOQ, and lead time for my Faire sourcing shortlist.”
• “Return a CSV-ready table with Faire brand ratings and minimum orders.”

Data quality and limitations

The Actor extracts public values available in Faire's server-rendered product state at run time.

Optional fields differ by product and brand.

The primary active option is flattened; all public option objects are nested in options, not emitted as separate rows. Values unavailable from the public source remain missing, not invented wholesale prices.

Currency can depend on the public session geography and Faire's current presentation rules.

The Actor does not log in and cannot access buyer-only wholesale prices, private discounts, checkout data, or account dashboards.

Faire may change its page structure or anti-bot controls.

A total extraction failure makes the run fail so monitoring systems can detect the problem.

Troubleshooting

The run says my URL is unsupported

Confirm the URL begins with https://www.faire.com/product/p_ and contains a real public product token.

Remove search, category, brand, sitemap, referral, login, and dashboard URLs.

A product could not be extracted

Open the URL anonymously and confirm the product is still public.

Keep retries at the default value and use the recommended SHADER US proxy configuration.

Inspect RUN_SUMMARY for failed canonical URLs, categories, HTTP status and attempt counts. If every URL fails, the run fails. For a partial run, retry the summary's failed URLs or enable failOnPartialFailure to signal incomplete snapshots.

A field is missing

Faire does not publish every optional value for every product.

Missing is different from zero or false, so the Actor omits unavailable optional fields.

The same product was submitted twice

Duplicate product tokens are intentionally processed once to prevent duplicate rows and charges.

Is scraping Faire legal?

This Actor accesses public product pages without logging in.

Scraping legality depends on your jurisdiction, purpose, contract, and use of the data.

Respect Faire's terms, applicable database and copyright rules, privacy laws, and reasonable request volumes.

Do not use the Actor to access private accounts, evade authorization, republish protected creative assets without permission, or make automated purchasing decisions without review.

You are responsible for ensuring that your collection and downstream use are lawful.

Frequently asked questions

Do I need a Faire buyer account?

No. The supported workflow reads public product-detail pages.

Can it search Faire for products?

No. V1 requires supplied product URLs and does not claim search or category discovery.

Can it process a Faire sitemap?

No. Sitemap input is deliberately outside this version's contract.

Does it extract wholesale buyer prices?

It extracts public retail-price and order-term values only, not private buyer pricing or deals.

Does it return every variant?

Yes, every option supplied by the public response is included in options. The primary active option remains flattened into the product row; variants do not add chargeable rows.

Can I monitor products every day?

Yes. Use an Apify schedule and compare numeric values by productToken and scrapedAt.

Why are monetary values in cents?

Integer cents avoid floating-point errors and preserve the source representation for calculations.

What happens if Faire blocks every request?

After bounded proxy-session retries, the run fails rather than returning an empty successful dataset.

Related ecommerce scrapers

Expand the same catalog workflow with other Automation Lab actors:

• Amazon Scraper for retail marketplace search data
• Amazon Reviews Scraper for review intelligence
• Google Shopping Scraper for cross-retailer product comparisons
• Shopify App Reviews Scraper for ecommerce software research

Related actors cover different public sources and do not replace Faire-specific wholesale order fields.

Data handling and dependencies

This Actor uses deterministic parsing, not AI, and sends no input or output to model providers. It requests public Faire URLs through Apify Proxy by default. Apify hosts the run, logs, product dataset and RUN_SUMMARY; the Actor operator covers the default infrastructure cost within the documented events. If you supply a custom proxy, you control its credentials, terms and any provider charges.

Only public product/brand catalog fields are saved. Buyer accounts, brand owner identities and private account state are not exported. Proxy sessions are ephemeral; credentials, raw pages and cookies are not saved in result storage. Canonical product URLs and safe failure categories may appear in logs. Run datasets, summaries and logs remain in your Apify account under its storage retention settings until expiry or deletion; this Actor creates no external persistent cache or automatic deletion schedule. Delete run storage through Console/API when no longer needed. Faire receives product requests, and the selected proxy provider handles the request traffic. Use only URLs you intend to collect.

This is an independent Automation Lab tool, not affiliated with or endorsed by Faire. It uses Apify's standard Store terms.

Support

For a reproducible issue, include the public Faire product URL, run ID, approximate run time, and the relevant log message.

Do not post Apify tokens, proxy credentials, Faire account details, or other secrets.

Field requests should explain the public source value and the sourcing or catalog workflow it supports.