Skip to content
Alva Digital Downloads

Updating Product Mappings

Learn how to update existing product mappings, manage file changes, and handle updates without disrupting customer access.

Why Update Mappings?

Section titled “Why Update Mappings?”

Product mappings need updates when:

  • ✅ Adding new files to existing products
  • ✅ Removing outdated files
  • ✅ Replacing files with updated versions
  • ✅ Fixing errors in original mapping
  • ✅ Responding to customer feedback
  • ✅ Seasonal updates or improvements

Accessing Existing Mappings

Section titled “Accessing Existing Mappings”

Find Mapped Products

Section titled “Find Mapped Products”
  1. Go to Products in Alva app
  2. Look for products with Mapped badge
  1. Click product to view/edit mapping

View Mapping Details

Section titled “View Mapping Details”

Product mapping page shows:

  • Current mapped files/packs
  • Download type (ZIP or Individual)
  • ZIP title
  • Variant mappings (if applicable)
  • Last updated date
  • Recent orders using this mapping

Adding Files to Existing Mapping

Section titled “Adding Files to Existing Mapping”

Add More Files

Section titled “Add More Files”
  1. Open product mapping page
  2. Scroll to Files section
  3. Click Add Files button
  1. Select additional files from selector
  2. Click Add Selected Files
  3. New files appear in mapping
  1. Reorder if needed (drag handles)
  2. Click Save

What Happens When You Add Files

Section titled “What Happens When You Add Files”

For New Orders:

  • ✅ Customers get all files (original + new)
  • ✅ ZIP automatically regenerates with new files

For Existing Orders:

  • ⚠️ Depends on your settings:
    • Dynamic links: Get new files automatically
    • Static links: Keep original files only

Removing Files from Mapping

Section titled “Removing Files from Mapping”

Remove Individual Files

Section titled “Remove Individual Files”
  1. Open product mapping
  2. Find file to remove
  3. Click × or trash icon next to file

  1. Confirmation dialog appears: “Remove file from mapping? Existing customers will lose access.”

  2. Click Confirm Remove

  3. File removed from mapping

  4. Click Save

What Happens When You Remove Files

Section titled “What Happens When You Remove Files”

For New Orders:

  • ✅ Customers don’t get removed file
  • ✅ ZIP regenerates without removed file

For Existing Orders:

  • ⚠️ Important: Existing customers lose access to removed file
  • ⚠️ Their download links may break if relying on that file
  • ⚠️ Consider communication before removing

Safe File Removal Process

Section titled “Safe File Removal Process”

  1. Check Usage

    • How many orders include this file?
    • Recent orders (last 90 days)?

  2. Communicate (if significant changes)

    • Email affected customers
    • Explain changes
    • Offer alternatives

  3. Set Grace Period

    • Wait 30-60 days before removing
    • Allows existing customers to download

  4. Remove File

    • After grace period
    • Remove from mapping

Replacing Files

Section titled “Replacing Files”

Scenario: Updated Version

Section titled “Scenario: Updated Version”

You have a new version of a file and want to replace the old one:

Method 1: Replace in Mapping

  1. Upload new version of file
  2. Open product mapping
  3. Remove old file
  4. Add new file
  5. Save

Impact:

  • New orders get new version
  • Existing customers keep old version (unless link regenerates)

Method 2: Update File in Place

  1. Keep same filename
  2. Upload new version with identical name
  3. Old file is replaced in storage
  4. Mapping unchanged
  5. ZIP automatically regenerates

Impact:

  • ALL customers get new version (including existing)
  • More seamless transition
  • No mapping changes needed

Recommended for:

  • Bug fixes
  • Minor updates
  • When all customers should get new version

Method 3: Version Both Files

  1. Keep old file (rename to file-v1.pdf)
  2. Add new file (file-v2.pdf)
  3. Both in mapping temporarily
  4. Later remove v1

Impact:

  • Customers can choose version
  • Smooth transition period
  • More storage used

Updating Multiple Products

Section titled “Updating Multiple Products”

Bulk File Updates

Section titled “Bulk File Updates”

When the same file is mapped to multiple products:

Scenario: bonus-guide.pdf is mapped to 10 products. You have an updated version.

Option 1: Update File Directly

  1. Upload new bonus-guide.pdf (overwrites old)
  2. All 10 products automatically use new version
  3. No mapping changes needed

