Skip to content
StockControls
REQUIREMENTS & LIMITS

A good fit starts
with a clear check.

Separate what the plugins require from what has actually been tested. Then verify your own products and integrations on staging.

On smaller screens, scroll the table to see all columns.

RequirementFree 1.1.27Pro 1.1.25
WordPress6.5+6.6+
PHP7.4+8.1+
WooCommerce9.1+9.1+
StockControls FreeThis packageMinimum Free 1.1.23 / API2; current demo checked with Free 1.1.27
Product storageStandard WooCommerce product storeSame
DatabaseMySQL/MariaDB named locks and InnoDB tablesSame

Install Free first, then the matching Pro add-on. Network-wide activation and custom product data stores are unsupported.

PRACTICAL BOUNDARIES

Choose the right path for the work.

CSV imports

The mapped path accepts 200 rows / 1 MB, with up to 25 rows applied per click. The separate resumable Large CSV imports path supports 10,000 rows / 10 MB with exact template headers.

CSV guide

Catalog planning

Pro live priority views cover up to 2,000 matching stock owners. Saved complete plans support up to 50,000 owners, subject to time, memory, storage and complete-coverage checks.

Planning guide

Purchasing & counts

One supplier and up to 50 product lines per purchase order. The Pro stocktake selection screen starts a count with up to 25 products from the current page. Reconciliation and receipts use reviewed, bounded work with saved results.

Stocktake guide

Sales refresh

A sales refresh scans up to 50,000 orders in its chosen window. Shorter windows may be needed. A failed or capped run retains the previous complete snapshot.

Replenishment guide

Stock precision and storage

Decimals work only when your WooCommerce configuration preserves the requested precision, up to six decimal places. Standard whole-unit setups reject unsupported fractional inputs. Replenishment suggestions round up to whole units; alternative supplier terms can carry precise quantities when the store supports them.

Stock, audit and purchasing tables need InnoDB and MySQL/MariaDB named-lock support. Unsupported storage cannot accept StockControls stock changes. Your hosting provider can confirm these capabilities.

What this product does not cover

Warehouse quantity allocation, cross-store synchronization, camera scanning, barcode-label generation, supplier email/API ordering and accounting integrations are not included. A keyboard scanner can enter an exact SKU; saving scanned count progress requires Pro. Unknown stock is labelled unavailable instead of assumed to be zero. Correct its inventory record before relying on a suggestion.

QUALIFICATION, WITH ITS SCOPE

Tested behavior.
Honest boundaries.

The preceding matched 1.1.23 runtime received selected native checks on the current and minimum environments below. Earlier 1.1.20 coverage remains separately labelled. Requirements are not a claim that every host, theme or extension combination has been tested.

Still test with your own setup

Test your hosting and database configuration, other stock/POS/import extensions, product types, persistent-cache rules, theme, permissions and usual checkout flow. Network-wide activation and arbitrary custom product stores are unsupported. Two-site integration checks are not full multisite certification.

Keep a backup. Install Free first, then matching Pro without uninstalling, and verify a known stock workflow. Rebuild earlier saved replenishment plans after 1.1.20; source records, stocktakes and orders remain.

Selected 1.1.23 runtime checks

Current: WordPress 7.1.4, WooCommerce 11.2.1 and PHP 8.5.4. Minimum Free: WordPress 6.5, WooCommerce 9.1.0 and PHP 7.4.3. Minimum Pro: WordPress 6.6, WooCommerce 9.1.0 and PHP 8.1.34.

Selected Free and Pro workflow checks passed on both environments, with controlled fictional licensing responses. The new workspace, Help & guides, More Plugins and Free preview preference also have separate native browser checks. These checks do not establish real payment, inbox delivery or customer-host update delivery.

Historical 1.1.20 environments
Free minimum

PHP 7.4.3 & 8.0.8

WordPress 6.5 · WooCommerce 9.1.0

Free-only stock, CSV, receiving and export checks. Selected minimum Free Firefox/WebKit workflows and actual PDF rendering were exercised.

Pro minimum

PHP 8.1.34

WordPress 6.6 · WooCommerce 9.1.0

Native Pro workflows and authenticated graphical counting, planning, purchasing and CSV checks. This closes the earlier minimum-Pro browser gap. License service responses were fictional.

Current and intermediate

PHP 8.2–8.5

PHP 8.2.33, 8.3.6, 8.4.26 and 8.5.4 · WordPress 7.1.3 · WooCommerce 11.2.1

Selected stock/history, CSV, purchasing and Pro workflow checks. The late stock-reader correction has separate current/minimum proof.

Historical 1.1.20 databases, orders and browsers

Native checks used MariaDB 11.8.6 and MySQL 8.0.46. Actual legacy and HPOS WooCommerce order stores were verified separately, with order stock deductions, cancellation, quantity refunds and demand/history checks. A two-site integration used Redis Object Cache 3.0.0 with Predis. These are selected integrations, not coverage of every cache or network configuration.

Firefox 155 and WebKit 26.6 WPE covered current, minimum Free and minimum licensed-Pro workflows with desktop and phone-like viewports. Actual PDF responses were parsed and rendered, including PHP 7.4. Firefox download events passed; WPE was checked through authenticated PDF HTTP responses because its attachment download event was unavailable. These tests do not certify Safari, iPhone, physical devices or assistive technology.

Which checks applied to the final 1.1.20 ZIP?

The final 1.1.20 Free archive passed unmodified official Plugin Check 2.1.0 default, expanded and all five runtime checks with Pro physically absent: zero errors and warnings. Both readmes passed the official validator. Private Pro retains two errors and three warnings for its private updater and Update URI under WordPress.org directory rules; runtime checks pass. Pro is distributed privately.

Broader suites used earlier 1.1.20 candidates. The final raw-stock, numeric precision and layout corrections have separate native/browser regressions and fresh exact-archive package checks. PHP 8.2, 8.3 and 8.4 targeted raw-reader results precede the final scientific-notation branch. Earlier results are not relabelled as a complete rerun of every feature on the final archive.

Historical 1.1.20 import and saved-plan samples

A synthetic 5,000-product import exercised cancellation after 1,001 saves, uncertain-response recovery and a 3,999-row replacement. Final quantities and all 5,000 distinct movements were verified. The shared-host run took about five minutes and observed about 128 MiB peak memory; it is not a guarantee for 128 MB hosting or production checkout load.

Saved plans were checked with 10,000 and 50,000 synthetic products, expected quantities, ordering and totals and selected-supplier rows. A second 50,000-product run covered the corrected raw reader and corrected saved-plan calculations; it used integer stock and predates the final scientific-notation and CSS additions. Its warm shared-host sample used PHP 512M, with default browse samples around 2.4–3.8 seconds. This is not a full-final-package capacity or sustained-load claim.

Updates and real-service boundaries

WordPress automatic update tests on minimum and current Pro stacks preserved selected stock, history, settings, counts, purchasing and local license state. Provider metadata, tickets, signatures and entitlement were controlled fictional fixtures and earlier source generations. They do not prove current paid-provider delivery through a customer host’s ordinary network.

Historical browser-update and TEST-mode payment checks retain their earlier version labels. Genuine paid purchase, renewal, refund, inbox delivery, customer automatic updates and installation of WordPress.org’s actual generated Free ZIP need separate acceptance checks.

See the screens. Then test your own setup.

The demo shows the real workflow with fictional data. A staging copy checks the fit with your products and extensions.