API Integration – WooCommerce Shipping Plugin for FedEx FAQs

Why is my WooCommerce FedEx shipping plugin not calculating shipping costs and showing the API as disabled despite having the correct license code?

The plugin license must be actively activated to enable live shipping rate calculation via the FedEx API. If the API appears disabled even though you have entered the license code, it is likely the license is not fully activated. To resolve this:

1. Go to the WooCommerce FedEx Shipping plugin’s License Activation page in your WooCommerce admin.
2. Find the section for API Key Deactivation and enable the “Deactivate API Key” option. Save these changes.
3. Log in to your PluginHive.com account, navigate to **My Account → API Keys**, and delete any previous activations associated with your license key.
4. In your WooCommerce admin, deactivate and then reactivate the WooCommerce FedEx Shipping plugin to refresh its state.
5. Return to the License Activation page, go to API Key Activation, enter your license API key and Product ID again, and save the changes.

This process re-establishes the license validation and activates the FedEx API connection, allowing the plugin to fetch live shipping rates. If these steps are correctly followed, your store should calculate FedEx shipping costs properly.

Why does the WooCommerce FedEx Shipping Plugin show a subscription expiration warning even though I purchased upgraded licenses recently and updated the API key?

This issue typically occurs because the plugin requires proper synchronization of the license status with the updated API key. To resolve the warning banner despite having updated the API key, follow these steps:

1. Deactivate the plugin license from the plugin settings.
2. Reactivate the plugin license using the correct, updated API key and Product ID.
3. Deactivate the entire plugin from the WordPress plugins page.
4. Reactivate the plugin again.
5. Clear your website cache thoroughly (if you use caching plugins or server cache).
6. Perform a hard reload of your browser (e.g., Ctrl + F5) to ensure all updated data is fetched.
7. Refresh the WooCommerce backend page where the warning appeared.

This process re-establishes the correct license verification and will remove the renewal warning banner.

Why do I get a critical error when enabling real-time FedEx shipping rates in WooCommerce after entering all required FedEx API credentials and product details?

1. Verify that all your FedEx API credentials—API key, Product ID, secret, Client ID, and License Key ID—are correctly registered in the plugin settings.
2. Ensure all products have accurate weights and dimensions entered.
3. Confirm that the “Ship from” address is properly set.
4. Update WooCommerce to the latest stable version, as older versions may have compatibility issues causing critical errors.
5. After updating, re-enable the real-time rates and check if the errors persist.

Why am I not getting shipping rates even though my FedEx API keys are validated in the PluginHive WooCommerce FedEx plugin?

1. Complete the FedEx registration process via the plugin as described in the guide here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number
2. After successful registration, do not edit or manually change the FedEx credentials.
3. This connection method will enable the plugin to fetch shipping rates correctly without errors.

Which FedEx APIs need to be selected and activated in the FedEx Developer Portal for integrating with the PluginHive FedEx shipping plugin?

You do not need to create or activate any API credentials directly through the FedEx Developer Portal for the PluginHive FedEx shipping plugin. Instead, PluginHive offers a FedEx Compatible Registration process that allows you to connect your FedEx account by simply providing your FedEx account number and billing address. This eliminates the need to select or activate individual FedEx APIs such as Address Validation API, Rate and Time-in-Transit API, Shipping API, or others. After completing the registration, you can immediately start using FedEx services on your website through the plugin.

For detailed setup instructions, follow the guide here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx

This approach simplifies integration, removing the complexity of managing multiple API activations on the FedEx platform. If you encounter any issues or need further assistance, PluginHive support is available to help.

Where do I find and enter the API Key and Product Key for the WooCommerce FedEx Shipping plugin?

1. In your WordPress dashboard, navigate to **Settings > FedEx Activation**.
2. Open the **API Key activation** section.
3. Enter the new **API Key** and **Product ID** associated with your recent purchase.
4. Activate the plugin license to complete the setup.

Where do I enter the API key for the WooCommerce FedEx Shipping Plugin if I don't see a dedicated FedEx section in WooCommerce settings?

• FedEx Account Number
• FedEx Meter Number
• Web Services Key
• Web Services Password

Where can I locate my API Key for the WooCommerce FedEx Shipping plugin?

1. Checking the renewal or purchase confirmation email sent to you by PluginHive, where the API Key is provided.
2. Logging into your PluginHive **My Account** page on their website and navigating to the **API Keys** section.

Where can I find detailed instructions to activate the WooCommerce FedEx shipping plugin license and API key through PluginHive?

Detailed instructions for activating the WooCommerce FedEx shipping plugin license and API key through PluginHive can be found at:

Set Up WooCommerce FedEx Shipping Plugin

Where and how do I enter the License API key for the PluginHive WooCommerce FedEx Shipping plugin?

1. Follow the detailed step-by-step instructions provided in the PluginHive knowledge base article here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#activate_plugin_license
2. After entering the license key, refresh the plugin page or verify updates by navigating to WordPress Dashboard → Updates → Check Again.
3. If needed, you can also download the latest plugin version from your PluginHive account at PluginHive.com, under "My Accounts."
4. For installing a downloaded update: deactivate and delete the old plugin version in WordPress (your current settings will be preserved), then upload and activate the new version.

When I click "Renew" in the WooCommerce FedEx Shipping Plugin, it generates a new API key instead of renewing the existing one. Is this normal?

Yes, this behavior is normal. Clicking the "Renew" button generates a new API key as part of the renewal process. However, to ensure the warning banner disappears and the plugin functions properly with the renewed license, you must:

1. Deactivate the current plugin license.
2. Reactivate the license using the newly generated API key.
3. Deactivate the WooCommerce FedEx Shipping Plugin itself.
4. Reactivate the plugin.
5. Clear your site cache.
6. Perform a hard browser reload.
7. Refresh your WooCommerce backend page.

Following these steps ensures the renewed license is applied correctly and the expiration warning will be removed.

What is the updated registration process for the WooCommerce FedEx Shipping Plugin to comply with FedEx API changes starting August 31, 2024?

1. Ensure you have the WooCommerce FedEx Shipping Plugin version 7.0.9 or later installed.
2. Remove any old Web Services credentials (Meter Number, API Key, Web Services Password) from the plugin settings.
3. Prepare your FedEx Account Number and billing address details. These are now the only required credentials.
4. Access the registration interface within the plugin and enter your FedEx Account Number and the billing address exactly as registered with FedEx.
5. Submit the registration form and wait for confirmation within the plugin that registration succeeded.
6. Refer to the official FedEx Registration Guide video here for detailed visual instructions: https://www.youtube.com/watch?v=Ven0orsNqeQ
7. If your license is active and registration is successful, your plugin will continue functioning without disruption after August 31, 2024.
8. Contact PluginHive support if you encounter any issues during registration or activation.

What causes the PHP fatal error "Call to undefined method WooCommerce::is_store_api_request()" and how can I fix it for the FedEx plugin?

1. Update your WooCommerce installation to the latest stable version (for example, version 9.9.3 or newer).
2. After updating, check if the error persists by testing the FedEx shipping options again.

Is there an older version of the FedEx plugin compatible with WooCommerce 5.8.1 and WordPress 5.8.1 that uses the RESTful API?

Older versions of the FedEx plugin, including version 6.0.0 and 6.0.1, which introduced support for the RESTful API, are not compatible with WooCommerce 5.8.1 and WordPress 5.8.1. The minimum supported WooCommerce version remains 7.7 for these plugin versions, and older versions of WooCommerce and WordPress are not supported. Additionally, older plugin versions lack integrated FedEx direct registration and may not function properly with the current FedEx API.

How should businesses shipping lithium-ion batteries under Limited Quantity exemptions handle shipping configuration in the WooCommerce FedEx Shipping Plugin given current FedEx API limitations?

1. Mark lithium-ion battery products as either Battery (for ground shipments within the U.S.) or as full Dangerous Goods when shipping by air or requiring compliance with full DG rules.
2. Accept that FedEx Ground services with Battery classification and FedEx Express services with Dangerous Goods classification are treated separately by the FedEx API and plugin, and cannot be combined on a single product configuration.
3. Use FedEx Express services for full DG shipments and FedEx Ground services for batteries when permitted by regulation and FedEx policy, understanding the plugin will only return applicable services per product classification.
4. If your business requires mixed shipping logic for the same product, consider discussing a paid customization with PluginHive.

How do I use the new Product Order API key for the WooCommerce Shipping Methods and Rate Adjustment license if the WordPress plugin interface does not have an API key entry field?

The Hide WooCommerce Shipping Methods & Rate Adjustment plugin does not require manual API key entry on the WordPress admin interface. Instead, once the plugin is installed and activated, it automatically recognizes the API key linked to your PluginHive account associated with that product. To resolve any licensing or activation issues:

1. Ensure you have installed and activated the Hide WooCommerce Shipping Methods & Rate Adjustment plugin properly on your WordPress site.
2. Verify that your new Product Order API key is active and linked in your PluginHive dashboard under the relevant product.
3. If activation issues persist, perform license refresh steps such as deactivating and reactivating the license via the PluginHive portal and WordPress plugin.
4. If problems continue, contact PluginHive support with plugin details and site access for further assistance.

How do I correctly enter the License API key for the PluginHive WooCommerce FedEx Shipping plugin?

1. Access your WordPress admin dashboard and navigate to FedEx Shipping → License Activation → API Key Activation.
2. Enter your License API key and the Product ID exactly as provided by PluginHive.
3. Refresh the plugin settings page or go to Dashboard → Updates → Check Again to verify the license activation.
4. If you have downloaded the latest plugin version from your PluginHive account, you can deactivate and delete the old plugin version (settings will be preserved), then upload and activate the new version.
5. After license activation, your site will be entitled to plugin updates and support.

How do I configure the latest API key in the WooCommerce FedEx Shipping Plugin to ensure uninterrupted shipping service after subscription renewal?

1. Obtain the new API key provided upon subscription renewal (usually found in your purchase confirmation or renewal email).
2. Log in to your WordPress admin dashboard.
3. Navigate to the WooCommerce settings area and select the FedEx Shipping Plugin section.
4. Locate the API key or credentials input fields within the plugin settings.
5. Enter or paste the updated API key exactly as provided.
6. Save the settings to apply the update.
7. Clear your site cache if applicable, and test shipping functionality on your store to confirm everything is working correctly.

How do I activate the PluginHive WooCommerce FedEx Shipping plugin license using the Product ID and API Key?

The Product ID and API Key are used solely to activate the plugin license, not for FedEx API integration. For guidance on the license activation process, please follow the detailed instructions available here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number. This will ensure your plugin license is activated correctly and ready for use.

How can Pluginhive support assist if we are unable to activate the WooCommerce FedEx Shipping Plugin using the API Key?

1. Create a new WordPress user with Administrator privileges using the email [email protected].
2. Ensure the WordPress dashboard language is set to English before sharing access.
3. Reply to the Pluginhive support team confirming the account creation.
4. Provide the site login URL and password securely to the support team.

How can I verify if my WooCommerce FedEx Shipping Plugin is properly installed and registered according to the latest FedEx API requirements?

1. Confirm your plugin is updated to version 7.0.9 or later. You can download the latest version from your PluginHive account under My Account → API Downloads at www.pluginhive.com.
2. For registration using the latest FedEx Compatible Solution, you only need your FedEx Account Number and your billing address—no longer the Meter Number, API Key, or Web Services Password.
3. Follow the updated registration process exactly as outlined in the official FedEx Registration Guide video: https://www.youtube.com/watch?v=Ven0orsNqeQ
4. After registration, ensure that the plugin status shows as activated within your WooCommerce backend.
5. If you previously registered using older Web Service credentials, you must re-register using this new process to avoid disruptions, as FedEx will disable legacy Web Services on August 31, 2024.
6. If you require assistance during this process, reach out to PluginHive support.

How can I resolve the "Service is invalid" error returned by the FedEx API when creating a Freight shipment using the WooCommerce Shipping Plugin for FedEx?

1. Verify that the shipment details and service code are correctly configured and supported by the FedEx API in your account.
2. Confirm that the FEDEX_FREIGHT_PRIORITY service is active and enabled for your FedEx account.
3. Test the same shipment details via the FedEx Ship Manager on fedex.com to ensure the service works outside the plugin.
4. If the shipment works on FedEx Ship Manager but not via API, it implies the issue is with the API integration or account permissions.
5. Contact FedEx technical support for API-related issues. Provide them with your API request and response logs, error messages, and account details for a detailed investigation.
6. For Freight shipment API support, use the FedEx API Customer Service at phone number 312.300.7907 or email [email protected] to create a support case and obtain reference numbers for your troubleshooting.
7. Keep detailed records of all communications with FedEx support to expedite issue resolution.

How can I locate and retrieve my API key for the WooCommerce FedEx Shipping Plugin?

1. Log in to your account at www.pluginhive.com.
2. Navigate to the **My Account** section.
3. Click on **API Keys**.
4. You should see your API key listed there.

Has the PluginHive WooCommerce FedEx shipping plugin been updated to support FedEx's new RESTful APIs?

Yes, the PluginHive WooCommerce FedEx shipping plugin has been updated to support FedEx's RESTful APIs. With this update, the plugin no longer requires the Meter Number and Web Service keys for configuration. Instead, you need to register your FedEx account directly through the plugin interface. For detailed steps on completing the FedEx account registration within the plugin, refer to the PluginHive knowledge base article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. This update ensures seamless integration with FedEx’s latest API system.

Does the WooCommerce FedEx Shipping Plugin support FedEx RESTful API integration, and how do I set it up?

Yes, the plugin supports FedEx’s RESTful API. To set it up, simply connect your FedEx account inside the plugin by entering the required account details (outlined above). The plugin manages REST API authentication internally, so no separate Meter Number or additional API credentials setup is needed within the plugin interface.

Does the PluginHive WooCommerce FedEx Shipping Plugin support the new FedEx RESTful APIs after the deprecation of FedEx’s SOAP-based Web Services?

PluginHive is actively working on an update to support the new FedEx RESTful APIs. This update is scheduled for release by the third week of July 2025, ensuring continued compatibility well before the FedEx SOAP API deprecation deadline of August 31, 2024. After the update, your shipping integration will function without interruption using the REST API.

Does PluginHive support resolving custom development issues related to WooCommerce API method usage, such as undefined functions?

PluginHive support primarily assists with issues related to PluginHive plugin operations, WooCommerce compatibility, and shipping label generation. For custom development queries involving WooCommerce core methods or custom code, including handling undefined methods like `get_shipping_phone()`, it is recommended to consult your development team or WooCommerce developer resources. However, PluginHive can clarify compatibility requirements, such as required WooCommerce versions, to help troubleshoot integration issues.

Do I need to take any action regarding the email about updating to the FedEx API in the PluginHive WooCommerce FedEx Shipping plugin?

Yes, you need to complete the FedEx Registration process included in the latest version (7.1.0) of the PluginHive WooCommerce FedEx Shipping plugin. This process involves connecting your FedEx account by providing your FedEx Account number and Billing address within the plugin settings on your site. This step must be completed before August 31st to ensure uninterrupted service. You can verify and perform this setup by following the detailed guide here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. Make sure your plugin is updated to version 7.1.0 or later before proceeding.

Could Cloudflare’s country blocking, WAF, or firewall settings prevent the PluginHive FedEx WooCommerce plugin from communicating with FedEx’s API, and which domains or IPs should be allowlisted to avoid connection issues?

1. Review and whitelist essential FedEx domains and IP addresses used by the PluginHive FedEx plugin to connect to FedEx’s API. Although PluginHive does not publish a fixed list, allowlist domains related to FedEx API endpoints based on your plugin’s documentation or support resources.
2. Temporarily disable or loosen Cloudflare’s blocking rules, WAF, or firewall for testing if these interfere with the connection.
3. Ensure Cloudflare and your server firewall permit outbound HTTPS requests to FedEx endpoints.
4. Collaborate with your web developer or hosting provider to verify that no country blocks (e.g., for USA or Singapore) affect outbound API calls to the FedEx services.
5. Monitor plugin logs or error messages to identify connection failures that help pinpoint which services might be blocked.

Can I get a second 10% discount coupon code for purchasing an additional WooCommerce Canada Post plugin API?

