Author: Kiwi Commerce

Managing a Magento 2 store involves far more than uploading products and fulfilling orders. With multiple admin users, developers, and third-party extensions all accessing the backend, it’s crucial to have full visibility over every change made.

That’s where the Kiwi Commerce Admin Activity Log makes a real difference.

This powerful, performance-friendly extension gives Magento 2 store owners complete oversight of admin activity — improving accountability, enhancing security, and making it easier to troubleshoot issues, all from an intuitive interface.

Full Visibility Into Admin Actions

The Admin Activity Log records nearly every action taken in the Magento backend.

Whether someone updates a product, edits a CMS page, changes a store setting, or modifies customer information, the log captures:

• The specific action taken
  
• The user responsible
  
• The time and date
  
• Before-and-after values, where applicable
  

For example, if a product price is unexpectedly altered, you’ll know exactly who made the change and what was changed. This level of visibility is vital when investigating configuration errors or unintended changes.

Boost Security and Accountability

When multiple people have access to your Magento admin panel, the chances of mistakes, oversights, or unauthorised changes increase.

The Admin Activity Log helps you:

• Improve accountability by linking actions to specific users
  
• Detect unwanted or accidental changes quickly
  
• Maintain a complete audit trail for compliance and peace of mind

This is especially important for enterprise-level or B2B Magento stores that handle sensitive data or operate under strict regulatory standards.

Streamline Debugging and Development

Debugging Magento issues without knowing what changed — and when — can waste valuable time.

The Admin Activity Log provides immediate insight into recent backend actions, allowing store owners and developers to:

• Quickly identify what may have caused an issue
  
• Filter logs by user, action, entity, or date
  
• Reduce time spent troubleshooting by pinpointing root causes faster

Whether you’re managing extension updates, adjusting configurations, or launching new features, having this visibility is a major asset.

Lightweight and Easy to Use

Many Magento extensions can be heavy or complex, but the Kiwi Commerce Admin Activity Log is:

• Simple to install and configure
  
• Lightweight, running efficiently in the background
  
• Designed with usability and performance in mind
  

You can also customise the retention period for logs and export records for reporting or audit purposes.

Built for Agencies, Teams, and Growing Businesses

This extension is ideal for any Magento store with a collaborative backend environment. It’s particularly valuable for:

• Magento stores with multiple admin users
  
• Agencies managing stores on behalf of clients
  
• Merchants making frequent catalogue or content updates
  
• Businesses dealing with sensitive pricing or customer data
  
• B2B or enterprise-level operations requiring detailed audit logs
  

Final Thoughts

If you’re serious about managing your Magento 2 store with confidence and control, the Kiwi Commerce Admin Activity Log is a must-have.

It delivers clarity, accountability, and peace of mind — without adding unnecessary complexity or affecting performance. Whether you’re running a solo store or managing a multi-user team, this extension gives you the tools to stay on top of everything happening in the admin panel.

In a platform as powerful as Magento, understanding what’s happening behind the scenes isn’t just helpful — it’s essential.

Ready to take control of your admin panel?
Visit the Kiwi Commerce website to learn more or download the Admin Activity Log extension today.

Handling a large product catalogue in Magento 2 can be a real headache. While Magento is powerful and highly adaptable, managing tens—or even hundreds or thousands of products often causes slowdowns, mainly due to the way indexing is handled. If your admin panel feels sluggish, changes don’t appear quickly on the frontend, or site search isn’t working as expected, poor indexing could be the culprit.

In this article, we’ll explain what indexing in Magento 2 actually does, why it’s critical for large catalogues, and how you can customise and optimise it for peak performance—without diving too deep into the technical weeds.

What Is Indexing in Magento 2?

Indexing is Magento’s method of reformatting core data (like product details, pricing, and category assignments) into a structure that loads quickly on your website. Each time you update a product—whether it’s a price change or a new category assignment—Magento must reindex that data to ensure it displays correctly on the frontend.

Magento 2 comes with a set of default indexers, including:

• Product Prices
• Category Products
• Product Attributes
• Stock Levels
• Catalogue Search
• …and several others.

