datawebotFaire wholesale data: products, variants and case packs
Separate Faire brand, product, variant, case-size and order-minimum records. Compare wholesale price with MSRP and retain currency, account and order context.
Read Faire's terms and account boundary first
The linked General Terms article was rechecked October 4, 2026. It is titled Main TOS - CAN and shows Last Updated: April 15, 2026. This section summarizes that posted version, not its application to any person or project. Check the terms shown for the relevant account and region. The clause mentioning generally available browsers does not establish permission for automated access or reuse.
Scroll to compare →
| Posted section | Faire's wording in brief | Data boundary |
|---|---|---|
| §7(2) — Restrictions | Limits commercial exploitation of the Services or Collective Content and restricts copying, republishing, downloading, and related use of site material, subject to the Terms. | Do not treat a visible wholesale listing as permission to copy or reuse its content. |
| §14(6) — Prohibited Uses | Restricts attempts to access, search, or download Service content through tools such as spiders, robots, crawlers, and data-mining mechanisms, other than Faire-provided software/search agents or generally available third-party browsers. | The browser wording is not a blanket authorization for automated collection. |
| §14(13) — Other users' information | Restricts collecting or storing other users' personally identifiable information without express permission and consistently with the Privacy Policy. | Keep buyer identity, account details, messages, and personal information out of product records and examples. |
| Terms version | The linked Help Center article was rechecked October 4, 2026; it is titled Main TOS - CAN and shows Last Updated: April 15, 2026. | This is a dated summary of the labeled version; use the terms presented for the account and region. It is not a legal determination. |
Map the buyer-facing wholesale record
Faire connects brands and other sellers with retailer and business-use buyers. Keep the seller's brand, a Faire marketplace listing, the retailer's account context, and any downstream POS item as separate records. The retailer search guide distinguishes brand location, ship-from location, and product-level made-in information; it also lists buyer-facing price, brand minimum, ship window, preorder, and lead-time filters.
Scroll to compare →
| Record layer | Details Faire may show in this context | Comparison boundary |
|---|---|---|
| Brand or seller | Displayed brand identity, brand 'based in' location, and seller-set context. | A brand's business location does not establish where an item is made or ships from. |
| Product listing | Product/category details, wholesale price per item, MSRP, brand minimum, ship window, preorder month, and lead time where shown. | Filters and listing visibility can vary with account, market, store type, brand settings, publication status, and preorder eligibility. |
| Ships-from and made-in context | The primary shipping location and the product-level country-of-origin field when available. | Keep ship-from, brand location, and country of manufacture separate; a missing value stays unknown. |
| Retailer POS item | A product a retailer has purchased and then links or adds through a supported POS integration. | This downstream record is not the retailer's view of Faire's complete marketplace catalog. |
Separate products, options, variants, and selling methods
A Faire product listing can have named options such as color, size, or scent. A variant is the selected combination that the brand offers as an item. Preserve identifiers and attributes only when supplied by the authorized source; do not join records by a similar display name alone.
Scroll to compare →
| Grain | Details to keep together | Faire-specific boundary |
|---|---|---|
| Brand product | Brand identity, product title and description, category, listing URL, and publication state when the source provides it. | A product is the family/listing context, not necessarily one sellable option. |
| Option | Option label and source-displayed values, such as size or color. | Retain the label and its order; don't assume all products share the same option set. |
| Variant | The selected option combination, its SKU or other supplied identifier, and item-level price or inventory only when returned by an authorized source. | Keep variant-specific values attached to that option combination; do not infer a private SKU or exact inventory. |
| Selling method | Whether the listing is sold by the item, by the case, through open sizing, or as a prepack where supported. | Open sizing lets a retailer select sizes within a style minimum; prepacks represent a set size run. Case requirements apply to the selected option. |
| Collection or bundle group | A group of individually listed products presented together through Faire's Collections feature. | Faire's product guidance distinguishes this from products packaged and billed as one bundled unit. |
Keep case size, product MOQ, and brand minimum apart
Faire uses separate quantity rules at option, product/style, and brand-order levels. Its retailer case-size article gives an instructional example: for a product offered in three colors with a case size of six, choosing two colors requires six units of each selected color. This example is not a current product listing.
Scroll to compare →
| Rule | Level and meaning | What not to conflate |
|---|---|---|
| Case size | Number of individual units required for a selected option; the retailer-facing help says orders meet the case increment for each option selected. | A six-unit case is not six different options or necessarily a single prepack. |
| Product minimum order quantity (MOQ) | Optional minimum number of units for a product; Faire's brand help distinguishes it from the brand's order minimum. | The ordinary item method does not set a separate MOQ for each option. Open sizing instead describes a style-level minimum; case orders cannot set an MOQ below case size. |
| Brand order minimum | Minimum wholesale spend for the retailer's first order or reorder with that brand; first and reorder values can differ and may be configured by location. | It is a spend threshold, not a unit count, case quantity, or product MOQ. |
| Illustrative option selection | Synthetic illustration from Faire's help example: select two colors from a three-color product; each selected color meets its own six-unit case increment. | Do not carry this help example forward as a live listing, price, or current brand threshold. |
Compare wholesale price, MSRP, and order total
Wholesale price per item, suggested resale price, and the retailer's eventual order total answer different questions. Keep price attached to its product option, currency, market, account context, and observation time. Faire's product guidance describes currency-specific prices and daily exchange-rate conversion when a brand has not entered a price for that currency; record a conversion basis only when the authorized source makes it explicit.
Scroll to compare →
| Value | Context to retain | Interpretation boundary |
|---|---|---|
| Wholesale price | Selected product/variant, per-item basis, currency, market/account context, and observation time. | Do not mistake a case quantity or order subtotal for the unit wholesale price. |
| MSRP | The displayed suggested retail price with its currency and matching product option when available. | It is a resale reference, not the wholesale amount paid by the retailer. |
| Currency and regional display | Whether a listed currency amount is entered by the brand or explicitly shown as a converted value. | Regional display can differ; don't infer a conversion method or carry an old rate forward. |
| Order or invoice total | Order-level shipping, tax/fees, discounts, promotions, payment terms, and timestamp only when provided in an authorized order record. | These values are contextual and changeable, not fixed product attributes. |
Keep authorized account routes and order/POS records distinct
As checked October 4, 2026, Faire's retailer Help lists Shopify, Square, Clover and Lightspeed Retail POS (X-Series), and says retailers are not offered API keys/tokens for a custom direct Faire integration; the Help says Clover's connection is available only to retailers in North America. The linked developer portal URL returned an internal error when checked October 4, 2026; its current API eligibility, scope and schema are unverified here. Keep those routes distinct: retailer POS mappings do not define a marketplace feed, and product/order minimums remain separate marketplace records.
Scroll to compare →
| Route or record | What an authorized source may represent | Boundary |
|---|---|---|
| Brand or partner route | The linked developer portal URL returned an internal error on October 4, 2026; current brand/partner API eligibility and scope could not be verified from the portal. | Treat those details as unverified. This guide asserts no current API schema or public catalog access and does not carry forward legacy endpoint fields. |
| Retailer account and POS | Current retailer Help lists Shopify, Square, Clover (North America only), and Lightspeed Retail POS (X-Series); it describes purchased-product sync through those connections and says retailers receive no API keys/tokens for a custom direct integration. | This is a retailer-account POS path, not an API guarantee or a public catalog feed; its features and field mapping depend on connector, region and settings. |
| Order and line item | Keep an authorized order header separate from its line items, selected products/variants, quantities, and status when those relationships are explicitly supplied. | Do not infer order contents from a public listing or expose retailer identity, messages, payment, or account eligibility. |
| Shipment and inventory | Retain only the shipment or inventory records returned within the authorized account and current integration scope. | These are account- and configuration-scoped records, not public catalog facts or exact marketplace-wide stock. |
| Connector-specific POS fields | Faire's current POS Help lists different synced fields by connection: for example, Shopify includes SKU, barcode and shipping weight; Square includes SKU and GTIN; Lightspeed includes wholesale price. | These examples describe named retailer POS integrations only; they are not a shared Faire API schema or a complete marketplace product record. |
Content reviewed 2026-10-04.