Direct Sale AI

App Bundles

Official guide · English · Version 9c253d0cf11816df

App Bundles are curated, atomic installations of compatible App Store-managed items. While checkout is unavailable, a published bundle must be free. Linked integrations are configured individually, and local plugins without registered runtime consumers remain Draft/internal, so current built-in bundle candidates are storefront templates only.

Browsing Bundles

Bundles appear at the top of the App Store main page when no category or search filter is applied. Each card shows the bundle name, item count, current tenant status, price availability, and discount metadata when present.

Click a bundle card to view its detail page and included apps.

Eligibility and Preconditions

A new installable bundle must satisfy all of these rules:

  • It contains at least one app.
  • Every member is published and free while checkout is disabled.
  • Every member is a storefront template or a local plugin with a registered runtime consumer. Current built-ins have no registered local runtime consumers, and linked integrations are excluded from bulk installation.
  • It contains at most one storefront template.
  • Any required configuration field has a valid non-sensitive default. Bundles do not collect a separate interactive configuration form for each member.
  • Dependencies inside the bundle are resolved together. Dependencies outside the bundle must already be active for the tenant.
  • Published bundles and App Store-managed members have no minimum Required Plan until runtime downgrade enforcement is available. Draft records may retain that future metadata.

Info: If a template (or a future local app with a registered runtime consumer) needs tenant-specific required input, install it individually and complete its pre-install Configuration form instead of putting it in a bundle.

Installing a Bundle

  1. Open the bundle detail page.
  2. Review the included apps, configuration defaults, and dependencies.
  3. Click Install Bundle.
  4. The server validates every item before writing anything, then installs eligible items in one transaction.
  5. If any validation or write fails, the transaction rolls back rather than leaving a partially installed bundle.

When a member was already installed independently, bundle installation skips it and does not claim ownership of that existing record. Newly created installation records are marked as owned by the bundle.

Warning: Paid and freemium bundle activation remains disabled until App Store checkout and payment verification are available. A displayed future price is not an active purchase path.

Legacy Bundles with Linked Integrations

Older data may contain a bundle with a linked integration. The detail page directs the tenant to configure each integration on its dedicated settings page and does not show a misleading bulk-install action. New Admin forms exclude these integrations from bundle membership.

Uninstalling a Bundle

  1. Open the bundle detail page.
  2. Click Uninstall Bundle and confirm.
  3. The App Store removes only installation records created and owned by that bundle.
  4. Apps that existed independently before bundle installation are preserved.
  5. If the removed bundle owned the active template, the storefront switches to another installed template or the safe Modern fallback.

Reverse dependencies are checked before removal. If another active app outside the bundle depends on a bundle-owned item, resolve that dependency before uninstalling.

Info: Ownership is record-based, not inferred from catalog membership. Merely appearing in a bundle does not make an independently installed app removable by that bundle.

Managing Bundle Members

Bundle-owned templates (and future local apps with registered runtime consumers) appear on App Store > Installed with the bundle name. They can be configured, activated, deactivated, or uninstalled individually. Doing so can change the bundle from fully active to partial; the bundle detail page reflects the remaining owned and operational records.

Linked integrations always remain managed on their dedicated settings page, even if they appear in a legacy bundle.

Bundle Pricing and Plans

  • Required Plan is Draft-only metadata until runtime downgrade enforcement is available; published bundles must leave it empty.
  • Included Free With Plans is future pricing metadata for Draft bundles; it has no effect while published bundles must be free and have no Required Plan.
  • While checkout is disabled, only free bundles can be published or installed.
  • Discount and price fields may be prepared on Draft records for future checkout, but they do not authorize activation today.

Finding Bundles for a Specific App

When an app belongs to a published bundle, its detail sidebar lists that bundle and links to its detail page. Use that page to review the complete contents and current eligibility before installing.

Best Practices

  • Use bundles for items that can be installed safely without tenant-specific secrets or required interactive input.
  • Keep linked provider setup on the dedicated encrypted integration pages.
  • Put related dependencies in the same bundle when possible; document any external dependency that must already be active.
  • Treat a bundle as the owner only of records it created, and verify the Installed page before removing it.