Pre-built store configuration templates for common business types. Use whenever user asks for templates, examples, starting points, or mentions fashion/electronics/subscription store setup. Not for custom product type design (use product-modeling).
Instrucciones de origen · Vista previa de solo lectura
name
configurator-recipes
version
2.0.0
description
Pre-built store configuration templates for common business types. Use whenever user asks for templates, examples, starting points, or mentions fashion/electronics/subscription store setup. Not for custom product type design (use product-modeling).
allowed-tools
Read, Write
license
MIT
compatibility
Claude Code or Claude.ai. Requires @saleor/configurator CLI installed.
Configurator Recipes
Overview
Recipes are ready-to-use config.yml templates for common store types. Pick one that matches your business, customize it, and deploy. They save you from building your store configuration from scratch.
When to Use
"How do I set up a fashion store?"
"Is there a template for electronics?"
"Can I see an example config.yml?"
"What's a good starting point for my store?"
"How do I set up a subscription service?"
When NOT looking for CLI commands -- use instead
configurator-cli
When NOT designing custom product types -- use product-modeling instead
Electronics Store -- Single channel (USD), product types for Smartphones, Laptops, Tablets, Accessories, and Software. Attributes include Brand, Storage, RAM, Screen Size, and Warranty. See templates/electronics-store.yml.
Subscription Service -- Subscription portal channel, product types for Monthly/Annual subscriptions, One-Time Purchases, and Add-Ons. Attributes include Plan Tier, Billing Cycle, User Limit, and Storage Limit. See templates/subscription-service.yml.
Customization Tips
After copying a recipe:
Rename channels to match your brand and regions
Adjust currency and country codes for your markets
Modify categories for your actual product catalog
Add or remove product types you don't need
Test on staging first before deploying to production
Common Mistakes
Mistake
Fix
Using a recipe without customizing identifiers
Update all slugs and names to match your brand before deploying
Not adjusting currency/country codes
Change currencyCode and defaultCountry to your actual markets
Deploying a recipe straight to production
Always test on a staging instance first
Keeping entity types you don't need
Remove unused product types, categories, etc. to keep your config clean
Forgetting to update channel references
Products reference channels by slug -- make sure they match after renaming
Creating Your Own Recipe
Template Structure
A recipe template should follow this structure:
# Recipe: [Business Type] Store# Description: [What this recipe sets up]# Customize: [List key things users should change]channels:-name:"Main Store"# ← User should renameslug:"main"# ← User should updatecurrencyCode:USD# ← User should set regiondefaultCountry:USisActive:trueproductTypes:# Each type should have a comment explaining its purpose-name:"[Type Name]"isShippingRequired:trueproductAttributes: [...]
variantAttributes: [...]
categories:# Keep hierarchy to 3 levels max-name:"[Root Category]"slug:"[root-slug]"subcategories: [...]
