datawebotMagalu product data: SKUs, sellers and delivery context
How Magalu product, seller, price and CEP delivery data fit together in Brazil, and how to separate variants from seller offers.
Updated · datawebot team
A product, its seller offer and its delivery operator are separate
A Magalu product page can combine a catalog item with one or more commercial offers. The seller shown beside an offer is not always the company handling its delivery. Magalu Help uses the phrase “Vendido e entregue por” followed by the store name, and says that some partner items can be delivered by Magalu. An official listing can also show “Produto vendido por loja parceira e entregue pelo Magalu”. Preserve the displayed phrase verbatim so seller and delivery roles stay clear. The public Magalu Regulations page says partner sale, price and delivery conditions are defined by the partner and assigns responsibility for product quality and defects to the partner.
Scroll to compare →
| Record | What it describes | Keep distinct from |
|---|---|---|
| Product family | Shared catalog identity and product-level specification | Any single seller's offer |
| Seller offer | The seller, offer state, channel and commercial terms for one item | Other sellers offering the same family |
| Delivery operator | The party responsible for dispatch or delivery in the displayed arrangement | The seller identity and fulfillment stock owner |
| Customer-facing label | “Vendido e entregue por” followed by the store name, or “Produto vendido por loja parceira e entregue pelo Magalu” | Normalize the displayed seller and delivery roles only after preserving the original wording |
Catalog identity is different from a seller SKU and a selected option
A product family groups options that a shopper can choose on one product page; a seller SKU identifies a seller's own catalog item. Preserve both the family relationship and each seller's own SKU rather than treating the product-page code as a universal identifier.
Scroll to compare →
| Identifier or field | Meaning in the record | Modeling guidance |
|---|---|---|
| Código / product code | Store-facing product identifier shown on a product page | Retain with the source and observed page context |
| seller SKU | Seller-scoped identifier for a seller's own catalog item | Do not assume it is shared by every seller for the same family |
| Selected option | A variation such as color, size or voltage | Store as a value on the specific SKU, not as a new family by default |
Category rules shape the product attributes
Category requirements can differ: a variation selector may define which option a shopper chooses, while a datasheet value describes the item. Depending on the category, useful labels can include brand, model, reference, color, voltage, dimensions, capacity, material or package contents. Treat these as category-dependent fields, not a universal required set.
Scroll to compare →
| Attribute group | Typical role | Validation question |
|---|---|---|
| Category | Places the item in the store's category hierarchy | Which attribute definitions apply to this category? |
| Variation attributes | Distinguish selectable SKUs, for example color, size or voltage | Do related SKUs in one family use the same attribute names? |
| Datasheet | Technical details that help a buyer assess the item | Is this field shown for this category, and in which unit? |
| Package and dimensions | Describe the item or its packaged form where supplied | Is the value item-level or package-level, and which unit applies? |
Price, list price and payment conditions answer different questions
A customer-facing offer can show an effective sale price, a reference “de” price, and PIX or installment conditions. PIX and installment amounts are payment contexts and should not overwrite the base offer price. A useful observation keeps seller, channel, currency, payment method, stock state and retrieval time beside the amount. Do not merge amounts across sellers or payment methods, even when they refer to one product family.
Scroll to compare →
| Value | Question it answers | Capture with |
|---|---|---|
| Sale price | What effective sale value is displayed for this offer? | Seller, channel, currency and timestamp |
| Reference “de” price | What reference amount accompanies that sale price? | The same seller and channel scope as the sale price |
| PIX condition | Is there a payment-method-specific displayed amount or discount? | Payment method and applicable offer context |
| Installments | What number of payments and conditions are displayed? | Payment term, interest or fee context when stated |
CEP and stock location can change delivery options
Magalu's customer guidance asks buyers to check delivery timing from their CEP, and says items in one order can have different dates when products come from different stock locations. Public shipping guidance also ties freight to dimensions, weight, distance and the delivery location. Store a CEP-derived region or quote context with its retrieval time; avoid treating one quote as nationwide availability or collecting a full customer address. Pickup, scheduled delivery and partner shipping depend on the specific item and location.
Scroll to compare →
| Delivery field | Why it matters | Do not infer |
|---|---|---|
| CEP or delivery region | Defines the location context used for a freight or timing quote | That an offer is available at every Brazilian address |
| Quoted freight and delivery time | Captures a location-specific displayed condition | That a quote remains valid after stock or offer changes |
| Stock location | Helps explain availability, dispatch path and differing delivery dates | That every item in one order ships from the same location |
| Seller and delivery operator | Shows who sells and who dispatches or delivers | That seller and carrier are always the same entity |
Robots.txt describes crawler directions, not content rights
Checked on 2026-10-03 Singapore time (2026-10-02 UTC), the Magalu storefront's 85-line robots.txt contains an `Alexabot` group with `Allow: /`, a wildcard group excluding operational paths, and additional Googlebot exclusions for selected search and facet URLs. AdsBot-Google, Mediapartners-Google and APIs-Google groups repeat operational exclusions. The file has no `Sitemap:` declaration and no explicit GPTBot, OAI-SearchBot, Google-Extended, ClaudeBot or PerplexityBot group. These are crawl directions only; they do not establish permission to collect, republish or commercially reuse catalog content.
Scroll to compare →
| Robots observation | Current file scope | Interpretation |
|---|---|---|
| Alexabot | Explicit Allow: / group | A crawler directive in this file, not a reuse license |
| Wildcard and ad/API groups | System/static, purchase, invoice and payment-slip paths are excluded; AdsBot-Google, Mediapartners-Google and APIs-Google repeat these exclusions | The listed paths do not establish a general account-path block |
| Googlebot | Additional search, filter, selection, seller and /r/ patterns are disallowed | Some query and discovery paths are treated differently from general pages |
| Sitemap and AI crawler names | No Sitemap line or named GPTBot, OAI-SearchBot, Google-Extended, ClaudeBot or PerplexityBot group was present | Do not interpret absence as authorization or a legal position |
A reliable Brazilian retail record links item, offer and provenance
For catalog enrichment, model Magalu's product family, seller SKU, offer and delivery quote as related records. Preserve the pt-BR labels and observation time; keep CEP-derived delivery context coarse.
Scroll to compare →
| Record | Useful fields | Provenance to preserve |
|---|---|---|
| Product family | Product code, brand, reference/model, category and variant group | Store URL, locale pt-BR and observed-at timestamp |
| Seller SKU | SKU, category attributes, datasheet and seller channel | Documented source basis and observed-at timestamp |
| Offer | Seller identity, sale price, reference price, payment and inventory state | Channel, currency, offer context and retrieval timestamp |
| Delivery quote | CEP-derived region, freight, delivery time and operator | Quote time and location granularity; avoid unnecessary personal address data |
Content reviewed 2026-10-24.