This guide covers every setting and option available when creating or editing products in Naayya. Use this as a reference for understanding what each field does and how it affects your products.
Universal Settings#
These settings apply to all product types (bundles, memberships, physical products).
Product Type Selection#
What are you selling?
- Packages & Bundles: Prepaid products with credits and expiry dates
- Physical Products: Tangible goods without class credits
- Memberships: Recurring subscriptions with ongoing billing
This is the first and most important choice - it determines which other settings become available.
Basic Information#
Product Name
- What customers see during purchase
- Used in receipts, invoices, and customer communications
- Keep it clear and descriptive
- Example: "10 Class Pass" not "bundle_10_classes"
Category
- Organizes products for easier management
- Available options: Class Pass, Workshop, Membership, Private Session, Equipment, Merchandise, Retreat, Teacher Training, Other
- Choose "Other" to create a custom category
- Used for reporting and product organization
Custom Category (appears when "Other" is selected)
- Enter your own category name
- Becomes the category for this product
- Example: "Nutrition Coaching", "Corporate Programs"
Pricing#
Price
- Amount customers pay (in your default currency)
- For bundles/physical: One-time payment
- For memberships: Amount per billing cycle
- Must be greater than 0
- Supports decimal values (e.g., 99.99)
Currency
- Automatically populated from your Stripe account
- Cannot be changed per-product
- All products use the same currency as your Stripe configuration
Product Status#
Available for Purchase
- Toggle switch to control product visibility
- ON: Customers can see and purchase the product
- OFF: Product is hidden from customer view
- Use OFF for: Discontinued products, seasonal items, testing new products
Environment
- Production (prod): Live products that customers can purchase
- Development (dev): Test products for internal use only
- Always use "prod" for customer-facing products
- "dev" is useful for testing new product configurations
Description#
Description
- Optional detailed information about the product
- Shown to customers during purchase
- Include important terms, conditions, or benefits
- Use for: What's included, usage restrictions, special instructions
- Supports multi-line text
Bundle-Specific Settings#
These settings only appear when "Packages & Bundles" is selected.
Credit System#
Credits
- Number of class bookings included in the package
- Must be at least 1
- Each regular class typically uses 1 credit
- Premium/special classes might use 2+ credits
- Set high numbers (50+) for "unlimited" packages
Validity Period (days)
- How long credits remain usable after purchase
- Leave blank for no expiration (not recommended)
- Common values: 30, 60, 90, 120 days
- Shorter periods create urgency; longer periods increase sales
Membership-Specific Settings#
These settings only appear when "Memberships" is selected.
Billing Configuration#
Billing Interval
- How often the customer is charged
- Options: Weekly, Every 2 Weeks, Monthly, Every 3 Months, Every 6 Months, Yearly
- Most common: Monthly
- Weekly works well for limited access plans
- Quarterly/yearly improve cash flow but require larger commitment
Usage Limit Per Period
- Maximum classes allowed per billing cycle
- Leave blank for unlimited access
- Set a number for limited plans (e.g., 4, 8, 12 classes per month)
- Resets each billing period
Activation Settings#
When Subscription Starts
Immediate (default):
- Membership begins immediately upon purchase
- Customer is charged right away
- Can book classes immediately
- Best for: Standard memberships
First Use:
- Membership begins when customer attends their first class
- Customer is charged when they first use the membership
- Reduces commitment anxiety for trials
- Best for: Intro offers, trial memberships
Scheduled Start:
- All customers start on the same specific date
- Enables synchronized billing cycles
- Requires setting a "Fixed Start Date"
- Best for: Cohort programs, seasonal memberships, challenges
Eligibility Rules#
Who can purchase this subscription?
Everyone - No restrictions (default):
- Anyone can purchase, including existing customers
- Allows multiple concurrent memberships
- Most flexible option
- Best for: Standard ongoing memberships
Once Per Customer - Can only buy once:
- Each customer can only purchase this specific membership once
- Prevents repeat purchases of the same product
- Automatically disables auto-renewal
- Requires a fixed end date
- Best for: One-time intro offers, trial memberships
First Subscription Only - New subscribers only:
- Only for customers who have never had any subscription
- More restrictive than "once per customer"
- Best for: New member specials, first-time subscriber discounts
Renewal Settings#
Auto-Renewal
- Controls whether the subscription continues automatically
Auto-Renewal ON (default):
- Continues billing until customer cancels
- Standard behavior for ongoing memberships
- Cannot have a fixed end date
- Best for: Regular monthly/annual memberships
Auto-Renewal OFF:
- Stops after one billing period
- Requires manual renewal or repurchase
- Allows fixed end dates
- Best for: Trial periods, limited-time offers, seasonal memberships
Fixed Date Settings#
Fixed Start Date (only when "Scheduled Start" is selected):
- Specific date when all memberships begin
- All customers who purchase will start on this date
- Creates synchronized billing cycles
- Required for scheduled activation
Fixed End Date (only when auto-renewal is OFF):
- Specific date when membership automatically ends
- Required for "once per customer" eligibility
- Cannot be used with auto-renewal ON
- Good for: Trial offers, seasonal programs, limited-time memberships
Advanced Configuration Tips#
Internal Product Management#
Product Name vs Display Name
- The system auto-generates an internal name from your product name
- Internal name uses lowercase and underscores (e.g., "10_class_pass")
- Display name is what customers see
- Internal name is used for system operations and API calls
Environment Usage#
Development Environment:
- Use for testing new product configurations
- Test pricing, billing intervals, and customer flows
- Products don't charge real money
- Switch to "prod" when ready for customers
Production Environment:
- Live products that process real payments
- Always double-check settings before activating
- Changes to active products affect existing customers
Multi-Product Strategy#
Product Variations:
- Create similar products with different terms (intro vs. regular pricing)
- Use different eligibility rules for new vs. returning customers
- Offer both limited and unlimited versions of similar memberships
Category Organization:
- Use consistent categorization across related products
- Custom categories help organize unique offerings
- Categories are useful for reporting and analysis
Validation Rules & Restrictions#
The system enforces several rules to prevent invalid configurations:
Membership Rules#
- "Once per customer" eligibility requires a fixed end date
- "Once per customer" cannot have auto-renewal enabled
- Auto-renewal ON prevents setting fixed end dates
- Scheduled activation requires a fixed start date
Bundle Rules#
- Credits must be at least 1
- Validity period must be at least 1 day (if specified)
- Price must be greater than 0
Universal Rules#
- Product names must be at least 2 characters
- Prices must be greater than $0.01
- Categories must be selected
Common Configuration Mistakes#
Membership Issues:
- Forgetting to set usage limits for "limited" plans
- Setting auto-renewal ON with eligibility "once per customer" (not allowed)
- Using "scheduled start" without setting a fixed start date
- Pricing monthly memberships too close to bundle prices
Bundle Issues:
- Setting validity periods too short for large packages
- Pricing credits inconsistently across different bundle sizes
- Using unclear names that don't indicate credit count
General Issues:
- Creating products in "dev" environment and wondering why customers can't see them
- Forgetting to set products as "Available for Purchase"
- Using vague product names that don't describe what's included
Testing Your Products#
Before making products live:
- Create in dev environment first
- Test the purchase flow (use Stripe test mode)
- Verify all settings work as expected
- Check customer communications (emails, receipts)
- Test booking behavior for credit-based products
- Switch to prod environment when ready
- Set to "Available for Purchase"
Product Management After Creation#
Once products are live, you can:
- Edit most settings (price changes affect new purchases only)
- Enable/disable availability
- Update descriptions and categories
- Monitor usage and performance
- Create variations based on popular products
Remember: Changes to active memberships may affect existing subscribers, so test thoroughly and communicate changes to customers when necessary.
For specific product type guidance, see our dedicated guides for Bundles, Memberships, and Physical Products.