Yes, you can receive a second 10% discount coupon for purchasing an additional WooCommerce Canada Post plugin API. To obtain this coupon, contact PluginHive support with your email address. They will provide a coupon code with a specified validity period and usage restrictions tied to your email. For example, a coupon like "Ph_offer_10_Jordan" valid until a certain date and allowed only for the registered email address can be issued. Use this coupon code at checkout to apply the 10% discount on your additional plugin purchase. If you have further questions, you can reach out to PluginHive support for assistance.

Are there older versions of the FedEx plugin compatible with WooCommerce 5.8.1 and WordPress 5.8.1 that use the RESTful API?

No, older versions of the FedEx plugin, including versions 6.0.0 and 6.0.1 which introduced RESTful API support, still require WooCommerce 7.7 or higher and do not support WooCommerce 5.8.1 or WordPress 5.8.1. Additionally, these older plugin versions lack current FedEx API integration features like direct registration and may not function properly with the latest FedEx services.

After renewing my WooCommerce FedEx Shipping Plugin subscription, do I need to update or change API keys for the service to continue working?

1. In your WordPress dashboard, go to **Settings** and locate the **FedEx Activation** section within the plugin settings.
2. Enter the new API keys in the appropriate fields.
3. Once entered, your plugin license will be activated.
4. After activating the license, update the plugin via the WordPress **Plugins** page or the WordPress Update dashboard.
5. Finally, connect your FedEx account by following the detailed steps in the “WooCommerce FedEx” article provided by PluginHive.

After purchasing the WooCommerce FedEx Shipping Plugin again for renewal, do I need to update or change the API key on my site?

Yes, after purchasing the plugin again, you must configure the new API key associated with your latest purchase on your website. To do this:

1. Log in to your PluginHive account.
2. Navigate to the "API Keys" section.
3. Retrieve the new API key generated for your purchase.
4. Go to your WooCommerce FedEx Shipping Plugin settings on your site.
5. Replace the old API key with the new one to activate the new license.

For detailed instructions, you can refer to the PluginHive knowledge base article here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#activate_plugin_license

Why is the FedEx plugin sending incorrect product weights in the API request, causing rate mismatches?

1. Deactivate all plugins except WooCommerce and the FedEx plugin to eliminate conflicts.
2. Test shipping rates again to see if the correct weight is passed to FedEx.
3. If the issue persists, provide access to a staging site for further investigation or permission to create a test product.

Why does WooCommerce Blocks Checkout cause multiple FedEx API requests and longer shipping rate load times compared to Classic Checkout?

WooCommerce Blocks Checkout uses a modern, dynamic block-based page architecture where shipping rates refresh automatically upon several user actions like changing product quantity or shipping address. This results in multiple FedEx API requests during a single user session or interaction. In contrast, Classic Checkout performs a single API call per update or page load, reducing cumulative API calls and therefore leading to faster rate return. This architectural difference inherently causes longer cumulative load times for FedEx rates on Blocks Checkout, given FedEx’s relatively slower API response compared to UPS.

Why does the PluginHive plugin show a "Forbidden" error when attempting to fetch FedEx shipping rates after renewing the subscription and entering a new API key?

1. Update the PluginHive FedEx Shipping plugin to the latest version (ensure version 7.1.3 or higher).
2. Deactivate the current plugin license by navigating to **FedEx Shipping > License Activation** in your WordPress admin panel.
3. Re-activate the plugin license.
4. Re-register your FedEx account again via **FedEx Shipping > Registration** to link the FedEx credentials correctly with the plugin license.
5. Confirm that the API status shows as active.

Why does the "Generic API Settings" section in the WooCommerce FedEx Shipping plugin flash and then disappear, and how do I enter my FedEx credentials for test or live mode?

The "Generic API Settings" section briefly appearing and then disappearing is normal behavior because it contains internal details used by the plugin to communicate with FedEx. This section is intentionally non-editable and hides automatically after loading, so you should not attempt to enter or modify any values there. Instead, the plugin uses an integrated FedEx-compatible account registration process that handles all authentication automatically. This means:

1. You do not need to manually enter FedEx credentials such as Meter Number or Web Services Key.
2. There is no need to submit FedEx test labels or obtain separate certification from FedEx.
3. Once you connect your FedEx account via the plugin’s registration flow, you can generate live shipping labels immediately.

Simply follow the registration flow in the plugin settings to link your account, and the plugin will manage credentials and communication behind the scenes.

Why does my FedEx Shipping plugin API key deactivate after a week with 0/1 activations, and how can I fix it?

Follow these steps to resolve the API key deactivation issue:

1. Navigate to the FedEx Shipping Activation page in your PluginHive dashboard.
2. Locate the "API Key Deactivation" section and enable the "Deactivate API Key" option.
3. Save the changes made on this page.
4. Go to your PluginHive.com account, then to "My Account" and select "API Keys."
5. Delete any previous activations associated with your license key to clear outdated entries.
6. Deactivate the FedEx Shipping plugin on your system.
7. Reactivate the FedEx Shipping plugin.
8. Return to the FedEx Shipping Activation page and locate the "API Key Activation" section.
9. Configure the license API key along with the appropriate Product-ID.
10. Save the changes again.

By completing these steps, the API key should remain active and the plugin should function correctly. If problems persist, reach out to PluginHive support for further assistance.

Why are no shipping rates showing in the checkout even though the FedEx API is returning rates during debugging?

1. Ensure that the shipping services returned by the API are supported and enabled in your plugin settings. Some FedEx services like FEDEX PRIORITY EXPRESS and FEDEX PRIORITY may not be included in the current plugin version.
2. Check that the product and shipping address details are correctly configured in WooCommerce and the plugin.
3. Confirm that your FedEx account details and billing address are accurately entered in the plugin settings.
4. Make sure the shipping method is enabled for the shipping zones applicable to the checkout address.
5. Since some FedEx services' availability depends on the plugin version, consider updating the plugin when new support for these services is released.

Where do I enter the API key to activate the PluginHive FedEx Shipping plugin?

1. Log in to your WordPress admin dashboard.
2. Navigate to **Settings > FedEx Activation**.
3. Locate the **API Key Activation** section.
4. Enter the **API Key** and **Product ID** that you received from your latest purchase.
5. Click the **Save Changes** button to apply the settings.

Where can I find the web services password for FedEx API validation in the PluginHive FedEx shipping plugin?

1. Use the FedEx Direct Registration feature inside the plugin to input your existing FedEx account number and billing details.
2. The plugin will then generate and manage the necessary API credentials automatically, including the web services password.
3. For detailed steps and guidance on this process, refer to the PluginHive knowledge base article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

Where can I find the API key and Product ID needed to activate the UPS shipping plugin?

You can find the API key and Product ID by logging into your PluginHive account and navigating to the “API Keys” section under your My Account dashboard. Use these credentials to activate the plugin license during the UPS plugin activation process. If you encounter any difficulties, you can contact PluginHive support for assistance.

When and how should I update the WooCommerce FedEx plugin on my website to the REST API version?

1. Wait for notification or check that version 8.0.0 is available.
2. Download and install the updated plugin via your WooCommerce backend as you do with other plugin updates.
3. Follow the step-by-step setup and registration guide provided by PluginHive for REST API configuration, available at: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST
4. If needed, you can switch between SOAP and REST API connections within the plugin settings.
5. For assistance, you can contact support or arrange a quick Zoom call with the PluginHive team.

What should I expect after providing API credentials and confirming the project scope?

1. PluginHive will validate the API connections with your test credentials.
2. Upon successful validation, a final purchase link for the $1,500 USD development will be sent.
3. An estimated timeline and development milestones will be shared alongside the purchase link.
4. Development will start once the purchase is completed.
5. You will be asked to perform testing within your WooCommerce environment (staging or live) to confirm correct functionality before full deployment.
6. Support for bug fixes and updates will be provided as part of the PluginHive plugin licensing terms.

What should I do when I get an error code related to FedEx API in the PluginHive plugin and the error references a placeholder like "phiveAccountNumber"?

1. Do not worry about placeholder terms—they are not actual error causes.
2. Provide PluginHive support with your valid FedEx account details (Account Number, Meter Number, Authentication Key, and Password) so they can verify and escalate if needed.
3. Allow PluginHive to communicate with FedEx directly as issues may be related to production server-side problems.
4. Use SOAP API connection in the meantime as an alternative to maintain shipping functionality.
5. Follow up regularly with PluginHive support for status updates on the investigation and resolution.

The plugin was reactivated by updating the API key, but it does not find shipping rates. How can I troubleshoot this issue?

1. Go to the plugin settings in your WooCommerce dashboard.
2. Enable the “Debug Mode” option to capture detailed logs.
3. Go to your cart or checkout page and attempt to get shipping rates again to reproduce the issue.
4. Return to the plugin settings and navigate to the "Help & Support" page.
5. Submit a Diagnostic Report from there, referencing your support ticket number (e.g., 304037).

Is there a sandbox or test mode available in the PluginHive FedEx plugin for testing with FedEx RESTful APIs before switching to production?

Currently, the PluginHive FedEx plugin does not support FedEx RESTful APIs and, consequently, does not provide a sandbox or test mode based on RESTful API credentials. The plugin operates with the existing setup that uses FedEx's traditional credentials, and any test or sandbox modes correspond to that system. For testing and setup, follow the standard procedures available in the plugin documentation.

If I have an active subscription for the WooCommerce FedEx Shipping Plugin with Print Label, do I need to acquire new API keys from FedEx or take any action due to FedEx’s upcoming Web Services changes?

No, if you have an active subscription for the WooCommerce FedEx Shipping Plugin with Print Label and you have already registered your FedEx account using your account number and contact details via the plugin’s FedEx Compatible Solution, you do not need to acquire new API keys from FedEx or take further action. FedEx is discontinuing the older Web Services (which required Account Number, Meter Number, API Key, and Web Services Password) on August 31, 2024. The plugin now uses a streamlined registration method that only requires your FedEx account number and contact details. As long as you have completed this registration and have an active license, your integration will continue to work without disruption.

I have renewed the subscription and changed the API key but the shipping rates are still not showing. How can I troubleshoot this issue?

1. Go to the plugin settings in your admin panel.
2. Navigate to the "General" tab and enable the “Debug Mode” option.
3. Reproduce the issue by checking for shipping rates on your cart or checkout page.
4. After reproducing the problem, go to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report through the instructions provided on that page. This report collects essential error logs and data, helping the PluginHive support team identify the root cause.
6. Note your reference ticket number (e.g., 339102) when submitting the report to ensure proper case tracking.

I followed the activation steps for the FedEx plugin API key but the product still shows as deactivated. What should I do next?

• Username
• Password
• Site WP-Admin login URL

How does the FedEx Compatible Solution in the current PluginHive plugin work to maintain shipping after FedEx legacy APIs are discontinued?

The FedEx Compatible Solution allows you to connect your FedEx account by entering your FedEx account number and billing address. This setup maintains communication with FedEx shipping services without relying on the discontinued FedEx web services, so your shipping labels and tracking will continue to function seamlessly during and after the FedEx API migration.

How do I resolve the warning related to an expired or inactive API key for the FedEx plugin on PluginHive?

1. Navigate to the FedEx Activation page in your PluginHive dashboard.
2. Go to the API Key Deactivation section.
3. Enable the "Deactivate API Key" option and click "Save Changes."
4. Deactivate the FedEx plugin, then reactivate it.
5. Return to the FedEx Activation page and go to the API Key Activation section.
6. Enter your license API key and Product-ID into the respective fields.
7. Click "Save Changes" to activate the license and complete the setup.

How can I troubleshoot the issue when my website shows "No shipping options found" after activating the PluginHive FedEx plugin and adding the API key?

1. Enable Debug Mode in the plugin settings by navigating to the **General Tab** and checking the "Debug Mode" option.
2. Attempt to fetch shipping rates again on your website.
3. Go to the **Help & Support** page within the plugin and submit a **Diagnostic Report** as per the instructions provided there.
4. Share the diagnostic report with the PluginHive support team so they can analyze and identify the root cause of the problem.

How can I resolve the issue of losing the ability to create and print FedEx labels from my WooCommerce store after renewing the PluginHive API?

To resolve this issue, please follow these steps:

1. Verify that your PluginHive FedEx Shipping plugin is updated to the latest version (currently v7.1.3). If not, update the plugin to this version.
2. Confirm that you have completed the FedEx registration process correctly within the plugin settings. If not, re-register your FedEx account by following this guide:
3. After updating and confirming registration, check if you can create and print FedEx labels successfully.
4. If the problem persists, gather diagnostic information as follows:

Following these steps will help identify and fix any configuration or plugin-related issues affecting label generation and printing.

How can I provide the necessary details to PluginHive support for resolving API key activation or shipping rate issues?

1. Prepare your website’s WordPress admin login URL and access credentials (username, password).
2. Locate your Product API Key and Product ID from the PluginHive dashboard or plugin settings.
3. Share these details securely with support through official PluginHive communication channels. Avoid sharing sensitive information publicly.
4. Once received, the support team can log in to your website, verify configurations, activate the API key manually if required, and troubleshoot any errors related to license activation or shipping rates.

How can I handle Duties and Taxes charges in shipping rates if the FedEx API does not return these amounts through the PluginHive FedEx plugin?

1. Navigating to the plugin settings under "Rates & Services."
2. Applying either a Fixed Amount or a Percentage markup adjustment to the FedEx returned shipping rates based on your typical Duties and Taxes cost.
3. This allows you to collect additional charges from customers at checkout to cover Duties and Taxes, improving approximate cost recovery even though it's not dynamically fetched from FedEx.

How can I facilitate PluginHive support in resolving FedEx API account mismatch issues more effectively?

1. Provide complete and accurate FedEx account credentials and API keys securely (avoid sharing publicly).
2. Share API request and response logs showing the exact payloads sent to FedEx.
3. Ensure temporary WordPress admin access is provided if requested, so the PluginHive team can observe plugin settings and replicate the issue directly.
4. If possible, create a staging or development site mirroring production with the REST API configured, allowing safe testing by support without impacting your live store.
5. Keep open communication for timely sharing of updates, fixes, or feedback from FedEx support escalations.

Does the WooCommerce FedEx Shipping Plugin with Print Label expose tracking numbers through the WooCommerce REST API?

No. The WooCommerce FedEx Shipping Plugin with Print Label does not expose tracking numbers through the WooCommerce REST API. Tracking numbers created by this plugin are managed internally and are not accessible via WooCommerce’s API endpoints. As a result:

• External systems like Fishbowl cannot retrieve or update tracking information using the WooCommerce REST API provided by this FedEx plugin.
• To enable API-based management of tracking numbers—including creating, updating, or syncing tracking info—an additional plugin (e.g., WooCommerce Shipment Tracking extension) must be installed and active.
• Without such a plugin, attempts to post shipment tracking data via the REST API will result in 404 errors because those API routes do not exist.

Can I access the Duties and Taxes invoices through the PluginHive FedEx plugin or FedEx API when generating shipments?

No. Duties and Taxes invoices are generated and provided by FedEx based on your FedEx account invoicing configuration and are not available via the PluginHive plugin or through FedEx API shipments. You must access these invoices directly through FedEx.com using your FedEx account credentials. The plugin supports rate calculation and label creation but does not provide access to these separate invoicing documents.

With the planned deactivation of the FedEx SOAP API on August 31, 2024, will the current PluginHive FedEx plugin registration process still work?

Yes, the current FedEx registration process used by the PluginHive FedEx plugin will not be affected by the expiration of the FedEx SOAP API on August 31, 2024. You can continue using the registration feature to connect your FedEx account as normal without disruption. However, note that the plugin will be updated to support the FedEx RESTful API in a future release planned for the fourth quarter of this year, which will fully replace SOAP API workflows. For now, the existing registration ensures uninterrupted FedEx services integration.

With FedEx moving from legacy Web Services (SOAP) to new FedEx REST APIs and the disablement of legacy services on August 31, 2024, do I need to do anything to ensure the new APIs are used in PluginHive's FedEx plugin? Do I need to re-register my FedEx account or provide my API key?

The latest version of PluginHive’s FedEx plugin includes a FedEx Compatible Solution that uses a simplified Registration process connecting your FedEx account via your FedEx Account Number and Billing Address. You do **not** need to use or enter a Web Service key and password in the plugin. Currently, the plugin does not require you to enter the API key you obtained from developer.fedex.com, as it does not have a field to input it.

1. Update the plugin to the latest version (version 6.0.0 or higher).
2. Complete the FedEx Registration process within the plugin using your FedEx account number and billing address. This replaces the older SOAP credential setup.
3. Continue using the plugin as normal; the plugin is designed to automatically support the current FedEx services and will be made compatible with FedEx’s REST API before FedEx completes their migration.
4. When the plugin fully supports RESTful APIs, you will be able to switch to that easily within the plugin.