Why Indexing Becomes a Challenge for Large Stores

For small stores, reindexing happens in seconds. But when you’re working with 50,000+ products, the process can take several minutes—or even longer. This leads to:

• Slow product saving actions
• Outdated content on the frontend
• Cron jobs failing or stalling
• Admin users facing timeouts

In most cases, indexing is the performance bottleneck.

How to Optimise Magento 2 Indexing for Large Catalogues

Here are several effective ways to improve indexing efficiency and overall site performance:

1. Switch to “Update by Schedule” Mode

Always configure your indexers to “Update by Schedule” rather than “Update on Save”. The latter forces a full reindex every time you make changes—something that can cripple performance on a large catalogue.

Run the following CLI commands to check and set the indexer modes:

php bin/magento indexer:show-mode  

php bin/magento indexer:set-mode schedule

Also, confirm that your cron jobs are set up properly, as scheduled reindexing relies on them.

2. Enable Partial Reindexing

Magento supports partial indexing—only updating items that have changed. This drastically reduces indexing time, especially when adjusting prices or stock for a subset of products.

Check whether any custom modules or third-party extensions are triggering full reindexes unnecessarily. Where needed, develop custom indexers that respond to specific events and process only relevant data.

3. Create a Dedicated Cron Group for Indexing

On high-traffic stores, the default cron setup can become overloaded. Isolate indexing tasks into their own cron group to prevent conflicts with newsletters, sitemap generation, and other scheduled jobs.

Add a new group in crontab.xml:

<group id=”index”>

    <schedule>*/5 * * * *</schedule>

    <job name=”indexer_reindex_all_invalid”

         instance=”Magento\Indexer\Cron\ReindexAllInvalid”

         method=”execute”/>

</group>

Then update your server’s crontab to run this group separately.

4. Tune MySQL for Indexing

Since indexing is heavily database-driven, optimising your MySQL configuration can have a significant impact. Key adjustments include:

• Increasing innodb_buffer_pool_size
• Enabling slow query logging
• Regularly optimising large tables (e.g. catalog_product_index_price)

It’s worth collaborating with your hosting provider or DevOps team for this.

5. Use Asynchronous Indexing (Where Applicable)

If you’re running a large-scale or enterprise-level Magento installation, implementing asynchronous indexing via Magento’s Message Queue (e.g. RabbitMQ) is a smart move. It decouples indexing from real-time frontend and admin operations, improving overall site speed and admin responsiveness.

Creating Custom Indexers

Got a bespoke feature—like vendor-based pricing or a complex shipping matrix—that needs regular updates? Building a custom indexer can keep your core indexers lightweight and efficient.

Magento provides a framework interface for this:
\Magento\Framework\Indexer\ActionInterface

Make sure your custom indexer is optimised for incremental reindexing to handle large datasets with ease.

Final Thought

Indexing is often a hidden bottleneck in Magento 2 performance, particularly for stores with large or complex product catalogues. By scheduling indexers, enabling partial updates, separating cron processes, and considering advanced techniques like custom or asynchronous indexing, you can significantly reduce delays and improve backend responsiveness.

At Kiwi Commerce, we’ve helped many merchants unlock the full potential of their Magento 2 setup by tackling indexing issues head-on. If your store is struggling with performance, start with indexing—you might be surprised just how much of a difference it makes.

Need help scaling your Magento store? Get in touch with Kiwi Commerce for expert Magento performance solutions.

 

“Why dig through the backend when you can make changes directly from the storefront?”

Welcome to a new era of real-time product editing. At Kiwi Commerce, we’re proud to introduce the Frontend Product Editor for Magento 2 — an extension built for merchants, marketers, and developers who value speed, simplicity, and seamless workflows.

Whether you’re correcting a typo, adjusting pricing during a flash sale, or rewriting product content on the fly, this extension enables direct editing on the product page itself — no need to enter the Magento admin panel.

What Does It Do?

The Frontend Product Editor allows you to:

• Edit product name, price, description, and short description directly on the frontend
  
• Toggle between global and store-view scope when saving updates
  
