Managing Extensions in the Administration Panel

Learn how to evaluate, install, configure, enable, disable, update, and troubleshoot e-commerce extensions from the administration panel.

An extension is an add-on component that introduces or changes store functionality. Extensions can add payment providers, shipping calculations, storefront content, reports, analytics, themes, marketplace integrations, and many other capabilities.

A core feature is included in the platform itself and is maintained as part of the main system. An extension is installed separately, usually from a package, marketplace, or third-party vendor. Extensions allow a store to gain specialized functionality without changing every part of the platform core.

Administrators are responsible for selecting suitable extensions, checking compatibility, configuring them correctly, protecting credentials, testing customer-facing behavior, and maintaining or removing extensions safely. Begin extension management from the Extensions area of the administration panel.

Extension categories

Categories organize extensions by the part of the store they affect. The category usually determines where the extension is managed in the administration panel and where its result appears on the storefront or in store operations. Category names and available types can differ by platform version and installed packages.

Category	Primary purpose	Typical configuration	Where the result appears
Modules	Add storefront features or content blocks.	Status, content, layout, page assignment, position, and sort order.	Storefront pages such as the home page, product pages, or sidebars.
Themes	Control visual presentation and sometimes template behavior.	Theme selection, branding, templates, responsive settings, and assets.	Across the storefront.
Payments	Allow customers to pay through a provider or payment method.	Credentials, sandbox mode, zones, currencies, order statuses, and sort order.	Checkout payment step and payment administration.
Shipping methods	Calculate or present delivery options.	Zones, rates, weight, price, tax, customer groups, and sort order.	Checkout shipping step.
Order totals	Add, subtract, calculate, or display amounts in an order.	Priority, tax class, thresholds, discounts, and display rules.	Cart, checkout, invoices, and order totals.
Feeds	Send product or store data to external services and product channels.	Data fields, schedules, currencies, filters, and destination credentials.	External marketplaces, shopping channels, or generated feed output.
Reports	Provide operational or sales analysis.	Date range, store scope, filters, permissions, and export settings.	Administration reports and exports.
Analytics	Measure visits, events, conversions, or campaign activity.	Tracking identifiers, consent behavior, event rules, and environments.	Storefront tracking and external analytics service.
Fraud prevention	Assess transactions or customer activity for risk.	Provider credentials, risk thresholds, rules, and order actions.	Checkout decisions and order review screens.
Marketplace integrations	Connect products, inventory, orders, or listings to marketplaces.	API credentials, mappings, synchronization schedules, and status rules.	Administration synchronization tools and external marketplace.

Finding and evaluating extensions

Open the Extensions area and browse by category. Review installed extensions first to understand what is already active. A category may contain extensions that are installed but disabled, installed and enabled, or available for installation.

Before installing an extension, evaluate more than its feature list. Confirm the platform version, store version, PHP or runtime requirements where relevant, and compatibility with the current theme and other extensions. Check the vendor's reputation, release history, changelog, support process, documentation, licensing terms, and required external services.

Check	Why it matters	How to verify	Risk if skipped
Version compatibility	Prevents incompatible code or database changes.	Compare the package requirements with the platform and runtime versions.	Installation failure, errors, or broken checkout.
Vendor reputation	Indicates maintenance quality and support reliability.	Review vendor history, support responses, and independent feedback.	Unmaintained or unsafe software.
Update history and changelog	Shows whether defects and security issues are addressed.	Read release notes, dates, and upgrade instructions.	Unexpected behavior or unresolved vulnerabilities.
License and support	Clarifies permitted use and how help is obtained.	Read license terms, support scope, and renewal conditions.	Compliance problems or no assistance during an incident.
Required services and dependencies	Extensions may need libraries, companion extensions, APIs, or permissions.	Read documentation and dependency notices before installation.	Incomplete installation or runtime failures.
Security and privacy	Extensions may access orders, customers, credentials, or payment flows.	Review permissions, data collection, security practices, and provider access.	Data exposure, fraud, or privacy violations.
Performance	Extra queries, scripts, or remote calls can slow pages and checkout.	Test in a non-production environment and inspect page behavior.	Slow storefront or failed time-sensitive requests.
Conflicts	Two extensions may change the same template, event, total, or checkout step.	Compare affected areas and test with existing extensions enabled.	Duplicate output, incorrect totals, or checkout errors.

Installation workflow