For detailed step-by-step instructions on the Registration process, refer to this knowledge base article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

In summary, you do not need to re-register your FedEx account or manually input your FedEx API key at this time. Just ensure your plugin is updated and complete the registration using your FedEx account credentials as described above.

Will there be any service interruptions after August 31, 2024, if the FedEx plugin is currently not fully compatible with FedEx REST APIs?

Service interruptions can be avoided if the FedEx direct registration process has been completed within the plugin. This registration aligns with FedEx’s new requirements and ensures that shipping and tracking services remain functional after August 31, 2024, when FedEx discontinues the SOAP API endpoints. Users should verify that they have completed this process by following the steps outlined here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. Completing this registration is essential to maintain uninterrupted FedEx service through the PluginHive plugin.

Will the WooCommerce FedEx Shipping Plugin APIs be compatible with the new FedEx REST APIs after re-registration?

Yes. Once you complete the FedEx account re-registration using the updated WooCommerce FedEx Shipping Plugin version, all plugin APIs will be fully compatible with FedEx’s new REST APIs. This means no additional actions are required from your side after registration to ensure ongoing compatibility. The plugin handles all necessary API updates internally to provide seamless integration with FedEx’s latest technology.

Will the plugin notify me if we are using the old FedEx integration method?

The plugin does not explicitly notify you if you are using the old FedEx Web Services integration. However, you can verify your current integration by clicking on "FedEx Registration" in the plugin’s left toggle menu. If you see the new registration screen as shown in the provided guide, you are using the latest method. If you still integrated FedEx using Account Number, Meter Number, API Key, and Web Services Password, you are using the old method. It is important to update to the FedEx Compatible Solution before August 31, 2024, because FedEx will discontinue support for Web Services tracking, address validation, and postal code validation after that date.

Will the FedEx Web Services WSDLs disablement affect our website address verification or require us to update any APIs?

The current address verification process on your website will not be affected by the FedEx Web Services WSDLs disablement. The PluginHive team is already updating the plugin to use the new FedEx REST APIs to accommodate this change. At this time, no action or updates are required from your side. If any changes become necessary, you will be informed promptly.

Will the FedEx web services migration to API be integrated into the PluginHive FedEx plugin, or will web services still be supported?

FedEx has migrated to using REST APIs for their services. The PluginHive FedEx plugin is updated to work with this REST API integration. To ensure smooth functionality with the plugin, you need to register your FedEx account properly. You can complete this setup process by following the detailed instructions provided in the PluginHive knowledge base article here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. This will enable the plugin to communicate correctly with FedEx’s current API system.

Will the existing PluginHive FedEx plugin functionality remain intact after August 31, 2024, when FedEx stops supporting SOAP Web Services? What does the certification process mean for users?

Yes, the existing plugin functionality will remain intact beyond August 31, 2024, and will continue to operate normally using the current Registration model. Certification refers to PluginHive’s internal process of working with FedEx to ensure full compatibility with the FedEx REST APIs. This process does not affect user experience or plugin functionality. There will be no expiration or loss of features within the plugin because of this certification.

Will the current SOAP functionality continue to work after August 31, 2024, or is the FedEx REST API required immediately? What should users expect in terms of changes?

The current SOAP-based functionality will continue to work after August 31, 2024, so there is no immediate need to switch to the REST API. The REST API integration primarily supports adding new features and future compatibility. For users who have already registered their FedEx account through the plugin, no immediate action is required. PluginHive will provide straightforward migration steps once the plugin is fully compatible and certified with the FedEx REST API. This migration will be simple and will not cause any data loss.

Will PluginHive update the FedEx plugin to support FedEx’s new REST API?

Yes, PluginHive is aware of FedEx moving to REST API and is actively working on updating the FedEx plugin to support it. Although there is no exact estimated time of arrival (ETA) for the release, the PluginHive team will notify users once the REST API integration is completed. When the update is available, detailed steps to implement and use the new REST API will also be provided.

Will PluginHive meet the FedEx REST API migration deadline, or has FedEx extended the deadline?

PluginHive plans to complete the REST API integration before FedEx fully migrates to the new system. While the exact timeline cannot be guaranteed, PluginHive will keep users updated on progress. The current FedEx Compatible Solution ensures your shipping functionality continues reliably during the interim.

Why was the FedEx REST API integration delayed beyond the initially promised timeline, and how is PluginHive addressing customer communication during this period?

The FedEx REST API integration release has been delayed beyond the initially communicated ETA due to the extended approval process and finalization of technical changes after FedEx certification. PluginHive acknowledges this delay and is actively working to complete the changes to deliver a fully certified and functional solution. To improve transparency and customer support, PluginHive has appointed a primary contact (Keerthi) who will provide timely updates and respond to queries directly. Customers are encouraged to reach out directly via email to receive ongoing progress information. PluginHive commits to informing customers as soon as the solution is available for use. This approach ensures that while the implementation is ongoing, customers remain aware of progress and timelines, addressing concerns caused by earlier communication gaps.

Why might the PluginHive website appear misleading regarding the use of REST API in the FedEx shipping plugin?

The PluginHive website mentions REST API integration because the plugin includes Beta support for FedEx’s RESTful APIs as part of an ongoing migration effort. This Beta feature is available in recent versions but is not yet the default or exclusively used API connection. The SOAP API remains active and is used in production until official FedEx certification of the REST integration is complete. Communicating about REST API included in changelogs or product pages is meant to keep customers informed of upcoming capabilities, not to imply the plugin is already fully using REST exclusively. The transition is carefully managed and publicly communicated to avoid surprises, but some users may perceive this status as misleading if they expect full REST implementation immediately. PluginHive support emphasizes upfront disclosure about the current SOAP usage and migration status to preserve transparency and trust.

Why is there no "Generic API Setting" option in the PluginHive FedEx plugin, and how should I configure the plugin instead?

The "Generic API Setting" option is no longer applicable because the PluginHive FedEx plugin is now fully compliant with FedEx’s Compatible Registration process for account connection. Consequently, the API settings have been removed from the General Settings tab. To configure your FedEx account with the plugin, follow the instructions specific to the Compatible Registration process detailed in this article section: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. Use this process instead of searching for generic API settings. If you face any difficulties during setup, you can reach out to PluginHive support for help.

Why is the shipping functionality not working for shipments within Panama, even though it works for the rest of the world and the website origin is Panama?

FedEx does not support intra-country shipments within Panama, meaning shipping services are only available for international shipments originating from Panama, not for shipments solely within the country. This limitation is enforced by FedEx itself and is not controlled or adjustable via the WooCommerce Shipping Plugin for FedEx. Therefore, shipping within Panama cannot be enabled through the plugin.

Why is the API Key Status showing as "Deactivated" after entering the correct key and product ID, and how can I fix it?

1. Navigate to the FedEx Activation page in your plugin settings.
2. Locate the "API Key Deactivation" section and enable the "Deactivate API Key" option, then save the changes.
3. Go to your account at PluginHive.com, access "My Account" > "API Keys," and delete any previous activations of the license key linked to your product.
4. Return to your plugin setup and deactivate the FedEx plugin. Then, reactivate the FedEx plugin to refresh the connection.
5. Go back to the FedEx Activation page, choose "API Key Activation," enter your license API key and Product ID (you can find these under PluginHive.com > My Account > API Keys), and click "Save Changes."

Why does the WooCommerce FedEx Shipping Plugin not allow external updates to tracking numbers via the WooCommerce REST API, and how can I enable that functionality?

• External systems cannot retrieve or update FedEx tracking numbers through WooCommerce API endpoints provided by this plugin.
• Attempts to POST tracking data to WooCommerce endpoints without additional support will fail with errors like “No route was found matching the URL and request method.”

1. Install an auxiliary plugin such as the **WooCommerce Shipment Tracking** extension, which adds shipment tracking API endpoints to WooCommerce.
2. Configure the shipment tracking plugin according to its documentation to enable API interactions.
3. Use the shipment tracking plugin’s API endpoints to push tracking details into WooCommerce orders programmatically.

Without such a shipment tracking plugin that extends WooCommerce’s API, external software cannot update tracking numbers via REST API calls. This is necessary for syncing tracking data created outside WooCommerce (e.g., from Fishbowl).

Why does the PluginHive plugin show as deactivated after entering the API key and code, and how can I reactivate it?

The plugin showing as deactivated after entering the API key and code indicates that the license activation was not successful. To resolve this, you need to contact PluginHive support with your site details so their team can activate the license remotely from their end. Once support confirms the license is activated, refresh the plugin status in your WordPress dashboard. The plugin should then show as active, allowing you to update and use it normally. Always confirm with support once the activation is complete to ensure proper functionality.

Why does the PluginHive FedEx plugin license API key deactivate automatically, and how can I prevent this from happening?

1. Ensure that the PluginHive FedEx shipping plugin remains active at all times within your WordPress admin plugins page. Do not deactivate or delete the plugin.
2. Avoid any scheduled tasks or external processes that might deactivate or update the plugin inadvertently.
3. Regularly monitor your plugin status and license activation from the plugin’s License or Activation page.
4. If the issue persists without any intentional deactivation, consider enabling WordPress debug logs to track any plugin or server-level triggers that might cause deactivation.
5. Contact PluginHive support with relevant site access and logs if you cannot identify the cause, so they can investigate further.

Maintaining continuous plugin activation is key to ensuring the license API key remains active and your FedEx shipping functionality is uninterrupted.

Why does the plugin show as deactivated after entering the API key and code, and I am unable to update it due to this deactivation?

If the plugin shows as deactivated after entering the API key and code, it indicates that the license has not been activated successfully. In this case, PluginHive support can activate the license from their end. You should contact PluginHive support with your site details so they can log in and activate your license remotely. Once the license is activated by the support team, you should refresh your plugin status, and the plugin should no longer be deactivated, allowing you to update and use it properly. Always confirm with the support team once activation is complete.

Why does the API key revert to the old number and not activate after I enter and save the new one?

1. Double-check that you are entering the correct API key and Product ID from your PluginHive account.
2. If the problem persists, PluginHive support can activate the license for you if you provide your WordPress admin credentials.
3. Note that two-factor authentication may prevent support from accessing your site; temporarily disable 2FA to allow support to log in and activate the license on your behalf.

Why does my renewal notification link not work, and do I need to set up the API again after purchasing the plugin renewal manually?

The renewal notification link does not work because your previous purchase was not under the Subscription model, so the plugin license does not auto-renew automatically. Currently, all PluginHive plugins are sold under a Subscription model, but for your renewal, you need to manually purchase the plugin again. After purchasing manually, you will receive a new API key, which must be updated manually on your site. This is a one-time manual process. From the next year onward, the license will auto-renew without the need for manual purchases or API key updates.

Why does activating the API key on my staging site deactivate it on my production site and vice versa, even though the API keys are different but have the same Product ID?

The plugin license activation is tied to the site URL and API key. Since you have two licenses (one for staging and one for production), they should be activated separately with their respective API keys. However, resolving conflicts like one site deactivating the other requires support team intervention to check your site URLs and API key details. Please provide your WordPress admin URLs and API key details to the PluginHive support team for manual activation to avoid overlap or conflicts.

Why do no shipping options show up after updating the PluginHive FedEx plugin and entering a new API key, accompanied by an error saying the subscription needs renewal though I just purchased it?

1. Retrieve the new "Product API Key" and "Product ID" from your PluginHive account under My Account → API Keys.
2. Go to your website’s WordPress Dashboard → FedEx license activation page and deactivate then reactivate the license using the new API key and Product ID.
3. After license activation, go to FedEx Registration inside the plugin and re-register your FedEx account.
4. Refresh your website’s cart/checkout page to verify shipping rates display correctly.

Why do I see the FedEx SOAP registration page instead of the REST registration page in the PluginHive plugin, and how can I enable the REST API registration screen?

1. Update the plugin to version 8.0.2 if not already done.
2. Once updated, the plugin will automatically show the FedEx REST API registration page instead of the SOAP page.
3. Note that with FedEx REST API, you no longer need to enter the FedEx Meter Number; only the FedEx Account Number and API credentials are required.

Why do I see the FedEx SOAP registration page instead of the REST registration page in the PluginHive plugin, and how can I access the REST API registration options?

1. Ensure you are using the latest version of the PluginHive FedEx plugin. The REST API registration feature is available starting from version 8.0.2.
2. If you are on the correct version but still see only the SOAP registration page, update the plugin to the latest version to enable the REST registration interface.
3. With the FedEx REST registration, you do not need to provide a Meter Number; only a FedEx account number and related details are required.
4. After updating, the REST API registration page will replace the SOAP registration form you were previously seeing.
5. This update will allow you to register using REST API and use related features, including testing REST functionality on your staging environment before moving to production.

Why do I see the FedEx Soap registration page instead of the expected FedEx REST registration screen in the PluginHive plugin, and how do I get the REST registration option?

To see the FedEx REST registration screen, you need to use the latest version of the PluginHive plugin. In version 8.0.2, the REST API registration option is included. If you are currently seeing the FedEx SOAP registration page, please confirm that you have updated to version 8.0.2 or later. Once updated, the plugin will show the REST registration screen, allowing you to register using FedEx REST API credentials instead of the legacy SOAP method.

Why do I see the FedEx SOAP registration form instead of the REST registration screen in the PluginHive plugin, and how can I access REST API setup?

1. Confirm that your plugin is updated to version 8.0.2 or newer.
2. Once updated, access the plugin’s FedEx settings. The interface will then show the REST registration screen instead of the SOAP form.
3. Note that with FedEx REST API integration, you no longer need to provide a Meter Number; only your FedEx Account Number and related details are required.

Why do I see the FedEx SOAP registration form instead of the REST API registration screen in the PluginHive plugin, and how do I get the REST registration option?

The FedEx SOAP registration form you are seeing is the default form for older API integration. To access the REST API registration screen in the PluginHive plugin, you must be using version 8.0.2 or later. Once you update to or confirm you have version 8.0.2, the plugin will provide the REST API registration option in the FedEx setup. The REST registration form replaces the need for a Meter number; instead, you only need your FedEx account number and associated details. Make sure your plugin is updated to 8.0.2 or newer to see and use the REST API integration screen.

Why do I see a FedEx SOAP registration form instead of the expected FedEx REST registration screen in the PluginHive plugin, and how can I enable the REST API registration?

This occurs because the version of the plugin you are using may not have fully switched to showing the FedEx REST registration by default. To resolve this:

1. Confirm you are using the latest plugin version, which is 8.0.2 or higher.
2. If you are not on version 8.0.2, update the plugin to this version.
3. Once updated, the plugin will display the FedEx REST registration screen instead of the SOAP registration page.
4. Note that with FedEx REST API registration, you do not need a Meter Number; only the FedEx account number and other FedEx account details are required.
5. You can test the REST API functionality in your staging environment safely before migrating all settings to your live site.

Why do I not receive a response from the FedEx API when adding 4 or more packages, and how can I resolve the issue?

1. Ensure all FedEx shipping services are enabled in the PluginHive FedEx plugin settings.
2. Verify on the official FedEx website that the shipment—from the ShipFrom address to the ShipTo address with the given package dimensions and weights—is serviceable by FedEx.
3. Enable “Debug Mode” in the plugin settings to capture logs during the checkout process when multiple packages are added.
4. If problems persist, generate and submit a Diagnostic Report from the plugin’s "Help & Support" page referencing your case for further analysis.

Why do FedEx shipping rates not appear on the WooCommerce checkout page when using the FedEx REST API, and how can the "Account Number Mismatch" error be resolved?

1. Double-check that your FedEx account and Payor account details are correctly and identically configured in the plugin settings.
2. Recognize that this limitation is due to the beta status of the REST API integration and the lack of support for sending required nodes like the Child Key.
3. PluginHive support can escalate the issue with FedEx if provided with live account details, billing address, and validation OTP or WordPress admin access to replicate and troubleshoot the problem directly.
4. Until the REST API integration is stable and supports all required FedEx data fields, switch your FedEx plugin settings to use the SOAP API integration, which is more stable, avoids this error, and reliably shows shipping rates.

Why do FedEx shipping rates in the PluginHive FedEx shipping plugin’s SOAP API connection not match my FedEx account rates, and how can I fix this discrepancy?

