Product data
Atölye reads the definitions below; installing the theme does not create them. Use the exact namespace, keys, metaobject types and field keys. Create only what you need. You own these definitions; see Modules for where each one is used.
1. Create metaobject definitions
- Open Settings → Custom data (called Metafields and metaobjects in some admin versions), then Metaobjects → Add definition.
- Enter a name and set its Type to the exact identifier below. Add each field with its exact key and type.
- Enable Storefronts access for the definition and save. If entry status is enabled, entries must be Active to appear. You do not need to generate a web page for each entry. See Shopify's custom data options.
| Metaobject type | Fields |
|---|---|
lilya_spec | group: single-line text, optional; label: single-line text; value: single-line text or number; unit: single-line text, optional; key: single-line text, optional |
lilya_vehicle | make, model: single-line text; year_from, year_to: integer; trim: single-line text, optional; collection: collection reference, optional |
lilya_document | title: single-line text; file: file reference, or url: URL; kind: single-line text, such as Manual |
For specs, single-line text for value accommodates values such as 1/2; choose one type for your definition. Keep units in unit. Use stable keys such as length, height, drive and weight for matching rows and collection columns.
For vehicles, leave year_to empty for a model still in production. A vehicle's optional collection is used directly by the finder, so populate that collection with the intended products yourself.
For documents, provide a file or URL on each entry. If both are filled, the file wins. The lilya_document definition is needed only if you choose metaobject references for documents below.
2. Create metafield definitions
- Return to Settings → Custom data → Products → Add definition.
- Enter a readable name. Set Namespace and key exactly as shown, replacing Shopify's suggested
custom.*value. - Select the content type. Choose List of values for list fields and One value for single fields. For metaobject references, select the matching definition from step 1. Restrict the drawing and exploded file fields to images.
- Enable Storefronts access and save. Pin definitions if you want them readily visible on the product page.
- Repeat under Variants for the rows that also support variants. Product and variant definitions are separate, even when their namespace and key match.
| Owner | Namespace and key | Content type | Used by |
|---|---|---|---|
| Product and variant | lilya.specs | List of metaobject references → lilya_spec | Spec table, comparison; product specs also feed cards and drawing labels |
| Product | lilya.fits | List of metaobject references → lilya_vehicle | Fitment status and finder filter |
| Product | lilya.fits_all | True or false (boolean) | Universal-fit status |
| Product | lilya.documents | List of files or list of metaobject references → lilya_document | Documents block |
| Product and variant | lilya.preorder | True or false (boolean) | Pre-order block |
| Product and variant | lilya.preorder_date | Date | Pre-order date |
| Product | lilya.drawing | File, one value, images only | Drawing tab |
| Product | lilya.exploded | File, one value, images only | Exploded tab |
| Product | lilya.parts | List of product references | Numbered list and first three image links in the Exploded tab |
| Product | lilya.media_groups | JSON | Variant IDs mapped to product media IDs; no alt-text parsing |
| Product | lilya.badges | JSON | Tag-conditional New / Pro badges |
Choose one type for lilya.documents; a single definition cannot contain both a file list and a metaobject list. Use files for simple downloads, or document entries for titles and kinds.
3. Create entries and fill a product
- Open Content → Metaobjects, select a definition, and add entries. For example, create a
lilya_specentry with labelLength, value228, unitmm, keylength. Save it and make it Active if that status option exists. - Create any vehicle and document entries you need. Upload drawing images and downloadable files in Content → Files, or select/upload them through the relevant file field.
- Open Products, choose a product, and scroll to Metafields (or open all metafields).
- In Specs, select your spec entries. In Fits, select compatible vehicle entries; set Fits all to true only for genuinely universal products. In Documents, select files or document entries according to your definition.
- Select a drawing image in Drawing, an exploded image in Exploded, and products in Parts. Arrange parts in the order that matches your illustration's numbers. Save the product.
- For variant-specific specs or pre-order data, open the variant and fill its metafields, then save. A variant spec overrides a product spec with the same
key, or the same label when no key is present.
4. Display and verify
Open the product in the theme editor. The supplied product template already contains Media with drawing tabs, Spec table, Documents and Vehicle fitment. Fill the fields, save, and preview that product. Empty data-dependent blocks can show editor hints while remaining empty on the storefront.
The Drawing tab reads product specs keyed length and height; the image is not a measured scale drawing. The Exploded tab uses the first three lilya.parts references as pawl, spring and body/rebuild links over the exploded and assembled drawing views. It retains the complete parts list below. These approximate positions fit the demo ratchet; only assign matching art and ordered parts. Home Image hotspots positions are editable.
For filtered finder results, add the lilya.fits product metafield as a filter in Shopify Search & Discovery, then select the result collection in Vehicle finder. A product's universal-fit flag controls its status message; it does not automatically add that product to every filtered collection result.
Pre-order fields take effect only when the Pre-order block is added to the product section. They do not configure inventory availability, deferred payments or fulfillment; configure those separately. See Modules for placement and behavior.