FastOps for WooCommerce
Sign in Book a demo

Chapter 01 · User guide

Getting started

Install the two plugins, activate your licence, start the background worker and decide whether this site is production or staging.

01 · Before you install

What the site needs

FastOps for WooCommerce runs inside your own WordPress site. Nothing about your theme, checkout or data moves anywhere.

  • WordPress 6.6 or newer, PHP 7.4 or newer, WooCommerce 8.2 or newer.
  • High-performance order storage (HPOS) enabled in WooCommerce. See Open the workspace if it is not.
  • A single site, or one WooCommerce subsite on a multisite install. Network activation is not supported; activate FastOps on each store separately.
  • A way to run one background process: a system cron entry on shared hosting, or Supervisor / systemd on a VPS.
Back up firstTake a database and file backup before installing, as you would for any plugin that adds tables.

02 · Install the plugins

Two plugins, in order

FastOps ships as a Community plugin and a Pro add-on. Install both from the ZIP files you were sent.

  1. In WordPress, open Plugins → Add New → Upload Plugin and upload the Community ZIP. Activate it.
  2. Upload and activate the FastOps Pro ZIP the same way. Use the paired versions supplied for the first installation.
  3. On multisite, do this from the individual store's own Plugins screen, not the network screen.

03 · Activate the licence

Enter the key and choose the environment

  1. Open FastOps → Pro licence in the WordPress admin menu.
  2. Paste your Licence key.
  3. Under Environment, choose Production for the live store or Staging for a copy. This decides which seat on your plan the site uses.
  4. Leave Recovery token empty. It is only needed when reconnecting an installation whose stored secret was lost.
  5. Activate. The key is exchanged once and is not stored on the site.

The page then shows the licence state and when it was last checked. Use Check licence now to force a fresh check, for example after your plan was changed. Checks run in the background and never slow down the workspace, checkout or storefront.

If the site address changesThe licence page will say the site address changed and ask you to activate again. Choose Staging if this is a copy of another store. Choose Production only if it is the same store at a new address; the old installation keeps its seat until an operator revokes it.

04 · Start the background worker

One process that runs bulk jobs and syncs

FastOps needs a background worker on the server. It runs bulk jobs and keeps the workspace in step with WooCommerce. You start it in one of two ways, depending on the hosting.

Shared hosting: one cron entry

Add a single line to the hosting account's cron (cPanel, SiteGround and similar). It starts a short-lived worker every minute; overlapping runs are rejected automatically.

* * * * * cd /path/to/site && FASTOPS_PHP=/absolute/path/to/php-cli FASTOPS_WP=/absolute/path/to/wp FASTOPS_SITE_PATH=/path/to/site FASTOPS_SITE_URL=https://store.example.com /absolute/path/to/bash wp-content/plugins/fastops-for-woocommerce-pro/fastops-worker.sh --max-seconds=180
  • FASTOPS_PHP must point at a command-line PHP binary (on standard cPanel that is /usr/local/bin/php), not the web PHP.
  • Paste the command as one uninterrupted line and keep the full fastops-worker.sh file name.
  • Do not add FASTOPS_SUPERVISE=1 on shared hosting unless the provider explicitly allows permanent processes.

VPS or dedicated server: Supervisor or systemd

Run the worker as a service under Supervisor or systemd so it is restarted automatically. Do not add the cron entry as well; a service manager already restarts processes.

If the worker is not runningThe workspace shows a plain notice that some actions may take longer. Edits still go through, but bulk jobs wait until the worker is back. See Troubleshooting.

05 · Open the workspace

Build the index and check order storage

  1. Open FastOps from the WordPress menu. On the first visit it prepares its tables. If your host delays background database tasks, choose Run upgrade now on that screen.
  2. If FastOps reports that the store uses legacy order storage, enable HPOS from WooCommerce → Settings → Advanced → Features after WooCommerce's own synchronisation checks pass. FastOps never changes order storage itself.
  3. Choose Build index. Lists fill in as the index completes; on a large store this runs in the background and you can keep working.
The FastOps workspace open on the product list after installation.
The workspace once the index is built. Everything you manage is one click away in the top bar.
  1. Orders, Products, Subscriptions, Coupons, Activity, Analytics and Marketing. Subscriptions only appears when WooCommerce Subscriptions is installed.
  2. The record count confirms the index has finished building.
  3. Refresh the list by hand if you have just changed something in WordPress.
  4. Add a new product, order, subscription or coupon from the same place on every list.

06 · Staging and production

Test on a copy first

Your plan includes staging seats so you can try FastOps on a copy of the store before the live site. Activate the copy with the same key and Staging as the environment.

  • Run the store's real workflows on staging: a few product edits, an order status change, a small bulk update, and anything your extensions add.
  • Keep the staging worker running for a while and confirm the workspace shows no worker notice.
  • If you restore a production database into staging later, activate the licence again as Staging; the licence page will prompt you.

07 · Automatic updates

Opt in to unattended Pro updates

By default, FastOps Pro updates wait for a click on the Plugins screen like any other plugin. You can let WordPress install them for you.

  1. Open FastOps → Pro licence and find Automatic updates.
  2. Tick Install FastOps Pro updates automatically and choose Save update preference.

Updates are signed and follow any staged rollout declared for your installation. Your theme, checkout and store data are never touched by an update.

Installation secretThe same page shows when the site's installation secret was last replaced. This happens automatically every 90 days. Use Replace installation secret if you believe it was exposed, for example after restoring a backup somewhere else. Nothing else needs changing afterwards.