Install with confidence.
Pre-launch documentation for ProofFlow 0.1.0. Downloads and checkout are not yet available.
Requirements
- WordPress 7.0 or 7.1; WooCommerce 11.0 or 11.1.
- PHP 8.1 through 8.4 and HTTPS in production.
- A WordPress customer account linked to the order. Guest approval links are not included.
- Access to your web-server configuration if automatic Apache protection is unavailable.
Your first installation
- Back up the WordPress database and uploads. Start on a staging store.
- Open Plugins → Add New → Upload Plugin and select the ProofFlow ZIP.
- Activate WooCommerce, then activate ProofFlow.
- Open ProofFlow storage diagnostics. Confirm the PDF, JPG, JPEG and PNG protection checks return HTTP 403.
- Create a test order linked to a customer account and upload a harmless sample proof.
- Sign in as that customer. Request a change, upload a revised proof as the merchant, then approve it as the customer.
- Confirm the approved version and production-ready indicator appear beside the order.
Private storage is required
Apache hosts that allow .htaccess overrides can use the protection installed by the plugin. Nginx hosts must add the supplied nginx-proof-flow.conf.example rule to the WordPress server block and reload Nginx. Ask your host if you do not manage the server.
A CDN must deny public access to the protected file extensions and bypass caching for the proof directory. Extra CDN origins require an explicit allowlist. Re-run the storage checks after configuration. ProofFlow stays disabled when protection cannot be verified.
Updates and workflow limits
Version 0.1 uses manual ZIP updates. Back up first, then upload the new ZIP and replace the installed plugin. Do not change the storage backend of an existing installation without migrating and verifying its files.
An approval is final for that workflow. ProofFlow does not change native WooCommerce order statuses or automatically stop production. It does not provide annotations, guest links, or artwork uploads at checkout.