When managing multi-site WordPress environments, keeping track of resource limits requires regular verification during routine maintenance intervals. Multi-site administrators frequently need to confirm whether mid-term resource additions share the exact expiration timeline as the master annual license before allocating more product slots across different sub-domains. Without a clear audit checklist, operators risk misinterpreting how resource volume and contractual durations interact.
Each quantity added via the Oltora Price Monitor – Additional Product Capacity module expands your tracking ceiling by 1,000 competitor items on a designated installation, but this upgrade increases product capacity only. It does not renew or extend your annual license. Understanding this architectural separation prevents planning errors during budget reconciliation and ensures that multi-site networks maintain accurate monitoring boundaries.
Post-Launch Audit Steps for Network Administrators
Conducting a structured audit of your tracking infrastructure prevents unexpected monitoring gaps when catalogs expand. Reviewing active installations involves a systematic inspection of dashboard assignments rather than broad account-level assumptions. Network supervisors should execute these specific verification steps during routine reviews:
- Verify Site-Specific Limits: Confirm that the active product ceiling matches the assigned quantity for each individual domain installation rather than assuming a uniform network-wide cap.
- Check Expiration Alignment: Cross-reference the add-on activation date against the primary annual subscription expiry to confirm that extra room terminates concurrently with the master license.
- Audit Multi-Site Distribution: Verify that high-volume product categories are mapped to the correct domain installation, ensuring busier sites receive necessary increments while smaller sites retain baseline limits.
Managing Uneven Capacities Across Multisite Networks
Multi-site licenses allow different WordPress installations to operate with distinct product limits under a single master agreement. For instance, a primary retail domain might require a 5,000-product ceiling, while secondary informational or regional storefronts operate comfortably on the default 1,000-product baseline. When scaling these environments, administrators must ensure that capacity add-ons are explicitly targeted to the correct WordPress directory from the dashboard.
Because additional capacity remains active only until the expiration date of the current annual license, any mid-term purchase will co-terminate with the primary subscription. When the annual license expires, features and additional capacity become unavailable until a new annual license is activated. Establishing a regular audit schedule ensures your team catches expiration milestones early and reallocates resources without administrative friction.

