Faire Product & Brand Details Scraper avatar

Faire Product & Brand Details Scraper

Pricing

Pay per event

Go to Apify Store
Faire Product & Brand Details Scraper

Faire Product & Brand Details Scraper

๐Ÿ›๏ธ Turn supplied public Faire product URLs into sourcing-ready stock, retail-price, MOQ, option, image, orderability, lead-time, rating, review, and brand minimum records.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Share

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 primary-option details
  • ๐Ÿ“ฆ 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, the primary active option, stock availability, and brand-level details.

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?

GroupExample fieldsWhy it matters
IdentitycanonicalUrl, productToken, title, categoryJoin and deduplicate products
Contentdescription, imageUrls, badgesEnrich catalogs and merchandising reviews
AvailabilityavailableUnits, productState, brandAvailabilityTrack whether a product can be ordered
Retail priceretailPriceCents, currencyCompare suggested retail economics
Product termsminOrderQuantity, unitMultiplier, perStyleMinOrderQuantityEstimate opening inventory
Pack ruleshasPrePacksAvailable, soldInPrePacksUnderstand case and pre-pack handling
OptionoptionToken, optionName, optionSku, optionGtinMap the primary active option
Measurementsweight, massUnitSupport shipping and catalog workflows
BrandbrandToken, brandName, brandPublishedProductsCountGroup products by supplier
Brand minimumbrandMinimumOrderCents, brandMinimumOrderCurrencyModel supplier opening orders
Lead timebrandLeadTimeDays, lower and upper boundsPlan replenishment timing
ReputationbrandAverageRating, brandReviewCountAdd supplier quality signals
Pricing flagshasVolumePricingIdentify products with quantity pricing
FreshnessscrapedAtCompare 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 tierPrice per Faire product1,000 products plus start
Free$0.00074073about $0.75
Bronze$0.00064411about $0.65
Silver$0.00050241about $0.51
Gold$0.00038647about $0.39
Platinum$0.00025765about $0.26
Diamond$0.00018035about $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

ParameterTypeRequiredDescription
startUrlsarrayYesPublic Faire product-detail URLs
maxItemsintegerNoMaximum unique products to save, from 1 to 1,000
maxRequestRetriesintegerNoProxy-session attempts per product, from 1 to 5
proxyConfigurationobjectNoApify Proxy or custom proxy configuration

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

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 flattens the first active, non-deleted option into stable option columns.

This keeps one chargeable row per supplied product and makes CSV exports usable.

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.

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; additional option objects are not emitted as separate rows in v1.

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.

If every URL fails, inspect the run log for HTTP challenge or embedded-state errors.

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.

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?

It reports the option count and flattens the primary active option into the product row.

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.

Expand the same catalog workflow with other Automation Lab actors:

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

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.