Updates follow the same two paths as installation: from WordPress.org (recommended — one click) or from a ZIP file. Your settings, boxes, shipments, and order data are all stored in your site’s database and uploads, and an update does not touch them.

​
Update from WordPress.org

1

Open the Updates screen

Go to Dashboard → Updates. If an update is available, “TeamzLab FedEx Shipping” appears in the plugins list with a checkbox.
2

Update

Tick the checkbox and click Update Plugins. WordPress downloads the new version from WordPress.org and swaps the files; your data stays where it is.
3

Confirm the version

Go to Plugins and check the version number under the plugin’s name against the release you expect.
You can also update from the plugin row on Plugins: WordPress shows an Update now link whenever a newer version exists.

​
Update from a ZIP

If you received a ZIP from TeamzLab directly (for example, a pre-release build):
1

Deactivate first

Go to Plugins and deactivate “TeamzLab FedEx Shipping”. Deactivating is safe — it changes nothing in your data (see Uninstalling and removing your data for what deactivate vs. delete means).
2

Delete the old version — after checking the warning

Click Delete on the deactivated plugin.
Deleting the plugin permanently removes its shipments and settings from your database. If your intention is only to swap files, ask your developer to replace the plugin folder by SFTP instead of using Delete — or take a database backup first.
3

Install the new ZIP

Go to Plugins → Add New → Upload Plugin, choose the new ZIP, install, and activate.

​
After every update: a two-minute check

  1. Open FedEx Shipping → Settings and confirm your credentials and address fields are still filled in and the Environment shows what you expect (sandbox or production).
  2. Place a sandbox test order (or a real low-value order in production) and confirm a shipping label creates as before.
  3. Check that tracking updates arrive on that order — this exercises the webhook path, which is the most common thing a store notices after an update.

​
Compatibility before you update

Check Compatibility for the WordPress, WooCommerce, and PHP versions the new release supports, and update WooCommerce itself first if it is behind — the plugin is tested against specific WooCommerce versions.
Version history and changelog entries are maintained with each release. If you need to know exactly what changed between two versions, ask TeamzLab support and include your current version number (shown on the Plugins screen).

​
What’s next

Compatibility

Supported WordPress, WooCommerce, and PHP versions.

Troubleshooting

If something behaves differently after an update, start here.