datawebotDolls Kill product data: brand labels, collabs and sizing
Plan Dolls Kill data extraction across style-led categories, brand and collaboration labels, apparel and shoe sizing, product details, and market-aware offers.
Organize the catalog by product type and style label
Dolls Kill’s official navigation places clothing, shoes, accessories and Halloween under distinct store groupings. Clothing and collections also use vibe labels such as boho, festival, girlypop, goth, rave, punk and western. Treat category, subcategory and style label as separate facets; the navigation changes, so omit catalog totals.
Scroll to compare →
| Store grouping | Examples in the official navigation | How to model it |
|---|---|---|
| Clothing | Corsets, dresses, jumpsuits and rompers, lingerie, matching sets, outerwear, plus, swim, tops, bottoms, skirts and more. | Keep the product type and subcategory separate from collection or vibe labels. |
| Shoes | Boots, platforms, heels, sandals, sneakers, flats, slippers, cowboy boots and Mary Janes. | Use a footwear category and the item’s own shoe-size labels; do not reuse apparel sizing fields. |
| Accessories | Bags, jewelry, hats, beauty, belts and harnesses, hair accessories, hosiery and home decor. | Retain the listing’s item type and only the attributes that its product page supplies. |
| Halloween | Costumes, apparel, accessories, shoes and wigs, with further costume groupings in the menu. | Keep seasonal collection membership distinct from the item’s underlying product type. |
| Style or vibe | Boho, festival, girlypop, goth, rave, punk and western are examples shown in clothing navigation. | Store these as source merchandising labels, not as product types or fixed taxonomy. |
Keep brand labels separate from named collaborations
The store presents Brands and Collabs as separate navigation groups. Preserve a listing’s displayed brand or vendor label separately from a collaboration name, product title and category; a menu label alone does not establish that every listed brand is Dolls Kill-owned.
Scroll to compare →
| Identity field | Official listing or navigation example | Keep distinct from |
|---|---|---|
| Brand/vendor label | The Brands menu lists labels such as Current Mood, Club Exx, Widow, Sugar Thrillz and dELiA*s; the Laced Up Nighty Dress identifies Jaded London as its brand. | Do not relabel every menu entry as a house brand or substitute the storefront for the item’s own label. |
| Collaboration | The Rules Mini Dress is labeled Dolls Kill x Death Note and displays size options XXS through XXL. | Keep the named collaboration attached to this dress listing, not as a replacement for product category or option labels. |
| Product record | The collabs collection spans multiple categories, while a collaboration product retains its own title and selected option. | Store title, category, source-reported brand/vendor, collaboration and option as separate values where available. |
Keep fit and construction details with each product
The Laced Up Nighty Dress shows why construction, fit, material and care belong with the exact item. Its source describes a mini dress with floral print, lace trim, flocked detailing, a side slit and bodycon fit, and separately lists its materials and care. These descriptors describe this listing, not a category-wide fit rule.
Scroll to compare →
| Listing field | Laced Up Nighty Dress example | Modeling note |
|---|---|---|
| Brand and type | The listing identifies Jaded London and classifies the item as a dress. | Preserve source labels alongside the product title. |
| Silhouette and details | Mini length; all-over floral print; lace trim; flocked detailing; side slit; bodycon fit. | Keep each source-described feature tied to this exact listing; do not turn it into general fit advice. |
| Materials | 90% polyester and 10% elastane. | Store the listed composition as product-specific material data. |
| Care | Hand wash. | Keep care wording with the item and source URL rather than applying it to other dresses. |
Keep apparel labels, conversions and shoe sizes distinct
Dolls Kill’s support size guide says its charts are general guidelines, not specific to brands or products. It separates body-measurement references, international conversions and shoe conversions. Preserve the option string on the product itself rather than converting it into a universal fit claim.
Scroll to compare →
| Source example | Displayed sizing structure | Interpretation boundary |
|---|---|---|
| General size guide | Separate women’s and men’s measurements, international size conversions, and footwear conversions with inch/centimeter and regional labels. | Use as a general reference only; the support guide says it is not product- or brand-specific. |
| Jaded London Nighty Dress | Options include mixed labels such as `US S/AUS 8` and `US S/UK 8`. | Keep each exact option label with this product and its market context; do not collapse AU and UK labels. |
| Teen Craft Oxford Shoes | The dELiA*s by Dolls Kill listing presents US shoe options 5 through 15. | This is the range shown for this shoe listing, not a claim about all Dolls Kill footwear. |
| Option record | Capture category, product URL, selected market and the source’s option label verbatim. | Keep shoe sizes separate from clothing sizes and avoid model measurements or personal sizing advice. |
Model each selected-market offer as a dated observation
If offer fields are used in a later product history, tie every observation to the selected market and exact option. Keep promotion text separate from amounts and distinguish explicit pre-order wording from an ordinary availability signal.
Scroll to compare →
| Observation field | Capture when displayed | Decision rule |
|---|---|---|
| Selected offer | Current amount, compare-at amount, explicit promotion label and currency, each attached to the chosen option. | Keep these values separate; do not print a live amount or discount as evergreen page copy. |
| Market and option | Destination market, exact product URL, selected apparel or shoe option, and any exposed identifier under the source’s label. | Do not assume one country’s currency, size option or offer applies to another market. |
| Availability wording | The selected option’s displayed state and any explicit pre-order wording, recorded separately. | Do not infer stock from a “Notify me” control or a missing option. |
| Observation time | Timestamp and source URL for the exact option and market view. | Treat the value as a dated observation that can change, not a timeless current fact. |
Keep market policies separate from product and customer records
Shipping, taxes, checkout currency and returns are destination-specific policy information, not product attributes. Dolls Kill's shipping help was updated October 1, 2026 and says rates and delivery times vary by destination, local duties, taxes and advancement fees may apply, and the order is charged in the currency shown at checkout. Its UK/AU/EU Terms were last updated May 6, 2026 and cover those destinations only; the Returns article was updated September 1, 2026. Check the linked policies for current detail.
Scroll to compare →
| Record area | Useful source fields | Keep outside the product row |
|---|---|---|
| Shipping and checkout | Shipping help (updated October 1, 2026): destination-specific shipping rates and delivery times, possible local duties/taxes/advancement fees, and the currency displayed at checkout. | Do not store volatile rates, delivery estimates or fee amounts as timeless product attributes; the charged currency is determined at checkout. |
| UK, AU and EU sale terms | UK, AU and EU terms (last updated May 6, 2026): keep the stated region, source URL and update date with any currency or tax interpretation. | Do not project these terms onto the US or other destinations. |
| Returns policy | Returns article (updated September 1, 2026): retain its current destination/method scope and update date with policy references. | Do not turn date-sensitive return windows, fees or seasonal cutoffs into a universal product attribute. |
| Customer-only information | Keep public product attributes separated from operational datasets. | Exclude order history, customer email or account details, wishlist and notification signups, and review text from public product records. |
Content reviewed 2026-10-03.