Option 2: Bulk Remap

  1. Upload new file as bonus-guide-v2.pdf
  2. Use bulk mapping to add to all 10 products
  3. Use bulk unmapping to remove old version
  4. More control, more work

See: Bulk Product Mapping

Updating Pack-Based Mappings

Section titled “Updating Pack-Based Mappings”

When Packs Change

Section titled “When Packs Change”

If product is mapped to a Pack:

Product Mapping Type:

  • Dynamic Pack Link: Updates automatically when Pack changes
  • Static File Copy: Doesn’t update when Pack changes

Dynamic Pack Updates

Section titled “Dynamic Pack Updates”

Products with dynamic Pack links:

  1. Edit Pack (add/remove/reorder files)
  2. Save Pack
  3. All products mapped to Pack automatically updated
  4. ZIPs regenerate
  5. No product mapping edits needed

Benefits:

  • ✅ Update once, applies everywhere
  • ✅ Consistency across products
  • ✅ Efficient management

Use when:

  • Products should always have latest Pack version
  • Maintaining consistency is important
  • Managing multiple products with same content

Static File Mapping

Section titled “Static File Mapping”

Products with static file copies:

  1. Edit Pack
  2. Pack changes
  3. Products DON’T update automatically
  4. Must manually update each product mapping

Benefits:

  • ✅ Products remain stable
  • ✅ Control over which products get updates
  • ✅ Version locking

Use when:

  • Products shouldn’t change automatically
  • Different products need different Pack versions
  • Stability over consistency

Managing Mapping Versions

Section titled “Managing Mapping Versions”

Version History

Section titled “Version History”

View past product mapping changes:

  1. Open product mapping
  2. Click Version History tab

Shows:

  • Date of change
  • User who made change
  • What changed (files added/removed)
  • Version number

Rollback to Previous Version

Section titled “Rollback to Previous Version”

Restore previous mapping:

  1. View version history
  2. Click Restore on previous version
  3. Confirm restoration
  4. Mapping reverts to that state

Use cases:

  • Accidentally removed wrong files
  • Customer issues with new version
  • Testing changes (easy rollback)

Updating Variant Mappings

Section titled “Updating Variant Mappings”

Add Variant Mapping to Existing Product

Section titled “Add Variant Mapping to Existing Product”

Product currently has default mapping only:

  1. Open product mapping
  2. Toggle Enable Variant-Specific Mapping
  1. Variant list expands
  2. Map files to each variant
  3. Save

Impact:

  • Customers now get variant-specific files
  • Default mapping becomes fallback

Update Variant Files

Section titled “Update Variant Files”

Change files for specific variant:

  1. Open product mapping
  2. Find variant in list
  3. Add/remove files for that variant
  4. Save

Impact:

  • Only affects that variant
  • Other variants unchanged

Remove Variant Mapping

Section titled “Remove Variant Mapping”

Revert to default mapping for all variants:

  1. Open product mapping
  2. Toggle Disable Variant-Specific Mapping
  3. Confirm
  4. All variants now use default mapping

ZIP Configuration Updates

Section titled “ZIP Configuration Updates”

Change ZIP Title

Section titled “Change ZIP Title”
  1. Open product mapping
  2. Locate ZIP Title field
  3. Enter new title
  4. Save

Impact:

  • New orders get new ZIP filename
  • Existing orders keep old filename
  • ZIP regenerates with new name

Change Download Type

Section titled “Change Download Type”

Switch between ZIP and Individual Files:

  1. Open product mapping
  2. Change Download Type dropdown
  3. Save

ZIP → Individual Files:

  • ZIP cache deleted
  • Customers download files separately

Individual Files → ZIP:

  • ZIP generated
  • Customers download bundle

Update Notifications

Section titled “Update Notifications”

Notify Customers of Updates

Section titled “Notify Customers of Updates”

When making significant changes:

Option 1: Email Customers Directly

  1. Export customer list from Orders
  2. Send update email via your email system
  3. Explain changes
  4. Provide new download link if needed

Option 2: Use App Notification Feature (if available)

  1. Go to Orders → Send Update Email
  2. Select orders to notify
  3. Compose message
  4. Send notification with updated download link

What to include:

  • What changed (new files, updated versions)
  • Why it changed (improvements, bug fixes)
  • How to access updates
  • Support contact if issues