1. In the plugin settings, set the **Request Type** to **Account Rates**—this configures the plugin to request rates based on your specific FedEx account pricing.
2. Verify all shipment details carefully:
3. Review the **Insured Value** setting in the plugin configuration; this parameter can influence shipping costs and should reflect your declared shipment value. Note: When asked about “Insurance” settings, this refers to the same field sometimes labeled “Third Party Insurance” in the plugin.
4. If rates still do not align after these checks, compare plugin rates to the FedEx Rate Finder tool: obtain a complete screenshot of the rates from https://www.fedex.com/ratefinder/home for the same shipment parameters.
5. Generate a **Diagnostic Report** from the plugin’s **Help & Support** page and submit it to PluginHive support along with the FedEx screenshot. This allows PluginHive to analyze plugin behavior versus FedEx live rates and assist further.

Why do FedEx requests logged in PluginHive v7.x still appear in SOAP XML format even though FedEx is moving to REST APIs?

Although FedEx is deprecating SOAP APIs for tracking, address validation, and postal code validation, core shipping rate and shipment requests are still supported via SOAP until the FedEx REST API integration completes certification. PluginHive’s current plugin version continues using SOAP for shipping function calls, which is why logs show SOAP XML. No user settings changes are needed. The plugin will switch to REST API after official FedEx certification and release of an updated plugin version.

Why do FedEx requests logged by PluginHive v7.x still show SOAP XML format while FedEx is moving to REST API?

• No plugin setting changes are needed on your end at this time.
• SOAP XML requests will continue to be visible in logs.
• The transition to REST API will occur after official FedEx certification and PluginHive release.

Your shipping rate and label functionality remain unaffected during this interim.

Why do FedEx requests in the PluginHive v7.x logs appear in SOAP API XML format when FedEx is deprecating SOAP and moving to REST API? Do I need to change any settings to use REST API JSON structure?

The PluginHive plugin currently uses SOAP API for shipping rate and shipment requests, as FedEx is only deprecating SOAP APIs related to tracking, address validation, and postal code validation. The core shipping functions your plugin relies on are still supported via SOAP until FedEx completes their certification of the REST API solution. PluginHive has already developed the REST API integration and is awaiting FedEx certification before the new update is rolled out. Therefore, no additional setting changes are needed now; your plugin continues to function normally with SOAP for shipping rates and shipments until the updated REST API version is released.

Why do API keys and some plugin settings disappear or not show in the FedEx plugin’s settings page?

With the enhanced account integration process, API keys created by the plugin are hidden for security reasons and are intentionally not displayed persistently on the settings page. Due to caching, these may appear briefly and then disappear. This is normal behavior and does not indicate a problem. You can trust that the plugin securely stores the keys internally. If rates are showing correctly for configured countries, the API connection is active.

Why did PluginHive change their licensing policy to restrict usage to one domain at a time when previously I could use it on production and staging simultaneously?

The licensing change correlates with FedEx’s migration from SOAP-based WSDL APIs to RESTful APIs, which employ OAuth token-based authentication for enhanced security. FedEx requires each integration to be registered individually per domain to ensure secure, isolated access and prevent misuse. This upgrade also aligns with FedEx phasing out older services like Address Validation and Tracking. As a result, PluginHive updated their licensing to comply with FedEx’s new security standards, requiring separate licenses per domain to maintain security, data integrity, and compliance.

Why can't I add FedEx API production/secret keys in the PluginHive FedEx plugin, and how do I properly set up the FedEx connection on my live site?

1. Navigate to the settings page of the FedEx shipping plugin in your WooCommerce admin area.
2. Use the provided instructions in the official PluginHive knowledge base guide for FedEx registration: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number
3. Complete the Auto Registration process as outlined, which will automatically generate the necessary credentials and link your store with FedEx.
4. Avoid trying to manually enter FedEx API keys, as the plugin does not require them and fields for manual entry are disabled as part of this improved, automated workflow.

Why are the FedEx key input fields hidden or disabled by JavaScript after completing the FedEx direct registration through the plugin?

Once the FedEx direct registration process is completed, the FedEx credential key fields in the plugin settings are intentionally hidden and disabled to prevent manual modification, as the account is directly linked with the plugin backend. This is by design to maintain secure and consistent integration. Do not attempt to modify these fields manually or disable the hiding styles via browser Developer Tools. Instead, if you need to update credentials or resolve issues, re-register your FedEx account through the plugin’s FedEx Registration settings to refresh the connection.

Why are shipping labels not being generated through the FedEx Restful API in the PluginHive FedEx plugin?

The current PluginHive FedEx plugin does not support FedEx Restful APIs, which is why shipping labels are not generated through that method. Instead, the plugin uses a FedEx Compatible Registration process that connects your FedEx account directly using your FedEx Account number and billing address. This method does not require sending shipping labels to FedEx for verification, allowing you to view services and print labels without API integration. The plugin will gain FedEx Restful API compatibility in a future update, but for now, using the registered FedEx account connection is the supported workflow.

Why are no shipping options appearing when I click "Calculate Cost" after renewing the plugin and reactivating with a new API key?

1. Deactivate the current plugin license by navigating to the FedEx Registration section > License Activation.
2. Reactivate the license by re-registering your FedEx account credentials within the plugin settings.
3. After reactivation, try clicking "Calculate Cost" again to confirm that shipping options now display correctly.

Why are my FedEx shipping prices not showing on my website even after updating the latest API key in WooCommerce settings?

1. Go to the General Tab of the PluginHive plugin settings in your WordPress dashboard.
2. Enable the "Debug Mode" option to capture detailed logs.
3. Check if the shipping rates appear on your website at checkout or cart after enabling debug mode.
4. Next, navigate to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report as instructed on the page. This report will collect the necessary data to analyze the issue further.

Why are FedEx shipping rates not showing on the WooCommerce checkout page after switching to the FedEx REST API?

1. WooCommerce has removed shipping rate estimates at the Cart level in recent updates, which might impact visibility of rates depending on your setup.
2. Using a block-based checkout page can affect how shipping options are rendered if the plugin or theme does not fully support it.
3. The REST API integration for FedEx is still in beta and may have stability issues.
4. The likely cause includes an "Account Number Mismatch" error in the FedEx API logs, meaning the payment type "SENDER" requires the ShippingChargesPayment Payor Account Number to match the shipper account number. Correcting this in your FedEx account settings is essential.

Why are FedEx shipping rates not loading after renewing my subscription and activating the plugin with a new API key?

If FedEx shipping rates are not loading even after renewing your subscription and activating the plugin with a new API key, follow these steps to resolve the issue:

1. Go to the plugin settings and enable the “Debug Mode” option.
2. Reproduce the issue by checking the shipping rates on the cart or checkout page.
3. After reproducing the issue, navigate to the "Help & Support" page within the plugin settings and submit a Diagnostic Report with reference ticket number 330079 as instructed on the page.
4. Upon reviewing the diagnostic report, if you see a "Forbidden" error in the logs, this indicates that your plugin license activation is not properly linked to the FedEx Account registration process.
5. To fix this, go to the FedEx Shipping plugin section and select License Activation.
6. Deactivate the current plugin license.
7. Re-activate the license by re-registering your FedEx account again through the license activation page.
8. After completing re-activation and registration, the shipping rates should load correctly on your store.

Following these steps ensures your plugin license is fully authorized with FedEx, allowing shipping rates to be retrieved properly.

Why are FedEx shipping rates not displaying on my WooCommerce store after API registration, and how can I troubleshoot this?

1. Account Number mismatch between your FedEx account credentials and plugin settings.
2. Incorrect API integration type (such as REST vs. SOAP) causing compatibility errors.
3. Plugin or WordPress compatibility issues resulting in fatal errors that stop rate generation.

Why are FedEx shipping rates not being returned when using the REST API integration with the FedEx WooCommerce Shipping plugin?

The failure to return shipping rates using the REST API integration is caused by an issue with FedEx REST API registration on FedEx’s side. This prevents the plugin from successfully retrieving rates. The PluginHive technical team is actively working with FedEx to resolve this registration issue. Until then, the REST API integration remains unstable and may not return shipping rates. To ensure consistent shipping rates, it is advised to switch to the SOAP connection, which is stable and fully functional. This is the recommended workaround while waiting for the REST API registration problem to be fixed by FedEx.

Why are FedEx shipping costs not populating for customers at checkout even though the correct plugin and API key are installed and addresses are entered correctly?

1. Navigate to your WordPress dashboard.
2. Go to FedEx Registration > License Activation.
3. Deactivate the current plugin license key.
4. Reactivate the license key by entering your API key and Product ID again.
5. After license re-activation, go to FedEx Registration > Registration and re-register your FedEx account within the plugin.
6. Test shipping cost calculation again by entering correct addresses at checkout.

Why am I still receiving notifications from FedEx about transitioning away from SOAP despite using PluginHive version 7.0.6?

FedEx is not fully migrating all services to REST API at this time. Only specific services like Tracking and Address Validation are being transitioned to REST API, which require a new registration process with FedEx. If you are still using the FedEx Meter number and web services keys, those services will continue to work even after August 31st, but you will keep receiving notifications about the transition. To stop these notifications and ensure full compatibility, you need to complete the new FedEx Registration process within the plugin. You can verify if this is done by navigating in your WooCommerce site to the FedEx Registration section. For detailed instructions, refer to the PluginHive knowledge base article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. If registration is not completed, assistance is available to guide you through the process.

Why am I seeing the FedEx SOAP registration page instead of the REST registration page in my PluginHive plugin, and do I still need a Meter Number if I activate the REST API for FedEx?

If you are seeing the FedEx SOAP registration page instead of the REST registration page, ensure that you are using the latest version of the PluginHive plugin, which is version 8.0.2 or later. The REST registration options are available only in this updated version. Regarding Meter Number usage, once you activate the FedEx REST API, you no longer require the Meter Number. Instead, you will need to use your FedEx account number and related account details for registration and API integration. You can safely perform testing of REST API features on your staging site before deploying them to your live site.

Why am I seeing a warning message that the license is expiring soon even though the API key expiration is set for 2025?

1. Log in to your plugin settings.
2. Confirm and update the API key with the latest valid key you have.
3. Save the changes.
4. Clear your platform cache to ensure the new settings take effect.

Why am I seeing a "migration failed" error after updating from PluginHive version 3.0.5 to version 7.x, and how can I fix it?

The "migration failed" error occurs because you are upgrading from a very old plugin version (3.0.5) that used the SOAP API to a much newer major version (7.x) that uses REST API. To resolve this issue, follow these steps:

1. Deactivate the plugin on your site.
2. Clear your website cache and browser cache.
3. Reactivate the plugin.

This process usually clears the migration error message. If the error persists or you face other issues with the latest plugin version, reach out to PluginHive support for assistance.

Why am I receiving the message "No shipping options were found for Maple Grove, MN 55330" when adding heavy items after switching my FedEx Plugin from SOAP to REST?

This issue could be related to how the FedEx REST API handles freight quotes for heavier items differently than the SOAP API. To diagnose and resolve this problem, follow these steps:

• Go to the General Tab of the FedEx Plugin settings.
• Turn on the "Debug Mode" option to capture detailed logs.

2. Reproduce the Error: – Attempt to create a shipping quote with the heavy item that triggers the "No shipping options were found" message.

• Navigate to the "Help & Support" page within the plugin settings.
• Follow the instructions on that page to generate and submit a Diagnostic Report.

Why am I receiving an email about license or API key issues despite my next payment being set to a future date, and why has the current API been deactivated without notification?

The email you received is an auto-generated message that can be disregarded as your license is active until the specified future date (e.g., Feb 8, 2025). The API key deactivation occurs when the plugin itself is deactivated because deactivating the plugin also deactivates the license. This process is under your control; PluginHive does not deactivate the plugin from their end.

1. Navigate to the FedEx Shipping Activation page in your plugin.
2. Go to the API Key Deactivation section, enable the "Deactivate API Key" option, and save changes.
3. On PluginHive.com, visit My Account → API Keys, and delete any previous activation of the license key if present.
4. Deactivate the FedEx Shipping plugin from your WordPress dashboard.
5. Reactivate the FedEx Shipping plugin.
6. Return to the FedEx Shipping Activation page, go to API Key Activation, and re-enter your license API key and Product ID.
7. Click Save Changes.

Following these steps should resolve the issue with the license and API key activation.

Why am I not seeing FedEx shipping rates even after renewing the PluginHive FedEx plugin and activating the new API key?

1. Deactivate the plugin license from the FedEx Shipping → License Activation section in your WooCommerce admin.
2. Update the FedEx plugin to the latest version (at least version 7.1.5).
3. Reactivate the plugin license and re-register your FedEx account within the plugin settings. This step is necessary to link your license with FedEx correctly.
4. Ensure that the billing and shipping addresses in the plugin settings exactly match the addresses on your FedEx account to avoid errors during registration.
5. If you encounter an "Invalid Billing Address" error during re-registration, verify the billing address details directly from your FedEx account or invoice and update the plugin settings accordingly.
6. Once re-registration succeeds with verified address and account details, FedEx rates should start showing on the cart and checkout pages.

Why am I not seeing any shipping options in my WooCommerce cart after updating all plugins, themes, WordPress, and WooCommerce on my staging site without activating the FedEx API Key?

When the FedEx API Key is not activated on the site, the plugin will not retrieve live shipping rates. Therefore, no shipping options will be displayed in the cart regardless of the shipping address entered. Activating the API key and license is required for the plugin to fetch and display shipping rates.

Why am I getting the "Account Number Mismatch" error when generating FedEx shipping rates using the REST API, and how can I resolve it?

1. Verify that the FedEx account number entered in the plugin matches exactly with your FedEx shipper account number.
2. If the payment type is SENDER, ensure the payor account number for shipping charges is the same as the shipper account number in your FedEx account details.
3. If the issue persists with the REST API integration, it is recommended to re-register your FedEx account using the SOAP-based integration within the PluginHive FedEx plugin:

Why am I getting an "Account Number Mismatch" error when using the FedEx REST API for shipping rates, and how can I resolve it?

The "Account Number Mismatch" error occurs because, when the payment type is set to "SENDER," FedEx requires that the ShippingChargesPayment.Payor.AccountNumber matches the shipper’s registered FedEx account number. In your request, ensure that the actual FedEx account number is correctly injected into both the "accountNumber.value" and the payor's account number fields rather than a placeholder string. The PluginHive plugin automatically replaces your registered FedEx account number before sending the rate request; however, this mismatch error may sometimes be caused by FedEx expecting the payor account number in a specific format or API node not fully documented. If you encounter this in production, coordinate with PluginHive support and FedEx to verify your account details and request structure. In the meantime, do not revoke any temporary access provided for investigation and verify your FedEx account numbers used for shipping and billing are consistent.

Why am I getting a "forbidden" error from the PluginHive FedEx API endpoint with a message saying "You are not authorized for registration," and how can I resolve it?

1. Deactivate and then reactivate your PluginHive license.
2. Completely clear your website’s cache and any transient data related to the PluginHive plugin.
3. Retry the FedEx account registration process after the cache is cleared.
4. Ensure all FedEx account details, such as street address and company name, conform to length limits (generally not exceeding 25-30 characters).
5. Enter the phone number without any country code prefix.
6. Verify that the shipping address you enter exactly matches the billing address on your official FedEx shipment invoices.

Which FedEx API version does the PluginHive WooCommerce FedEx Shipping plugin currently use, and what should I consider regarding RESTful vs. SOAP APIs?

• The plugin does not use FedEx RESTful API for shipping functions.
• All billing address validation and shipping transactions occur through FedEx’s SOAP Web Services API.
• If FedEx support references RESTful API logs with no errors found, it is expected because the plugin doesn’t use that API yet.
• PluginHive plans to update the plugin to support FedEx RESTful API in the future, but currently, integrations rely on SOAP Web Services.

Which FedEx API key should I use in the PluginHive FedEx plugin—test or production?

If you have completed FedEx’s direct account registration process with PluginHive, you must use the **Live (Production) API key**. The plugin requires Live mode to function properly after direct registration. The test API key or sandbox environment will not work correctly for live shipping rates or label generation. Therefore, always ensure your API mode is set to Live in the plugin settings.

Where do I enter the new License API key in the PluginHive FedEx shipping plugin?

1. Log into your WordPress admin panel.
2. Navigate to **Settings → FedEx Activation**.
3. Enter the License API key you received after purchasing/renewing the license.
4. Save and activate the license.
5. Refresh your plugins page and update the FedEx plugin to the latest version.
6. After successful activation, test the checkout page to confirm delivery options are showing.

