Documentation and support
Start with one shipping rule that matters. If the check cannot finish, open the result details. They show whether a shipping option or price changed, or why the check stopped.
Open WooCommerce → Shipping Contract Guard and choose the first suggested shipping rule. The plugin preselects a simple shippable product when it can.
Check the made-up addresses, exact shipping options, and prices. You choose the correct result; the plugin does not decide for you.
You will see “Everything works,” “Problem found,” or “Could not verify.” The last result means the check was unsafe, ambiguous, unsupported, or incomplete.
Result guide
On a small screen, swipe sideways to see all columns.
| Result | Meaning | Next step |
|---|---|---|
| Everything works | Each shipping option and price matched the result you saved. | Keep the check and rerun it after a plugin, theme, product, or shipping setting changes. |
| Problem found | An expected shipping option is missing, an unexpected option appears, or a price changed. | Compare the saved and current results, then inspect the suggested setting first. |
| Could not verify | The check was unsafe, unsupported, unclear, or incomplete. This never counts as working. | Open the result details and follow the reason shown. Rerun the same test cart only after you resolve that reason. |
On a small screen, swipe sideways to see all columns.
| Reason | Meaning | Next step |
|---|---|---|
| Unsupported shipping option | The plugin cannot safely test that shipping option automatically. | Run it manually, or review whether the check may contact the provider before you save the exact WooCommerce result. |
| Incomplete calculation | WooCommerce or the shipping option stopped before returning a full result. | Check WooCommerce logs and whether the carrier or provider is available, then rerun the same test cart. |
| Unsafe store change | The test tried to create or change a store record. | Stop running that check, download the support file, and contact support. |
Compatibility
Version 1.9.4 requires WordPress 6.5, WooCommerce 8.2, and PHP 8.1 or later. The table shows the oldest supported versions and the newest versions that release testing covers. A third-party shipping extension is not automatically supported just because it is installed.
On a small screen, swipe sideways to see all columns.
| Area | Versions supported or tested | Important limit |
|---|---|---|
| WordPress | 6.5 or later; release tests used 7.1 | Each new version needs a fresh release check |
| WooCommerce | 8.2 or later; release tests used 11.0.1 | We test classic checkout on both the oldest and newest listed versions |
| PHP | 8.1 or later | Code checks and tests for the oldest supported setup use PHP 8.1 |
| Checkout blocks | Tested with WooCommerce 11.0.1 | We exclude WooCommerce 8.2 block rendering because it creates a draft order |
| High-Performance Order Storage (HPOS) | Supported | The plugin creates no order and does not depend on WooCommerce order storage |
| Shipping options | WooCommerce Flat Rate, Free Shipping, and Local Pickup; other options WooCommerce returns after you review the test | Live carrier availability and private extension settings are outside the check |
Magento Open Source 1.1.0 preview
Read the Magento 1.1.0 preview guide before installation. It explains Composer and source installation, reviewing and approving a test, Local and Operator commands, report permissions, temporary-quote cleanup, history, deletion, connecting Operator later, schedules, disconnecting, and troubleshooting.
The preview passes Magento Open Source 2.4.7-p10 with PHP 8.2 or 8.3, 2.4.8-p5 with PHP 8.3 or 8.4, and 2.4.9 with PHP 8.4 or 8.5. It supports Magento’s built-in Flat Rate, Free Shipping, and Table Rate methods only when they have not been replaced or changed. Adobe Commerce and other carriers are not included in the 1.1.0 compatibility claim. Operator is not for sale yet.
We review free Local requests on Belgian business days, without a guaranteed response time. We can explain installation, supported tests, result messages, cleanup, local data controls, and how to reconnect Operator safely later. We do not operate the store, repair checkout, bypass billing, or support an unlisted carrier.
Current release
Before publication, version 1.9.4 passed automated WordPress, code-quality, runtime, compatibility, release, and local browser checks. No issues were recorded in those checks.
Support file
The downloadable support file includes product versions, whether the database and automatic checks are working, whether Operator is connected, and totals from the latest run. It leaves out products, product codes, saved checks, addresses, customers, orders, payment details, service identifiers, and passwords.
Optional WooCommerce logging is off by default. When enabled, it records only the Shipping Contract Guard admin action and whether it succeeded. Turn it off again after reproducing the issue.
Support expectations
Email hello@shippingcontractguard.com with the support file, the result shown on screen, and the steps you took. Do not send database exports, customer addresses, order data, service keys, carrier passwords, or payment information.
We review requests on Belgian business days. The free plan has no guaranteed response time.
We review messages from stores with an active Operator subscription first. Operator monitors checks; it does not repair your store or provide emergency support.