• Use a native Magento-styled modal with AJAX-based submission
  
• Access Magento’s built-in WYSIWYG editor for rich text formatting
  
• Make product updates without navigating the admin panel
  

Why Use It?

1. Save Time and Streamline Your Workflow

Editing in the Magento backend can be time-consuming. With this extension, product updates happen where you see them — on the live product page. No grid navigation, no loading delays, no wasted clicks.

2. Built the Magento Way

This isn’t a workaround — it’s built using Magento’s best development practices:

• Implements ProductRepositoryInterface
  
• Fully respects store scope and attribute overrides
  
• Loads TinyMCE via Magento’s backend configuration
  
• Uses clean, secure fetch() with JSON for AJAX calls
  
• Avoids third-party CDNs or external libraries
  

3. Perfect for Merchants, Editors and Store Managers

Designed for usability and speed, this extension is ideal for teams who manage catalogue content regularly.

Once logged in, users will see an Edit Product Info button directly on the product page. Clicking it opens a clean, intuitive modal that allows you to update:

• Product Name
  
• Price
  
• Short Description
  
• Full Description (with rich text support)
  
• Meta Title and Meta Description
  
• Any additional editable product attributes
  

No more hunting for SKUs or loading heavy admin grids. Updates are saved via AJAX and appear instantly — reducing effort and improving accuracy.

Access Control & Future-Proofing

• Limit editing to authorised users via session or Magento ACL
  
• Ready for future features such as:
  
  • Inline content editing
    
  • Role-based field permissions
    
  • Bulk editing capabilities
    

Store Scope Toggle: Full Control Over Product Data

A dropdown at the top of the modal allows users to choose:

• This Store View Only – apply changes to the current store view
  
• All Store Views (Global) – update globally and clear any local overrides
  

Behind the scenes, our logic ensures that Magento’s multi-store setup is properly respected. For example:

if ($storeId === 0) {

    foreach ($this->storeManager->getStores() as $store) {

        $storeScopedProduct = $this->productRepository->getById($productId, false, $store->getId());

        $storeScopedProduct->setData($field, null); // Clear override

        $this->productRepository->save($storeScopedProduct);

    }

}

Key Benefits

• Real-time editing without needing admin panel access
  
• Faster updates during sales or product launches
  
• Rich content editing with Magento’s WYSIWYG support
  
• Full compliance with Magento’s store view and global scope logic
  
• An intuitive, efficient experience for merchants and content teams
  

Coming Soon

We’re continuing to improve the extension with the following planned features:

• Attribute whitelisting via admin configuration
  
• Revision history with rollback functionality
  
• Inline editing with contenteditable
  
• Field-level permissions managed via ACL
  
• Bulk updates directly from category grids
  

Final Thoughts

If you’re managing catalogues, building stores for clients, or simply tired of Magento’s admin overhead, the Frontend Product Editor is the productivity tool you’ve been waiting for.

It brings Magento’s powerful editing capabilities to the storefront — in a fast, secure, and user-friendly way.

Interested in trying it?

Contact the Kiwi Commerce team or explore our Magento 2 extensions to learn more.

Looking to elevate your Adobe Commerce (Magento 2) site? Adobe Optimizer, powered by Adobe Target, brings intelligent A/B testing, multivariate experimentation, and AI-driven personalisation directly into your Magento setup. With a seamless integration, it helps deliver customised content, improve conversion rates, and test user experiences—without interrupting daily operations.

Key Features at a Glance

• A/B and A/B/n Testing: Run side-by-side comparisons of different page versions.
  
• Automated Personalisation: Deliver targeted, AI-backed experiences to users.
  
• Visual Experience Composer (VEC): Visually edit and test page elements.
  
• Server-Side Delivery: Eliminate flickering during tests with backend rendering.
  
• Magento Data Layer Integration: Use cart, checkout, and customer data to power relevant advertising and targeting.
  

What You Need Before You Begin

Adobe Experience Cloud Requirements:

• A valid Adobe Experience Cloud account
  
• Access to Adobe Launch (Tag Manager)
  
• Adobe Optimizer workspace credentials and API access
  

