datawebotMaryum N Maria product data: set, style and market fields
Map Maryum N Maria style codes, pret and unstitched sets, garment components, size variants, and market-specific offers.
Separate ready-to-wear sets from unstitched products
Maryum & Maria's catalog mixes ready-to-wear/pret clothing with unstitched suits. A set label such as two-piece or three-piece describes the source's product offer; it does not by itself enumerate every garment or accessory in a photograph. Keep the product form and each source-named component explicit.
Scroll to compare →
| Source label | Catalog interpretation | Keep distinct |
|---|---|---|
| Ready to wear / pret | Record the exact source label and whether the listing identifies a two-piece or three-piece outfit | The style name, product type and individual size option. |
| Unstitched | Preserve “Unstitched” as a product form, not a wearable size | Any separate size option or tailoring measurement. |
| Component list | Store each named garment piece under its parent style | Items shown only in a campaign photo or styling scene. |
| Set count | Capture the page's two-piece/three-piece description with its source URL | An inferred shirt/trouser/dupatta list that the page does not state. |
| Parent and piece | Relate each piece to the set/style from which the source lists it | Standalone products that merely share a collection or image. |
Keep the style code beside the name and its collection facets
Listings pair a display name with a short style code, then place the item in season, fit, type or collection navigation. Treat the code as a source-assigned identifier: preserve it exactly, but do not guess what a letter prefix means or derive product attributes from it.
Scroll to compare →
| Field | Record | Boundary |
|---|---|---|
| Display name | Exact name shown on the product listing | Do not replace it with a collection name or descriptive image text. |
| Style code | Exact visible code, such as MSS5688 or MSU6941 | Do not parse the prefix as a verified fabric, season or fit code. |
| Source product URL | Canonical product URL plus the storefront host | Keep market storefront paths separate unless the retailer confirms a match. |
| Collection and season | Source collection name and current season label | These are navigation facets and can change independently of product fields. |
| Fit and product type | Exact fit/type labels, including formal, wedding, pret or unstitched where shown | Do not infer garment construction from marketing category alone. |
Attach fabric, color and workmanship to the named garment piece
The SAIREN - MSS5688 product page is a useful example of the retailer's field structure: it describes a two-piece pret style and separates shirt fabric, bottom fabric and color. For comparison, keep each attribute tied to the component or whole garment that the source names; do not copy its promotional description or infer details from the photo alone.
Scroll to compare →
| Garment record | Source field to preserve | How to compare |
|---|---|---|
| Parent style | Style code, display name and set description | Use the exact product page as the evidence boundary. |
| Shirt/top | Named shirt fabric, cut or workmanship detail where stated | Do not carry this field to the trouser or full outfit. |
| Bottom/trouser | Named bottom fabric and any stated style detail | Keep it separate from the top's material and embellishment. |
| Color | Source-reported color label and the storefront/variant | Do not use image color as a substitute for a text field. |
| Embroidery, print or trim | Only the technique/detail the text identifies | Preserve source wording; do not infer thread, method or placement from imagery. |
| Product imagery | Image reference and associated item/variant if relevant | The retailer says displayed color can vary with lighting and device settings. |
Keep size labels and size charts attached to their market
A stitched product may expose ready-to-wear sizes, while an unstitched item is labeled as fabric/set form. The international size guide uses garment and body measurements across separate clothing components. Preserve the chart's original label, measurement name, unit and storefront; do not silently convert or repair a value from a chart with inconsistent-looking unit strings.
Scroll to compare →
| Size data | Capture | Avoid |
|---|---|---|
| Variant size | Available source label and the specific product/market | Treating “Unstitched” as a size equivalent to S, M or L. |
| Size chart | Chart title, market, garment group, measurement and displayed unit | Applying one chart to every collection or storefront. |
| Component measurement | Shirt, trouser or other named component measurement | Flattening different garment measurements into one generic size field. |
| Storefront market | Source host and region, such as Pakistan, international or UAE | Assuming identical currency, variant choices, price or policy across hosts. |
| Chart revision | URL and observation date for the chart used | Normalizing ambiguous or inconsistent source strings without verification. |
Date price, stock and delivery observations by storefront
The Pakistan storefront displays PKR, the international storefront displays USD and the UAE storefront displays AED. Similar names or style codes are not enough to merge their offers. Record the storefront, currency, selected size, price state and observation time; regional return, shipping and sale terms can differ too.
Scroll to compare →
| Observation | Fields to retain | Data boundary |
|---|---|---|
| Regular and sale offer | Displayed amount, currency, selected size, sale label, host and capture time | Do not treat a promotion or compare-at amount as a stable catalog attribute. |
| Size availability | In-stock/backorder state for the selected size and storefront | Do not infer other sizes from one listing card. |
| Delivery scope | Destination region, shipping statement and policy URL/date | Avoid generalizing a Lahore or Pakistan message to international orders. |
| Return/exchange rule | Applicable storefront, order status and stated exception | Local and international policies are not interchangeable. |
| Terms and content | The displayed Terms identify site materials as owned/controlled and frame site use as personal and noncommercial | Do not infer permission to reuse product copy, photos or design material. |
| Uncertain display | Source field, exact page, market and timestamp | The retailer notes that image color can differ with photography and device display. |
Questions about Maryum N Maria product records
These answers explain source labels and catalog relationships; they do not provide tailoring or purchase advice.
Scroll to compare →
| Question | Answer | Useful distinction |
|---|---|---|
| Does “Unstitched” describe a size? | No. It is the source's product form and should remain separate from a stitched size option. | Product form versus size variant. |
| What does a two-piece or three-piece label prove? | It records the set count stated by the product page; use the page's component list for the pieces. | Set label versus named garment components. |
| Can a style-code prefix identify fabric or season? | Not from the listing examples reviewed. Keep the code intact without decoding its letters. | Source identifier versus inferred taxonomy. |
| Can similarly named items on PKR, USD and AED stores be merged? | Only when the source confirms that the storefront records refer to the same item and option. | Cross-market identity versus a name/code resemblance. |
| Should every store use the same size chart? | No. Preserve the chart and units linked from the relevant storefront and product context. | Market-specific chart versus universal conversion. |
Content reviewed 2026-10-05.