datawebotLiverpool México product data: sellers, variants and availability
Understand Liverpool México product codes, seller offers, variants and store availability. Dated robots rules guide search and AI crawlers, not content reuse.
Liverpool product identity and Marketplace offers are separate records.
Liverpool’s department-store catalog can display offers sold by Liverpool or by a Marketplace seller. The current seller portal says suppliers control their own stock, prices and offers. Keep the product page and each seller offer connected, while preserving the exact “Vendido por” wording and offer count shown for the observation.
Scroll to compare →
| Storefront detail | Record it as | Why the distinction matters |
|---|---|---|
| Product page | Page URL, displayed product name, brand and department | The retailer page identifies the catalog item; it does not by itself identify the seller for every offer. |
| Seller attribution | Exact “Vendido por” label and seller name, attached to the offer | Marketplace seller responsibilities and stock can differ from a Liverpool-sold offer. |
| Offer count | Displayed count and observation date, when present | The number of offers can change; it is not a permanent product attribute. |
Código de producto, skuid and selected options answer different questions.
A Liverpool product page can show a “Código de producto” while its URL includes a skuid parameter. Keep the displayed code, page URL and selected option in separate fields. The URL parameter is an observation from that page; it is not evidence that every department uses one stable cross-category identifier. A selected color or size also should not be inferred from the product title alone.
Scroll to compare →
| Field | Preserve | Avoid assuming |
|---|---|---|
| Código de producto | The value and exact Spanish label displayed on the page | Do not equate it with a universal SKU, GTIN or manufacturer part number without source evidence. |
| Product URL and skuid | Full page URL and any query parameter as observed | Do not treat a URL parameter as a stable product key across categories or time. |
| Selected option | Visible color, size, finish, capacity or configuration | Do not combine distinct selections into one sellable item when the page separates them. |
| Product identity | Title, brand, department and model when shown | Do not match two items on title similarity alone. |
Specifications should follow the department and the source labels.
Liverpool’s category pages expose different kinds of detail. A compact field map helps teams compare like with like while retaining the storefront’s wording and measurement units. It is a starting point for research, not a claim that every product has the same attributes.
Scroll to compare →
| Department example | Useful page fields | Comparison note |
|---|---|---|
| Apparel | Brand, garment type, displayed size, color and material | Keep the selected size distinct from any size-chart body measurement; retain the chart unit and audience. |
| Furniture | Dimensions, material, finish, capacity and piece count | Store each value with its source field. If description text and a structured specification disagree, retain both with page and observation time. |
| Electronics | Brand, model, screen or storage capacity, connectivity and included components | Compare products on matching configurations and units; do not infer an unlisted technical feature. |
| Beauty | Brand, product type, shade or format, stated size and package contents | Keep shade/format selection and package quantity separate from the product-family name. |
Precio en rojo belongs to a specific offer and promotion context.
Liverpool’s current storefront footer explains that “Precio en rojo” applies the highest discount and that promotions may differ from those in physical stores. Treat the label as storefront context, not a permanent price rule. Keep any observed amount with its seller, selected option, channel, payment wording, promotion text and timestamp.
Scroll to compare →
| Observation | Keep together | Do not infer |
|---|---|---|
| Displayed price label | Exact label and amount, currency, selected option and page URL | Do not assign one seller’s offer amount to another seller or option. |
| Promotion/payment text | Visible campaign, installment or payment wording and date | Do not assume an online promotion applies in a Liverpool store or continues after the observation. |
| Comparison snapshot | Seller, item, option, channel and checked time | Do not compare different sellers or dates as if they were one simultaneous offer. |
Store availability and Click & Collect depend on the chosen location.
Liverpool’s current guidance asks shoppers to select a product and state, then choose a store where it is available. Its two-hour collection message is conditional on stock at the selected store, and collection times vary by branch and season. A product page may also request a store or postal code for fulfillment options. Record the location and exact status beside the selected product option; availability is a time-bound observation.
Scroll to compare →
| Fulfillment field | Useful observation | Scope |
|---|---|---|
| Click & Collect | Selected product/option, state, store, displayed stock status and checked time | A two-hour estimate depends on selected-store stock and is not a nationwide service promise. |
| Home delivery | Selected option, postal-code context and displayed delivery wording | Keep the estimate with the location and observation date; do not generalize it to another address. |
| Store-level availability | Store identifier or name, exact availability label and time | Do not turn one store’s status into regional or chain-wide inventory. |
Crawler directives help explain discovery, not content-use rights.
Liverpool’s robots.txt, whose comment says it was updated August 20, 2026, allows the root path for its wildcard rule and named search and AI crawlers, including Google-Extended, GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot and Applebot-Extended. It also lists CCBot and Bytespider. The file points to a main sitemap, image sitemaps and product-detail sitemaps. These are crawl and discovery signals; they do not establish permission to reuse text, images or prices.
Scroll to compare →
| Evidence | What it shows | Boundary |
|---|---|---|
| Robots snapshot | Updated comment: August 20, 2026; root-path directives for named agents | Directives describe crawler access preferences and do not grant content rights. |
| Sitemap discovery | Main sitemap plus image and product-detail sitemap locations | A sitemap helps a crawler discover URLs; it does not promise a page will be indexed. |
| Terms evidence | The current footer Terms link resolved to an index with no readable terms text during review; the accessible static legal PDF is dated 2015. | That older file does not establish Liverpool’s current automated-access or reuse rules. |
A useful Liverpool dataset joins catalog, offer and fulfillment with provenance.
For assortment, competitor-price or local-availability analysis, model the product, seller offer and fulfillment observation separately, then connect them with stable references from the source. Store original labels and units alongside normalized fields so a later comparison does not erase what Liverpool actually displayed.
Scroll to compare →
| Record | Candidate fields | Provenance to retain |
|---|---|---|
| Product | Page URL, title, department, brand, Código de producto and selected option | Exact source label, page and observation timestamp. |
| Seller offer | Vendido por, offer count, price label, displayed amount and payment/promotion wording | Offer-to-product link, currency, channel and timestamp. |
| Fulfillment | Mode, state/store or postal-code context, status and displayed estimate | Selected option, location, exact wording and checked time. |
| Specification | Department-specific value, original unit and normalized value where justified | Source section/label and a flag when page fields conflict. |
| Policy reference | Robots or readable policy URL and its stated date/version | Keep crawl directives, terms evidence and content rights as distinct records. |
Content reviewed 2026-10-02.