datawebotMicas clothing product data: Curve sizes, fit and variants
Model Micas clothing records with Curve size options, body and garment charts, item attributes, option SKUs, locale-specific offers, and published access terms.
Micas is a fashion catalog with distinct product families
This page is about the women's fashion retailer at shopmicas.com. Its catalog organizes tops, bottoms, outerwear, dresses, denim, knitwear, jumpsuits, sets, swimwear, accessories and shoes, with Curve families alongside standard categories. Keep the source's product family with every record; the category list and inventory change over time.
Scroll to compare →
| Catalog group | Examples in Micas navigation | What to preserve |
|---|---|---|
| Core apparel | Tops, bottoms, outerwear, dresses, denim and knitwear | Use the source category and item type; avoid fitting every garment to one shared attribute list. |
| Sets and coordinated items | Skirt, trouser, short and knitwear sets | Keep the listed set as one product unless the source separately identifies its pieces. |
| Curve | Curve tops, bottoms, dresses, denim, knitwear and sets | Store Curve classification separately from the actual size options on an item. |
| Other merchandise | Swimwear, lingerie/sleepwear, jewelry, bags and footwear | Use the item's own material, fit and option fields; garment measurements may not apply. |
Keep the style, option and SKU at their own level
A Micas product can offer color and size options with an option-specific SKU. In one current listing, the visible style code appears in the SKU alongside color and size; treat the SKU as an opaque source identifier rather than decoding its segments or assuming every item follows the same pattern.
Scroll to compare →
| Record level | Micas field shape | Modeling distinction |
|---|---|---|
| Style | Product name and product path/code | The style identifies the parent item; collection labels and descriptive names may change. |
| Option | Raw color and size values | Each color-size combination is a separate option when the source lists it that way. |
| Variant identifier | Variant ID and SKU where displayed | Keep IDs as source keys; do not synthesize a missing SKU or infer undocumented code meanings. |
| Set or family link | Source category, including Curve Sets where shown | A category label does not guarantee that every size or component is sold with every option. |
Body measurements and garment measurements are different tables
Micas size guides distinguish Body Size from Product Size, offer inch and centimeter views, and map labels such as U.S., AU/UK and EU. Product pages say exact measurements vary by style. Preserve the displayed chart type, market label and unit so a body-size range is not mistaken for a garment measurement.
Scroll to compare →
| Chart detail | Example in Micas sizing | How to retain it |
|---|---|---|
| Table meaning | Body Size and Product Size are separate chart labels | Record the chart label alongside every row; don't combine both tables. |
| Regional labels | U.S., AU/UK and EU size columns | Keep source labels as published rather than treating them as universally equivalent. |
| Measurement | Shoulder, bust, waist and hip in body tables; style-specific dimensions in product tables | Keep measurement names and the body/product context distinct. |
| Unit and basis | IN/CM display and a product-specific “measured in size” value | Store the unit and sample size used for garment measurements; don't imply that values describe every option. |
Curve filters do not define every item's size range
Micas groups Curve tops, bottoms, dresses and sets in its catalog. Curve filters can span labels from 0XL through 5XL, but each listing exposes its own available options and size chart. Some product detail blocks also give a “measured in size” sample that differs from the selected option; retain both values rather than treating one as a contradiction or a universal size range.
Scroll to compare →
| Curve record detail | What the listing can show | Why item-level context matters |
|---|---|---|
| Category | Curve Tops, Curve Sets and other Curve product families | Keep classification as its own field rather than inferring it from the size label. |
| Filter range | A collection may expose 0XL–5XL filters | A filter is a browse facet, not proof that one product has every filtered size. |
| Variant options | The item's own color and size choices | Represent only the options shown for that product and observation. |
| Fit sample | “Measured in size” beside item dimensions | Keep the measurement sample size separate from the selected sellable variant. |
Separate garment facts, shopper inputs and changing offers
Micas product detail blocks can include composition, fabric, lining, fit, stretch, sheerness, care and garment dimensions. A separate “My Size” widget asks shoppers for body or foot measurements; those user-entered values are not product facts. Price, discount, variant availability and shipping speed are time- and context-dependent observations.
Scroll to compare →
| Data group | Examples | Keep separate from |
|---|---|---|
| Item attributes | Composition, fabric, lining, fit/stretch, sheerness, care and dimensions | Don't apply one product's claims or size details to a whole category. |
| Shopper measurements | Height, weight, shoulder, bust, waist, hip, foot length and foot breadth in “My Size” | Keep user-entered profile values out of catalog item and variant records. |
| Price and promotion | Displayed price, compare-at amount, currency and offer context | Save the storefront/market and observation time; offers can vary by locale and channel. |
| Availability and delivery | Exact variant state, “Speedy Shipping” label and selected destination/method | Do not turn a stock or delivery message into a permanent product attribute or promise. |
The published Terms and policies set important boundaries
Micas's Terms of Use include a representation against automated or non-human access, including bots and scripts, and prohibit automated data-mining or similar data-gathering tools. They also prohibit systematic retrieval to compile a database without written permission. A field map does not grant access or reuse rights; this guide contains no collection steps. The store's first-party return summaries also differ: the root Refund Policy states 30 days, while the linked en-ab FAQ says to contact support within 14 days. Check the page and locale that apply to the intended use.
Scroll to compare →
| Source statement | Where it appears | How to interpret it |
|---|---|---|
| Automated/non-human access and automated data gathering | Micas Terms of Use | Review the current terms and required authorization; this guide offers no automated access method. |
| Systematic retrieval for a database | Micas Terms of Use; written permission is named in the clause | Do not treat public catalog visibility as permission to compile or reuse site content. |
| Return window summaries differ | Root Refund Policy: 30 days; en-ab FAQ: 14-day contact instruction | Preserve the cited page and locale; do not publish one deadline as a universal Micas rule. |
| Shipping and offer context can change | Locale policy and product/storefront pages | Recheck destination, platform and current policy before relying on an offer or delivery detail. |
Content reviewed 2026-10-05.