datawebotMAYBERRY product catalog data: fit, size and variant fields
Model MAYBERRY apparel and footwear data with style-specific size charts, color and size variants, optional SKUs, and changing offer context.
A mixed fashion catalog needs family-aware records
MAYBERRY's collection directory spans dresses and jumpsuits, footwear, bags, jewelry, hats, knitwear, outerwear and accessories. Its all-products view mixes garments, sets and shoes. Keep the source's family or collection context with each item; a single apparel attribute list will not describe every product well.
Scroll to compare →
| Catalog family | Examples in MAYBERRY collections | Modeling distinction |
|---|---|---|
| Apparel | Dresses, jumpsuits, tops, trousers, knits and outerwear | Capture garment type and only the fit dimensions the individual listing provides. |
| Coordinated sets | Two-piece outfits and matching sets | Keep the set as its listed product; do not invent component records unless the listing identifies them. |
| Footwear | Sandals, sneakers, boots, heels and loafers | Use a footwear size model with foot-length units and source size labels. |
| Accessories | Bags, jewelry and hats | Keep category and item-specific options; apparel measurements usually do not apply. |
Record a product separately from its options
MAYBERRY product pages show option axes such as color and size, while the exact choices differ by item. Some page variants have no SKU. Preserve each displayed option and any source identifier without treating a SKU as a universal product key.
Scroll to compare →
| Record level | Fields to keep together | Why it matters |
|---|---|---|
| Product | Displayed title, source product URL or handle, product family and collection | Names can be descriptive and do not always function as stable identifiers. |
| Variant | Raw option names and values, such as color plus size | A selected color or size represents one option combination, not the whole style. |
| Identifier | Source variant ID and SKU when present; retain a missing value as missing | Observed product data can omit SKU, so do not merge variants or fabricate codes to fill gaps. |
| Description | Source-stated material, design details and fit notes, attributed to the product | Keep listing claims attached to the style they describe rather than generalizing them across a collection. |
Apparel size charts belong to individual styles
The Julianne wrap dress page labels bust, sleeve, length, waist and hip measurements in inches. Other MAYBERRY clothing pages use different measurements, and the Plus Size collection notes that availability varies by style. Store each chart with its product, chart label and units; a shared size name does not prove that two garments fit alike.
Scroll to compare →
| Fit field | Example from MAYBERRY apparel | Handling rule |
|---|---|---|
| Style and chart | Product name plus the chart shown on its own page | Never attach one style's chart to every dress or top in the collection. |
| Size label | A label such as S, M, XL or 3XL | Preserve the displayed label and its ordering; don't equate labels across styles. |
| Measurement | Bust, sleeve, length, waist or hip where listed | Keep each measurement name and number as a distinct field. |
| Unit and coverage | The Julianne chart uses inches; Plus Size describes extended sizes with style-dependent availability | Retain the unit and actual options offered on the specific item; do not infer coverage from a collection name. |
Footwear sizing needs its own conversion record
MAYBERRY shoe pages pair color and numeric size choices with charts that map foot length in centimeters to U.S. and sometimes U.K. or EU labels. The observed Chelsea chart repeats some EU labels across adjacent foot-length entries. Preserve the table as published and review mappings at the model level before normalizing them.
Scroll to compare →
| Footwear field | Example value shape | Keep the distinction |
|---|---|---|
| Product model | The named shoe style | Size guidance belongs to that model, not all MAYBERRY shoes. |
| Variant options | A color plus a numeric U.S. size | Store option values exactly as shown, including the size scale. |
| Measurement | Foot length with a centimeter unit | Keep measured length separate from a market size label. |
| Source conversions | U.S. and EU labels, sometimes with U.K. sizing | Retain each original column; don't silently resolve repeated labels into a different conversion. |
Keep promotions and availability with their context
MAYBERRY listings can show regular and sale prices, variant availability, scarcity messages and cross-collection Stack & Save offers. These values can change by item, option, market and time. The returns policy also says a multi-item discount may be recalculated after a partial return, so keep order-level promotion adjustments separate from product prices.
Scroll to compare →
| Observation | Useful fields | Interpretation |
|---|---|---|
| Price | Displayed amount, currency, regular/compare-at amount, selected variant and capture time | Treat each price as an observation, not a permanent property of the style. |
| Availability | Exact product option, displayed availability state and capture time | A message on one size or color does not describe every variant. |
| Promotion | Offer name, eligible item scope, threshold or rule, and observation time | Keep a changing cart offer distinct from a product's base identity; don't hard-code today's discount. |
| Partial return | Order-level discount adjustment and items retained | The source policy describes recalculating discounts when returned items change offer eligibility. |
Check MAYBERRY terms before reusing site content
Section 2 of MAYBERRY's displayed Terms of Service says users may not reproduce, duplicate, copy, sell, resell or exploit any portion of the website or service without express permission. The page describes catalog fields and source-specific modeling considerations; readers should review the current terms and obtain any required permission before reusing site content.
Scroll to compare →
| Question | What the reviewed page says | Practical data-modeling note |
|---|---|---|
| What is restricted? | The Terms describe reproduction, copying, resale or exploitation of website/service content without express permission. | Do not treat a field list as permission to copy product descriptions, images or other content. |
| Does the text specify automated extraction? | The reviewed section does not specifically describe an automated collection method. | Avoid converting the broader wording into a specific scraping rule; check the current Terms for the intended use. |
| Which commerce details can change? | Product options, size charts, offers, shipping and return details are shown in separate store pages. | Recheck the relevant item and policy page when those facts affect a decision. |
Content reviewed 2026-10-05.