How to bulk download and install products

Documentation
, , ,
1

How to bulk download and install products

This guide explains high-volume deployment workflows with bulk download and bulk install, including safety gates and failure handling.

Required access: Plan with Bulk Download and/or Bulk Install features.

When to use bulk workflows

Use bulk actions for onboarding new websites, client handovers, or recurring setup profiles.

Pre-bulk checklist

Before running bulk actions:

  1. Confirm your plan includes the required bulk features.
  2. Prepare product list (or collection) first.
  3. Confirm target site is connected and healthy.
  4. For large changes, test on staging first.
  5. Ensure you can identify partial failures quickly.

How to run bulk download and install

  1. Open your product workflow in the dashboard.
  2. Select multiple products.
  3. Start bulk download or choose a connected site for bulk install.
  4. Monitor progress until all jobs finish.
  5. Re-run failed items individually.
  6. Record completed stack for reuse.

Verification checklist

After bulk actions:

  • Expected product count completed
  • Failed items are identified and retried
  • Site remains healthy after batch install
  • License limits were not exceeded
  • Team can reproduce the same stack on another site

What happens after bulk actions

  • Successful items are applied immediately.
  • Failed items remain visible for retry and troubleshooting.
  • Usage and feature limits remain enforced by your plan.

Troubleshooting

If bulk options are missing, check your license feature badges and confirm bulk features are enabled for your plan.

Related guides

  • How collections work
  • How to install plugins and themes from GrootMade Connect
  • How billing and subscription management works

Exact route paths

  • /dashboard
  • /dashboard/sites
  • /dashboard/history

Expected UI state after each step

  • Step 1: Multi-select controls appear for product selection.
  • Step 2: Bulk action buttons are visible for eligible plans.
  • Step 3: Batch progress updates while jobs run.
  • Step 4: Failed jobs remain visible for retry.

Screenshot map (step-level)

  1. Bulk selection and workflow

  2. Batch operation visual

Operational objective

Complete the “How to bulk download and install products” workflow with predictable outcomes, clear auditability, and repeatable execution quality across team members and projects.

Acceptance criteria (all must pass)

  • The workflow can be completed without missing permissions or blocked route access.
  • All required dashboard routes load successfully for the active account.
  • The expected UI states are visible in the same order as documented.
  • At least one end-to-end validation confirms the process works in practice.
  • Evidence artifacts are captured for support and audit handoff.

Routes that must be reachable during validation:

  • /dashboard
  • /dashboard/sites
  • /dashboard/history

Failure modes and exact remediation

  • Permission failure: Recheck plan/license entitlements and retry after session refresh.
  • Route loads but action is missing: Confirm feature flags/plan gates and selected context (site/license).
  • Action runs but state does not update: Refresh, re-open the relevant page, and verify from history/log view.
  • Partial success in multi-step operations: Retry only failed sub-steps and preserve successful state.
  • Cross-page mismatch: Reconcile with dashboard history and capture timestamps before escalation.
  • Persistent failure after one controlled retry: Open support ticket with full evidence package.

Evidence package for support escalation

Collect all items before escalating:

  • Account email and user role
  • Affected route path and exact action taken
  • Site URL, product/license identifier (if relevant)
  • Timestamps for first failure and latest retry
  • Expected result vs actual result
  • Screenshot set listed below

Screenshot evidence checklist

  • Step 1: Bulk selection and workflow
  • Step 2: Batch operation visual
  • One screenshot with visible timestamp (system clock/browser tab)
  • One screenshot showing route context or breadcrumb
  • One screenshot showing final persisted result
  • Replace any generic placeholder/demo visuals with real environment captures

FAQ

Can I skip steps if I already know this workflow?

Skip only after all acceptance criteria still pass. If any criterion fails, run the full sequence exactly as documented.

Should I run this in production first?

Use staging first for medium/high-impact changes. Promote to production only after validation evidence is complete.

What if my screen does not match the guide exactly?

UI can vary by plan and feature access. Validate route access, plan gates, and expected state outcomes instead of pixel-perfect layout.

How many retries should I perform before escalation?

Run one controlled retry after checklist validation. If failure persists, escalate with full evidence to avoid hidden side effects.

Who owns this guide operationally?

Implementation Team owns this guide and its periodic review cycle.

Guide metadata

  • Difficulty: Intermediate
  • Estimated completion time: 20-35 minutes
  • Owner: Implementation Team
  • Last reviewed: 2026-03-18