Where do I enter the API key to reactivate the PluginHive FedEx plugin if it is down and no shipping options are showing in WooCommerce cart?

1. Enable Debug Mode in the plugin settings.
2. Reproduce the issue in your WooCommerce cart.
3. Submit a Diagnostic Report from the Help & Support page in the plugin settings referencing your support ticket number.
4. The problem is often due to license activation not being linked with FedEx account registration. Proceed to deactivate and then reactivate your plugin license.
5. Update the plugin to the latest version (e.g., 8.0.2).
6. Re-register your FedEx account within the plugin to complete the activation process.

Where can I find a guide to register and configure the FedEx REST API for the PluginHive WooCommerce FedEx Shipping Plugin?

A detailed, step-by-step manual for FedEx REST registration and plugin setup is available at:

Set Up WooCommerce FedEx Shipping Plugin

When will the WooCommerce FedEx plugin with the REST API update (version 8.0.0) be available?

The WooCommerce FedEx Shipping Plugin version 8.0.0, featuring Beta support for FedEx’s RESTful APIs, will be available before the end of next week. The release was initially planned for June 10, 2025, but was slightly delayed to early the following week. You will be notified as soon as the update is live.

What will the migration process look like when PluginHive moves fully to FedEx REST APIs, and will there be any data loss or disruption?

PluginHive will communicate detailed migration steps once the plugin is certified and ready for REST API usage. The migration is designed to be simple, user-friendly, and will not result in any loss of data or interruption of service. Users can anticipate a seamless transition guided by PluginHive’s instructions.

What type of FedEx API integration does the current PluginHive FedEx plugin use for shipping rate calculation?

The PluginHive FedEx plugin currently uses the SOAP API integration for shipping rate calculations. Although PluginHive is in the process of migrating the plugin to the REST API and awaiting FedEx certification, at present the plugin operates via the SOAP API. It integrates directly with your FedEx account number without requiring REST API credentials such as child keys or bearer tokens.

What troubleshooting steps should I follow if the FedEx plugin is not generating labels or working as expected despite using the latest API key?

1. Confirm that the API key used is the latest and active one from your PluginHive account.
2. Verify the plugin license status on your WordPress site; the license must be active for proper plugin operation.
3. Check plugin settings for correct API credentials and ensure no typos or extra spaces.
4. Review product shipping settings, specifically FedEx Shipping Details for declared values and shipping options.
5. Test by creating a new order and attempting to generate a label to isolate if the issue is order-specific.
6. Clear any caching plugins or server caches that might interfere with plugin operations.
7. Enable plugin debug logs (if available) to capture errors during label generation.
8. Contact PluginHive support with debugging information for advanced troubleshooting.

What steps should I take to re-register my FedEx account in the PluginHive FedEx WooCommerce plugin using SOAP integration?

1. Login to your WordPress admin dashboard.
2. Navigate to the FedEx Shipping settings section.
3. Select the Registration tab or module.
4. Locate the option to either disconnect the current REST API registration or directly select the SOAP API method.
5. Choose to reconnect or register with the SOAP-based integration.
6. Enter your FedEx account credentials and necessary details as requested, ensuring all information matches your official FedEx shipper account.
7. Save the settings and test to confirm that FedEx shipping rates appear correctly on the cart and checkout pages.

What steps should I take if my FedEx API history or connection shows "expiration date: when cancelled" and rates are not returning?

1. Confirm that your FedEx API Production Key, Secret Key, and Account ID are correctly entered and valid in the plugin settings.
2. Re-register your FedEx account credentials in the plugin, especially if you have activated a new license or created a new FedEx account after subscription lapses.
3. Verify that the correct API services are enabled (Rates and Transit Times API, Address Validation API, Freight LTL API, etc.) on FedEx Developer Portal.
4. Check that the plugin license is activated and linked to your current FedEx account to allow proper API authentication.

What steps should I take if I want to participate in testing the PluginHive FedEx REST API plugin in a live production environment?

1. Confirm your interest with PluginHive to receive instructions.
2. Provide your FedEx Account Number and Billing Address.
3. Share a recent FedEx shipment invoice if available; if not, opt for OTP alternative authentication.
4. Provide your preferred time and time zone for OTP verification and your contact number.
5. Complete the OTP verification when requested.

What steps should I take if I repeatedly have to confirm the “YES” consent and migration prompts during FedEx registration in PluginHive before being able to enter shipping information?

1. Clear all PluginHive-related options and transients from your WordPress database to reset plugin state.
2. Fully deactivate and reactivate the PluginHive plugin to refresh license and configuration.
3. Ensure you have accepted all terms correctly and followed prompts without interruption.
4. Verify that your license status is showing as “Activated” in PluginHive’s settings.
5. Contact PluginHive support to check for any backend issues with your account state that may cause repeated prompts.
6. Only after these steps succeed should you proceed to enter shipping details and validate your account.

What steps should I take if I continue to encounter the same shipping label generation issue after updating the plugin and switching to REST API?

1. Ensure the plugin is updated to the latest version (8.0.0 or above).
2. Perform REST API registration on the live site as per the provided guide.
3. Enable the “Debug Mode” option from the plugin settings to capture detailed logs.
4. Reproduce the issue by attempting to generate the shipping label again for the problematic order.
5. Go to the "Help & Support" page within the plugin settings and submit a Diagnostic Report to PluginHive Support, including the reference ticket number provided.
6. Await further investigation and guidance from the support team based on the diagnostic data.

What steps should I take if I cannot find any API keys under my current account email though we had previous purchases linked to another email?

1. Identify the correct account email that was originally used to purchase the plugin (e.g., [email protected]).
2. Log in using that original email account to locate the existing API keys.
3. Check the license status associated with that account to ensure it is still active.
4. If access to that account is unavailable due to personnel changes, you will need to purchase a new license under your current credentials to generate a new API key and activate the plugin.

What steps should I follow to switch from using the FedEx SOAP integration to the FedEx REST API integration in the PluginHive WooCommerce FedEx Shipping Plugin?

If you are already using the FedEx SOAP integration, there is no separate or complicated process to switch to the REST API integration. You can simply proceed by selecting the option "Connect to Rest" within the plugin settings and continue with the REST API integration setup as per the provided instructions. Ensure that you review and accept any disclaimers or limitations mentioned regarding the REST API version. For detailed setup instructions, refer to the official knowledge base article here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST

This process allows you to transition smoothly without needing to uninstall or deactivate the SOAP integration first. Just update your settings to connect with the REST API and complete the configuration steps outlined in the documentation.

What steps should I follow to register for FedEx REST API support in the PluginHive FedEx Shipping Plugin?

1. Access the step-by-step setup guide provided by PluginHive here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST
2. Complete the FedEx REST API registration by creating credentials via FedEx Developer Portal as instructed.
3. Enter the obtained credentials into the PluginHive plugin settings.
4. Upon successful registration, the plugin will automatically send your Admin Store URL to the PluginHive Support Team to facilitate smoother onboarding and faster issue resolution.
5. Test your setup by creating test shipments and verifying rate requests to ensure REST API communication is working correctly.
6. For any issues during registration or setup, contact PluginHive support for assistance.

What steps should be taken if facing difficulties during FedEx API registration in the WooCommerce FedEx Plugin by PluginHive?

1. Collect and verify all your FedEx account details and credentials.
2. Create WordPress admin access for [email protected] and share securely with PluginHive support.
3. Clear your browser cache to avoid conflicts and retry the registration process.
4. Share your registration process details, including validation method and any error messages, with PluginHive support.
5. Be prepared for a detailed troubleshooting session via Zoom if requested, with your webmaster or technical resource available for assistance.
6. Follow any update or fix implemented by PluginHive, and retest the API registration promptly as advised by their support team.
7. Confirm resolution by accessing and using FedEx features via the plugin without errors.

What steps do I need to follow to switch the PluginHive FedEx shipping plugin from the SOAP API to the REST API for FedEx, and is there anything else required besides updating the plugin and completing the registration process?

1. **Update the Plugin**: Ensure you are using the latest version of the PluginHive FedEx shipping plugin. The updated plugin includes a FedEx-compatible registration solution that allows you to connect your FedEx account via the account number and billing address without needing the Web Service key and password.
2. **Complete the New Registration Process**: Use the new registration process provided in the plugin to link your FedEx account. Detailed step-by-step instructions are available in the PluginHive knowledge base here:
3. **No Additional Steps Required for Now**: Beyond updating the plugin and completing registration, no other actions are currently needed. FedEx may send notifications to many users as part of their transition, but once you have updated and registered, your setup will be ready for the upcoming switch.
4. **Switch to REST API When Supported**: PluginHive plans to enable full REST API compatibility in a future plugin release. Once that update is available, you will be able to switch over fully to the REST API. Until then, continue using the updated SOAP-compatible registration workflow provided in the plugin.

What steps can I take if the FedEx shipping service suddenly stops working on my store without any changes to settings or products?

1. Deactivate the PluginHive FedEx Shipping license within the plugin settings.
2. Reactivate the license with your valid key to reset licensing validation.
3. Re-register your FedEx account details in the plugin to refresh the API connection.

What should I use for FedEx integration in the WooCommerce FedEx Plugin—Web Services API or REST API?

Currently, the PluginHive WooCommerce FedEx Shipping plugin does not support FedEx REST API integration as it is not yet compatible. You should continue using the plugin’s supported FedEx Registration method, which requires your FedEx account number and billing address. PluginHive provides a FedEx Compatible Registration process that works with the current API standards supported by the plugin. Ensure your plugin version is up-to-date to benefit from the latest supported methods.

What should I know about the upcoming FedEx SOAP API endpoint changes and how do they affect the WooCommerce FedEx Shipping Plugin?

The FedEx SOAP API endpoints are set to be deprecated by the end of August, but the WooCommerce FedEx Shipping Plugin already includes a FedEx Compatible Solution that connects using your FedEx Account Number and Billing Address without requiring a Meter Number. The plugin team is actively working on integrating the new REST API and will release the update before FedEx transitions fully to REST API. Therefore, your current plugin should continue to function normally during this transition period. For detailed setup, refer to the official guide: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

What should I know about registering for the FedEx REST API to work with the updated plugin?

1. Follow the step-by-step REST API registration guide at https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST
2. Once your REST API registration is complete, the plugin automatically sends your Admin Store URL to PluginHive Support to enable smooth onboarding and faster support.
3. If you experience any issues or need assistance during the registration or setup process, PluginHive’s support team is available to help.

What should I do while waiting for a fix for the REST API shipping error in the FedEx WooCommerce Shipping plugin?

1. Switch your FedEx integration from REST API to SOAP API within the plugin settings. SOAP is the stable, recommended connection and will avoid the current error and rate retrieval issues.
2. Continue monitoring PluginHive announcements for updates regarding the new plugin version that will address these REST API problems.
3. Prepare diagnostic logs or other data you can share with PluginHive support if further troubleshooting is needed, but avoid site access requests if not possible.

What should I do to prepare for the discontinuation of FedEx Web Services on August 31, 2024?

1. Check if your WooCommerce FedEx Shipping Plugin license is active; if expired, renew it to maintain plugin functionality.
2. Register your FedEx account via the **FedEx Compatible Solution** within the WooCommerce FedEx Shipping Plugin. This method only works if you have an active license.
3. The compatible solution requires you to register using your FedEx account number and contact details through the plugin interface rather than older Web Services credentials (Account Number, Meter Number, API Key, Web Services Password).
4. If you have already registered via the plugin using your account number and contact details, no further action is required—you will continue to operate smoothly.
5. For assistance with the registration process, refer to the official **FedEx Registration Guide** video provided by PluginHive or contact their support team.
6. Take advantage of any renewal discounts offered by PluginHive before registering, if needed.

What should I do if updating the plugin and reactivating the API key does not restore shipping rates on my WooCommerce store?

1. Ensure you have also re-registered your FedEx (or UPS) account credentials in the plugin settings to fully link your license and account.
2. Check that you have installed the plugin’s latest version.
3. If the shipping rates still don’t show, submit a diagnostic report for further support.

What should I do if the shipping issue persists after purchasing a new license and updating the API key?

1. Navigate to the plugin’s General tab in settings.
2. Enable "Debug Mode."
3. Reproduce the issue on your site (e.g., seeing no shipping options).
4. Go to the "Help & Support" page within the plugin settings.
5. Submit the Diagnostic Report following the instructions provided there.

What should I do if the FedEx shipping option does not appear in the cart or checkout after switching from REST to SOAP API and enabling debug mode?

1. Enable "Debug Mode" in the PluginHive FedEx plugin settings under the General tab.
2. Reproduce the problem by adding a product and proceeding to the cart or checkout to confirm no shipping options appear.
3. Navigate to the "Help & Support" page within the plugin settings and submit a Diagnostic Report as instructed.
4. Once you have submitted the report, review the logs carefully—check if any shipping rates are being received from FedEx.
5. Ensure that all relevant FedEx shipping services are activated within the plugin settings; disable any unneeded services and enable the necessary ones to make sure they appear at checkout.
6. If rates appear in logs but shipping options still do not show, consider sharing temporary WordPress admin access for your site and your FedEx account credentials with PluginHive support to enable a deeper review.

What should I do if the FedEx REST API returns an account number mismatch error, but my provided account numbers appear correct in the API request?

1. Confirm you are using the correct FedEx shipping account number associated with your API credentials. Note that having multiple FedEx accounts (e.g., one for freight shipping) can cause confusion.
2. Check the FedEx API documentation or PluginHive update notes to verify if there is a newly required node or field to be passed with the ShippingChargesPayment.Payor.AccountNumber that might not be implemented.
3. Coordinate with PluginHive support to escalate and engage directly with FedEx Senior Support, as sometimes issue stems from FedEx expecting undocumented request structure or account validation issues on their side.
4. If possible, create a staging environment to isolate and test REST API integrations without affecting production.
5. Meanwhile, consider using the SOAP connection temporarily to maintain operations until REST API issues are resolved.

What should I do if the FedEx REST API integration is not fetching rates, and can using the SOAP API help?

If the FedEx REST API fails to provide shipping rates, it is recommended to switch to the SOAP API, which is currently more stable and reliable than the REST version that is still in beta. Using SOAP can serve as an effective workaround for rate calculation and label generation issues while the REST API problems are being resolved. This approach helps maintain your shipping functionality without disruption.

What should I do if PluginHive support cannot access my site to activate the API because of two-factor authentication?

If PluginHive support cannot access your WordPress admin due to two-factor authentication (2FA), temporarily disable 2FA on your site. Once disabled, notify the support team so they can log in and activate the license key for you. After they confirm the activation is complete, you can re-enable 2FA for your site’s security.

What should I do if my two websites with identical security plugins behave differently when updating FedEx API keys, where one activates successfully and the other does not?

1. Verify that both sites have identical server-level settings, including firewall and outgoing request permissions.
2. Ensure the IP address of the site that is failing is whitelisted as PluginHive may require IP whitelisting for license activation.
3. Temporarily disable security/anti-spam plugins and test again.
4. Check for any hosting provider restrictions that may differ between the two sites.
5. If needed, provide the admin access, Product API Key, and Product ID of the problematic site to PluginHive support for manual assistance with license activation and troubleshooting.

What should I do if my shipping workflow depends on HazMat, ORM-D, or FedEx C.O.D. services that are not supported in the REST API?

1. Go to the plugin settings in your WooCommerce admin dashboard.
2. Switch the API connection mode from REST back to SOAP.
3. Save the changes.

What should I do if my shipping workflow depends on FedEx HazMat, ORM-D Dangerous Goods, or C.O.D. services which are not supported by the REST API?

1. Continue using the legacy SOAP API connection as the REST API currently does not support HazMat and ORM-D Dangerous Goods shipments.
2. FedEx C.O.D. is deprecated and no longer available in the plugin; you will need to adjust your shipping process accordingly.
3. You can switch back and forth between SOAP and REST anytime within the plugin settings to match your shipping needs without disrupting your store.

What should I do if my current plugin does not support the FedEx test API environment to generate test shipping labels?

1. Identify plugins or integrations that support the FedEx test environment to generate test labels. Many free plugins may lack this feature.
2. Consider purchasing a compatible plugin that supports full FedEx API test environment capabilities to complete the certification testing.
3. Install and configure the new plugin with the FedEx test API credentials, enabling you to generate the required test labels.
4. After successful testing, update the integration with the production credentials to go live.