Obtain the package from a trusted source. Confirm its version, checksum or authenticity process where provided, license, and documentation.
Back up the site. Include files, database, extension settings, and any relevant configuration. Test that the backup can be restored.
Use the supported installation method. Depending on the platform, this may be a marketplace installation or an administration-panel package upload. Avoid manually copying or deleting files unless the vendor's supported procedure explicitly requires it.
Review dependency checks. Resolve required platform versions, libraries, services, companion extensions, and administrator permissions.
Complete file deployment and database steps. The installer may place files, create tables, register events, or add settings.
Refresh modifications and caches when applicable. Some platforms use a modification layer that must be rebuilt before extension code changes take effect. Generated caches may also need refreshing.
Configure the extension. Installation does not necessarily make the extension active or customer-facing.
Test before activation. Use a staging environment where possible. Check relevant storefront pages, checkout paths, logs, and external service responses.

Installation, activation, and configuration are separate lifecycle actions. An installed extension can remain disabled while settings are prepared. An enabled extension can still be ineffective if it has no layout assignment, valid credentials, or eligible store scope.

Configuring an extension

Open the extension's settings form from its category. Common fields include the following:

Enabled status: controls whether the extension can operate.
Store scope: selects one store or multiple stores in a multi-store installation.
Layout and position: determines where a display-oriented module is rendered.
Sort order or processing priority: controls display sequence or the order in which calculations and methods are processed.
Geographic zone: limits availability by country, region, or configured zone.
Credentials and API keys: authenticate the extension with an external provider.
Sandbox or production mode: selects a test environment or live service.
Tax class: determines how applicable taxes are calculated or displayed.
Order-status mapping: maps provider responses to statuses such as pending, paid, failed, or refunded.
Display settings: control labels, content, images, customer groups, dates, and visibility.

An API key is a credential used to authenticate an extension with an external service. Treat API keys, passwords, tokens, private certificates, and webhook secrets as sensitive data. Use a restricted administrator account, avoid placing secrets in support screenshots, do not commit them to source control, and use production credentials only after sandbox testing succeeds.

Save settings, then validate them. Confirm that required fields are accepted, the selected store and zone are correct, and the provider reports a successful connection where supported. Test the exact customer journey rather than relying only on a successful save.

Practical configuration examples

Enable a new payment provider

Confirm that the provider extension supports the platform version, currency, countries, and checkout flow.
Install the provider extension and complete any dependency or modification-refresh steps.
Enter sandbox credentials first and select sandbox mode.
Set the enabled status, geographic availability, order-status mapping, and sort order.
Run a test checkout using a permitted test address and payment details.
Review the order, callback or webhook result, logs, and customer-facing messages.
Switch to production credentials only after the complete test succeeds, then perform a controlled live transaction if appropriate.

Add a storefront promotional module

Install and enable the module.
Create or select its promotional content.
Assign it to the relevant layout, page, store, and position.
Set its sort order relative to other modules in that position.
Check the desktop and mobile storefront, including the exact page route and any customer-group restrictions.

Extension placement and ordering

A layout position is the designated area of a page where a display extension is rendered. A module may be enabled but invisible if it is assigned to the wrong layout, page, store, customer group, or position. Page assignments might include the home page, category page, product page, cart, or checkout.

Sort order is a numeric or priority setting that controls display or processing sequence. For modules, it determines which block appears first. For order totals, it can affect calculation order. For shipping and payment methods, it controls the order in which choices are presented. After changing placement or priority, test the storefront and checkout to detect overlap, duplicate output, incorrect totals, or an unexpectedly selected method.

Permissions and access control

Administrator user groups commonly have separate access permission and modify permission. Access permission allows a user to open or view an area. Modify permission allows the user to save or change it. A user with neither permission may not see the extension; a user with access but no modify permission may see the form but receive an authorization error or be unable to save.

Grant only the privileges required for the person's role. Restrict sensitive configuration screens, especially payment credentials, API keys, customer data integrations, and marketplace synchronization. If an extension is not listed, cannot be opened, or cannot be saved, check the user group's access and modify permissions before assuming that installation failed. Review permissions in the administration panel and related system configuration where applicable.

Enabling, disabling, and uninstalling

Action	What it changes	Data impact	When to use it	Verification step
Install	Deploys the extension and may register code, settings, events, or database structures.	May create files, settings, tables, and registrations.	When adding the capability.	Confirm the package and dependencies completed successfully.
Enable	Allows the installed extension to operate.	Usually preserves existing settings and data.	After configuration and testing.	Test the affected storefront or administration workflow.
Disable	Stops normal operation without necessarily removing the extension.	Usually retains settings and data.	Temporary testing, maintenance, or incident isolation.	Confirm the problem or behavior changes as expected.
Uninstall	Runs the platform's removal procedure.	May remove settings, tables, event registrations, placements, and extension data.	Only when the extension is no longer needed.	Check active workflows, storefront output, checkout, and residual credentials.

