Compatibility

The video summarizes compatibility in a minute; the tables below are the reference to check before you install or update. Every requirement below is taken from the plugin itself (its version header and code), current for plugin version 1.2.3.

​

Requirements at a glance

​

HPOS

Supported. WooCommerce can store orders in its modern, high-performance order tables instead of the classic posts table. The plugin declares this compatibility to WooCommerce (FeaturesUtil::declare_compatibility( 'custom_order_tables', __FILE__, true )), so it works whichever storage WooCommerce uses. Shipment records are stored separately from orders and are unaffected by the choice.

​

Checkout: classic and block both supported

The automatic label pipeline runs on both of WooCommerce’s checkout types:

• Classic checkout (the shortcode-based checkout) — supported.
• Block checkout (the block-based checkout) — supported. The plugin listens to the event WooCommerce fires when a block-checkout order is placed, exactly as it does for classic checkout.

The one honest caveat: if your store uses a headless or heavily customized front end that bypasses WooCommerce’s own checkout entirely, the plugin cannot see the order being placed and will not create a label automatically. Stores using WooCommerce’s standard checkouts — classic or block — are covered.

​

Multisite

Not advertised. The plugin installs and runs per site, and no multisite-specific behavior is claimed or documented beyond cleanup: if you delete the plugin on a multisite network, the cleanup runs on every site in the network. If you run a multisite network, test the plugin on a staging site first and treat it as untested territory rather than a supported configuration.

​

Languages and translations

Translation-ready, with no translations shipped. The plugin registers the teamzlab-fedex text domain and ships a languages/ folder, which is what translation plugins look for. In the current release the folder contains no actual translation files, so the admin interface is English only. A translation plugin can fill that folder once translations become available.

​

Server requirements beyond the header

• Outbound HTTPS to apis.fedex.com and apis-sandbox.fedex.com must be allowed by your host. Typical managed WordPress hosts allow this.
• Scheduled tasks must run, because the shipment-confirmation email is sent about five minutes after checkout by WordPress’s scheduler. This is standard on most hosts.
• Nothing else: no extra PHP extensions, no command-line tools, no separate background workers.

​

Not supported

• No headless-checkout guarantee — see above.
• Two optional FedEx sandbox endpoints were retired by FedEx, affecting two optional features; details in Troubleshooting.
• No label image post-processing — labels follow FedEx’s own formats (choose them on the Labeling tab); the plugin does not modify the images.

​

External factors: FedEx changes its side too

FedEx retired its older SOAP interface in 2026, and this plugin is built on FedEx’s current REST APIs. FedEx can change or retire endpoints on its own schedule, so the practical rule is to keep the plugin updated — updates are how the plugin tracks FedEx’s side.

​

Licensing and daily limits

The plugin bundles the Freemius licensing SDK, but in the current build no feature is locked behind a plan. What a plan does change is the daily shipment limit: Without a connected plan, a store runs at the Free limit. The quota panel on the Settings page shows today’s usage; it is read-only and has no reset control.

​

What’s next