What should I do if my API key appears to be for a different plugin than the one showing the deactivation error?

1. Identify the correct API key and Product ID for the plugin causing the issue.
2. Use that exact API key and Product ID on the plugin activation page of the respective plugin.
3. If you only have the API key for a different plugin (e.g., UPS, but the error is on FedEx), retrieve the correct API credentials from PluginHive or within your PluginHive account.
4. Apply the valid key to the plugin in question and save to activate. This ensures no cross-plugin activation issues occur.

What should I do if I want to test the Beta release of the FedEx REST API plugin but have limited capacity for ongoing monitoring?

• It is recommended to wait for the stable public release rather than participate in the Beta testing phase.
• Use the current SOAP API connection to avoid service interruptions while awaiting a fully stable REST API version.
• Coordinate closely with the PluginHive support team if you decide to test in a staging or production environment, and communicate your monitoring capacity limits upfront.
• Prepare to revert easily to SOAP if any issues arise during Beta testing to minimize client impact.
• Stay updated with PluginHive release notes and announcements for the stable release timeline and full production readiness.

What should I do if I receive a license expiration warning but my API key is valid?

1. Verify that the plugin is configured with the latest API key by checking the plugin settings.
2. Update the API key if needed and save the changes.
3. Clear the cache on your website or application to remove any stored data referencing the old license status.
4. Re-activate the license if required to refresh the status.

What should I do if I encounter the "ShippingChargesPayment Payor AccountNumber should match the shipper account number" error with FedEx REST API integration through PluginHive?

1. Ensure your FedEx account is connected using the "Soap Process" method within the PluginHive plugin.
2. This connection method allows proper live shipping options to load and aligns your account credentials correctly.
3. If you have not connected via Soap Process, switch your FedEx account setup to this method.
4. After switching, test the shipping rates again to verify if the error is resolved.
5. If issues persist, share the Diagnostic Report with support for further investigation.

What should I do if I encounter issues with the FedEx REST API integration reported in an ongoing support ticket?

1. Confirm that your issue is documented in the existing support ticket (for example, ticket 331842 as mentioned).
2. Provide detailed information and any relevant logs or error messages via the support ticket to help the PluginHive team analyze the problem thoroughly.
3. Monitor the support ticket for updates from PluginHive’s technical team.
4. Meanwhile, you can check your API credentials, confirm network connectivity to FedEx endpoints, and verify plugin settings for any misconfigurations.
5. Avoid duplicating tickets to maintain continuity of support.
6. Await communication from the PluginHive team who are actively investigating the issue and will provide resolutions or workarounds as soon as possible.

What should I do if I encounter issues or have questions while setting up or migrating to the new FedEx REST API in the PluginHive plugin?

1. Review the detailed REST API registration guide available at: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST
2. Ensure all credentials and API configurations are correctly entered.
3. Use the plugin’s built-in logs and debugging features to identify errors.
4. Reach out to PluginHive Support directly via their support channels with detailed information about the issue.
5. Provide logs, screenshots, or error messages to facilitate faster resolution.
6. Support is available to help you resolve configuration problems, API failures, or any other questions related to the REST API migration.

What should I do if I encounter errors or bugs during FedEx REST API registration while using the PluginHive plugin?

If you experience errors or issues such as missing validation codes, form errors, or no rates showing after REST API registration, try the following:

1. Verify your FedEx developer account is active and properly linked to your business FedEx account.
2. Ensure that the REST API credentials entered are accurate and complete.
3. Wait an appropriate amount of time after registration for the system to update rates.
4. If validation codes are missing or errors occur during the form submission, check for network or browser issues.
5. If the problem remains unresolved, consider temporarily reverting to the SOAP API to keep real-time rates functioning.
6. Contact PluginHive support with detailed error messages and your FedEx account status if you want assistance troubleshooting the REST API registration.

What should I do if I encounter a "migration failed" error after updating the PluginHive plugin from version 3.0.5 (SOAP API) to version 7.x (REST API)?

1. Deactivate the PluginHive plugin on your WordPress site.
2. Clear your website cache (including any caching plugins) and your browser cache.
3. Reactivate the PluginHive plugin.

What should I do if I do not understand the FedEx registration process or am unsure if my site’s FedEx integration is properly updated?

1. Contact PluginHive support with temporary access to your WordPress admin panel (wp-admin credentials), so they can directly verify your settings and registration status. This access should be shared securely via [email protected].
2. Alternatively, request a live Zoom call session with PluginHive support for step-by-step guidance to help you complete or verify the FedEx registration and integration.
3. These options are aimed at simplifying the process for you and ensuring your FedEx shipping functionality is correctly updated and will continue smoothly.
4. If you prefer self-help, reviewing the official knowledge base documentation on FedEx registration and plugin settings can also clarify the process: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/

What should I do if I believe I am using the correct plugin version but still do not see the expected FedEx REST API registration screen?

1. Clear your browser cache and refresh the plugin registration page to ensure no cached content is being displayed.
2. Confirm there are no plugin conflicts by temporarily disabling other plugins and testing again.
3. Check the site for any access restrictions or errors (such as 404 errors) that could be blocking the registration page.
4. Validate that you are logged in with an administrator account and have appropriate permissions to view plugin settings.

What should I do if FedEx shipping calculations fail during a FedEx API technical issue?

1. Monitor the problem without making major changes to your WooCommerce setup immediately.
2. Communicate with FedEx support for updates on their API status.
3. Inform customers about potential shipping method unavailability or checkout issues related to shipping calculation.
4. Maintain correspondence with your plugin support provider (such as PluginHive) to ensure they are aware and can provide further assistance if required.
5. After FedEx resolves the issue, test your checkout thoroughly and ensure all shipping options function properly.

What should I do if FedEx REST API shipping rates are not showing correctly on my PluginHive-integrated store?

1. Verify that the FedEx REST API credentials are properly configured in the PluginHive plugin settings within your WordPress admin panel.
2. Confirm that your API registration with FedEx is fully activated and approved from FedEx’s side. Sometimes FedEx requires additional activation steps.
3. Reach out to FedEx technical support to troubleshoot and ensure that your REST API access is enabled and unrestricted.
4. Clear any caching on your website and test the checkout page again.
5. If issues persist, contact PluginHive support with detailed information including API registration and error messages for further assistance.

What should I do if enabling a new API key in the PluginHive FedEx shipping plugin causes a critical error on my site?

1. Verify that you have downloaded and installed the latest version of the PluginHive FedEx shipping plugin. Older plugin versions may not be compatible with the new API keys.
2. Update the API key in the plugin settings only after ensuring the plugin is up to date.
3. If the error persists, check your site’s WooCommerce logs by navigating to WooCommerce → Status → Logs. Look for the latest “Fatal error” log and review its contents to identify any specific error messages related to the plugin.
4. Capture a detailed screencast or screenshot replicating the error occurrence to assist in troubleshooting.
5. Reach out to PluginHive support with your purchase details, plugin version, error logs, and any screencasts/screenshots to get further assistance.

What should I do after completing the REST API registration within the PluginHive FedEx plugin?

1. The plugin will automatically send your Admin Store URL to PluginHive Support to assist with onboarding and troubleshooting.
2. Confirm in your plugin settings that REST API is activated and your FedEx credentials are correctly entered.
3. Test label generation and shipping rate calculations to ensure the REST connection is functioning properly.
4. Reach out to PluginHive support promptly if you experience any issues during or after the migration, so you can receive timely assistance.

What should I check if the PluginHive FedEx plugin does not show rate options or costs after switching to a new FedEx API method?

1. Confirm that the plugin license is deactivated and reactivated to reflect the new API integration.
2. Ensure you have re-registered your FedEx account within the plugin using updated credentials.
3. Double-check that all order shipping addresses are complete with required details, particularly phone numbers.
4. Test for site conflicts by temporarily disabling themes or other plugins to rule them out as causes.
5. If none of these resolves the issue, enable debug logging, reproduce the problem, and send PluginHive a diagnostic report for advanced troubleshooting.

What security or privacy considerations should I be aware of when registering the FedEx REST API through the PluginHive plugin?

1. Facilitate smoother onboarding.
2. Enable faster and more effective issue resolution by the support team.

What options are available if live FedEx rates are not appearing on the website despite updating the plugin and API key?

If live FedEx rates do not appear after updates, you can request a live troubleshooting session with PluginHive support. They offer Zoom calls where they can directly assist you with setup verification, error diagnosis, and configuration adjustments. To organize this, reply to their support communication with your preferred timing.

What limitations should I be aware of when using the FedEx REST API with PluginHive’s WooCommerce FedEx plugin?

1. No support for HazMat and ORM-D Dangerous Goods shipments, as per FedEx’s API restrictions.
2. FedEx Cash On Delivery (C.O.D.) services have been deprecated by FedEx and removed from the plugin.

What is the process to register and set up the FedEx REST API with the PluginHive WooCommerce FedEx plugin?

1. Follow the step-by-step REST API registration guide provided by PluginHive at: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Need-to-Register-With-FedEx-REST
2. Complete the registration with FedEx to obtain credentials necessary for REST API access.
3. Enter the REST API credentials into the plugin configuration in WooCommerce.
4. Upon successful registration, the plugin will automatically send your Admin Store URL to PluginHive Support to facilitate smoother onboarding and faster support.
5. Test the integration by generating shipping labels and verifying the connection.

What is the plan for the PluginHive FedEx plugin once FedEx fully disables SOAP API support?

PluginHive is actively working to make the FedEx plugin compatible with the FedEx REST API. The plugin will receive updates to support REST API integration before FedEx discontinues SOAP services completely. Until that migration is finalized, continue using the existing registration process with the SOAP API as it will remain functional. PluginHive will notify users once the REST API compatibility updates are available to ensure a smooth transition.

What is the current status of the FedEx RESTful API update for the PluginHive WooCommerce FedEx shipping plugin?

The PluginHive WooCommerce FedEx shipping plugin has already completed development and migration to FedEx's REST API. The plugin now supports a **FedEx Compatible Solution** registration where you can connect using your FedEx account number and billing address without requiring a meter number. Rates and shipping labels will continue to function seamlessly with this new integration. Currently, PluginHive is working with the FedEx team to obtain certification for the REST API implementation. Once certified, the plugin will switch fully to the REST API before FedEx’s complete migration, expected by the last quarter of this year. For detailed setup and usage, refer to the documentation here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

What is the current status of the FedEx REST API integration in PluginHive, and when will it be available?

The FedEx REST API integration has been submitted for FedEx Certification and is currently awaiting their approval. The final, certified version of the integration is expected to be released by the second week of February. Once approved, the feature will be made available within the PluginHive platform.

What is the current status of the FedEx REST API integration in PluginHive, and what is the revised expected release timeline?

The FedEx REST API integration is currently in its final Quality Assurance (QA) phase. The development and certification processes are complete, and the team is focused on thorough testing to ensure stability and reliability before release. The release is on track to be ready by mid-June. PluginHive is committed to providing a fully tested and stable solution prior to launch to avoid further delays. Customers are encouraged to share this update with their clients and reach out if they have additional questions.

What is the current status of PluginHive’s FedEx plugin support for the new FedEx REST API migration happening on August 31st?

PluginHive's FedEx plugin currently supports FedEx Compatible Solution (Registration), allowing you to connect your FedEx account using your FedEx Account Number and billing address without needing a meter number. While the plugin does not yet support the new FedEx REST API, the team is actively working on it and aims to complete the REST API integration before FedEx’s full migration on August 31st. For configuration details on connecting without a meter number, you can refer to the following guide: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

What is the current status and expected timeline for the FedEx REST API integration release in PluginHive?

The FedEx REST API integration with PluginHive has completed the approval stage after a meeting with the FedEx team, marking a significant milestone. Currently, the integration is in the finalization phase where necessary changes are being implemented. The updated PluginHive solution integrating FedEx REST API is expected to be released in April, with a high probability of availability in the early weeks of the month, but definitely by the end of April at the latest. Once the release is live, PluginHive will proactively communicate the update details to all customers. For any immediate questions or to stay informed, you may contact the customer success manager directly at [email protected].

What is the correct FedEx registration deadline for PluginHive’s FedEx plugin integration, and how can I confirm this information?

1. The current FedEx plugin by PluginHive is integrated using FedEx Web Services and will continue to work until December
2. 2
3. 0
4. 2
5. FedEx has confirmed that the REST API migration will happen after this period. The REST API integration is planned to be completed before FedEx fully migrates to the new system, expected in the fourth quarter of
6. 2
7. 0
8. 2
9. To confirm this timeline, you can directly contact the FedEx support team. This ensures your plugin will function properly without interruption until the REST API version is released.

What initial troubleshooting steps should I take if live shipping rates are not displaying on my WooCommerce checkout page after setting up the FedEx API key?

1. Confirm that your PluginHive license key is successfully activated without errors.
2. Check and whitelist your server’s IP address if required by PluginHive.
3. Re-register your account credentials via the plugin’s registration section (UPS Registration > Registration > Re-Register) to refresh authentication tokens.
4. Verify that your WooCommerce shipping zones and methods are correctly configured to use FedEx.
5. Disable any conflicting or security plugins temporarily to rule out interference with API calls.
6. Clear your WooCommerce and site cache to ensure fresh data is loaded.
7. Test the checkout to see if live rates now appear. If issues continue, contact PluginHive support with relevant details for further assistance.

What information and access should I provide to PluginHive support to troubleshoot FedEx API registration issues?

1. WordPress Admin Access: Create an admin user with the email [email protected], and share the Site URL, username, and password securely.
2. FedEx Account Details including:
3. Verification Method: Specify which validation method was used (e.g., SMS OTP) during account verification.
4. Optional: If SMS OTP is inconvenient, share a recent FedEx invoice for verification purposes.

What happens if my support ticket related to the FedEx REST API integration is closed—will I still be contacted when the feature is ready?

Yes, even if your ticket is closed, PluginHive retains your information in their system and will proactively notify you when the REST API integration is available. They encourage users to reach out anytime but ensure that customers on related requests will receive updates without needing to reopen tickets.

What happens after I successfully register for the FedEx REST API through the plugin?

Upon successful REST API registration, the plugin automatically sends an email to PluginHive Support containing your Admin Store URL. This process is designed solely to facilitate a smoother onboarding and support experience and does not share any sensitive data beyond the store URL.

What functionality is affected by the expiration of FedEx SOAP Web Services for Tracking, Address Validation, and Postal Code Validation, and how does the plugin handle this?

Though FedEx has discontinued SOAP Web Services for Tracking, Address Validation, and Postal Code Validation, the PluginHive FedEx plugin will continue to provide these functionalities through the new FedEx REST APIs once certification is complete. Currently, no features will expire or be lost in the plugin. PluginHive is coordinating with FedEx to ensure these services continue uninterrupted within the plugin environment.

What explanation can be provided to clients regarding the delay in the FedEx REST API integration release beyond the initially promised date?

The delay occurred because the PluginHive team extended the final QA and testing phases to ensure the integration is fully stable and free of issues before release. While the initial estimate aimed for availability by the end of April, more comprehensive testing was required to meet quality standards. PluginHive apologizes for the inconvenience and emphasizes their commitment to delivering a reliable product. The integration is very close to release, expected by mid-June, and updates will be communicated promptly once live.

What does the message about FedEx Plugin Settings indicating successful configuration with Meter Number and operation until May 15, 2024 mean, and are there any necessary next steps to maintain FedEx functionality?

The message indicates that the FedEx Web Services currently in use will be replaced with the FedEx REST API on May 15, 2024. Your plugin is configured with the older Web Services using a Meter Number, which will continue to work only until that date. To maintain uninterrupted FedEx shipping functionality after this cutoff, you need to complete the FedEx Direct Registration process within the PluginHive plugin. This allows you to connect your existing FedEx account and billing details using the updated FedEx REST API, enabling continuation of shipping rates, label generation, and other features. Detailed registration instructions are available here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx

What does the error "Failed to get Internal Endpoints" mean and how can I resolve it in the PluginHive FedEx integration?

1. Verify that the PluginHive FedEx plugin license is active on your site. Go to **FedEx Registration → License Activation** in your WordPress admin panel and confirm the license status.
2. If the license is active and the error persists, deactivate the plugin license first by navigating to **FedEx Registration → License Activation** and choosing to deactivate.
3. Reactivate the license by re-entering the license key on the same screen.
4. Re-register your FedEx account within the plugin to refresh connection credentials. To do this, go to **FedEx Registration → Registration**, and complete the account registration steps again.
5. After completing these steps, test label generation and rate fetching again.