Update Impact Assessment

Section titled “Update Impact Assessment”

Before Updating, Ask:

Section titled “Before Updating, Ask:”

Scope:

  • How many products affected?
  • How many customers affected?
  • How many orders in last 90 days?

Impact:

  • Breaking changes? (files removed)
  • Improvements only? (files added/updated)
  • Critical updates? (bug fixes)

Communication:

  • Do customers need notification?
  • How urgent is update?
  • Support team prepared?

Testing:

  • Tested new files?
  • Verified ZIP generation?
  • Checked on multiple devices?

Update Scheduling

Section titled “Update Scheduling”

Best Time to Update

Section titled “Best Time to Update”

Good Times:

  • Off-peak hours (minimize active downloads affected)
  • After announcements/marketing
  • Scheduled maintenance windows

Bad Times:

  • During active sales/promotions
  • Right before product launches
  • When support team unavailable

Tracking Updates

Section titled “Tracking Updates”

Update Log

Section titled “Update Log”

Keep record of mapping updates:

What to track:

  • Date of update
  • Product(s) affected
  • Changes made
  • Reason for update
  • Who performed update
  • Test results
  • Customer notifications sent

Automated Logging

Section titled “Automated Logging”

App automatically logs:

  • Mapping changes
  • File additions/removals
  • Version updates
  • Bulk operations

Access via Settings → Activity Log

Update Best Practices

Section titled “Update Best Practices”

1. Test Before Applying

Section titled “1. Test Before Applying”

Never update production mapping without testing:

  • Create test order with new mapping
  • Download and verify
  • Check on multiple platforms
  • Confirm customer experience

2. Update During Low Traffic

Section titled “2. Update During Low Traffic”

Schedule updates when:

  • Fewest active customers
  • Support team available
  • Can monitor impact

3. Communicate Proactively

Section titled “3. Communicate Proactively”

For significant updates:

  • Notify customers in advance
  • Explain benefits
  • Provide timeline
  • Offer support

4. Version Your Files

Section titled “4. Version Your Files”

Use versioning in filenames:

  • template-v1.psd, template-v2.psd
  • Easy to track
  • Clear progression
  • Can offer both versions temporarily

5. Document Changes

Section titled “5. Document Changes”

Keep changelog:

  • What changed
  • When
  • Why
  • Impact

6. Monitor After Updates

Section titled “6. Monitor After Updates”

Check after updates:

  • Download success rate
  • Customer support tickets
  • Error logs
  • Customer feedback

7. Have Rollback Plan

Section titled “7. Have Rollback Plan”

Before major updates:

  • Document current state
  • Export mapping data
  • Know how to rollback
  • Test rollback process

Handling Update Issues

Section titled “Handling Update Issues”

Issue: ZIP Won’t Regenerate

Section titled “Issue: ZIP Won’t Regenerate”

Solution:

  1. Click Regenerate ZIP manually
  2. Wait 2-3 minutes
  3. Check version history
  4. Contact support if stuck

Issue: Customers Still Getting Old Files

Section titled “Issue: Customers Still Getting Old Files”

Cause: Cache not cleared

Solution:

  1. Force ZIP regeneration
  2. Check download link expiry
  3. Have customers use new download link
Section titled “Issue: Broken Download Links”

Cause: File removed from mapping

Solution:

  1. Re-add file temporarily
  2. Notify affected customers
  3. Provide updated download links

Issue: Variant Mapping Confusion

Section titled “Issue: Variant Mapping Confusion”

Cause: Variant updates not saved correctly

Solution:

  1. Review each variant mapping
  2. Ensure saved properly
  3. Test order for each variant
  4. Verify correct files delivered

Update Rollback Procedure

Section titled “Update Rollback Procedure”

If update causes issues:

  1. Assess Problem

    • What’s broken?
    • How many customers affected?

  2. Quick Fix or Rollback?

    • Small fix possible? → Quick fix
    • Major issues? → Rollback

  3. Perform Rollback

    • Access version history
    • Restore previous version
    • OR manually revert changes

  4. Verify Rollback

    • Test download
    • Check with affected customers
    • Monitor for issues

  5. Communicate

    • Notify customers of temporary issue
    • Explain resolution
    • Provide timeline for proper fix

Next Steps

Section titled “Next Steps”