datawebotLowe's product data: identifiers, local offers and partner feeds
Map Lowe's item, model and package fields; preserve store or ZIP context for offers and understand the documented partner catalog route.
Separate Lowe's Item #, Model # and partner identifiers.
A Lowe's listing can show its own Item # beside a manufacturer's Model #. Lowe's partner catalog documentation also uses an omniItemId. These values answer different matching questions, so preserve each with its identifier type, product option, source and review date rather than treating them as aliases.
Scroll to compare →
| Value on the record | Store it as | Matching boundary |
|---|---|---|
| Item #6019159 | Lowe's listing identifier plus the exact Lowe's product URL | The reviewed listing labels this separately from Model #; do not use it as the maker's model. |
| Model #QI004494.WT.4 | Manufacturer model string exactly as displayed | Use as a candidate product match, then verify the finish, configuration and pack. |
| omniItemId | Lowe's partner-catalog identifier in its own field | Lowe's API documentation uses this name; do not assume it equals Item #, Model # or a GTIN. |
| UPC or GTIN | Barcode value with its identifier type | Keep distinct from both retailer and manufacturer identifiers; include only when a source provides it. |
| Package Quantity 4 | Pack count or purchase unit | This is package context, not a product identifier or the buyer's requested quantity. |
Preserve the configuration and unit behind a home-improvement match.
Home-improvement catalogs mix products whose similar names may conceal a different size, finish, electrical specification or package. The Lowe's lighting example has its own dimensions, finish, technical specifications and four-pack label. Keep category-specific attributes with the selected configuration, and do not flatten every product into the same field list.
Scroll to compare →
| Product detail | Record with the item | Why it changes the match |
|---|---|---|
| Selected option | Finish, size, model option and the displayed selection | A family listing may include more than one configuration; preserve which one the record describes. |
| Category specifications | The named attribute, value and unit, such as dimensions or electrical rating | Lighting, lumber, appliances and plumbing require different compatibility fields. |
| Package contents | Pack count, included components and whether accessories are separate | A multi-pack or bundle is not the same purchasable unit as one fixture or tool. |
| Purchase unit | Each, pack, length, area or other unit shown with the product | Compare quantities on the same basis before calculating a like-for-like project cost. |
| Cross-catalog match | Candidate maker model plus verified option and source evidence | A shared family name or close title alone does not establish fit or equivalence. |
Keep Lowe's offer observations tied to store, ZIP and fulfillment.
A product offer is incomplete without its market and time context. Lowe's partner catalog documentation distinguishes national from local information and says a storeId is required for store-specific price. Preserve the lookup context beside any price or availability observation; do not treat one location's result as nationwide inventory.
Scroll to compare →
| Context | Record when documented | Interpretation |
|---|---|---|
| Market level | National/default or local result | The partner catalog docs describe national data when no location is supplied and local data when store or ZIP context is used. |
| Store and destination | Store identifier and/or ZIP used for the lookup | The documentation says storeId is required for store price; keep ZIP and store values distinct. |
| Fulfillment | Pickup, delivery or shipping choice and its displayed state | A fulfillment option is not an exact shelf count and may differ by destination. |
| Offer basis | Currency, price label, package/unit and promotion context | A per-each amount, multi-pack amount and promotional amount are not directly comparable without their basis. |
| Observation | Source, timestamp and whether a value was missing or unavailable | A prior observation does not establish present price, inventory or delivery eligibility. |
Lowe's partner catalog is a distinct integration route.
Lowe's Developer Hub describes partner product feeds and product-detail capabilities for storefronts that present Lowe's products. Its documentation discusses registering an organization, creating an app, obtaining credentials and subscribing to feeds. The pages differ on API readiness, so confirm the capability and terms with Lowe's before planning around a particular feed or endpoint.
Scroll to compare →
| Documented component | What Lowe's describes | What a public guide can establish |
|---|---|---|
| Product catalog feed | A daily full-catalog export with descriptions, images, specifications, categories and attributes; the component page describes CSV feeds via SFTP. | A public description does not identify whether a particular partner is enrolled or what its agreement covers. |
| Product detail | The Product Discovery guide describes using a Product Detail API for price, inventory and promotions in a partner experience. | It is not an open public endpoint for general collection from shopper pages. |
| Partner setup | The Developer Hub describes organization registration, app setup, credentials, feed subscription and sandbox testing. | Documentation of a partner flow does not establish permission for unrelated collection or downstream reuse. |
| API readiness | The Product Catalog component page labels a REST API as coming soon, while also showing API patterns and the Product Discovery guide describes an API. | Confirm current availability with Lowe's; do not rely on one page's wording as proof that a capability is provisioned. |
Read the displayed Lowe's Terms before choosing a data route.
The Lowe's Terms & Conditions of Use displayed on October 5, 2026 carry an effective date of April 13, 2026. They prohibit specified manual and automated processes for retrieving or copying site content, and separately define reseller activity to include gathering site information connected with downstream product sales. The Developer Hub describes a separate partner integration program; its existence does not establish permission for unrelated collection or reuse.
Scroll to compare →
| Terms detail | Displayed scope | How to represent it accurately |
|---|---|---|
| Effective date | April 13, 2026, as shown at the start of the Lowe's Terms | Keep this date attached to the reviewed version; terms may change. |
| Manual and automated retrieval | The Terms name robots, spiders, site-search/retrieval apps and other manual or automatic processes used to retrieve, index, data-mine, reproduce or circumvent the site's navigation or content. | Attribute the clause to Lowe's Terms; do not broaden it beyond the described site and activity. |
| Reseller activity | The Terms define this to include extracting, scraping, mining, copying or otherwise gathering site information connected to downstream product sales. | Keep the connection to downstream sales in the summary; do not reduce the clause to a generic rule about every product comparison. |
| Partner documentation | Lowe's separately documents credentialed partner feeds and storefront APIs. | Do not imply that those materials override the displayed site Terms for other collection or reuse. |
Content reviewed 2026-10-05.