This process ensures that the license and FedEx API credentials are properly synced and should resolve connectivity errors with FedEx endpoints.

What does the "SHIPMENT.ACCOUNTNUMBER.UNAUTHORIZED" error mean when generating FedEx labels using the REST API, and how can I resolve it?

1. Confirm that your FedEx account is fully registered and authorized by FedEx for API usage, specifically for REST API label generation. Contact FedEx Customer Service to verify your account status and enable the necessary permissions if required.
2. Double-check that the FedEx account number entered into your PluginHive FedEx plugin matches exactly the account number registered with FedEx.
3. If the REST API integration continues to produce authorization errors, switch to using the SOAP API integration within the PluginHive FedEx WooCommerce Shipping plugin, as it is generally more stable and accepted for many account configurations.
4. Re-register your FedEx account using the SOAP integration by navigating in your WordPress admin to FedEx Shipping → Registration, selecting the SOAP API option, entering your FedEx account details, and saving the settings.
5. After switching to SOAP API, test generating labels and verify that the error no longer appears and shipments process successfully.

What does the "FedEx direct registration option" mean in the FedEx WooCommerce plugin? Can I still enter my API key and secret key manually?

The "FedEx direct registration option" is a built-in plugin feature that enables users to create and connect their FedEx account directly through the plugin interface using the FedEx REST API. FedEx has deprecated the older method of manually entering API credentials. Therefore, recent plugin versions no longer support manual input of API key and secret key. Instead, the plugin guides you through a registration workflow to securely connect your FedEx account, ensuring seamless access to FedEx shipping rates and services without manual credential entry.

What does the "Failed to get Internal Endpoints" error mean in the PluginHive debug log, and how can I resolve it if it's related to FedEx API authentication issues?

1. Update the PluginHive plugin to the latest version (at least version 7.1.3).
2. Deactivate your current plugin license by navigating to **FedEx Registration → License Activation** within the plugin settings.
3. Reactivate the plugin license using your license key.
4. Re-register or reconnect your FedEx account within the plugin settings to refresh the API credentials and ensure the proper connection with FedEx’s endpoints.

What does the "Connection failed to the License Key API server" error mean, and how can I resolve it?

1. Check if you have any security plugins installed (e.g., firewall, security scanners).
2. Temporarily deactivate these security plugins at a suitable time and then attempt to activate the license again.
3. If no security plugins are installed or deactivation does not fix the issue, contact your hosting provider to verify if server security settings or firewall rules are blocking outgoing requests from your site.
4. Ensure that your web server can reach external API endpoints without restrictions.

What does "FedEx direct registration option" mean in the context of the FedEx WooCommerce plugin? Will I still be able to enter my API key and secret key directly in the plugin?

The "FedEx direct registration option" refers to the plugin’s new built-in feature that facilitates FedEx account registration and API credential management directly within the plugin interface, using the FedEx REST API. FedEx has deprecated the old method of manually entering API credentials (API key and secret key) directly into the plugin. Therefore, with recent plugin versions, you no longer manually enter API credentials. Instead, you complete registration and connect your FedEx account through the built-in registration workflow provided by the plugin. This integration ensures seamless access to FedEx rates and services.

What do I need to know about FedEx SOAP API endpoints deprecation and REST API migration concerning the PluginHive FedEx plugin?

FedEx is transitioning from SOAP to REST API endpoints, with partial migration affecting tracking and address validation services. The PluginHive FedEx plugin includes a compatible solution where you connect your FedEx account via your FedEx Account number and billing address, without requiring a meter number. You should complete the direct registration process via the plugin’s FedEx Registration menu to avoid service interruptions. PluginHive has developed and is in the process of certifying the REST API version of the plugin to ensure uninterrupted service. Until the REST API version is fully released, current functionalities will continue operational if registration is complete.

What details are required to connect and validate my FedEx account with the PluginHive FedEx REST API plugin?

1. FedEx Account Number
2. Billing Address associated with your FedEx account
3. A recent FedEx shipment invoice (if available)

What default settings are required in the delivery API to ensure customers receive the correct FedEx shipping deal after integration?

To provide customers with the correct FedEx deal via the delivery API after integration, you need to configure the shipping settings that correspond to your FedEx account agreements within the WooCommerce FedEx Shipping Plugin by Plugin Hive. This typically involves:

1. Ensuring your FedEx account number is correctly set up in the plugin settings.
2. Confirming that the plugin is connected using the appropriate FedEx credentials and environment (production/live).
3. Selecting the correct shipping services that match the FedEx deals you have negotiated so that these services appear at checkout.
4. Enabling automatic label generation so labels correspond with the chosen shipping service.
5. Verifying the plugin settings allow customers to select shipment services on the checkout page.

If these configurations are correctly done, the delivery API will automatically apply your FedEx shipping deals when customers place orders.

What changes from FedEx’s Web Services do I need to be aware of, and how can I ensure FedEx services continue to work on my website using PluginHive?

1. After August 31, 2024, FedEx Web Services for Tracking, Address Validation, and Postal Code Validation will no longer be available.
2. All remaining Web Services functionalities, including Shipping, will be disabled soon after.
3. FedEx will stop providing technical support for Web Services-related queries.

• PluginHive currently supports FedEx integration through a compatible solution that connects your account using your FedEx Account Number and billing address without requiring a FedEx Meter Number.
• The plugin’s existing version works with the current system while PluginHive actively develops the FedEx REST API version to comply with FedEx’s new requirements.
• PluginHive expects to complete and release the REST API-compatible plugin version before FedEx’s full migration deadline, ensuring a seamless transition with no service disruptions.

For detailed setup, refer to PluginHive’s documentation here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number

You do not need to take immediate action apart from monitoring PluginHive updates and preparing to upgrade to the REST API version once available. Contact PluginHive support for any further questions about the transition.

What causes the license API key to become invalid after deactivating and reactivating the PluginHive FedEx shipping plugin, and how can I fix this?

1. Go to **FedEx Shipping → License → API Key Deactivation** and enable the option to deactivate the previous license key from this site, saving changes.
2. Reactivate the FedEx plugin to refresh the state.
3. Re-enter the license API key and Product ID on the license activation page and save changes.
4. Ensure no other sites are using the same license key, as it only supports one active site per license.

What are the recommended steps if I continue to experience FedEx REST API account mismatch errors after PluginHive confirms the fix?

1. Double-check that your FedEx account numbers and API credentials configured in PluginHive are correct and up to date.
2. Clear caches, reauthenticate API connections if necessary.
3. Reproduce the issue with fresh API calls and share updated debug logs with PluginHive support.
4. Confirm you have not revoked any temporary access provided for troubleshooting.
5. Follow PluginHive’s guidance to escalate or open official support tickets with FedEx if needed.
6. Consider temporary fallback to the SOAP connection until a permanent resolution is confirmed.

These FAQs summarize actionable insights and steps from the conversation for users facing FedEx account mismatch errors during REST API integration with PluginHive.

What are the main benefits of switching to the FedEx REST API from the SOAP connection in the PluginHive WooCommerce FedEx Shipping Plugin?

1. Modern and future-proof architecture
2. Faster and more efficient communication with FedEx services
3. Enhanced security features ensuring safer transactions
4. Improved reliability for real-time shipping operations

What are the limitations of using the new FedEx REST API in the plugin, and should I continue using the SOAP API in some cases?

• No support yet for Hazardous Materials (HazMat) and ORM-D Dangerous Goods shipments, as restricted by FedEx’s API.
• FedEx C.O.D. service has been deprecated and is no longer available.

What are the key requirements to migrate from FedEx Web Services to the FedEx Compatible Solution using PluginHive?

1. Use the WooCommerce FedEx Shipping Plugin with an active PluginHive license (renew if expired).
2. Register your FedEx account through the WooCommerce plugin interface using your official FedEx Account Number and contact details.
3. Avoid using the older FedEx Web Services credentials (Account Number, Meter Number, API Key, Web Services Password) after August 31, 2024, as they will be disabled.
4. Follow PluginHive’s FedEx Registration Guide or provided instructional videos to complete your migration.

What are the implications if I do not adopt the REST API version of the WooCommerce FedEx plugin?

If you do not update to the REST API plugin, your current FedEx shipping functionality will continue to work for now. However, FedEx has officially retired its Web Services SOAP API as of August 31, 2024, and will completely phase it out. Once fully deprecated, the SOAP-dependent features will stop working, causing shipping disruptions. To ensure uninterrupted FedEx shipping service, it is essential to migrate to the REST API plugin.

What are the current recommendations to improve FedEx shipping plugin performance related to API usage?

• Make sure you are running the latest plugin update (v7.1.1 or newer), which has speed improvements for WooCommerce blocks checkout.
• Disable other non-essential plugins and use a default WooCommerce theme (Storefront) during testing to minimize conflicts.
• Turn off Debug mode in WooCommerce Shipping settings to enable proper caching and reduce latency.

What are the benefits of switching to the WooCommerce FedEx REST API plugin?

1. Faster performance due to improved API architecture.
2. Enhanced security leveraging OAuth 2.0 authentication, which is more secure than the older methods.
3. More accurate tracking and delivery estimate information with real-time reliability.
4. Compliance with FedEx’s latest API standards, future-proofing your shipping integration.

What are the benefits of switching the WooCommerce FedEx Shipping plugin from SOAP to the REST API?

1. Modern & Future-Proof Architecture – The REST API is FedEx’s latest standard and will receive ongoing improvements.
2. Faster, More Efficient Communication – REST provides quicker response times compared to SOAP.
3. Improved Real-Time Reliability – Enhanced accuracy and stability in rate calculations and tracking.
4. Enhanced Security – The REST API uses updated security protocols to better protect your shipment data.

What are the benefits of switching from the SOAP connection to FedEx’s REST API in the PluginHive WooCommerce FedEx plugin?

1. Modern and future-proof architecture that aligns with FedEx’s latest integration standards.
2. Faster and more efficient communication between WooCommerce and FedEx systems.
3. Improved real-time reliability, reducing errors during shipment processing.
4. Enhanced security features protecting data exchanges.

What are the benefits of switching from the legacy SOAP connection to the new FedEx REST API in the WooCommerce FedEx Shipping Plugin?

Switching from the legacy SOAP connection to the FedEx REST API in the WooCommerce FedEx Shipping Plugin offers several significant advantages:

1. Modern & Future-Proof Architecture: REST API is built on a more current and widely adopted framework that ensures better long-term support and compatibility.
2. Faster & More Efficient Communication: REST uses streamlined data formats and methods that reduce latency and improve transaction speed.
3. Enhanced Security Features: REST incorporates up-to-date security protocols to protect data exchanges more robustly.
4. Improved Reliability in Real-Time Operations: REST provides better stability and accuracy during live shipping transactions, reducing errors and delays.

What are the benefits and current limitations of using the FedEx REST API with the PluginHive plugin?

• Modern, future-proof architecture ensuring long-term support.
• Faster and more efficient communication with FedEx servers.
• Improved real-time reliability reducing shipment errors.
• Enhanced security features protecting transaction data.

• FedEx Hazardous Materials (HazMat) and ORM-D Dangerous Goods shipping are not supported via REST due to FedEx API limitations.
• FedEx Cash On Delivery (C.O.D.) service has been deprecated by FedEx and removed from the plugin’s REST API feature set.

If your shipping workflow depends on HazMat, ORM-D, or C.O.D., continuing to use the SOAP connection is recommended until REST support expands.

What are the benefits and current limitations of the FedEx REST API integration in the PluginHive WooCommerce FedEx Shipping plugin?

• Modern, future-proof API architecture designed by FedEx to improve system compatibility and longevity.
• Faster and more efficient communication between your WooCommerce store and FedEx servers, leading to quicker shipping rate calculations and label processing.
• Enhanced security features aligning with the latest API standards.
• Improved real-time reliability for shipping operations such as label creation and tracking.

• Does not support shipping of HazMat and ORM-D dangerous goods, as these are not available in FedEx’s REST API.
• FedEx C.O.D. (Cash on Delivery) services have been deprecated by FedEx and removed from the plugin.
• Presented as a Beta feature, the REST API integration may have fewer mature features compared to the stable SOAP connection at this stage.
• Users dependent on unsupported features should continue using the SOAP API connection until further REST API capabilities are implemented.

We received a FedEx notification about migrating from SOAP to REST APIs by August 31, 2024. Do we need to take any action with the PluginHive FedEx plugin? Is updating the plugin to the latest version enough?

Yes, action is required to ensure continued FedEx API connectivity. PluginHive’s latest FedEx plugin version supports the FedEx Compatible Solution registration, allowing you to connect to your FedEx account using your FedEx Account number and billing address without needing the Web Service key and password. Here’s what you should do:

1. Update your FedEx plugin to the latest version available.
2. Complete the FedEx Compatible Solution registration process integrated within the plugin. For step-by-step guidance, refer to this article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#donot_have_fedex_meter_number
3. Currently, the plugin still uses SOAP API, but PluginHive will update it to support FedEx RESTful API before the August 31, 2024 deadline.
4. After the RESTful API support is released, you will be able to seamlessly switch to the new FedEx REST API environment.

By starting the registration process now and keeping your plugin updated, you will remain compliant with FedEx’s new API requirements and avoid service disruption.

We have a FedEx Meter Number saved and our license is renewed until December 2024. What exactly do we need to do by December 2024 regarding FedEx integration and API setup?

FedEx is discontinuing some of its services that rely on the traditional FedEx Web Services Meter Number. Because of this, PluginHive’s FedEx plugin includes a FedEx Compatible Registration process designed to replace the old Meter Number method. Here is what you need to do:

• Navigate to **WordPress dashboard > Settings > FedEx Activation**.
• Enter your API Key and Product ID, which you can find at **pluginhive.com > My Account > API Keys**.

2. Update the FedEx plugin to the latest version (minimum version 7.1.0), as it includes the new registration workflow.

• Instead of using a Meter Number, add your FedEx account number and billing address directly in the plugin settings.
• This process allows you to use all FedEx services without creating or managing a FedEx API project on the FedEx developer portal.

4. Since API calls are routed through PluginHive’s system, you do **not** need to create or manage any new API projects on the FedEx developer portal yourself.

For detailed step-by-step setup instructions, refer to this knowledge base article: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx

Following these steps ensures uninterrupted FedEx service through your PluginHive integration after December 2024.

The website still shows that the PluginHive license needs to be renewed even after renewal, and the new API key is not recognized or linked properly. How can I fix this issue?

To resolve the license renewal notification and ensure the new API key is recognized on your website, follow these steps:

1. Deactivate the PluginHive plugin on your website.
2. Reactivate the plugin.
3. Navigate to FedEx Shipping → License Activation within your site’s admin panel.
4. Enter and activate your new API key.
5. Clear your website cache completely to remove any old cached data.

Since FedEx production keys are being discontinued, how does the PluginHive FedEx integration work now?

The PluginHive FedEx integration no longer requires production keys. Instead, it uses a FedEx Compatible Registration process that connects your FedEx account via your FedEx Account number and Billing address. After successful registration, production keys are neither needed nor stored, and the plugin fetches FedEx rates directly based on your account details. This streamlined approach simplifies setup and future-proofs your integration against FedEx’s discontinuation of production keys.

Should we click “Agree & Continue” in the plugin to proceed with the FedEx registration process, and what are the next steps after that?

Yes, you should click “Agree & Continue” within the plugin to initiate the FedEx Direct Registration process. Afterward, follow the detailed instructions provided in the official guide at https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. This will walk you through completing your FedEx account registration within the plugin, enabling the new FedEx REST API integration and ensuring uninterrupted FedEx shipping functionality.

Should I use the FedEx REST API or SOAP API with the PluginHive FedEx Shipping plugin?

You can use either the REST API or the SOAP API with the PluginHive FedEx Shipping plugin, as both are supported and the plugin works seamlessly with them. The SOAP API has been a reliable method for rate fetching and many users continue to use it successfully. The REST API is fully functional and is recommended for future-proofing, but its registration and validation process may sometimes encounter issues depending on the FedEx developer account status. Choose the API based on your comfort and current account behavior; if the REST API causes issues, continue using SOAP until you are ready to transition.

My site requires two-factor authentication (2FA) over SMS after login, which is blocking access for troubleshooting. Should this be disabled for plugin support?

