How to split price monitoring capacity across WordPress sites

When one site needs a heavier watchlist

A growing competitor list does not always mean every WordPress installation needs the same amount of monitoring. In practice, that is where setup decisions start to matter. One store may need a larger watchlist because its category is crowded, while another site under the same license may only need the default 1,000 monitored products. If you treat all sites the same, you can end up paying for capacity where it is not needed and leaving the busiest installation short.

Oltora Price Monitor includes 1,000 monitored products per licensed WordPress website by default. The capacity upgrade is designed for a specific installation, so the practical question becomes how to divide monitoring room across sites, not how to change the whole account at once.

You can review the product here: Oltora Price Monitor – Additional Product Capacity.

Why uneven capacity planning matters

Under a multi-website license, each activated WordPress site can have a different product limit. That flexibility is useful only if you use it deliberately. A store with 5,000 competitors to track does not benefit from borrowing unused attention from a quieter site if the larger site still runs into the default cap.

The cost of ignoring that imbalance is simple: the site with the most pressure becomes the one with the least room to work. Monitoring gaps do not always show up as a dramatic failure. More often, they appear as partial coverage, awkward workarounds, or the need to decide which products matter most instead of tracking the full set you intended to watch.

How the capacity upgrade is applied

The add-on is sold in 1,000-product increments. Each quantity adds 1,000 additional monitored products to the selected WordPress installation. That keeps the decision concrete.

• Quantity 1 adds 1,000 monitored products
• Quantity 2 adds 2,000 monitored products
• Quantity 3 adds 3,000 monitored products
• Quantity 5 adds 5,000 monitored products

If a site starts with the default 1,000 and you add quantity 2, the new total becomes 3,000 monitored products on that one installation. Another website under the same license can still keep its own separate limit.

That separation is the point. Capacity follows the selected WordPress website, not the entire license in a single block.

Choosing different limits for different sites

For teams managing more than one store, the smartest setup is often uneven. A higher-volume catalog can receive more room, while a smaller site stays at the default. That keeps the monitored-product budget aligned with actual workload.

For example, one license could be arranged so Website A has 5,000 monitored products, Website B has 1,000, and Website C has 3,000. None of those sites needs to match the others. The only thing that matters is whether each installation has enough room for the competitor set it actually has to track.

This is easier to manage when the monitoring plan follows the site’s role. A flagship store with a broad market may deserve more capacity than a smaller regional site. A newer store may stay at the default until its competitor list justifies a larger limit. That kind of allocation avoids overbuying on quiet properties and under-supporting the site that most needs coverage.

What this upgrade does not change

The capacity add-on only increases monitored-product room. It does not renew or extend your annual Oltora Price Monitor license. The added capacity remains active until the expiration date of the current annual license, and when that license expires, the plugin features and the extra capacity become unavailable until a new annual license is activated.

That detail matters when you are planning across multiple websites. Extra capacity is useful, but it is still tied to the active license term. If you are assigning larger limits to one installation, you should do so with the license timeline in mind rather than assuming the add-on changes the renewal date.

The practical way to decide

If your sites do not all need the same level of competitor monitoring, start with the installation that has the highest pressure. Give that site enough capacity first, then leave the quieter sites at lower levels unless their catalog sizes justify more.

That approach keeps the setup tidy. The crowded store gets the room it needs, the lighter sites do not carry unused overhead, and the capacity stays matched to the work each WordPress installation actually does.

For teams already using Oltora Price Monitor, that is the real value of the upgrade: not a bigger number in isolation, but a cleaner way to allocate monitoring space where it is needed most.