When one site can outgrow the rest

When one WordPress site starts doing the heavy lifting

A growing competitor watchlist does not always spread itself evenly across every site in a license. In many setups, one WordPress installation becomes the main place where price monitoring happens, while the others stay comparatively light. That is when capacity planning gets more specific. The question is no longer only how much extra room you need. It is whether the site doing the real work has enough monitored-product capacity to stay useful for the rest of the current annual term.

Oltora Price Monitor includes 1,000 monitored products per licensed WordPress website by default. If one installation has moved beyond that, the natural next step is a capacity increase on that site, not a change to the whole setup. You can review the add-on here: Oltora Price Monitor – Additional Product Capacity.

Why a mature monitoring setup needs site-level decisions

In a first setup, it is easy to think in simple totals. Later, the structure becomes less even. One store may carry the category with the most competitors, the busiest pricing checks, or the most frequent updates. Another activated site may only need the base allowance. Once that happens, treating all websites the same can leave the most important one short on room.

The product-capacity upgrade is built for that reality. Each quantity adds 1,000 additional monitored products to the selected WordPress website. That means the decision is not abstract. It is site-specific.

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

If the site that handles the heavier workload is already near its limit, the math is straightforward. A site with 1,000 monitored products that receives quantity 2 will move to 3,000 monitored products. That kind of step matters when the monitoring process is part of day-to-day catalog work, not a one-off task.

The real decision is coverage plus timing

When a setup grows, capacity and license timing stop feeling like separate admin details. They become part of the same planning decision. The add-on raises the number of competitor products one installation can monitor, but it does not renew or extend the annual license. The extra capacity remains active only until the expiration date of the current Oltora Price Monitor license.

That distinction matters most when the site doing the heavy lifting is also the one you expect to rely on for the rest of the term. If the annual license is close to ending, the purchase still increases capacity now, but only within that current window. If the term has a lot of time left, the same upgrade can make the monitoring setup more comfortable without changing the base license structure.

This is where mature systems differ from early-stage ones. At the beginning, you are trying to get monitoring running. Later, you are trying to keep the right site well supplied while avoiding unnecessary changes elsewhere.

How to think through the upgrade on one busy site

A useful way to approach the decision is to look at the site that is already carrying the pressure and ask three plain questions:

• Is this the installation that actually needs more monitored-product room?
• How many additional products would bring it back to a workable level?
• Does the current annual license term still cover the period when the extra capacity is needed?

Those questions keep the decision grounded in the real setup instead of in a vague sense that the account has grown. If the answer to the first question is yes, the capacity add-on belongs on that installation. If the answer to the third question is no, the timing deserves a closer look before you buy.

That is especially useful when different websites in the same license have different jobs. A quieter site does not need to borrow capacity from the busiest one. The stronger choice is usually to let each installation reflect its actual workload.

What the maximum tells you about growth

Oltora Price Monitor capacity can currently be increased up to 10,000 monitored products per WordPress installation. That ceiling is useful because it gives a clear outer limit for planning. If one site is growing fast, you can map the next steps in 1,000-product increments instead of guessing how far the setup can go.

That makes the upgrade practical for stores that are not static. A catalog can grow, competitor coverage can widen, and one installation can become the center of the monitoring workflow. When that happens, the most helpful move is often to expand the site that already handles the work, then keep the rest of the license structure intact.

The result is a cleaner operating model: one site can carry the heavier monitoring load, other sites can keep their own limits, and the annual license still defines how long the added room stays available.

When this add-on fits best

This upgrade fits best when the problem is specific and local:

• one WordPress installation has outgrown the default 1,000-product limit;
• the team wants to add monitored-product room in clear increments;
• the extra capacity needs to stay tied to a single site rather than spread across every installation;
• the current annual license still has value for the period ahead.

That is a different decision from renewing a license, and it should stay separate from it. If your price-monitoring workflow has become more mature, the right question is often not whether the tool still works. It is whether one site now deserves more room than the rest.

For the product details, visit Oltora Price Monitor – Additional Product Capacity.