• Disable 2FA or provide an alternative login method temporarily.
• Grant access with a temporary admin account, if possible, to expedite support.

Is there a beta version available for testing the new FedEx REST API integration in PluginHive’s WooCommerce FedEx Shipping Plugin?

The upcoming FedEx REST API version of the PluginHive WooCommerce FedEx Shipping Plugin is currently in the final phase of quality assurance. PluginHive offers early access through a beta testing program. Users interested in trying the beta version can contact PluginHive support to express interest and receive further instructions.

Is the SOAP API for FedEx shipping rates being discontinued, and how long can I continue to use it with PluginHive?

Currently, FedEx has not issued any official timeline or announcement regarding the discontinuation of their SOAP API services. You can continue using the SOAP API with the PluginHive FedEx Shipping plugin without immediate concern. However, it is advisable to plan for a future transition to the REST API when you are ready, as REST is the modern standard. PluginHive support is available to assist you during this transition whenever you decide to switch.

Is the PluginHive WooCommerce FedEx Shipping plugin currently using the REST API or SOAP API for shipping rate requests, and what is the status of the REST API migration?

The PluginHive WooCommerce FedEx Shipping plugin currently uses the FedEx SOAP API for shipping rate calculations and label printing. The migration to the FedEx REST API is actively in progress and considered a top priority. This transition requires official certification from FedEx, which is still underway. Until this certification is completed and approved, the plugin will continue using the SOAP API, ensuring uninterrupted functionality. The REST API integration has been introduced in a Beta release (version 8.0.0) where users can switch between SOAP and REST connections via the plugin settings. Users can choose to opt into the REST Beta or continue with the SOAP connection, especially if their shipping workflows rely on features not yet supported in REST, such as HazMat or ORM-D shipments. Once the FedEx REST API is officially certified and the plugin update finalized, PluginHive will switch all users smoothly to REST without disruption. Users are provided continuous updates via product pages and changelogs about the progress to keep them fully informed.

Is the PluginHive shipping plugin currently compatible with the new FedEx REST API?

No, the PluginHive shipping plugin is not yet compatible with the FedEx REST API. However, the existing FedEx account integration using the current API continues to work without issues. You can keep using your FedEx account as usual with the plugin. For any concerns or questions regarding your FedEx integration, you can contact PluginHive support for assistance.

Is the PluginHive FedEx WooCommerce plugin using SOAP or REST API for shipping rate requests, and how does this affect performance?

Currently, the PluginHive FedEx WooCommerce plugin primarily uses the FedEx SOAP API for shipping rate calculations. Although the plugin team has completed development for migrating to the FedEx REST API—which generally offers better performance and modern integration—they are awaiting FedEx certification of this implementation before going live. The plugin will switch to REST API after certification, ensuring smooth continuation of all functionalities including rates, labels, and tracking. Until then, the SOAP API remains in use, and performance characteristics reflect that. Users may observe REST API references in changelogs or updates reflecting this ongoing integration effort, but the live version still uses SOAP until the official switch is approved.

Is the PluginHive FedEx shipping plugin currently compatible with the FedEx REST API?

No, the PluginHive FedEx plugin is currently not compatible with the FedEx REST API. The plugin uses the traditional FedEx API for registration and shipment processing. The support team has completed the existing registration process on your site using the supported API, so live rates and shipping functionality work correctly with the current setup. Compatibility with the FedEx REST API is being developed separately but is not yet available at this time.

Is the PluginHive FedEx plugin currently using FedEx SOAP APIs, and does it support FedEx REST APIs? If not, how can I migrate to REST APIs?

Currently, the PluginHive FedEx plugin uses FedEx SOAP APIs and does not yet support FedEx REST APIs. Migration to REST APIs is not possible at this time because the plugin has not been updated for REST compatibility. The development team is actively working on completing the certification process with FedEx's new REST APIs, which is expected to take a few weeks. After certification, the plugin will be updated to be REST API compatible, but no exact timeline is available yet. Until then, continue using the SOAP-based integration, which works seamlessly once the FedEx Registration process is completed correctly within the plugin.

Is the PluginHive FedEx plugin currently compatible with the FedEx REST API?

The PluginHive FedEx plugin is actively working on REST API compatibility. Meanwhile, the plugin features the FedEx Compatible Solution (Registration) for connecting to FedEx accounts without a meter number using existing APIs. The team plans to complete the REST API version before FedEx fully migrates to the REST API, ensuring uninterrupted service. Users should continue using the current plugin version and monitor for official updates regarding REST API support.

Is the FedEx REST API integration stable for live usage in the PluginHive WooCommerce FedEx Shipping Plugin?

The FedEx REST API integration is currently in a beta phase and has not been fully validated in live environments by PluginHive, since they do not process live FedEx accounts themselves. This means some features might be unstable or require further testing. If you would like to assist with validating and stabilizing this integration, you can share your FedEx live account details confidentially with PluginHive for testing in their local environment. PluginHive assures that your account will not be charged during this testing process. This collaboration will help improve the stability and reliability of the REST API integration for all users. If you are comfortable sharing these details, you can contact PluginHive for the exact list of information and testing procedures.

Is label printing functionality mandatory for using the FedEx REST API with PluginHive, and how can I proceed if I do not use it?

1. Focus your setup only on enabling rate quotes and shipping options in the PluginHive settings.
2. Skip or disable the label generation modules or features in the plugin, if available.
3. Continue processing orders with FedEx shipping rates being shown and applied during checkout without generating shipping labels through the plugin.

Is it safe to delete the `ph_available_fedex_hold_at_location` meta key from orders to resolve memory issues, especially if my customers rarely use the Hold at Location feature?

You may delete the `ph_available_fedex_hold_at_location` meta key at your own discretion to reduce memory usage and resolve errors during syncing. However, this action is not officially supported and could cause unexpected issues with order data related to Hold at Location functionality. Proceed with caution, and consider backing up your database before removal. If you rely minimally on the Hold at Location feature, deleting this meta key could help mitigate memory problems temporarily.

Is it safe to change the API key in WooCommerce without losing my PluginHive plugin data?

Yes, it is safe to update the API key in WooCommerce for the PluginHive plugin. When you update the plugin license with the new API key and product ID, your existing plugin settings and data will remain intact. There is no risk of losing your plugin data during this process. You can proceed with the update confidently.

Why is the table with FedEx API credentials not showing in the plugin settings, and how can I resolve this issue?

The FedEx plugin no longer requires manual entry of API credentials after you have completed the FedEx Registration process within the plugin. Once registered, the plugin connects automatically to your FedEx account, which is why the API credentials table is hidden (set to display:none). You may briefly see the fields when the page loads due to caching, but they disappear quickly because these input fields have been removed. This behavior is expected and does not indicate an error. No action is needed for API credentials in the current plugin versions.

Why is my PluginHive FedEx plugin locked on demo PHIVE credentials and why can’t I edit the API settings to enter my real FedEx production credentials?

The PluginHive FedEx plugin uses a new FedEx-compatible account registration process where you connect your FedEx account by providing your FedEx account number and billing address only. Unlike earlier versions, you do not need to manually enter FedEx credentials such as Meter Number or Web Services Key. The plugin handles all credential management internally after registration. The briefly visible “Generic API Settings” section containing PHIVE credentials is part of the plugin’s internal communication setup, is intentionally non-editable, and disappears after loading. This is why the plugin page flashes and does not allow editing those fields. You should safely ignore this section and trust that your FedEx account is properly linked behind the scenes.

Why don’t shipments created via the FedEx shipping API in PluginHive show up in my FedEx account dashboard?

1. Use the Tracking ID from the order shipping details in your WooCommerce store or PluginHive plugin interface.
2. Enter the Tracking ID directly on the FedEx website tracking page to view shipment status and updates.

Why do the FedEx API keys appear briefly and then disappear in the PluginHive FedEx plugin, and how can I control which FedEx account is used?

The PluginHive FedEx plugin connects to your FedEx account using a FedEx Compatible Registration process where you provide your FedEx Account number and Billing address. For security reasons, sensitive API keys are masked and not displayed permanently within the plugin settings. The brief appearance of the API keys happens due to caching, but these keys disappear quickly to protect your account information. You do not need to manually enter API credentials; the plugin handles this automatically. Your control over the FedEx account used comes from the FedEx Account number you enter during registration. By entering the correct FedEx Account number, you effectively choose which FedEx developer account the plugin integrates with.

Why do the FedEx Account API credential fields appear prefilled and then disappear, and where should I enter my FedEx credentials in the PluginHive plugin?

The PluginHive plugin registers with FedEx using only the Account number and Billing address, so it does not require full FedEx API credentials. The credential fields you see initially are prefilled with PluginHive’s information as a placeholder but then get hidden once the page fully loads due to caching and plugin behavior. This is expected functionality to prevent users from entering unnecessary data. You do not need to enter any FedEx API credentials in those fields. Simply provide your FedEx Account number and Billing address as required by the plugin, and you can safely ignore the disappearing credential fields.

Why can't I find settings fields to enter FedEx API credentials, password, or production keys in the FedEx plugin, and how do I access or enable these options?

1. Ensure you have updated the FedEx plugin to the latest official version as older versions may not show all configuration fields.
2. Complete the plugin registration and initial setup steps—only after registering your FedEx account within the plugin will the API credential and production key fields appear.
3. Check under WooCommerce → Settings → Shipping → FedEx plugin settings. The API Key, Password, Account Number, Meter Number, and environment selection (sandbox or production) are usually found here.
4. If these options still don’t appear, verify that the user role you are logged in with has sufficient permissions to access all plugin settings.
5. Review the plugin documentation (https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/) for exact location and screenshots of the fields.

Why are the FedEx API credential fields (account number, meter number, API key, and password) hidden in the plugin’s general tab instead of being visible for entry?

The FedEx credentials fields are intentionally hidden in the current version of the PluginHive FedEx plugin because the plugin now uses an automated registration process to link your FedEx account directly during registration. Manually entering API credentials is not required for versions after 7.0.7. The credentials fields briefly appear with dummy data due to caching when the settings page loads but get hidden once the page finishes loading. This is normal behavior because the plugin no longer requires users to input these credentials manually. You can safely ignore these hidden fields as the plugin handles authentication internally once registration completes successfully.

Why am I no longer seeing the option to connect FedEx test or production APIs in the plugin?

If you have connected your FedEx account using the Registration Process within the plugin, the option to add FedEx Production or Test Credentials will no longer appear. This is because the plugin automatically activates your FedEx account for live use upon registration. Note that switching to Test Mode is not possible after this step. However, you can test the plugin safely in live mode without incurring charges, as FedEx will only bill you when labels are scanned. Thus, you can proceed with live mode testing without worry.

What was the issue causing the PluginHive FedEx plugin not to show live rates after I provided my FedEx login credentials, even though the API key seemed correct?

The issue was likely due to a synchronization problem after your FedEx account renewal. Although the API key appeared correct, the plugin needed to re-register your FedEx account credentials to refresh the connection with the FedEx API. Once the PluginHive support team re-registered your FedEx login within the plugin, live FedEx shipping rates started functioning properly. This step effectively resolved any stale or outdated API session or permission issues causing the plugin to not fetch rates.

What steps should users take now regarding FedEx account registration in the PluginHive FedEx plugin amid these API changes?

Users should ensure their FedEx account is properly registered via the plugin using the documented registration process here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx. If the account is already registered, users can continue using the plugin as usual without interruption. No immediate migration is necessary until PluginHive announces the REST API migration steps.

What steps do I take if my FedEx API Key is deactivated and I cannot register my FedEx account in the PluginHive plugin?

1. In your WooCommerce admin, go to **FedEx Registration → License Activation**.
2. Enable the "Deactivate API Key" option and save changes.
3. Log into your PluginHive.com account, navigate to **My Account → API Keys**, and delete any previous license key activations linked to your plugin.
4. Deactivate and then reactivate the FedEx Shipping plugin in WooCommerce.
5. Go back to **FedEx Registration → License Activation**, enable the "API Key Activation" option, configure your license API key and Product ID, then save changes.
6. Now, go to the FedEx registration page and complete the registration using your FedEx account details (account name, number, billing address).
7. Once registration completes, copy and securely store the Secret Key, Client ID, and License Key ID provided.

What are the current credential setup requirements for the WooCommerce FedEx Shipping Plugin by PluginHive, especially regarding API keys and account information?

For PluginHive’s FedEx Shipping Plugin version 7.0.7 and later:

1. You do not need to manually enter FedEx API credentials such as account number, meter number, API key, or password in the plugin’s general tab.
2. Authentication and linking to the FedEx account occur automatically during the plugin registration process within the WooCommerce admin panel.
3. The fields for entering credentials are retained only for legacy customers using versions prior to 7.0.7.
4. To set up, simply register your FedEx account through the plugin’s interface, making sure all required address and contact details comply with FedEx’s requirements.
5. After successful registration, the plugin will seamlessly authenticate and allow shipping rate retrieval and label generation without further credential input.

This new streamlined process reduces user errors and enhances security by avoiding manual credential handling.

Should I provide FedEx API developer account credentials or FedEx shipping account login details for troubleshooting?

Provide the FedEx shipping account login credentials (username and password), not the developer API account details. Additionally, supply your WordPress admin login, the product URL you are testing shipping rates for, and a complete shipping address so support can replicate and investigate the issue effectively.

How do I update or change my FedEx account details within the PluginHive FedEx plugin after reactivating the API key?

1. Open the PluginHive FedEx plugin settings in your WooCommerce dashboard.
2. Locate and click the "Re-Register" button within the FedEx registration section.
3. Complete the registration steps by providing the relevant FedEx credentials and account information.
4. Once re-registration is successful, verify that the new account details are reflected correctly and test shipping rates and label creation.

How can I verify that the PluginHive plugin correctly uses my FedEx account number in REST API requests?

1. Enable debug or logging within PluginHive to capture outgoing FedEx API requests.
2. Check the "accountNumber.value" field and ShippingChargesPayment.Payor.AccountNumber in the request payload to confirm they both contain your real FedEx account number (e.g., 100801981).
3. Confirm the shipping addresses and other required parameters are formatted correctly.
4. If discrepancies exist, ensure your PluginHive plugin settings have your FedEx credentials and accounts entered accurately.

Does the PluginHive plugin expose or reveal the WordPress administrator username through its communication with external servers or FedEx APIs?

No, the PluginHive plugin does not expose, share, or reveal your WordPress administrator username or any login credentials to third-party servers or FedEx. The plugin communicates with FedEx using a secure, tokenized system that only transmits necessary shipping data without disclosing any sensitive site information such as usernames or passwords. To verify this independently, you can temporarily disable the plugin and monitor if any such data is being transmitted. This ensures your administrator login details remain confidential and are not compromised by the plugin.

Does the PluginHive FedEx plugin require manual entry of FedEx API credentials for setup?

No, the PluginHive FedEx plugin uses a FedEx Compatible Registration process that requires only your FedEx account number and billing address to connect. You do not manually input FedEx API credentials such as keys or tokens. This simplifies setup and ensures secure integration with FedEx shipping services.

Do I need to enter FedEx API credentials (Client ID and Secret) from the FedEx Developer Portal in the PluginHive FedEx plugin?

No, you do not need to enter FedEx API credentials such as Client ID and Secret from the FedEx Developer Portal into the PluginHive FedEx plugin. The plugin uses a FedEx Compatible Registration process where you simply connect your FedEx account using your FedEx Account number and Billing address. This process eliminates the need to manage API credentials manually within the plugin.

Do I need to create a shipping API on my FedEx account to use the PluginHive FedEx WooCommerce plugin?

No, there is no need to create a shipping API on your FedEx account. The PluginHive FedEx plugin includes a FedEx-compatible registration process in which you connect your FedEx account to the plugin using only your FedEx Account number and Billing address. You do not need any FedEx API credentials separately. Keep in mind that this registration process does not include a test environment; all shipping labels and tracking numbers generated through the plugin are live. Also, WooCommerce order details do not transfer to the FedEx dashboard, and shipments created via the plugin’s API will not appear on fedex.com, though you can track them there using the provided tracking number.

Can I see the FedEx shipments created via the PluginHive API on my FedEx account dashboard?

No, shipments created via the FedEx Shipping API through the PluginHive plugin do not appear as shipping records on the FedEx website UI. However, you can track your shipments on the FedEx website by entering the Tracking ID of each shipment. FedEx has confirmed that labels created through their API are not listed in their user interface, so this behavior is expected.