> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/use-case-guides/other-mixed-catalog/use-case.md). # Use Case ### Prerequisites Before creating the "Use Case" metafield, ensure: * You have admin access to your Shopify store * Accentuate Custom Fields app is installed and activated * You have at least 3-5 product examples ready where you'll want to assign use cases (helps with testing) * Your theme supports Liquid code (most modern Shopify themes do) * You understand your product's primary use cases or applications (e.g., "Home Office", "Travel", "Gaming", "Professional Use") *** ### Key Concepts to Know First Scope: This metafield will be attached to your Products object, meaning each individual product can have its own use case data. Namespace & Key: We'll create a metafield with: * Namespace: custom * Key: use\_case * Full identifier: custom.use\_case Field Data Type Options: * Single Select - Choose this if each product has ONE primary use case (e.g., a laptop is for "Business" OR "Gaming") * Multi Select - Choose this if products can serve MULTIPLE use cases (e.g., a tool set works for "DIY", "Professional", and "Home Repair") * Multi-line Text - Choose this if you want to provide detailed descriptions of use cases * Rich Text - Choose this if you want formatted descriptions with bold, italics, or links For most Mixed/Other category products, Multi Select is recommended because products typically serve multiple purposes. *** ### Step-by-Step Guide Step 1: Open Accentuate Custom Fields * Log into your Shopify admin dashboard * Find and click on the "Accentuate" app in your apps list (left sidebar) * This opens the Accentuate Custom Fields dashboard Step 2: Navigate to Metafield Definitions * In the Accentuate app, locate the "Metafield Definitions" section * Click on "Create New Metafield Definition" or the "+" button * This opens the metafield creation form Step 3: Set Basic Information * Name: Type "Use Case" (this is the display name in your admin) * Description: Enter "The intended use case or application for this product (e.g., Business, Gaming, Travel, Home, Professional)" * Namespace: Keep as "custom" * Key: Type "use\_case" (no spaces, lowercase) * These settings ensure your metafield is properly identified in Shopify's system Step 4: Choose Your Field Data Type * Click the "Data Type" dropdown * Select "Multi Select" (recommended for versatility) * If you prefer single selection, choose "Single Select" instead * This determines how users will input use case values Step 5: Configure Your Metafield Options * In the options section, add your use case values: * Home Use * Professional Use * Business Use * Travel / Portable * Outdoor Use * Gaming / Entertainment * DIY / Hobbyist * Educational * Emergency / Backup * Premium / Luxury Use * You can add more or fewer options based on your product catalog * The order you list them will appear in the dropdown for staff to select Step 6: Save and Apply to Products * Click the "Save" button to create the metafield definition * The system confirms "Metafield Definition Created Successfully" * The metafield is now available for use across all products in your store *** ### Populating Values on Products #### Method 1: One-by-One Entry 1. Go to Products in your Shopify admin 2. Click on any product to open its detail page 3. Scroll down to find the "Accentuate Custom Fields" or "Metafields" section 4. Locate the "Use Case" field 5. Click on the Multi Select dropdown 6. Select all applicable use cases for that product (e.g., check "Home Use" AND "Professional Use" AND "DIY / Hobbyist" if all apply) 7. Click "Save" to apply the metafield value This method is best for small product catalogs or when each product needs thoughtful, individual attention. #### Method 3: CSV Import 1. Export your products to CSV from your Shopify admin 2. Add a column named metafields.custom.use\_case to your CSV 3. In this column, enter use cases as a semicolon-separated list (e.g., Home Use;Professional Use;Travel / Portable) 4. Save the CSV file 5. Import the file back into Shopify using the Products import feature 6. Shopify automatically maps the metafield values based on the column header This method is ideal for large catalogs or when migrating data from another system. *** ### Displaying on Storefront #### Method 1: Using Theme Editor 1. Go to Sales Channels → Online Store → Themes 2. Click "Customize" on your active theme 3. Navigate to a product template or product detail section 4. Look for a "Metafield" or "Custom Field" block 5. Select "Use Case" from the available metafields 6. Customize the display label (e.g., "Best For:" or "Ideal For:") 7. Save your changes #### Method 2: Using Liquid Code If your theme allows custom Liquid code, add this to your product template: `{% if product.metafields.custom.use_case %}` `
` `

