HALO Maximizer v1.3.0: The Biggest Update Yet

What's New in v1.3.0

Version 1.3.0 is the most significant update to HALO Maximizer since launch. This release touches nearly every part of the extension — from the core scan engine and API layer to the storefront bar UI and security model. Whether you run scans manually or let Auto-Pilot handle everything, you will notice faster performance, smarter filtering, and a more polished experience across the board.

Here is a breakdown of everything that changed and why it matters.

Performance Overhaul — 97% Fewer API Calls

The headline number is real: HALO now makes up to 97% fewer redundant API calls during scans. This was achieved through a combination of architectural changes that work together to eliminate wasted requests.

Dedup caching prevents the same campaign data from being fetched multiple times within a scan session. If HALO has already seen a campaign for a given ASIN, it skips the duplicate request entirely. This alone cuts a significant portion of unnecessary traffic.

Adaptive heartbeat replaces the old fixed-interval polling with a smarter approach that adjusts its frequency based on actual activity. When there is nothing new to report, HALO backs off. When campaigns are actively being discovered, it stays responsive.

Parallel multi-store collection means that if you have multiple Amazon store IDs, HALO now gathers sold-product data from all of them concurrently instead of sequentially. This dramatically reduces the wall-clock time for the initial data collection phase.

Quick Collect is a new lightweight data-gathering mode that grabs just the essentials needed for a scan without pulling full product details. For users with large catalogs, this translates to noticeably faster scan starts.

Progressive rate limiting replaces the old all-or-nothing throttle. Instead of hard-blocking when rate limits are approached, HALO gracefully slows down, keeping scans moving forward at a sustainable pace rather than stopping and retrying.

Event-driven waits replace fixed sleep timers throughout the scan pipeline. Instead of waiting a fixed number of seconds "just in case," HALO now listens for the actual completion signals from Amazon's API, moving to the next step the moment data is ready.

Pre-warmed auth cache ensures that authentication tokens are ready before a scan begins. Previously, the first API call of a scan might take longer because it had to authenticate on the fly. Now, HALO refreshes its auth state proactively so the first request is just as fast as the hundredth.

ASIN-Level Filtering

Previous versions of HALO checked for better deals at the brand level — if you had an active campaign for any product from a brand, HALO would skip other campaigns from that same brand. This was too aggressive. You could miss a higher-commission campaign for a different product just because another product from the same brand was already enrolled.

v1.3.0 switches to per-ASIN filtering. HALO now evaluates each product individually, so accepting a campaign for one product from a brand does not prevent you from finding a better deal on a completely different product from the same brand. This is a subtle but meaningful change that surfaces more high-value matches.

Duplicate detection has also been improved. The scan engine now catches more edge cases where the same campaign could appear under slightly different identifiers, preventing duplicate entries in your results.

Free Tier Daily Scan Limit

The free tier includes 1 scan per day.

After that daily scan is used, additional scans are unavailable until the next reset window. Users who need more than one scan per day can upgrade for higher limits and full-speed access.

Storefront Bar Improvements

The storefront bar — the overlay that appears on your Amazon storefront page during and after scans — received a major upgrade in this release.

Full results panel replaces the compact summary. You can now see all matched campaigns directly in the storefront bar without opening the popup. Each campaign shows its commission rate, time remaining, and match status. The panel scrolls independently so it works even with a large number of results.

ASIN pills appear inline for each matched campaign, giving you a quick visual reference for which products are involved. Clicking an ASIN pill copies it to your clipboard for easy reference.

Activity log provides a real-time feed of what HALO is doing during a scan. You can see each step as it happens — data collection, campaign matching, scoring, and acceptance — directly in the storefront bar. This replaces the old approach of showing only a spinner with a generic status message.

Auto-accept toggle lets you control whether HALO automatically accepts matched campaigns or just shows them for your review. This toggle is accessible directly from the storefront bar, so you can switch modes without opening the popup or navigating to settings.

4-way theme system replaces the old light/dark toggle. The storefront bar now supports four themes — light, dark, system (follows your OS preference), and transparent. The transparent theme blends the bar into the storefront page background, which some users prefer for a less intrusive look.

Dynamic version display shows the current extension version directly in the storefront bar footer, so you can always confirm which version is running without checking the Chrome extensions page.

Scheduler and Auto-Pilot

Auto-Pilot's scheduler now handles Chrome service worker restarts gracefully. Chrome's Manifest V3 architecture suspends service workers after a period of inactivity, which could previously cause Auto-Pilot to miss scheduled scans. v1.3.0 detects when the service worker restarts and immediately checks whether any scheduled runs were missed, running them right away if needed.

The midnight reset logic has been aligned to EST (Eastern Standard Time), matching Amazon's reporting day boundary. This ensures that daily scan counters, earnings totals, and scheduling intervals all roll over at the same time Amazon's data resets, eliminating edge cases where scans near midnight could produce inconsistent results.

Earnings and Display Fixes

Commission percentage display has been corrected. In previous versions, some campaigns showed the wrong commission rate in the results — the underlying data was correct, but the display formatting had a rounding issue that could make a 10% commission appear as 1% in certain edge cases. This has been fixed across the popup, storefront bar, and notification displays.

The day boundary for earnings tracking now properly aligns to 5 AM EST, matching when Amazon's reporting data rolls over. Previously, HALO used midnight local time, which could cause earnings from late-night purchases to be counted on the wrong day.

The 7-day rolling earnings calculation has been corrected to use a true 7-day window rather than a calendar-week boundary. This means your "last 7 days" earnings figure is always accurate regardless of what day of the week it is.

Security Hardening

v1.3.0 includes several security improvements that make the extension more resilient and privacy-conscious.

Message sender validation ensures that the extension only processes messages from known, trusted origins. Previously, any content script or injected script could send messages to the extension's background service worker. Now, incoming messages are validated against a whitelist of expected senders before being processed.

Filtered headers strip sensitive information from outgoing requests. Internal tokens, session identifiers, and other headers that are only needed for Amazon's authentication are no longer forwarded to HALO's own backend API calls. This reduces the data surface and follows the principle of least privilege.

Gated debug output ensures that console logging is suppressed in production builds. Debug-level logs that were previously visible in the browser console (and could expose internal state to anyone with DevTools open) are now gated behind a build flag. Only error-level messages are logged in production.

Minimum Chrome version enforcement ensures that the extension only runs on Chrome versions that support the security APIs it depends on. If a user's Chrome version is too old, the extension will display a clear upgrade prompt rather than running with degraded security.

Developer and Build Improvements

A new production build script standardizes how release builds are created. This ensures that debug code is stripped, version numbers are updated, and all assets are optimized before a release is packaged for the Chrome Web Store.

Module unification consolidates several previously separate utility files into cohesive modules. This does not change any user-facing behavior, but it reduces the extension's file count and makes the codebase easier to maintain going forward.

How to Get the Update

v1.3.0 is now live on the Chrome Web Store. The update rolls out automatically to all existing users — you do not need to reinstall the extension. Chrome handles updates in the background.

To confirm you are on the latest version, open the HALO popup and look for the version number in the footer, or check chrome://extensions and find HALO Maximizer in the list.

What's Next

We are already working on the next set of improvements. Expect continued performance optimizations, expanded storefront bar functionality, and new ways to discover and manage Creator Connections campaigns. Follow us on YouTube, Facebook, and X for the latest updates.