Magento 2 Setup:

• Adobe Commerce version 2.4.x
  
• Admin and CLI access for installation and configuration
  
• Theme file access to embed tracking and testing scripts
  

How Adobe Optimizer Works

Adobe Optimizer blends client-side and server-side technologies:

• Client-Side with AT.js: For DOM updates and faster rollout
  
• Server-Side SDKs (Node.js/PHP): For high performance and flicker-free delivery
  
• Edge Network: Fast, global decision-making via Adobe’s CDN
  

Installation & Configuration Steps

Step 1: Install the Extension

composer require magento/target-rule

bin/magento module:enable Magento_TargetRule

bin/magento setup:upgrade

Step 2: Add Your Credentials

Update the config with your Adobe details:

{

  “client_code”: “your_adobe_client_code”,

  “organization_id”: “IMS_ORG_ID”,

  “workspace”: “default”,

  “server_side”: true

}

Step 3: Inject Adobe Target SDK into Your Theme

In requirejs-config.js, add:

var config = {

  paths: {

    ‘adobe-target’: ‘https://assets.adobedtm.com/activation’

  },

  shim: {

    ‘adobe-target’: { ‘exports’: ‘adobeData’ }

  }

};

A/B Testing in Practice: A Simple Example

Scenario: Test Checkout Button Colour

Step 1: Set up two experiences in Adobe Target (e.g., green vs. blue button).

Step 2: Embed the logic in Magento’s cart template:

<div id=”checkout-button”>

  <?php if ($this->helper(‘Magento\TargetRule\Helper\Data’)->isEnabled()): ?>

    <div class=”target-experience” data-id=”checkout-btn-test”>

      <button class=”btn-default”>Proceed to Checkout</button>

    </div>

  <?php endif; ?>

</div>

Step 3: Apply the offer using Adobe Target:

require([‘adobe-target’], function() {

  adobe.target.getOffer({

    mbox: “checkout-btn-test”,

    params: { “pageType”: “cart” },

    success: function(response) {

      document.querySelector(‘.target-experience’).innerHTML = response;

    }

  });

});

Advanced: Server-Side Rendering Example

Use a plugin to modify content blocks dynamically:

class RenderTargetContent

{

  public function afterToHtml(\Magento\Checkout\Block\Cart $subject, $result)

  {

    $targetContent = $this->targetService->applyContent(‘checkout-btn-test’);

    return str_replace(‘btn-default’, $targetContent, $result);

  }

}

Tracking Events & Measuring Success

Track Conversions:

document.querySelector(‘#checkout-button’).addEventListener(‘click’, function() {

  adobe.target.trackEvent({ mbox: ‘checkout-click’, conversion: true });

});

Monitor Results in Adobe Target Dashboard

Best Practice Tips

• Prevent Flicker: Use server-side rendering or pre-hiding techniques.
  
• Use Contextual Data: Include SKUs, customer group, and basket value in offer requests.
  
• Cache Management: Exclude dynamic test content from full-page cache.
  
• Testing & Debugging: Use AT.js Debugger Chrome extension.
  

Success Metrics to Watch

Metric	Starting Point	Target	Tool
Personalisation ROI	0.1	5:1	Adobe Analytics
Time-to-Decision	300ms	<50ms	Chrome DevTools
Offer Cache Hit Rate	0%	>85%	Target Reports
Test Velocity	2/month	10/week	Activity Log
Lift Significance	N/A	>95%	Stats Engine

Troubleshooting Tips

• Offers Not Appearing?
  
  • Double-check IMS credentials.
    
  • Inspect the console for AT.js errors.
    
• Missing Data Layer?
  
  • Ensure Magento\TargetRule\Block\Data is loaded in your layout.
    

Final Thoughts

Adobe Optimizer adds serious testing and personalisation muscle to Magento 2. Whether you’re running basic A/B tests or scaling up to full AI-powered experiences, it offers flexibility without compromising performance. Start small, measure often, and evolve your UX based on data—not guesswork.

Perfect for  businesses looking to increase engagement, conversions, and customer satisfaction across their eCommerce experience.