Ideal For:

` `` `
` `{% endif %}` `For displaying with styled badges:` `{% if product.metafields.custom.use_case %}` `
` `{% for use_case in product.metafields.custom.use_case %}` `{{ use_case }}` `{% endfor %}` `
` `{% endif %}` `Add corresponding CSS for styling:` `.use-case-badges {` `margin: 15px 0;` `display: flex;` `flex-wrap: wrap;` `gap: 10px;` `}`
`.badge-usecase {` `background-color: #f0f0f0;` `padding: 8px 12px;` `border-radius: 20px;` `font-size: 14px;` `color: #333;` `border: 1px solid #ddd;` `}` #### Method 3: Using Storefront API If you're building a custom storefront: `query {` `product(handle: "your-product-handle") {` `metafields(first: 10) {` `edges {` `node {` `namespace` `key` `value` `}` `}` `}` `}` `}` This retrieves the use case data to display in your custom frontend. *** ### Tips & Best Practices 1. Keep Use Cases Clear and Consistent: Use the same terminology across all use case options. For example, don't mix "Home Use" with "Household" or "Personal Home Use." 2. Limit Your Options: Don't create more than 10-12 use case options. Too many choices confuse customers and staff. Focus on the most relevant distinctions for your product catalog. 3. Think About Your Customer Journey: Choose use cases that match how customers search and think about products. If customers ask "Is this good for travel?", make sure "Travel / Portable" is an option. 4. Use Customer Language: Use the words your customers use, not industry jargon. "Travel / Portable" is better than "High Mobility Configuration." 5. Group Related Use Cases: If you have 10+ use cases, consider grouping them in your internal documentation (e.g., "Work Use Cases" group: Business, Professional, Home Office). 6. Make It Filterable: If your theme or app supports it, expose use cases as product filters on your collection pages so customers can narrow results by use case. 7. Update Regularly: Review your use case options quarterly. Remove ones that are rarely used and add new ones that match emerging customer needs. 8. Train Your Team: Make sure warehouse, customer service, and content teams understand which products should have which use cases assigned. Create a quick reference guide. 9. Combine with Other Metafields: Use the "Use Case" metafield alongside others like "Product Type," "Compatibility," or "Certifications" to create comprehensive product profiles. 10. Test Before Going Live: Assign use cases to 3-5 test products and verify they display correctly on your storefront in different screen sizes (mobile, tablet, desktop). 11. Use in Product Recommendations: Some apps allow you to create recommendations based on metafields. Use "Use Case" to recommend related products that serve the same purposes. 12. Consider SEO: Use case information can be displayed in product descriptions and meta tags to improve search visibility. Products for "Gaming" use cases might rank for gaming-related searches. 13. Analytics Tracking: If your theme supports it, track which use cases are viewed most often. This data helps inform future product development and marketing. 14. Mobile Optimization: Ensure use case badges or lists display well on mobile devices. Consider stacking them vertically or limiting display to the top 3-4 use cases on small screens. 15. Localization: If you sell in multiple languages, remember that use cases may need translation. Plan ahead for this if you're expanding internationally.\
*** ### Quick Reference Summary Table | Aspect | Details | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Metafield Name | Use Case | | Namespace | custom | | Key | use\_case | | Full ID | custom.use\_case | | Data Type | Multi Select (recommended) or Single Select | | Scope | Products | | Required? | No (optional for products) | | Example Values | Home Use, Professional Use, Business Use, Travel / Portable, Outdoor Use, Gaming / Entertainment, DIY / Hobbyist, Educational, Emergency / Backup, Premium / Luxury Use | | Display Method | Theme Editor block or Liquid code with list or badge styling | | Best For | Products with multiple or varied applications (tools, electronics, furniture, accessories) | | Editing Method | Individual, Bulk Edit, or CSV Import | | Storefront Display | Product detail page, collection filters, product recommendations | | Character Limit | Each use case option up to 255 characters | | API Accessible | Yes, via Storefront API and Admin API | *** This "Use Case" metafield is particularly valuable for Mixed/Other category products because it helps customers immediately understand whether a product fits their needs, regardless of the product type. It bridges the gap between product categories and real-world applications.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.accentuate.io/use-case-guides/other-mixed-catalog/use-case.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.