Disabling is reversible and is often the safer first step during testing or maintenance. Uninstalling can remove configuration and stored data permanently. Before removal, back up files, database, settings, and relevant operational data. Review active orders, reports, feeds, subscriptions, callbacks, and staff procedures that may depend on the extension. Disable it first, verify that the store still works, and uninstall only after confirming that it is no longer needed. Remove unused credentials and confirm that no customer-facing option or event registration remains.

Updates and lifecycle maintenance

Read the release notes, changelog, compatibility statement, migration instructions, and known issues.
Back up files, database, extension settings, and current package versions.
Test the update in a non-production environment where possible.
Apply the supported update procedure, including required database migrations.
Refresh caches and modification layers if the platform requires them.
Verify storefront pages, checkout, order totals, payment callbacks, shipping rates, reports, feeds, and analytics events affected by the extension.
Keep a rollback path until validation is complete. A rollback restores the previous working version or backup after an unsuccessful change.

Use the platform's supported update and uninstall procedures rather than deleting extension files manually. Review the configuration area for related store, cache, or system settings before and after maintenance.

Troubleshooting extension issues

Use a controlled, repeatable process. First reproduce the problem and record the exact page, store, customer group, cart, address, time, and recent change. Then inspect settings and permissions, review application and server logs, verify dependencies and credentials, clear relevant caches, test for conflicts, and restore or roll back if necessary.

Symptom	Likely causes	Checks to perform	Typical resolution
Installed extension is not listed or cannot be opened.	Incomplete installation, incompatible version, missing dependency, or missing permissions.	Confirm installation completion; check compatibility and dependencies; verify access and modify permission; inspect logs.	Complete the supported installation, resolve requirements, or update the administrator role.
Enabled module is not visible on the storefront.	Wrong layout, page, position, store, customer context, status, date restriction, or theme conflict.	Check assignments, content rules, sort order, cache, exact route, and theme layout.	Correct placement or rules, refresh caches, and test desktop and mobile views.
Payment or shipping option does not appear.	Disabled status, zone, currency, cart total, tax, weight, customer group, invalid credentials, or provider outage.	Test with a matching address and cart; validate credentials and service status; inspect checkout logs.	Correct eligibility rules or credentials and retest the complete checkout.
Settings cannot be saved.	Missing modify permission, invalid required field, malformed credential, validation error, database error, or unsupported version.	Check user-group permissions, field formats, logs, database errors, and compatibility.	Grant required modify permission, correct values, or install a compatible release.
Recent change causes errors or slow pages.	Extension conflict, stale cache, unrefreshed modification, incompatible update, remote timeout, or inefficient query.	Disable the changed extension; compare with a working state; inspect logs and performance; refresh caches and modifications.	Resolve the conflict, configure timeouts, update, or roll back from a verified backup.
Duplicate output or duplicate processing appears.	Extension assigned twice, overlapping modules, repeated event registration, or theme and extension both providing the feature.	Inspect layouts, positions, sort order, event registrations, and theme templates.	Remove the duplicate assignment or disable the overlapping implementation.
API request fails.	Wrong endpoint, expired key, wrong environment, blocked outbound request, invalid signature, or provider outage.	Check endpoint, sandbox or production mode, credentials, timestamps, logs, and provider status.	Correct the environment or credentials and retest without exposing secrets.

When contacting a vendor, preserve the exact error message, timestamp, platform and extension versions, reproduction steps, affected route, and relevant log lines. Remove API keys, passwords, tokens, personal information, payment data, and other secrets before sharing screenshots or logs.

Extension lifecycle checklist

Evaluate compatibility, security, privacy, performance, support, licensing, and conflicts.
Back up files, database, settings, and relevant operational data.
Install through the supported marketplace or package workflow.
Resolve dependencies and refresh modifications or caches when required.
Configure scope, credentials, eligibility, layout, priority, tax, and order-status behavior.
Test in sandbox or staging before exposing the extension to customers.
Enable and monitor logs, checkout, storefront behavior, and external integrations.
Maintain with release-note review, backups, updates, post-update verification, and a rollback plan.
Disable before uninstalling when investigating or retiring a feature, then review data and customer-facing effects.