Marketplace
The Marketplace area lets buyers find, buy, install, update, rescan, and uninstall packages. Packages may include optional addons, AI tools, integrations, report modules, payment modules, themes, or operational extensions.
Dashboard and Catalog
The dashboard shows installed packages, updates, license status, and available products. The catalog can be filtered by product type, category, addon type, license, status, keyword, version, or compatibility. Product cards should show title, summary, version, price, license type, installed status, update status, and action buttons.
Buying Products
When the product uses Envato or a similar marketplace, buyers normally complete payment in the marketplace storefront, then return with a purchase code. For storefront cart flows, review the cart, checkout, payment status, invoice, and download links. Keep purchase codes private and store them only in the licensed installation.
Install With Purchase Code
- Open Marketplace and choose the product or addon.
- Enter the purchase code.
- Let the system verify license ownership and domain eligibility.
- Install the package and run migrations if required.
- Clear cache and verify menus, routes, plan fields, and pricing rows.
Install With ZIP File
Use ZIP installation when the seller provides an addon archive. Upload the ZIP, confirm package metadata, module name, provider list, version, and compatibility, then install. Never upload unknown packages to production without backup. If installation fails halfway, restore from backup or remove the partial module folder before retrying.
Packages Page
The Packages page lists installed packages with filters for installed, active, inactive, update available, core, addon, theme, integration, or payment-related packages. The package table should include module name, provider, version, license, install path, status, update date, and actions.
Updating, Rescanning, and Uninstalling
Update packages after backing up. Rescan packages when a module folder was uploaded manually or metadata changed. Uninstall only after disabling related plan permissions and confirming no critical records depend on the addon. Removing a package can hide routes, buttons, fields, pricing rows, sidebar items, scheduled jobs, and admin settings.
Best Practices and Troubleshooting
Update the core product before addon packages. Keep package versions compatible. Clear cache after installing, updating, or uninstalling. If a package is installed but the menu is missing, check provider registration, module status, plan permission, cache, and user role. If a package update fails, inspect logs and restore the backup before retrying.
Buyer Readiness Notes
Before using Marketplace in production, confirm that the application has been installed on the correct licensed domain, cache has been cleared after configuration changes, and all relevant workspace permissions have been tested with realistic user accounts. LeadFlow AI is often used as a customer-facing SaaS product, so a setting that looks internal during setup can affect paid users, published forms, funnel redirects, lead records, invoices, files, domains, or addon visibility.
For agency deployments, prepare a repeatable launch checklist for each workspace. The checklist should include workspace branding, form fields, consent copy, funnel pages, tracking fields, notification recipients, lead assignment rules, reports, file storage, custom domains, support ownership, and team permissions. For SaaS deployments, prepare a platform checklist that covers plans, payment gateways, mail delivery, queue workers, cron, file storage, AI provider settings, marketplace packages, backups, privacy pages, and production debug mode.
When troubleshooting this area, separate configuration problems from data problems. Configuration problems usually involve cache, plan permissions, missing addons, provider credentials, mail settings, queue workers, or route discovery. Data problems usually involve workspace ownership, hidden fields, duplicate slugs, invalid imports, deleted parent records, old embed codes, or team permission rules. Testing with a fresh private browser session and a non-admin account helps confirm the real customer experience.
Operational FAQ
Who should review this page?
Product owners, SaaS admins, agency operators, support staff, and implementation partners should review it before changing related production workflows.
What should be documented internally?
Record any custom domain rules, installed addons, plan limits, payment provider settings, AI provider settings, integration credentials, and client-specific visibility decisions.
What is the safest production habit?
Back up first, change one thing at a time, clear cache when the change affects Laravel configuration or package discovery, then test the exact user or client workflow that depends on the change.