Error Messages – WooCommerce Shipping Plugin for FedEx FAQs

Why is the WooCommerce FedEx Shipping plugin not returning any shipping rates even though no settings were changed and debugging shows no errors?

If the WooCommerce FedEx Shipping plugin suddenly stops providing shipping rates without any configuration changes and debugging does not show errors, the likely cause is that FedEx is returning a “Forbidden” error. To resolve this issue, follow these steps:

• Navigate to **FedEx Registration** → **License Activation** in the plugin settings.
• Deactivate the existing license.

• Go to the same **License Activation** page.
• Re-activate the license.

• Go to **FedEx Registration** → **Registration** within the plugin settings.
• Complete the re-registration process for your FedEx account.

After completing these steps, test the shipping rates again for any US address or your store location. This process refreshes the license and FedEx account connection, which typically resolves “Forbidden” errors and restores proper rate retrieval.

Why does the WooCommerce FedEx shipping method show the message "There are no shipping options available" at checkout even after updating WooCommerce and enabling debug mode without errors?

1. Verify that you are using the latest version of the PluginHive WooCommerce FedEx Shipping plugin (version 7.1.2 or later).
2. Ensure your FedEx account is connected correctly through the newest compatible registration method provided by the plugin, rather than the deprecated FedEx Web Services approach.
3. Follow the official PluginHive guide for setting up FedEx integration: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx
4. Activate the plugin license on your site.

Why does the Fatal error "Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given" occur when clicking the "Create Shipment" button in the PluginHive FedEx WooCommerce plugin, and how can it be fixed?

1. Check the order details for any missing or malformed numeric fields, such as product weight, quantity, or package dimensions. Ensure all numeric fields have valid numeric values.
2. Ensure your WooCommerce product data for the order is complete and correctly formatted (weights in numeric format, not text).
3. Verify that all related plugins, including PluginHive FedEx shipping, WooCommerce, and WordPress, are updated to their latest stable versions to prevent compatibility issues.
4. If you have customizations affecting the order data or shipping calculations, review them to confirm they provide proper numeric values, not strings.
5. If you have access to the plugin files, locate the line causing the error (`class-wf-fedex-woocommerce-shipping-admin-helper.php` around line 5080). Check if type casting to float or int before using `round()` is missing and could be temporarily added as a workaround.
6. Collect WooCommerce error logs and debugging information, then contact PluginHive support with this information for a permanent fix or patch.

Why does my website show a critical error "Allowed memory size exhausted" when activating the FOX Currency plugin alongside the PluginHive WooCommerce FedEx Shipping plugin, and how can I fix it?

1. Increase the PHP time limit to more than 1200 seconds.
2. Increase the WordPress memory limit to at least 4 GB.

Why does my website crash and show a critical error when I try to install a multi-currency plugin like FOX Currency along with the PluginHive WooCommerce FedEx Shipping plugin?

1. Increase the PHP time limit to more than 1200 seconds.
2. Increase the WordPress memory limit to at least 4 GB.

Why does activating the FedEx WooCommerce plugin cause a critical error with the message "Uncaught Error: Undefined Constant 'CURLOPT_HTTPHEADER'"?

1. Verify if the php-curl extension is installed and enabled on your server. This is typically done via your server’s PHP configuration or by contacting your hosting provider.
2. If it is not installed, request your hosting provider to install and enable the cURL extension.
3. Once cURL is enabled, the plugin will be able to function properly without throwing this error, and FedEx shipping rates should display on the checkout page.
4. After enabling cURL, reactivate the FedEx plugin and test the checkout page to confirm rates are showing correctly.

Why do I receive a TCPDF_PARSER ERROR related to decodeFilterFlateDecode when trying to bulk print FedEx shipping labels using the WooCommerce FedEx Shipping Plugin?

This error occurs because the current third-party PDF library used by the WooCommerce FedEx Shipping Plugin does not support bulk printing of FedEx labels. Specifically, the TCPDF parser encounters an invalid code during PDF processing, leading to the "decodeFilterFlateDecode: invalid code" exception. Bulk printing multiple FedEx labels via the "Bulk actions" option is not supported with the existing library.

Why do I get the error "Shipping There are no shipping options available. Please ensure that your address has been entered correctly" when a customer selects "FedEx Hold at Location (optional)" in PluginHive Shipping for WooCommerce?

This error typically occurs when the FedEx Hold at Location shipping method is not properly configured or when the entered customer address does not meet FedEx requirements for that service. To resolve this:

1. Verify that the FedEx Hold at Location option is enabled in your PluginHive Shipping plugin settings.
2. Ensure that the customer’s shipping address is correctly formatted and complete, including postal code and country information.
3. Confirm that your FedEx account supports Hold at Location services in the shipping region.
4. Check if your plugin license is active and updated, as expired licenses may disable certain shipping methods.
5. If you are using an outdated plugin version, consider renewing your license to receive updates and support, which can fix compatibility and service availability issues.

If the problem persists after these checks, contact PluginHive support with your purchase order number and detailed error information.

Why am I receiving an error when attempting to generate bulk FedEx shipping labels using the PluginHive FedEx WooCommerce Shipping plugin?

The error occurs because the current FedEx plugin uses a third-party library that does not fully support bulk label printing functionality. As a result, bulk printing FedEx labels via the plugin’s bulk actions feature is not working properly. To avoid issues, do not attempt to generate or print FedEx labels in bulk using the bulk action feature in this plugin until the limitation is resolved.

Why am I getting the error "Call to undefined method WC_Order::get_shipping_phone()" when creating a FedEx shipment label in WooCommerce after updating the FedEx shipping plugin?

This error occurs because the WooCommerce version you are using (3.8.3) is outdated and does not support newer methods that the updated FedEx shipping plugin relies upon, such as `get_shipping_phone()`. To resolve this issue, you need to update your WooCommerce plugin to the latest version (currently 9.4.1 or newer). Updating WooCommerce ensures compatibility with the FedEx shipping plugin and eliminates the fatal error during shipment creation.

Why am I getting the "1000 – Internal Service Error" when submitting the registration form in the WooCommerce FedEx Shipping plugin setup?

1. Ensure that the street address and company name fields do not exceed 25 to 30 characters.
2. Enter the phone number without the country code.
3. Make sure to use the exact billing address as registered in your FedEx account by verifying it at FedEx website under My Profile > Contact Information.

Why am I getting an "Internal Service Error" (error 1000) when registering the updated WooCommerce FedEx Shipping Plugin, and how can I resolve it?

1. Ensure that the street address line and company name do not exceed 25 to 30 characters.
2. Enter the phone number without including the country code.
3. Use the exact shipping address as listed on your FedEx invoice to avoid discrepancies.
4. After making these corrections, attempt to register the plugin again.

Why am I getting a fatal error "Unsupported operand types: int + string" in the FedEx WooCommerce Shipping plugin after upgrading to PHP 8.2, and how can I fix it?

1. Locate the affected line in the plugin file `class-wf-fedex-woocommerce-shipping.php` (line 1934 as per the error).
2. Update the code to ensure proper type casting before performing addition or other arithmetic operations. For example, cast string variables to integers or floats explicitly like:
3. Replace any other arithmetic operations mixing strings and integers with similarly safe, type-correct code.
4. Test the changes in a staging environment running PHP 8.2 to confirm the fatal error is resolved.
5. Alternatively, verify you are using the latest version of the FedEx WooCommerce Shipping plugin, as it may contain fixes for PHP 8.2 compatibility. If not on the latest version, update the plugin first and retest.
6. If the error persists after updating, you may need to apply the type casting fix manually or reach out to PluginHive support with detailed information for further assistance.

Why am I encountering a "Allowed memory size exhausted" error when syncing the database with the WooCommerce FedEx Shipping Plugin using HPOS, and what is causing it?

The error "Allowed memory size of 536870912 bytes exhausted" occurs because the plugin stores large amounts of meta data for each order, specifically the `ph_available_fedex_hold_at_location` meta key. This key contains data about all FedEx Hold at Location points, which can be very large if many records are stored (in your case, 5221 records occupying over 1GB). This significant data storage in order meta causes excessive memory consumption during database syncing, leading to the memory exhaustion error.

What steps should I take if I face a critical error related to the WooCommerce FedEx Shipping Plugin while creating shipment labels?

1. Check if the Insurance setting is enabled in the plugin. If yes, temporarily disable it to avoid the fatal error.
2. Update the plugin to the latest version (7.1.4 or above), as this version includes a fix for the issue.
3. After the update, retry creating the shipment label.
4. If the problem persists, enable Debug Mode in plugin settings to collect error logs and submit a diagnostic report to PluginHive support for further troubleshooting.

What steps should I take if I encounter a "Failed to get Internal Endpoints" error in the WooCommerce FedEx Shipping plugin?

1. Update the WooCommerce FedEx Shipping plugin to the latest version (at least version 7.1.4).
2. Go to the WordPress admin dashboard, then navigate to **FedEx Shipping → License Activation**.
3. Deactivate the current plugin license.
4. Reactivate the plugin license by re-registering your FedEx account in the License Activation panel.

What should I do when the WooCommerce FedEx Shipping Plugin causes a fatal error related to the method WC_Order::get_shipping_phone() on my site running older versions of WordPress and WooCommerce?

1. Update WordPress, WooCommerce, and the FedEx Shipping Plugin to their latest versions (currently FedEx plugin 7.1.3). These updates ensure compatibility and smooth functionality.
2. Since your site is complex and live, create a staging environment to perform these updates without affecting your live site’s functionality or sales.
3. After setting up the staging site, install the latest versions and test all key operations, including printing FedEx shipping labels, to confirm the issue is resolved.
4. Only after successful testing on staging, proceed to update the live site with the same versions.
5. Note that the plugin license must be active, and the FedEx account should be connected using the current registration process for the plugin to function correctly. You can find detailed setup instructions here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx

What should I do to diagnose critical errors occurring in the FedEx WooCommerce Shipping plugin when shipping orders?

1. Access your WordPress admin dashboard.
2. Navigate to WooCommerce → Status → Logs.
3. From the dropdown, select the latest fatal error log file related to the FedEx plugin (e.g., fatal-errorwf-fedex-woocommerce-shipping).
4. Open the log to review the detailed error messages.
5. Share the complete fatal error log content with the PluginHive support team for precise assistance, as debug data from unrelated logs may not help resolve the issue.

What should I do if the FTP server connected to the WooCommerce FedEx Shipping Plugin shows a timeout error and does not list directories?

1. Contact your hosting provider or server administrator to verify and modify the FTP user permissions. The user should have read and write permissions to the directories used by the plugin.
2. Ensure firewall or security software is not blocking FTP connections or causing timeouts.
3. Verify FTP settings such as port number, passive mode, and encryption type to be compatible with your hosting environment.
4. After permissions and settings are corrected, test FTP access again through the plugin or a standalone FTP client to confirm directories list correctly and uploads/downloads are possible.

What should I do if I receive the error "Failed to get Internal Endpoints" in the FedEx WooCommerce Shipping plugin?

1. Verify that your plugin license is active by going to FedEx Registration → License Activation in the plugin settings.
2. If the license is active but the error persists, deactivate the plugin license from the same License Activation section.
3. Reactivate the license immediately afterward.
4. After re-activating the license, re-register your FedEx account by going to FedEx Registration → Registration.

What should I do if I receive a critical PHP error related to the FedEx WooCommerce Shipping plugin on my website?

1. Take note of the exact error message and file location.
2. Update the FedEx plugin to its latest version as fixes may have been released.
3. Ensure that your WordPress core and WooCommerce plugin are updated and fully compatible.
4. Disable other plugins to identify potential conflicts.
5. Avoid using affected plugin features (e.g., uploading FedEx documents) until resolved.
6. Contact PluginHive support with detailed error logs, so their Level 3 team can analyze and provide a patch or guidance to fix the issue.

What should I do if I face difficulties after updating the FedEx WooCommerce Shipping plugin to fix the Kadence email designer fatal error?

1. Clear your site cache and browser cache.
2. Disable other third-party plugins temporarily to rule out conflicts.
3. Switch to a default WordPress theme (like Twenty Twenty-Three) to test for theme conflicts.
4. If the problem remains, reach out to PluginHive support with detailed information about your environment and the issue encountered.

What is the recommended solution if the WooCommerce FedEx plugin causes shipment creation errors due to the "Exclude Tax" option?

1. Backup your website and database as a precaution.
2. Go to the WordPress admin dashboard >> Plugins.
3. Locate the WooCommerce Shipping Plugin for FedEx with Print Label.
4. If an update is available, click “Update Now” to upgrade to version 7.1.6 or later.
5. After updating, verify shipment creation functionality works as expected even with the “Exclude Tax” option enabled.

What is the official resolution for the compatibility issue between the FedEx WooCommerce Shipping plugin and the Kadence WooCommerce Email Designer plugin that causes the fatal error?

The PluginHive team has identified and replicated this issue. They have released an updated version of the WooCommerce FedEx Shipping Plugin with Print Label (version 7.1.3) that includes enhanced compatibility with the Kadence WooCommerce Email Designer plugin, resolving the fatal error issue. Users experiencing this error should update their FedEx plugin to version 7.1.3 or later to fix the problem.

What is the minimum product weight required to avoid fatal errors when using the FedEx WooCommerce plugin?

The minimum product weight must be set to 0.01 units (lbs or kgs, depending on your store settings). Ensure no product involved in shipping calculations has a weight less than 0.01 to prevent fatal errors. This standardized minimum shipment weight is important for successful rate calculations and label generation.

What is causing the fatal error "Call to undefined method WP_Post::get_id()" in the FedEx WooCommerce Shipping plugin when editing WooCommerce orders, and how can this be resolved?

1. Identify the offending line in `ph-fedex-doc-upload-view-html.php` (line 25 as per the error).
2. Replace the method call `$post->get_id()` with `$post->ID` to access the post ID correctly, since WP_Post objects expose the ID as a public property, not a method.
3. Alternatively, verify that WooCommerce and WordPress versions are compatible with the plugin version used, and update all components if necessary.
4. Apply this fix in a staging environment to confirm it resolves the issue without side effects.
5. If unsure how to make this change safely, contact PluginHive support with error details and environment information (WordPress, WooCommerce, PHP versions).
6. As a best practice, keep WooCommerce, WordPress, and all plugins updated to avoid compatibility problems.

What information should I provide to PluginHive support to diagnose WooCommerce FedEx Shipping Plugin errors efficiently?

1. The full text of the WordPress error notification email that mentions the FedEx plugin or the fatal error.
2. The complete WooCommerce fatal error log(s) accessed via WooCommerce → Status → Logs, particularly the latest fatal error logs.
3. Your site’s URL to allow direct investigation if needed.
4. A detailed description of the issue, including when and how the error or crash occurs (e.g., during label printing, checkout, or other FedEx plugin actions).
5. Your current WordPress, WooCommerce, and WooCommerce FedEx plugin versions.
6. Any recent changes to the site environment such as updates, new plugins installed, or custom code added.

What does the FedEx error "1000 – Internal Service Error" mean when using the WooCommerce FedEx Shipping Plugin, and how can I resolve it?

1. Ensure that the street address line and company name do not exceed 25 to 30 characters. Shorten or abbreviate them if necessary.
2. Enter the phone number without including the country code. Only the local number should be used.
3. Verify that the shipping address exactly matches the billing or shipping address as listed in your FedEx invoice or FedEx account details. Inconsistent or mismatched addresses can trigger the error.
4. After correcting these details, retry registering or using the FedEx service in the plugin.

What does the error "Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given" in the FedEx WooCommerce Shipping plugin mean, and how can it be addressed?

1. Identify the context in which this error occurs by reviewing the stack trace and the plugin file mentioned (e.g., `class-wf-fedex-woocommerce-shipping-admin-helper.php` at line 5041).
2. Verify the data being passed to the function calling `round()` to ensure it is properly cast or sanitized as a numeric value before rounding.
3. Update or patch the plugin code to include type validation or conversion (`floatval()` or `intval()`) before applying `round()`.
4. Contact PluginHive support with the fatal error log to check for existing fixes or updated plugin versions that resolve this type mismatch.
5. As a temporary workaround, avoid input or order data that might trigger non-numeric values in this calculation until the fix is deployed.

What does the error "Uncaught Error: Class 'SYN_Shipping_Method' not found" mean in the FedEx plugin for WooCommerce, and how can it be resolved?

1. Verify that the FedEx plugin is fully installed and not missing any files. A partial or corrupted installation can cause class files to be missing.
2. Ensure that all plugin dependencies and base classes are installed and activated. Sometimes this class belongs to a core library or another plugin component that must be active.
3. Update the FedEx plugin to the latest compatible version, which might fix missing class declarations if they were added in updates.
4. Check for plugin conflicts by temporarily disabling other plugins to see if `SYN_Shipping_Method` becomes available.
5. If you customized any plugin files, restore original files because custom changes may remove or alter class definitions.
6. If your plugin source is purchased, confirm you have a valid license and access to updates from PluginHive, as they provide support and updated plugin versions containing needed classes.
7. Contact PluginHive support with your purchase details to get the correct plugin files and troubleshooting assistance.

What does the error "Customer matched zone locations not covered by your other zones" mean in WooCommerce, and how can I resolve it after switching servers and updating plugins?

The error "Customer matched zone locations not covered by your other zones" originates from WooCommerce’s shipping zone settings, not from the FedEx plugin. It typically appears when debug mode is enabled within WooCommerce’s shipping settings. To resolve this issue:

1. Go to WooCommerce > Settings > Shipping > Debug Mode and disable debug mode.
2. Review your shipping zones configuration under WooCommerce > Settings > Shipping to ensure that all customer locations are correctly assigned to an appropriate shipping zone.
3. Verify there are no conflicts or gaps in zone coverage that could cause customers to fall outside defined zones.
4. After adjusting zones, test the checkout process again to confirm the error no longer appears.

This error is a standard WooCommerce notification and is not controlled by the FedEx Shipping plugin.

What does the "Notice: Function ID was called incorrectly. Order properties should not be accessed directly" error mean when clicking on an order number in WooCommerce, and how can it be resolved?

1. Identify which plugin or theme code is causing direct property access by reviewing the backtrace and debugging logs.
2. Update the involved plugin(s) and theme(s) to their latest versions, as developers usually fix such deprecated usage in updates.
3. If you have custom code, modify it to use WooCommerce’s official getter functions, for example, `$order->get_id()` instead of `$order->ID`.
4. Enable WP_DEBUG and WP_DEBUG_LOG in your `wp-config.php` for detailed debugging and trace any other incorrect usage.
5. Consult WooCommerce developer documentation or support if unsure about proper usage.

What could be causing intermittent 502 Bad Gateway errors after installing the PluginHive WooCommerce FedEx plugin, and how can I troubleshoot it?

1. Deactivate all other plugins except WooCommerce and the PluginHive FedEx shipping plugin.
2. Check if the 502 errors persist with only these essential plugins active.
3. If the problem continues, consider providing WordPress admin access to the support team so they can inspect your setup and install the plugin correctly if needed.

What causes the PHP fatal error "current(): Argument #1 must be of type array, null given" in the FedEx WooCommerce Shipping plugin and how can it be fixed?

The PHP fatal error "current(): Argument #1 must be of type array, null given" typically occurs when the plugin expects an array input but receives a null value instead. This can happen due to:

• Corrupted or missing data related to shipment packages or settings.
• Plugin code attempting to process shipment data before it is properly initialized.
• Conflicts from running outdated plugin versions alongside newer WordPress or WooCommerce versions.

To fix this error:

1. Ensure the plugin is updated to the latest stable version.
2. Clear any cached data or transients related to shipping calculations.
3. Deactivate and then reactivate the plugin to refresh its internal data.
4. Follow the license reactivation process to ensure the plugin functions fully.
5. Check that all required shipping configurations and API credentials are correctly set.
6. If the problem continues, examine server logs to find the exact context of the null input.
7. Contact PluginHive support with the error details for advanced troubleshooting.

This error typically resolves by proper plugin updates and license reactivation combined with configuration verification.

What causes the fatal error when creating labels with the WooCommerce FedEx Shipping Plugin, and how can I resolve it?

The fatal error during label creation is caused by a type error in the plugin code where the function `sizeof()` receives a boolean value instead of an array or countable type. This occurs specifically in the file `class-wf-fedex-woocommerce-shipping-admin-helper.php`. To resolve this issue temporarily and be able to create shipping labels, disable the Insurance setting in the plugin. Disabling insurance will prevent the fatal error and allow label creation to proceed without interruption.

What causes the fatal error "Call to undefined method WC_Order::get_shipping_phone()" in the WooCommerce FedEx Shipping Plugin?

This error is caused by incompatibility between your WooCommerce version and the FedEx plugin version. The method `get_shipping_phone()` is not available in older WooCommerce versions (such as 3.6.7), but the latest FedEx plugin expects it. Running an older WooCommerce with a newer plugin leads to this error. To resolve it, update WooCommerce and WordPress to the latest versions so that all required methods exist and are supported by the FedEx plugin. If updating is not possible immediately, you must create a staging environment for safe testing before upgrading your live site.

What causes the "Uncaught DivisionByZeroError: Division by zero" error in the FedEx WooCommerce Shipping plugin, and how can I fix it?

1. Review your product catalog in WooCommerce.
2. Ensure every product has a valid, non-zero cost or price set.
3. Update any products that have missing or zero prices.
4. Clear any caching plugins or server cache to make sure changes are reflected.

What causes the "Fatal error: Division by zero in class-wf-packing.php" in the FedEx WooCommerce shipping plugin, and how can I fix it?

1. Verify that every product in your WooCommerce store has a minimum product weight set.
2. Set the minimum weight for all products to 0.01 (lbs or kgs depending on your unit setting).
3. Save changes and test shipping rates again.

What causes the "Fatal error: Call to a member function get_meta() on bool" when using the Kadence WooCommerce Email Designer plugin with the FedEx WooCommerce Shipping plugin?

This fatal error occurs because the FedEx WooCommerce Shipping plugin attempts to call the `get_meta()` method on a variable that unexpectedly holds a boolean value (false) instead of an object. This usually indicates a failed database query or missing object, causing the method call to fail. The Kadence WooCommerce Email Designer plugin triggers this condition indirectly by invoking FedEx plugin functionality while rendering email previews or during Appearance > Customize.

What causes the “Call to undefined method WP_Post::get_id()” fatal error in the FedEx WooCommerce Shipping plugin when uploading FedEx documents, and how can I fix it?

1. Confirm you are using the latest version of the PluginHive FedEx WooCommerce Shipping plugin, as updates often fix such bugs.
2. If the latest version is installed and the problem remains, consider:
3. If the issue persists, reach out to PluginHive support with the error details and allow their Level 3 support team to apply a patch or provide a code fix addressing this undefined method call.

What causes an error related to opening an order in WooCommerce that mentions `et_pb_add_custom_box`, and how can I address it when using the PluginHive FedEx plugin?

1. Identify that the source is the Divi theme or Divi-specific plugins by checking the error backtrace and logs.
2. Contact Divi support or consult Divi community resources for resolution or updates that fix compatibility issues with WooCommerce.
3. Temporarily switch to a default theme (like Twenty Twenty-Three) or disable Divi-related plugins to confirm the source of the conflict.
4. Consider updating Divi and all associated plugins to their latest versions to incorporate fixes for compatibility with WooCommerce.
5. If you receive error screenshots or logs specifically referencing `et_pb_add_custom_box`, share these with Divi support for troubleshooting.

Is the PluginHive WooCommerce FedEx Shipping plugin compatible with WooCommerce High-performance Order Storage, and how can I resolve compatibility errors related to this setting?

1. Verify that you are using the latest version of the plugin. Compatibility with High-performance Order Storage was ensured starting from version 7.1.0.
2. Update the plugin to version 7.1.0 or above through your WordPress dashboard or by manually uploading the updated plugin files.
3. After updating, clear your site and browser caches to prevent stale data issues.
4. Test the plugin functionality again to confirm that the compatibility error is resolved.

Is the FedEx WooCommerce Shipping plugin compatible with PHP 8.2, and how should I troubleshoot related fatal errors?

1. Confirm you are using the latest version of the FedEx WooCommerce Shipping plugin. Update if necessary.
2. Identify when and where the error occurs—during live checkout, shipping rate calculation, or elsewhere.
3. Check if any PHP compatibility checker plugins are issuing warnings that may be false positives. Real runtime errors during live operations should be prioritized.
4. Try reproducing the issue on a staging copy of your site with other plugins deactivated to rule out conflicts.
5. Collect detailed error logs and steps to reproduce the problem and share these with PluginHive support to help diagnosis.
6. If errors relate to type mismatches, review plugin code to ensure all mathematical operations cast string operands to numeric types beforehand, as PHP 8.2 enforces strict typing.

Is it possible to make the recipient phone number mandatory on the WooCommerce checkout page to avoid FedEx label errors?

1. From your WordPress dashboard, go to "Pages" and find the "Checkout" page.
2. Click “Edit” on the Checkout page.
3. Locate the shipping address section (or where phone number input is).
4. Set the phone number field to "Required" instead of optional.
5. Save the changes.

How should I troubleshoot and resolve shipping issues and critical errors on checkout caused by the WooCommerce FedEx Shipping Plugin?

1. Verify that WooCommerce is updated to the latest supported version.
2. Ensure your plugin version is the latest release.
3. Confirm that your server meets all PHP and WordPress version requirements specified by the plugin.
4. Deactivate other shipping or conflicting plugins temporarily to rule out compatibility issues.
5. Check for error logs in WordPress to identify specific error messages and fix accordingly.
6. Enter correct FedEx API credentials in the plugin settings.
7. If errors persist, contact plugin support with full details and error reports.

How should I systematically troubleshoot errors occurring when creating shipments with the PluginHive FedEx WooCommerce plugin?

1. Confirm you are running the latest versions of the PluginHive FedEx plugin, WooCommerce, and WordPress to avoid compatibility problems.
2. Check for recent plugin installations or updates that may conflict with the shipping process. Disable suspicious plugins temporarily to isolate conflicts.
3. Review WooCommerce logs by navigating to WooCommerce → Status → Logs. Open the Fatal Error Log to find detailed error messages related to shipment creation.
4. Examine if custom code modifications or themes might be triggering PHP type errors or deprecated function warnings.
5. Validate order data integrity, ensuring all required shipment-related fields (weight, dimensions, shipping class) are properly set and formatted as numbers where expected.
6. Replicate the error using specific orders and note exact error messages to provide thorough information to PluginHive support.
7. Provide error logs and specific order numbers to the support team for in-depth analysis and resolution.

How should I provide information to PluginHive support to help reproduce and resolve issues related to fatal errors in the FedEx WooCommerce Shipping plugin?

1. Exact error messages and stack traces as they appear in server logs or on screen.
2. The exact time and context when the error occurs (e.g., during live checkout, shipping rate calculation).
3. Steps to reliably reproduce the error on your site or a staging copy.
4. Screencast videos demonstrating how to trigger the issue if possible.
5. Details of your environment including PHP version, WordPress version, WooCommerce version, plugin versions, server OS, and any active caching or security plugins.
6. A staging site or cloned environment with admin access (if possible) where PluginHive support can perform troubleshooting without impacting your live site.
7. Confirmation about whether other plugins can be temporarily deactivated to rule out conflicts.

How should I format phone numbers and addresses to avoid registration errors with FedEx accounts in the PluginHive WooCommerce FedEx shipping plugin?

• Remove any country codes from the phone number. Enter only the local phone number digits.
• Limit address lines and company name fields to fewer than 30 characters each, preventing rejection due to field length.
• Use a valid 5-digit postal code for the billing and sender addresses (no extended zip codes or longer numeric strings).
• Ensure the fields in the FedEx profile are correctly assigned to their appropriate roles (company name, address line 1, address line 2, postal code, city, state).
• Use the sender address exactly as it appears in the FedEx account when registering the plugin.

How does PluginHive support diagnose critical errors related to the FedEx plugin on a WooCommerce site?

1. Verify that the user’s WooCommerce, WordPress, and FedEx plugin versions are current to rule out version compatibility issues.
2. Request information about the timing of the error onset and any recently installed plugins to identify potential conflicts.
3. Ask the user to retrieve and share the fatal error logs from WooCommerce’s status logs for detailed debugging information.
4. Review the site configuration and plugin settings by logging into the user’s admin panel (with permission).
5. Request specific order numbers related to the error to replicate the issue.
6. Seek permission to generate labels on behalf of the user to fully test and troubleshoot the shipment creation process.

How do I resolve the error when generating FedEx shipping labels related to account connection in the PluginHive WooCommerce FedEx Shipping plugin?

1. Follow the registration steps provided in the official PluginHive knowledge base article on setting up the WooCommerce FedEx Shipping plugin: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx
2. Complete the FedEx account registration within the plugin to enable label generation.

How do I resolve the error "Number of Commodities exceeds min or max limit" when creating a FedEx shipment in the WooCommerce Shipping Plugin for FedEx?

1. Do not modify the weight or dimension details of any product after the shipment package is initially generated by the plugin.
2. Use the plugin’s **Re-generate package** feature to recreate the shipment package data accurately.
3. After re-generating the package, proceed to **Create shipment** again.
4. This process resets the packaging details and helps comply with FedEx API constraints on the number of commodity items per shipment.
5. If the error persists, check your shipment's item count and packaging logic to ensure it adheres to FedEx’s minimum and maximum commodity limits per shipment.

How do I resolve the "Failed opening required 'includes/third-party-plugin-support/ph-fedex-woocommerce-blocks.php'" error in the FedEx WooCommerce Shipping plugin?

1. Verify that the plugin files were uploaded completely and correctly. Re-upload the FedEx WooCommerce Shipping plugin files via FTP or your hosting file manager, ensuring no files are missing.
2. Check the file path `/includes/third-party-plugin-support/ph-fedex-woocommerce-blocks.php` exists in the plugin installation folder.
3. If the file is missing, download a fresh copy of the plugin from the official source and replace the plugin directory.
4. Clear any caching mechanisms on your site and server to ensure the latest files are loaded.
5. Reactivate the plugin and check for any new errors.

How do I identify and fix errors caused by incorrect product configuration in the FedEx WooCommerce Shipping plugin?

1. Locate the product in your WooCommerce admin that relates to the error-triggering order.
2. Go to the Edit Product page.
3. Review any custom shipping values, such as "Custom declared value."
4. Remove invalid characters like hyphens or spaces that may cause calculation or API errors.
5. Save the product after updating the values.
6. Test label creation again to confirm the error is resolved.

How do I fix the fatal error caused by the FedEx WooCommerce Shipping plugin when used with the Kadence WooCommerce Email Designer plugin?

1. Log in to your WordPress admin dashboard.
2. Navigate to Plugins > Installed Plugins.
3. Locate the WooCommerce FedEx Shipping Plugin with Print Label.
4. Update the plugin to version 7.1.3 or the latest available version.
5. Clear any site and browser caches.
6. Verify that the error no longer occurs by visiting Appearance > Customize or using the Kadence Email Designer plugin.

How can I use the PluginHive WooCommerce FedEx Shipping plugin if I don’t have a FedEx Meter Number, Web Services Key, or Web Services Password, and I encounter the error "You are not authorized for registration"?

1. Reload the plugin registration page.
2. Clear your website cache and browser cache completely.
3. Attempt the registration process again using your FedEx Account Number and billing address as prompted by the plugin.

How can I troubleshoot barcode scanning errors on FedEx shipping labels generated by the WooCommerce FedEx Shipping Plugin?

1. Inspect the printed label (physical label or PDF) to ensure the barcode is complete, not blurry, cut off, or obscured.
2. Confirm the label format (ZPL, PDF) is compatible with your printer and FedEx expectations.
3. Try printing labels from different browsers or printing devices to rule out printer driver issues.
4. Check shipping service types used (FedEx Ground, Home Delivery) for any specific barcode or label requirements.
5. Cross-verify if the FedEx Ship Manager system can generate working labels for the same shipments.
6. Test scanning with different barcode scanners to rule out hardware issues.
7. Consult with FedEx representatives for any known scanning issues related to label types or shipping methods.
8. If the problem is consistently reproducible for multi-package shipments, gather sample labels (including ZPL files and PDFs) and provide these along with order numbers to PluginHive support to analyze the barcode generation process.

How can I troubleshoot and resolve shipping errors related to "Special Service COD is not allowed" for Panama orders using the WooCommerce Shipping Plugin for FedEx?

1. Open the WooCommerce Shipping Plugin for FedEx settings in your WordPress dashboard.
2. Navigate to the "Rates & Services" section.
3. Disable the option labeled "FedEx COD" since Cash on Delivery is not supported for Panama by FedEx.
4. Go to the "Special Service" tab and set the "Delivery Signature" option to "Service Default."
5. Save the changes.

How can I resolve the shipment creation error caused by the "Exclude Tax" option under Special Services in the PluginHive FedEx WooCommerce plugin?

1. Access your WooCommerce admin panel.
2. Navigate to the PluginHive FedEx shipping plugin settings.
3. Locate the Special Services section within the plugin configuration.
4. Find the "Exclude Tax" option and disable (uncheck) it.
5. Save the plugin settings.
6. Attempt to generate the shipment again from the order screen.

How can I resolve the parse error caused by an extraneous comma in the WooCommerce FedEx Shipping Plugin’s PHP file?

1. Locate the PHP file triggering the error. For example, `/wp-content/plugins/fedex-woocommerce-shipping/includes/class-wf-fedex-woocommerce-shipping-admin.php`.
2. Open the file in a code editor and carefully check the syntax, especially near the reported line.
3. Remove any extraneous commas or syntax errors identified.
4. Save the file and refresh your WordPress site to confirm the error is resolved.
5. To avoid manual fixes, update the plugin to the latest version (7.0.9 or higher), where this issue has been officially fixed by PluginHive. You can update the plugin via the WordPress admin dashboard under Plugins > Installed Plugins, then click “Update now” next to the WooCommerce FedEx Shipping Plugin.

How can I resolve the malware scan error related to `set_magic_quotes_runtime(0)` in the WooCommerce FedEx Shipping plugin?

To resolve the malware scan error, update your WooCommerce FedEx Shipping plugin to version 7.1.1 or later. This version removes the deprecated `set_magic_quotes_runtime` code that was triggering false malware alerts. You can update the plugin through your WordPress admin panel by navigating to the plugin section and installing the latest update. After updating, re-scan your system to confirm that the issue has been resolved. If you encounter any difficulties during the update, contact PluginHive support for assistance.

How can I resolve the critical error related to uploading FedEx documents in the WooCommerce FedEx Shipping Plugin?

To fix the critical error occurring when uploading FedEx documents on the order edit page, update your WooCommerce FedEx Shipping plugin to the latest version (version 8.0.2 or above). This update includes a fix that supports uploading documents to orders saved in both HPOS and WP Post tables via the REST API, which addresses the "Upload FedEx Documents" critical error. After updating, test the feature to confirm the issue is resolved.

How can I resolve or work around the bulk printing error for FedEx labels in the WooCommerce FedEx Shipping Plugin?

At present, there is no immediate workaround within the plugin because the bulk printing feature relies on a third-party library that cannot handle FedEx bulk label printing correctly. The plugin developer is actively creating a new internal library specifically to support bulk printing of FedEx labels. Users should:

1. Continue printing labels individually if bulk printing is critical and the issue blocks workflow.
2. Monitor official PluginHive communications for updates about the new library release.
3. Expect the bulk printing feature with FedEx label support in an upcoming plugin update targeting Q3 of this year.
4. Avoid attempting bulk printing with the current plugin version to prevent PDF generation errors.

How can I replicate the "Fatal error" caused by the interaction between the Kadence WooCommerce Email Designer plugin and the FedEx WooCommerce Shipping plugin?

1. Install the Kadence WooCommerce Email Designer plugin on a WordPress site with WooCommerce.
2. Also install and activate the FedEx WooCommerce Shipping plugin on the same site.
3. In the WordPress admin dashboard, navigate to Appearance > Customize.
4. The fatal error should appear due to incompatibility triggered during email preview or customization execution.

How can I permanently fix the fatal error encountered while creating shipping labels with the WooCommerce FedEx Shipping Plugin?

1. Update the WooCommerce FedEx Shipping Plugin with Print Label to version 7.1.4 or later from the WordPress admin panel.
2. After updating, test label creation again to confirm the error no longer occurs.
3. If you encounter any issues after the update, reach out to PluginHive support for assistance.

How can I fix the "Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given" error in the FedEx WooCommerce plugin?

1. Ensure you are using the latest version of the FedEx WooCommerce Shipping plugin (currently version 8.0.2).
2. If not updated, activate your plugin license key to enable automatic update notifications within WordPress.
3. Check for plugin updates via WordPress Dashboard → Updates → Check Again.
4. If no update option appears, download the latest plugin version from your PluginHive account on pluginhive.com under "My Accounts."
5. Deactivate and delete the old plugin version from your WordPress plugins list (your settings will be preserved).
6. Install and activate the downloaded latest version.
7. Verify that your FedEx account is registered correctly in the plugin using either SOAP or REST API (check under FedEx Shipping → Registration).
8. Enable Debug Mode in the FedEx plugin settings and test the shipping rate retrieval again.

How can I determine if the WooCommerce FedEx Shipping Plugin is causing a fatal error on my WordPress site?

1. Check the error notification email from WordPress carefully to see if it specifically mentions the FedEx plugin.
2. Access your WordPress dashboard and navigate to WooCommerce → Status → Logs. Open the latest fatal error log to review the error details.
3. Examine the error log paths and messages to see if they relate to files or functions within the FedEx plugin folder. If the paths point elsewhere (for example, core WordPress files such as `/wp-includes/formatting.php`), it indicates the issue may not be originating from the FedEx plugin.
4. If unclear, provide the complete WordPress error email and the site URL to support for further analysis. This helps verify if the FedEx plugin is responsible or if another component is causing the error.

Does the FedEx dimension limit error prevent the WooCommerce FedEx Shipping Plugin from calculating shipping costs?

No. Even when the FedEx API returns an error about package dimension limits for services like SmartPost, the plugin still obtains valid shipping rates from other FedEx services. The error message is informational and related specifically to parts of the rate request involving SmartPost. Therefore, shipping functionality continues without interruption despite the error message appearing. To eliminate these errors, disable SmartPost if you are not using that service.

After updating the WooCommerce FedEx Shipping Plugin, a critical error appeared on my website. How can I fix this issue?

1. Verify your WooCommerce plugin version.
2. Update WooCommerce to the latest version (at least version 9.4.3) via WordPress Dashboard → Plugins → Installed Plugins → Update now.
3. After updating WooCommerce, check if the critical error persists.

Why is the WooCommerce FedEx Shipping Plugin causing a critical error during checkout and the cart shipping not working after upgrading, and can I revert to the old database and files?

1. The most likely cause is that your WooCommerce version (6.1.
2. is outdated and incompatible with the latest plugin version. The plugin requires a more recent WooCommerce version to function properly. You should update WooCommerce to the latest version (such as 9.2.
3. to resolve compatibility issues and critical errors. Reverting the database and plugin files is possible but not recommended as a long-term solution. Always backup your website before performing upgrades or rollbacks.

Why are FedEx shipping rates not displayed and what should I do if I receive an error saying "City Name or Postal Code is required"?

1. Check if your checkout page is customized and confirm that the City and Postal Code fields are present and correctly integrated with WooCommerce’s standard field IDs.
2. If missing, add or fix these fields in the checkout so WooCommerce captures and sends them to the plugin.
3. Test by switching to a default WooCommerce theme like Storefront to see if the issue persists—this confirms whether the theme or customization is the cause.
4. Ensure the shipping address used for testing includes valid city and postal code entries.

What steps should I take if I encounter a critical error on my site when testing Canadian address shipping rates with the FedEx plugin?

1. Identify and fix the root cause of the critical error before further troubleshooting shipping rates. Check error logs, plugin conflicts, or theme issues to diagnose the cause.
2. Temporarily switch to a default theme like Storefront and deactivate other non-essential plugins to isolate the error.
3. Update all relevant plugins and WooCommerce to their latest versions.
4. Only after resolving the critical error, verify if WooCommerce can process Canadian addresses properly at cart and checkout.
5. Once WooCommerce handles Canadian addresses correctly, the FedEx plugin will be able to retrieve and display live shipping rates accurately.

What should I do if the FedEx plugin fails with an error "Class 'AutomatticWooCommerceBlocksUtilsCartCheckoutUtils' not found"?

This error indicates incompatibility between the FedEx plugin and the WooCommerce version installed. This particular class is available only in WooCommerce versions 7.7.0 and above. To fix this, update WooCommerce to the required version (7.7.0 or later). Once updated, the FedEx plugin will function properly without triggering this error.

What should I do after updating the PluginHive plugin if I still encounter difficulties or errors?

1. Contact PluginHive support with detailed information including the plugin version, error logs (if available), and a description of the issue.
2. Provide the relevant order number(s) where the issue occurs to help replicate the problem.
3. Follow further troubleshooting steps as suggested by the support team.

What is the recommended process for communicating and scheduling support calls with PluginHive when facing plugin errors?

1. Clearly specify your preferred dates and time ranges aligned with PluginHive’s office hours or the team’s availability.
2. Indicate your local timezone and working hours to avoid timing confusion.
3. Wait for PluginHive support to propose or confirm a meeting slot and send the invite.
4. Maintain open communication through the support channel for any changes or clarifications.
5. Be prepared with diagnostic logs and error details to use the live meeting effectively.

What immediate steps fix the shipment creation critical error after upgrading the FedEx WooCommerce plugin?

The critical error arises from incompatibility with an older WooCommerce version. Resolve it by:

1. Backing up your website and database.
2. Updating the WooCommerce plugin to the latest stable version available.
3. Testing the shipment creation process again after update.
4. If issues persist, enable the plugin’s debug mode and submit a diagnostic report to support.

Updating WooCommerce is essential since older versions lack functions required by the current FedEx plugin, causing fatal errors during label creation.

What does the "array_key_exists(): Argument #2 must be of type array, bool given" error mean and how can it be fixed in FedEx WooCommerce Shipping?

1. Check the plugin code or contact PluginHive support to ensure the data source returning the array is working correctly.
2. Temporarily disable the plugin and inspect if there is a corrupted or incomplete configuration or cache causing the function to receive false (boolean).
3. Ensure that all WooCommerce and FedEx plugin settings are correctly configured and no invalid options are present.
4. Update your PHP version if outdated, as compatibility issues can sometimes cause data type mishandling.
5. If comfortable, add conditional checks in the code to verify the variable is an array before calling `array_key_exists()`.

The plugin shows an error "There are no valid services available" during rate calculation. How can I fix it?

1. Make sure all required FedEx shipping services are enabled in the plugin settings.
2. Verify on fedex.com that FedEx supports shipping from your ShipFrom address to the ShipTo address with the package details you have provided.
3. Check FedEx special services settings—specifically the "FedEx Delivery Signature" option.
4. Save settings, then re-check rates.

Is FedEx plugin version 7.1.2 compatible with WooCommerce 5.8.1 and WordPress 5.8.1? Why am I getting fatal errors after updating?

1. No, FedEx plugin version 7.1.2 is not compatible with WooCommerce 5.8.1 and WordPress 5.8.
2. The minimum required WooCommerce version for this plugin is 7.7, and the plugin requires WordPress version 5.9 or higher (due to WooCommerce 7.7 requirements). The fatal errors occur because the plugin expects newer WooCommerce and WordPress environments. To resolve the errors, update WooCommerce to at least version 7.7 and WordPress to at least version 5.
3. After updating both, the plugin should operate without fatal errors.

How should I manage access when support requests FTP/SFTP details to investigate plugin errors?

1. Provide secure credentials limited to the support duration.
2. Use a dedicated account or change passwords after the investigation to maintain site security.
3. Share only the required access details without exposing sensitive data unrelated to the issue.
4. Keep communication documented for audit and follow-up.

How does the PluginHive WooCommerce FedEx plugin v8.0.0 resolve the "All Currency Types in the Requested Shipment must match." error?

1. The plugin now consistently enforces uniform currency codes across product prices, shipping charges, taxes, and declared values within a shipment request.
2. The improved multicurrency handling avoids FedEx rejecting requests due to mixed currencies.
3. Users should ensure they update to version 8.0.0 or later to benefit from this fix and maintain seamless FedEx shipment generation.

How can I verify that FedEx shipping options are appearing correctly on my product pages after fixing website errors?

1. Access the product page on your website (e.g., the product you want to test).
2. Check the shipping options displayed during the checkout or shipping calculator phase.
3. Confirm that FedEx shipping services show up as selectable options without error messages.

How can I troubleshoot intermittent fatal errors related to the FedEx plugin in WooCommerce?

1. Confirm you are running the latest FedEx plugin version (e.g., version 7.1.1).
2. Temporarily deactivate all other WordPress plugins except WooCommerce and the FedEx shipping plugin to rule out plugin conflicts.
3. Determine if the error is triggered by specific actions, such as clicking "create shipment" rather than "calculate cost."
4. Review the details of the orders causing the errors, focusing on product declared values and custom shipping fields.
5. Correct any invalid input data as per plugin requirements (e.g., no hyphens in declared values).
6. If errors persist, share detailed fatal error logs and exact reproduction steps with PluginHive support for in-depth assistance.

Can I revert my database and old files after upgrading if the cart shipping is not working and checkout shows a critical error? Could this be related to the WooCommerce version I am running (6.1.2)?

Yes, reverting the database and old files is possible if you experience issues after an upgrade; however, this should be done carefully to avoid data loss. The critical error related to cart shipping and checkout can indeed stem from WooCommerce version incompatibilities with the plugin you installed. WooCommerce 6.1.2 is relatively outdated, and many modern plugins require a higher minimum WooCommerce version to function correctly. It is recommended to check the plugin’s minimum WooCommerce version requirements and ensure your setup meets them before upgrading. Always back up your database and files before applying updates, and consider testing upgrades in a staging environment.

After FedEx corrected the address issue on their end, I am now receiving new unclear errors in the plugin. What should I do next?

1. Reproduce the issue by attempting to get Freight rates again in your store.
2. Enable debug mode if not already enabled (see previous FAQ).
3. Generate and submit a fresh Diagnostic Report from the plugin’s Help & Support page to PluginHive support.
4. Provide as much detail as possible regarding the new errors, including any error messages or behaviors observed.

Will PluginHive extend the refund period trial for the FedEx plugin to allow time to troubleshoot and implement packaging and rate functionality?

PluginHive can provide a short extension of two business days beyond the standard 30-day refund trial period to allow additional time for troubleshooting and verification. However, they do not offer a full one-month extension of the trial period. Any final decision regarding refund eligibility will need to be made based on results within this limited extension.

Why might the support team request FTP/SFTP access when troubleshooting FedEx plugin errors?

1. Inspect plugin files and custom code that may be causing conflicts or passing invalid parameters.
2. Review error logs and detailed system information unavailable via WordPress admin.
3. Perform controlled debugging and replicate issues in your environment.
4. Apply temporary fixes or patches if needed to resolve critical bugs.

Why is the UPS shipping calculator on my WordPress site not working after updating the API key, and how can I troubleshoot it?

1. Go to the plugin settings in your WordPress admin panel.
2. Enable the “Debug Mode” option to capture detailed logs and error messages.
3. Reproduce the issue by checking shipping rates on the cart or checkout page.
4. Navigate to the "Help & Support" page in the plugin settings and submit a Diagnostic Report, referencing the appropriate ticket number for support follow-up.
5. Analyze the debug logs for any errors such as missing product dimensions or API registration problems.
6. Ensure all products involved in shipping calculations have correct dimensions and other required data configured.
7. Confirm your UPS registration details, especially if UPS has changed requirements like new access keys, and update them accordingly within the plugin.

Why is the PluginHive FedEx shipping plugin showing the error "Product weight missing. Aborting." and not returning shipping costs?

1. Verify that each product has a valid weight value set in the product configuration within WooCommerce.
2. Check that the plugin is correctly reading the product weight; ensure no custom modifications override weight retrieval incorrectly.
3. If volumetric weight is enabled, confirm that product dimensions (length, width, height) are set properly and not zero.
4. After ensuring all weights and dimensions are properly configured, clear caches and test the shipping rate calculation again.

Why is the FedEx shipping cost not generating for some customers and showing an error, preventing order placement?

This issue typically occurs because your plugin license has expired and you are using an outdated version of the WooCommerce Shipping Plugin for FedEx. To resolve this:

1. Renew your plugin license to regain access to support, updates, and uninterrupted service.
2. Update the plugin to the latest version, currently version 7.0.7.
3. After renewal and updating, the plugin will function correctly, allowing accurate shipping cost generation and order placement without errors.
4. If any issues persist after renewal and updating, contact PluginHive support for further assistance.

Renewal and updates ensure that FedEx rates display correctly at checkout, labels can be printed, and all plugin features work seamlessly.

Why is the change address functionality on the cart page not working properly with the FedEx plugin active, showing an “Internal server” error when updating the address?

The “Internal server” error when updating the address on the cart page is caused by compatibility issues between the FedEx plugin and your WooCommerce version. The FedEx plugin requires WooCommerce version 7.7.0 or higher to function correctly. If your WooCommerce version is below 7.7.0, address updates could fail, triggering errors like the internal server error on the cart page. To resolve this issue, update your WooCommerce plugin to version 7.7.0 or above. After upgrading, recheck the address change functionality to confirm it works properly with FedEx live rates.

Why is the admin login page not accessible on the main site URL and gives a 403 error when accessed through the ‘trade’ subdomain?

• Firewall or server restrictions blocking access to the subdomain or specific directory.
• Security plugins or server rules limiting login access on specific URLs.
• Incorrect URL used for admin login; verify the exact login URL (e.g., https://trade.kingstonbrass.com/wp-login/) is correct and permitted.

Why is my plugin not returning shipping costs and showing the error "Customer matched zone 'Locations not covered by your other zones'" in debug mode after the last update and reactivation?

This error often indicates a configuration or communication issue between the plugin and the shipping provider. To diagnose the problem, enable Debug Mode from the General Tab in the plugin settings, reproduce the issue, and then generate and submit a Diagnostic Report from the "Help & Support" page within the plugin settings. This report helps identify specific errors such as permission or license-related problems.

Why is Google showing a malware warning when visiting the PluginHive website, and is this issue resolved?

The Google malware warning was caused by a malware breach attempt targeting PluginHive's demo stores, which is unrelated to the FedEx certification process. This security issue was promptly addressed and resolved with the highest priority. The site has been cleaned and secured, and users should no longer encounter the malware warning when visiting PluginHive’s website. If the warning persists, clearing browser cache or reporting to Google for reassessment may help.

Why is FedEx not showing shipping prices even though product weights are uploaded, and how can I investigate this issue?

1. Open the plugin settings and go to the General Tab.
2. Enable the "Debug Mode" option to capture detailed logs.
3. Reproduce the issue by attempting to calculate the shipping price again.
4. Navigate to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report from there as per the instructions provided on that page.

Why does the TCPDF_PARSER error occur when bulk printing FedEx labels, and what is PluginHive doing to resolve it?

The TCPDF_PARSER error arises because the PDF merging library currently used by the plugin is not fully compatible with the specific PDF content format of FedEx shipping labels. When attempting to merge multiple labels in a bulk print operation, this incompatibility causes a decode failure leading to the error. PluginHive is actively working on improving the bulk print label feature to resolve this issue permanently. The solution involves implementing more compatible PDF merging techniques (such as the Ezhuthachan method used in other integrations). Although this fix will be released in a future plugin update, until then, users are advised to bulk print labels in smaller batches (around 10 orders at a time) to avoid the error.

Why does the PluginHive plugin show the error "There are no shipping options available" for all addresses, and how can I diagnose this issue?

1. Go to the General Tab in the plugin settings.
2. Enable the "Debug Mode" option to capture detailed logs.
3. Reproduce the issue by trying to get shipping rates again.
4. Navigate to the "Help & Support" page in the plugin settings.
5. Submit a Diagnostic Report through the provided instructions.

Why does the PluginHive FedEx plugin show an error stating "SATURDAY_DELIVERY is not allowed for the origin/destination pair," and how should I resolve it?

1. Edit the order in WooCommerce for which you are generating the shipping label.
2. Locate and uncheck or disable the **Saturday Delivery** option or service add-on.
3. Regenerate the shipping label without Saturday delivery selected.

Why does the FedEx WooCommerce plugin cause a TCPDF_PARSER ERROR during bulk printing of shipping labels even when printing in batches of 10 or fewer?

The TCPDF_PARSER ERROR: "decodeFilterFlateDecode: invalid code" occurs due to incompatibility between the third-party PDF merging library currently used by the FedEx WooCommerce plugin and the specific PDF format generated by FedEx shipping labels. This error happens when merging multiple label PDFs into a single file during bulk printing, causing the decode process to fail. Even small batches of 10 labels or fewer can trigger this issue because the library does not fully support the PDF structure of FedEx labels. The plugin team is developing a new, proprietary library to resolve this permanently. Until that update is released, users may continue to experience these errors intermittently during bulk printing and should limit bulk print jobs as much as feasible.

Why does the FedEx plugin show the error "3002 – Invalid billing address" during registration?

The error "3002 – Invalid billing address" occurs when the billing address and shipping address entered in your FedEx account are different. This mismatch can cause the registration process to fail. To resolve this, verify the billing address you have provided matches the one on your FedEx account. If needed, contact your FedEx account representative to confirm or update the correct billing address for the registration. Ensuring both addresses are consistent should fix the error.

Why does the FedEx plugin show a fatal error only on some orders but not on all when creating shipping labels?

• Invalid or malformed input in product fields required for shipping calculations, like custom declared values containing non-numeric characters (e.g., hyphens).
• Differences in order product setups leading to unexpected values passed to the plugin’s shipping API calls or internal calculations.
• Intermittent plugin conflicts or data validation issues triggered by order-specific details.

Why does the FedEx plugin fail to return shipping fees and show a "Failed to get Internal Endpoints" error in the debug log?

1. Deactivate the FedEx plugin license via FedEx Registration → License Activation.
2. Reactivate the plugin license.
3. Re-register your FedEx account by entering the required details and submitting the form again.

Why does the FedEx authentication code screen sometimes reappear even after entering the code, without showing an error?

1. Enter the first verification code when prompted.
2. After the field reappears, enter the second verification code you received.
3. Once both codes are entered correctly, the connection will be successfully established.

Why does the FedEx API return the error "FEDEX_ENVELOPE cannot exceed the limit of 1.00 LB." only for Canadian shipments, but not for US shipments, when shipping a product over 1 lb?

The FedEx Envelope packaging type has a strict maximum weight limit of 1.00 lb for Canadian shipments, which is strictly enforced for FedEx International Connect Plus (FICP) services. This limit applies regardless of parcel type and differs from US domestic shipments, where FedEx One Rate allows envelopes/packages over 1 lb in some cases. For Canada, if the package exceeds 1 lb (e.g., your 30 Day Kit), FedEx API returns this error and disallows the FedEx Envelope service. This results from country-specific FedEx packaging and shipping rules.

Why does the error "There are no shipping options available. Please ensure that your address has been entered correctly" appear at checkout, and how can I resolve it?

1. Check if the Free Shipping option is enabled. If yes, disable it temporarily to see if other shipping options reappear.
2. Deactivate other plugins one by one and switch to a default WordPress theme to identify if a conflict is causing the issue.
3. Consult your website developer to assist with debugging these conflicts if needed.
4. In the PluginHive FedEx plugin settings, ensure the “Default to residential delivery” is disabled, as the FedEx API will automatically detect the address type and return the appropriate rates.

Why does the "Invalid ShipmentSpecialServiceType" error still occur even after disabling special services as recommended?

1. Access to your site via FTP/SFTP to review plugin files and logs.
2. Test with the same order details to replicate the issue.
3. Validation of the plugin’s handling of special services and packaging data fields.

Why does the "Invalid billing address" error occur when I try to finish FedEx registration, even though my address is correct?

1. Verify whether you have entered separate Billing and Shipping addresses during the FedEx account registration.
2. If they are different, ensure that the Billing Address matches exactly what FedEx has on file.
3. Contact your FedEx account representative to confirm the correct Billing Address associated with your account.
4. Update the Billing Address accordingly during registration to match FedEx records.

Why does shipping not calculate correctly when combining the bumper product with other products using the PluginHive FedEx plugin, and how can I fix this issue?

1. Review your product settings in WooCommerce for all items included in combined shipments.
2. Ensure that the **Delivery Signature** (or any similar special delivery options) settings are consistent—either enabled on all products or disabled on all products being shipped together.
3. If Delivery Signature is enabled on one product but not on others in the same order, FedEx will return an error and rates may not be calculated or displayed correctly.
4. Remove or disable the Delivery Signature option from products where it is not required to match other products in the shipment, or make sure all products have it enabled if necessary.
5. After aligning the Delivery Signature settings, check your cart shipping rates again; the plugin should then return accurate combined shipping rates.

Why does setting the customs value not resolve the "Invalid Customs Value" error in some cases?

Even after setting the customs value in the product or product variations, you may still see the error if the customs value is not correctly passed or calculated by the plugin for the order shipment. Also, compatibility issues with your WooCommerce version might affect plugin functionality, causing incorrect customs values to be sent. It is important to verify the customs values are saved properly for all products and variations and ensure your plugin version is compatible with your WooCommerce installation.

Why does setting the "Price Value to be passed invoice" as "Discounted" cause the "Invalid Customs Value" error, and how can I resolve it?

1. Change the "Price Value to be passed invoice" setting in the PluginHive FedEx plugin from "Discounted" to "Product."
2. This setting uses the original product price as the customs value, ensuring it is non-zero.
3. Save the settings and attempt to generate the shipping label again.

Why do I see the error message "FedEx is enabled, but the origin postcode has not been set." on the FedEx settings page, and how can I fix the blank "forbidden" page when saving the form?

1. Verify that the origin postcode field is correctly filled in the FedEx shipping settings under WooCommerce > Settings > Shipping > FedEx > General.
2. If the origin postcode is set but you still face issues, update the PluginHive FedEx plugin to the latest version (at least v8.0.0). Plugin version v7.1.8 has known issues leading to this error and permission problems when saving settings.
3. After updating, clear your site and browser cache, then try saving the settings again.
4. If the error persists, check your server permissions and security settings to ensure your user role has permission to modify shipping settings.

Why do I see a minimum order amount error when using US dollars (USD) with the FedEx plugin, but not when using Colombian Pesos (COP), and how can I locate the source of this message?

1. Verify your minimum order amount settings directly within the "Order Min/Max Amount" plugin, ensuring that the minimum is set appropriately for each currency or is properly converted.
2. Check if the currency switcher plugin correctly updates the minimum order amount conditions when switching currencies.
3. Review or enable debugging or logging features within these plugins to identify where the message is triggered.
4. Temporarily deactivate the "Order Min/Max Amount" plugin and test the cart behavior in USD to see if the message disappears.
5. Contact the support teams of the "Order Min/Max Amount" and "Currency Switcher" plugins for detailed assistance related to their interaction.
6. Since the FedEx plugin is confirmed to function normally with live rates showing, focus troubleshooting on the combination of currency switching and minimum order amount enforcement plugins.

Why do I see a "Forbidden" error and a black screen when trying to save plugin settings in the PluginHive FedEx WooCommerce plugin?

1. Contact your hosting provider and inform them that their security rules (especially ModSecurity or any other WAF) are blocking requests containing keys like `boxes[FEDEX_SMALL_BOX:2]`.
2. Request that they create an exclusion or disable the specific rule pattern that blocks these requests for your site.
3. If your host uses any CDN or additional security services, ensure these also have appropriate exclusions or whitelist the PluginHive domains:
4. If your hosting provider requires technical details, share the error pattern example and the context about nested array keys in plugin settings.

Why do I receive the error "3002 – Invalid Billing Address" when registering FedEx in PluginHive, even though my address is correct, and how can I fix it?

1. Verify whether you have entered separate billing and shipping addresses in your FedEx account settings.
2. Ensure that the billing address matches exactly with what FedEx has on file for your account.
3. If you have differences or are unsure, contact your FedEx account representative to confirm and update the correct billing address.
4. After confirming the billing address is correct and consistent with your FedEx account, try registering FedEx in PluginHive again.

Why do I receive a "Forbidden" error when trying to save the PluginHive FedEx Shipping Plugin settings, and how can I resolve it?

1. Confirm with your hosting provider whether the server enforces ModSecurity or another Web Application Firewall (WAF).
2. Share the following information with your hosting administrator: the plugin’s use of nested array keys (e.g., `boxes_name[FEDEX_SMALL_BOX:2]`) is being flagged by security rules causing the block.
3. Request the hosting team to whitelist or exclude this specific request pattern from the ModSecurity or firewall rules to allow plugin settings to be saved properly.
4. Note that the PluginHive team cannot alter the plugin’s data structure since the array format is critical for its functionality.
5. If needed, provide your hosting provider with technical details or logs from PluginHive support for further clarification.

Why do I receive a "Forbidden" error page when trying to save FedEx plugin settings, and how can I troubleshoot it?

1. Set up a staging (test) version of your WordPress site to avoid affecting your live store.
2. Deactivate all other plugins except WooCommerce and the PluginHive FedEx Shipping Plugin to rule out conflicts.
3. Switch the site theme to the default Storefront theme to eliminate theme-related issues.
4. Reproduce the issue on the staging site.
5. If the problem persists, provide access to this staging site as an administrator to PluginHive support for further diagnosis.

Why do I receive a "Forbidden" error after submitting all values on the Generic API Settings page, and how can I resolve it?

The "Forbidden" error usually indicates that the request is being blocked or restricted. To resolve this, please follow these steps:

1. Ensure you have entered the complete address in the plugin settings, including the postcode, as incomplete address information can cause issues.
2. Check if any security plugins or firewalls on your website are blocking the request. Temporarily deactivate all other plugins to see if the issue persists in a plain WooCommerce environment.
3. Contact your hosting provider to confirm there are no server-side restrictions or permission settings preventing the request.
4. After performing these checks and adjustments, attempt submitting the settings again.

If the issue continues after these steps, please provide detailed information so further assistance can be provided.

Why do I get the error "You are not authorized for registration" when connecting the PluginHive FedEx plugin, and how can I resolve it?

1. Reload your website page to refresh the session.
2. Clear your site cache completely to remove any stored data that may interfere.
3. Attempt the FedEx registration again after these steps.

Why do I get the error "Rating is temporarily unavailable, please try again later" when clicking "Create Shipment" on the orders page?

1. Obtain live FedEx API credentials from your FedEx account.
2. Enter these live credentials into the PluginHive FedEx plugin settings under the API credentials section.
3. Save changes and retry creating a shipment.

Why do I get the error "FedEx Create Shipment Error: Severity: ERROR Source: ship Code: 2209 Message: Inactive customer account" when trying to create a shipment?

1. Contact your FedEx representative or the FedEx support team directly.
2. Verify the status of your FedEx account and ensure it is active.
3. Request reactivation or address any outstanding issues that caused the account suspension.
4. Once your account is active again, you should be able to create shipments without encountering this error.

If the problem persists after FedEx confirms your account is active, please reach out to PluginHive support for further assistance.

Why do I get an error when trying to generate FedEx shipping labels, and how can I fix it?

1. Ensure your FedEx account is registered via the FedEx Compatible Registration process within the plugin settings. Follow the guide here: https://www.pluginhive.com/knowledge-base/setting-woocommerce-fedex-shipping-plugin/#Add_FedEx
2. Enable “Debug Mode” in the plugin settings to capture detailed logs.
3. Attempt to generate the shipping label (create shipment) after enabling Debug Mode.
4. If an error occurs, clear your server cache or any caching plugins you use, then try generating the label again, as caching can interfere with label generation.
5. If the issue persists, generate and submit a Diagnostic Report from the plugin’s “Help & Support” page for further analysis.

Why do I get a “Forbidden” error with a white screen when trying to save settings in the WooCommerce FedEx Shipping Plugin, and how can I fix it?

1. Inform your hosting provider about this issue and request them to check ModSecurity or other firewall rules that may be blocking such POST requests.
2. Ask your hosting administrator to exclude or whitelist the specific request pattern related to the FedEx plugin—particularly the pattern containing nested array keys with colons—to allow these POST requests to pass.
3. Note that this adjustment is needed because the plugin’s data structure relies on these keys for proper functionality, and the plugin cannot be modified to avoid this format.
4. If your hosting uses third-party Web Application Firewalls (WAFs) or custom firewall rules, ask them to investigate those layers as well.

Why do I get a "Forbidden" error when trying to save FedEx plugin settings in WooCommerce, while other WooCommerce settings save fine?

The "Forbidden" error when saving FedEx plugin settings is typically caused by security restrictions on your server, specifically due to Apache’s ModSecurity rules or other firewall security measures. The FedEx plugin settings include predefined FedEx standard boxes stored in a nested array format (e.g., boxes[FEDEX_SMALL_BOX:2]). This format is essential for the plugin’s functionality but can trigger ModSecurity rules because of the way the keys appear in the request, causing the server to block the save operation. Since the plugin’s data structure cannot be changed without breaking its functionality, this conflict needs to be resolved at the server level.

Why do I get a "Forbidden" error when trying to save changes on the FedEx plugin settings page in WordPress?

The "Forbidden" error occurs because your web server is blocking the request due to security restrictions, most commonly caused by Apache's ModSecurity rules. The FedEx plugin uses a nested array format in its settings (e.g., `boxes[FEDEX_SMALL_BOX:2]`) to manage predefined FedEx standard boxes. This unique format can trigger certain security rules on your server, which interpret these keys as potentially malicious, leading to the saving request being blocked. This is not an error in the plugin but a conflict with server-level security filters.

Why do I get a "Forbidden" error when trying to save changes in the PluginHive FedEx plugin settings, and how do I fix it?

1. Deactivate all other plugins temporarily to rule out conflicts and test the plugin in a plain WooCommerce environment.
2. Contact your hosting provider to check for any server-level restrictions, such as security plugins, firewalls, or permission blocks that could be preventing the request from being processed.

Why do I get a "Customer not eligible for service" error from FedEx when using the COD option, and how can I fix it?

1. Disable the COD option in your PluginHive FedEx plugin settings.
2. After disabling COD, test the shipping rates again for your products.
3. You should now see the available FedEx services without this error.

Why do I get a "1000 – Internal Service Error" when trying to register for FedEx in the PluginHive WordPress Admin, and how can I resolve it?

1. Ensure the street address line and company name do not exceed 25 to 30 characters in length.
2. Enter the phone number without including the country code.
3. Use the exact same shipping address as shown on your FedEx Invoice to avoid discrepancies.

Why do delivery options not appear at checkout and an error message shows up in the PluginHive FedEx shipping plugin?

This issue typically occurs when the plugin license is expired or inactive. The FedEx shipping plugin requires an active license to function properly. Without a valid license, the delivery options will not display at checkout, and an error message will appear. Confirm your license status in the plugin settings, and if expired, renew the license to restore functionality.

Why do customers see the error "There are no shipping options available" when trying to complete an order using the PluginHive FedEx Shipping plugin?

This error typically occurs if the plugin license activation is not properly linked to the FedEx account registration process. Without a valid license connection, the plugin cannot fetch or display shipping options.

Why did I receive the error message “The maximum amount for this coupon code is $8” and no discount was applied during checkout, and how can I resolve it?

1. Contact PluginHive support providing a detailed description of the error and your exact purchase scenario.
2. Share a screencast or screenshots showing the steps you followed and the error message encountered to help support diagnose the issue efficiently.
3. PluginHive support will review the coupon’s settings and issue a new coupon code if necessary, ensuring the correct discount applies to your purchase.

Why can the PluginHive support team not modify the plugin to avoid conflicts with server security rules causing the "Forbidden" error?

The plugin’s data structure uses nested array keys (e.g., `boxes[FEDEX_SMALL_BOX:2]`) internally to manage FedEx standard boxes. This format is critical for the plugin’s correct operation and interaction with FedEx services. Altering this structure would break the core functionality. Therefore, PluginHive cannot modify the plugin to circumvent server security rules that block these patterns. Instead, the recommended solution is to work with your hosting provider to whitelist or exclude the related ModSecurity rules or firewall filters that block these request patterns.

Why are shipping labels not showing in my order, and how can I troubleshoot this issue?

If shipping labels are not appearing in your order, follow these steps to troubleshoot and help identify the cause:

1. Go to the plugin settings in your platform.
2. Enable the “Debug Mode” option to capture detailed logs.
3. Attempt to generate the shipping label manually to reproduce the issue.
4. After reproducing the issue, navigate to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report using the instructions provided on that page. Make sure to reference your ticket number (e.g., 330680) when submitting the report.
6. Once the Diagnostic Report is submitted, the support team will review the logs and assist you further.

This process helps capture detailed technical information to diagnose why labels aren’t showing and expedite the resolution.

Why are no shipping options showing up during test orders even with a valid address, and the FedEx plugin settings cannot be saved due to a "forbidden" error in the backend?

1. Confirm you are using the latest versions of the FedEx plugin (7.1.8), WooCommerce, and WordPress.
2. Verify if you can save settings normally in WooCommerce > Settings > General to rule out a broader permissions issue.
3. If saving FedEx plugin settings leads to a "forbidden" page, try lowering your CDN security settings temporarily — this may allow saving changes.
4. For a long-term fix, deactivate your security or CDN plugin completely to see if the issue is caused by it blocking the FedEx plugin’s requests.
5. After disabling the security plugin, attempt saving the FedEx plugin settings again. If successful, configure your CDN or security plugin with exceptions or rules that allow the FedEx plugin operations.
6. If shipping options still do not show during checkout despite correct settings, enable “Debug Mode” in the FedEx plugin settings and retest.
7. Generate and submit a Diagnostic Report from the plugin’s "Help & Support" page for further analysis.

Why are no FedEx shipping rates being calculated after entering a zip code, and how can I troubleshoot this issue?

To troubleshoot missing FedEx shipping rates, follow these steps:

1. Ensure the plugin is connected to your FedEx account by completing the FedEx Registration process in the plugin.
2. Enable “Debug Mode” in the plugin settings:
3. Reproduce the issue by checking shipping rates on the cart or checkout page with a valid zip code entered.
4. After reproducing the issue, go to the "Help & Support" page in the plugin and generate a Diagnostic Report.
5. Submit this Diagnostic Report to the PluginHive support team for detailed analysis.

This process helps capture error logs and facilitate accurate troubleshooting.

Why are my shipping labels not generating when I press the button, and there is no error message shown?

1. Ensure that your plugin license is active and properly linked to your FedEx or UPS account registration within the plugin settings. An unlinked or expired license can cause label generation to silently fail.
2. Update the plugin to the latest version (FedEx plugin version 7.1.2 or the corresponding version for your carrier plugin).
3. If the license was recently re-instated or renewed, deactivate and reactivate the license through the plugin’s License Activation section to refresh the connection.
4. Confirm that your FedEx or UPS account details (including account number and contact information) are correct within the plugin settings. Incorrect account information can cause request failures without displaying an explicit error.
5. Enable Debug Mode in the plugin settings and generate a diagnostic report to identify underlying errors such as “Forbidden” status or authentication issues.

Why are FedEx shipping options not displaying on the WooCommerce checkout page, and how do I fix the "Failed to get Internal Endpoints" error in the logs?

The "Failed to get Internal Endpoints" error occurs when your PluginHive FedEx plugin license activation is not correctly linked to your FedEx account registration. To resolve this issue and display FedEx options at checkout, follow these steps:

• Go to WooCommerce dashboard → FedEx Shipping → License Activation.
• Deactivate the existing license key.

1. Update the plugin to the latest version (at least version 7.1.
2. to ensure all recent fixes are applied.

• Return to FedEx Shipping → License Activation.
• Enter your new license key and activate it again.

• In the FedEx plugin settings, follow the process to connect your FedEx account.
• Ensure all account details are correctly entered and saved.

Following these steps will re-link your plugin license to FedEx’s internal systems, resolving the "Failed to get Internal Endpoints" error and restoring the FedEx shipping options on your checkout page.

Why are error messages showing on the checkout page after fixing the FedEx shipping price issue, and how can I stop them?

1. Go to the General tab of the plugin settings.
2. Disable the "Debug Mode" option.

Why are customers not getting shipping rates on my website, and how do I troubleshoot this issue using PluginHive FedEx Shipping plugin?

1. Enable “Debug Mode” in the plugin settings to capture detailed logs.
2. Reproduce the issue by attempting to get rates on the cart or checkout page.
3. Locate the "Help & Support" page in the plugin settings and generate a Diagnostic Report, then submit it to the PluginHive support team for further assistance.
4. Ensure you have entered complete and correct shipping address details in the checkout.

Why am I unable to generate shipping labels and getting a "Forbidden" error with the PluginHive FedEx plugin?

1. Verify that your FedEx account is correctly registered and linked to the license key used by the plugin.
2. If the error persists, re-register your FedEx account within the PluginHive system to re-sync your credentials.
3. After re-registration, attempt to generate the shipping label again.

Why am I unable to create FedEx shipping labels using the PluginHive FedEx plugin, and how can I troubleshoot this issue?

1. Place a new test order in your WooCommerce store to isolate the problem from existing orders.
2. Attempt to generate a shipping label for this new order using the FedEx plugin.
3. If the label still does not generate, grant PluginHive support permission to place test orders on your site so they can investigate order creation and label generation issues directly.
4. Review any special services or shipping settings in the FedEx plugin that may cause conflicts (e.g., Delivery Confirmation, Saturday Delivery).
5. Check for conflicts with other shipping plugins like UPS that might interfere with label generation.

Why am I still receiving the "Invalid ShipmentSpecialServiceType" error after setting Delivery Confirmation to Service Default and disabling Saturday Delivery?

If the error persists despite these settings, the issue may be caused by an incorrect data format being sent to FedEx, such as an "Array" instead of valid values for ShipmentSpecialServiceType. This often requires deeper technical investigation, potentially involving checking your site's configuration and code. To troubleshoot further, you may need to provide access (e.g., FTP/SFTP) to the support team so they can replicate and debug the issue in your environment.

Why am I seeing the error "There are no shipping options available" when trying to complete payment with a valid USA shipping address in PluginHive FedEx Shipping plugin?

This error typically occurs because the plugin is unable to retrieve shipping rates due to an issue with license activation linked to the FedEx account. To resolve this:

1. Enable Debug Mode in the plugin settings.
2. Try reproducing the issue by entering a shipping address on the cart or checkout page.
3. Submit a Diagnostic Report via the "Help & Support" menu in the plugin settings.
4. Once the diagnostic report is reviewed, if you find an error like "Failed to get Internal Endpoints," it indicates that your plugin license activation is not properly connected to your FedEx account.
5. To fix this, deactivate your current plugin license by navigating to FedEx Shipping → License Activation in your WordPress dashboard.
6. Reactivate the license and re-register your FedEx account credentials within the plugin.
7. After reactivation, test shipping again to confirm that available shipping methods now appear.

Following these steps usually resolves the issue and allows the shipping options to display correctly at checkout.

Why am I seeing the error "There are no shipping options available" for FedEx shipping after a plugin update, and the FedEx API keys disappear from the FedEx Setup – General tab?

This issue can occur if the plugin’s API key settings are not properly retained or if there is an underlying configuration or communication problem after the update. To diagnose the cause effectively, follow these steps:

1. Open the plugin settings and navigate to the General tab of the FedEx Setup.
2. Enable the "Debug Mode" option to allow detailed logging and troubleshooting.
3. Reproduce the error by attempting a checkout or cart update where the shipping options fail to appear.
4. Go to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report from this page as instructed, which includes logs and configuration data needed for analysis.

Providing this diagnostic report to the support team will help identify if the API keys are being overwritten, lost, or if other conflicts are causing the shipping options to fail. This process ensures the issue is investigated thoroughly and resolved based on accurate system data.

Why am I seeing the error "There are no shipping options available. Please ensure that your address has been entered correctly, or contact us if you need any help." after entering the billing address on the checkout page? How do I fix it?

1. Avoid modifying FedEx credentials once you have completed the registration process, as this can cause shipping rates to fail.
2. Re-register your FedEx account with the plugin to ensure that all credentials and billing address information are accurate and match the FedEx account.
3. Verify that the billing address entered on the checkout page is complete and correctly formatted.
4. After re-registration, test again to confirm shipping rates display correctly.

If these steps do not resolve the issue, please review your FedEx account details and plugin settings thoroughly or contact support for additional assistance.

Why am I seeing an error related to my FedEx plugin even though I have purchased and activated the license?

1. Go to the FedEx Registration section in the plugin settings.
2. Navigate to License Activation.
3. Enter your API Key and Product ID accurately.
4. Click Save Changes to activate the license.

Why am I seeing a "Forbidden" error on my UPS and FedEx plugins after updating, and how can I fix it?

The "Forbidden" error occurs because the new license API keys are not linked to the UPS and FedEx account registrations. To resolve this, you need to re-register your UPS and FedEx accounts within the plugin settings. This will link the license API keys properly and restore plugin functionality. After re-registering, UPS rates should appear on the cart/checkout page. Note that this linking issue is temporary and will not occur in future license renewals.

Why am I seeing a "Forbidden" error and not receiving shipping rates from the FedEx plugin on my website?

The "Forbidden" error generally occurs when the plugin license activation is not correctly linked to your FedEx account registration. This prevents the plugin from fetching live shipping rates. To resolve this issue, you need to ensure that your FedEx account is properly registered and the license is activated in the plugin settings.

Why am I seeing a "Forbidden error" and unable to get shipping rates from FedEx via the PluginHive plugin even after re-registering twice?

A "Forbidden error" while trying to get FedEx shipping rates through the PluginHive plugin commonly indicates that the license renewal was not properly synced with FedEx registration on PluginHive’s backend. To resolve this:

1. Confirm you have successfully re-registered the FedEx account in the plugin.

2. Contact PluginHive support to verify that your license renewal has been properly updated and synced with your FedEx account registration.

3. PluginHive support will perform the necessary backend synchronization.

4. After the backend correction, you should be able to retrieve shipping rates successfully without encountering forbidden errors.

Why am I receiving the error "The COMMERCIAL_INVOICE requires an electronic LETTER_HEAD" when generating FedEx shipments, and how do I fix it?

1. Upload your company logo as a Letter Head in the FedEx carrier settings:
2. Note that the Commercial Invoice service is not enabled by default on all FedEx accounts. Your FedEx account must have the Electronic Trade Documents (ETD) upload feature activated.
3. Contact FedEx directly to request activation of the ETD upload image feature on your account using your FedEx credentials.
4. Once ETD is activated and the Letter Head uploaded, the commercial invoice will be properly formatted, and the error should no longer occur.
5. Retry generating the shipping label after these changes.

These steps will ensure the electronic Letter Head requirement is fulfilled and allow successful label generation with commercial invoices.

Why am I receiving an "InternationalDetail CustomsValue – Invalid currency" error when creating a FedEx shipment using Chilean Peso (CLP) in the PluginHive FedEx plugin, and how can I resolve it?

1. Understand that FedEx does not currently accept CLP for CustomsValue in the API, so using CLP in shipment requests that require customs or international details will cause errors.
2. If shipping domestically or for services without customs, ensure you are not setting customs values or international details with CLP; omit them or use supported currencies if possible.
3. Contact your FedEx Account Representative to inquire if there is a currency mapper or alternative resolved approach for CLP in your account or region.
4. PluginHive currently recommends using an alternative supported currency for customs-related shipment details when dealing with Chilean shipments, as the FedEx API restricts CLP usage.
5. Keep "PreferredCurrency" and any customs-related currency fields set to a FedEx-supported currency to avoid this error.
6. Refer to the PluginHive documentation or support to check the latest configuration recommendations for shipments from Chile using FedEx Priority services.

Why am I receiving a 403 Forbidden error from the FedEx live rates proxy, and how can I resolve it?

The 403 Forbidden error usually occurs when your PluginHive license activation is not correctly linked to the FedEx account registration process. To resolve this issue, follow these steps:

• Navigate to the FedEx Shipping section in your plugin settings.
• Select License Activation and deactivate your license.

2. Ensure your plugin is updated to the latest version (at least Version 7.1.7).

• After updating, go back to the License Activation area.
• Reactivate the license accordingly.

4. Re-register your FedEx account with the plugin: – Follow the in-plugin prompts to complete the FedEx account registration again.

These steps properly link your license with your FedEx account, which should eliminate the 403 Forbidden error and restore live rate functionality. If the issue persists, further assistance may be needed.

Why am I no longer getting FedEx rates after updating the plugin, and how do I resolve the "no XML document" error in the debug log?

1. Go to the plugin settings and enable "Debug Mode" to reproduce and confirm the issue by checking rates on the cart or checkout page.
2. Submit a Diagnostic Report from the "Help & Support" section as instructed (this step helps identify issues but is optional if you want to try resolving yourself).
3. Deactivate the plugin license: Navigate to FedEx License Activation > License Activation and deactivate the current license.
4. Reactivate the plugin license by entering your valid license details.
5. Re-register your FedEx account credentials within the plugin by going to FedEx Registration > Registration. Make sure all details are correct and saved.
6. After completing these steps, check if live rates are now appearing at checkout. This process resets the plugin’s connection with FedEx’s API and resolves authorization-related errors causing the "no XML document" and "Forbidden" messages.

Why am I getting the error "ShippingChargesPayment Payor – The payor's account number is invalid" when trying to generate FedEx shipping labels, even though shipping charges are set to "Sender"?

1. Verify the FedEx account number with FedEx to ensure it is correct and contains 9 digits.
2. Re-register the FedEx account in the PluginHive shipping plugin using the valid 9-digit number.
3. After re-registration, try generating the label again. This should resolve the invalid account number error and allow label printing to proceed.

Why am I getting the error "FedEx Create Shipment Error: Invalid ShipmentSpecialServiceType," and how can I fix it?

1. Set **Delivery Confirmation** to "Service Default":
2. Disable **Saturday Delivery** option:

Why am I getting the "FedEx Create Shipment Error: Service is not allowed" when creating labels, and how can I resolve it?

1. Use the "Calculate Cost" option on the orders page in the plugin, which shows available FedEx shipping methods for your order.
2. Select only the FedEx shipping methods displayed under "Calculate Cost," as these are valid for your shipment.
3. In the plugin settings, navigate to the "Special Services" tab and set "Delivery Signature" to "None" (or no signature required).
4. Attempt to generate the label again using the valid service selected.

Why am I getting a "Forbidden" error and unable to update the FedEx plugin settings or see international shipping rates?

1. Deactivate the plugin license via FedEx Shipping → License Activation.
2. Update the plugin to the latest version (Version 7.1.8).
3. Reactivate the plugin license.
4. Re-register your FedEx account within the plugin.

Why am I getting a "Forbidden" error and no FedEx rates are being returned at checkout after renewing my license and updating the plugin?

1. Deactivate the plugin license.
2. Reactivate the license by navigating to **FedEx Registration → License Activation** in the plugin settings.
3. Re-register your FedEx account details by going to **FedEx Registration → Registration** and entering the correct credentials again.

Why am I getting a "Call to undefined method WC_Order::get_shipping_phone()" error on my custom-coded checkout page, and how can I fix it?

1. Verify your WooCommerce plugin version by navigating to WordPress Admin > Plugins and locating WooCommerce.
2. Update WooCommerce to the latest stable version (at least version 9.2.3 or newer) to ensure compatibility with PluginHive.
3. Instead of using `get_shipping_phone()`, update your custom checkout code to use `get_billing_phone()` or the correct method from WooCommerce’s API for fetching phone numbers.
4. Test the checkout process again after updating WooCommerce and modifying the code. This will prevent the critical error caused by calling undefined methods.

Why am I encountering an error when trying to bulk print labels for multiple orders in the PluginHive plugin?

The error occurs because the current version of the PluginHive plugin does not support bulk printing labels for multiple orders at once. To avoid this error, do not attempt to bulk print labels for several orders simultaneously. Instead, print labels individually for each order until the issue is resolved by the PluginHive team.

When updating the shipping address on the cart page, why does the updated address not show and why is there a 500 server error in the console related to a wp-includes JavaScript file?

A 500 server error on the cart page's JavaScript file (wp-includes/js min) when changing the address suggests a server-side issue or conflict that prevents proper address update and shipping cost recalculation. Possible causes and solutions include:

1. **WordPress Core Update:** Ensure your WordPress installation is updated to the latest stable version, as outdated core files can cause compatibility errors.
2. **Plugin or Theme Conflict:** Deactivate other plugins and switch to a default theme temporarily to check for conflicts causing the error.
3. **Debug Mode:** Enable WordPress debug logging by adding or verifying the following lines in the wp-config.php file to capture detailed error logs:
4. **Check Server Logs:** Review your web server error logs to identify specific causes of the 500 error.
5. **Code Customization Review:** If you have custom code snippets or overrides, verify they are compatible with current WordPress and plugin versions.
6. **Consult Plugin Support:** Share error logs with PluginHive support for targeted troubleshooting.

Updating WordPress core is often a critical step, but first verify the above to pinpoint and fix the error causing the address and FedEx cost not updating on the cart page.

When receiving the "3002 – Invalid Billing Address" error while registering FedEx in PluginHive, does the "shipping address" refer to the address listed in WooCommerce or elsewhere?

The "shipping address" referred to in the context of the "3002 – Invalid Billing Address" error is the shipping address configured within your FedEx account, not the address listed in WooCommerce. To resolve the error, verify and ensure that both the billing and shipping addresses in your FedEx account are accurate and consistent with FedEx records. After confirming the correct addresses in your FedEx account, reattempt the registration process in PluginHive.

What was the cause and solution for the “FedEx Rate Exception — no XML document” error that prevented rate retrieval on one of the sites?

1. Identify that the FedEx account registration is not linked to the license in the plugin settings.
2. Link the license to the correct FedEx account registration manually within the plugin.
3. Re-register the FedEx account if necessary.
4. Clear cache and re-test by attempting to fetch shipping rates.

What troubleshooting steps should I take if I see the FedEx API error about package dimensions exceeding limits but the shipping rates still appear?

When encountering this error:

1. Verify if FedEx SmartPost or Ground Economy service is enabled in the plugin; this service has strict dimension limits.
2. If you do not intend to use SmartPost, disable it as described above to avoid unnecessary error messages.
3. Enable Debug Mode in the plugin to collect diagnostic reports if further investigation is needed:
4. Recreate the issue and generate a diagnostic report via the plugin’s **Help & Support** page.
5. Submit the report for support analysis if the problem persists.

This allows you to confirm if the error relates to SmartPost and ensures accurate troubleshooting.

What troubleshooting steps should I take if I encounter a connection error like "could not be connected. Please try again later" when using the PluginHive FedEx WooCommerce plugin?

1. Verify your FedEx credentials (API key, password, account number, meter number) are correctly entered in the plugin’s settings.
2. Check your internet connection and server’s ability to make outbound HTTPS requests to FedEx API endpoints.
3. Review any recent changes to your site’s infrastructure, such as Cloudflare integration, firewalls, or country-level blocking rules that may restrict outbound API communications. Temporarily disable such blocks to test if the connection succeeds.
4. Consult plugin logs or error reports to gather more specific failure details.
5. Follow PluginHive’s recommended process by setting credentials within the plugin rather than manual or alternate connection methods.
6. Reach out to FedEx support if the issue appears to be on FedEx’s side or relates to FedEx account problems.
7. Provide PluginHive support with a screencast or detailed steps reproducing the error to receive more targeted assistance.

What troubleshooting steps should I follow when my PluginHive FedEx plugin shows a "Forbidden" error preventing rate retrieval?

1. Verify that your FedEx account credentials and API keys entered in the plugin settings are accurate and active.
2. Update the plugin to the latest version to ensure compatibility and bug fixes.
3. Disable and then reactivate your plugin license in the FedEx Registration section to refresh authorization.
4. Perform a re-registration of your FedEx account through the plugin interface to resync API credentials.
5. Check if any security plugins, firewall rules, or server settings might be blocking XML API calls—temporarily disable them to test.
6. Enable debug mode in the plugin settings and review the diagnostic logs to check if any specific HTTP errors or blocks occur.
7. Provide PluginHive support with diagnostic reports, WP admin access (if comfortable), and shipping/product URLs for deeper investigation.

What troubleshooting steps should I follow if the FedEx WooCommerce plugin throws a critical error on activation?

1. Ensure the PHP cURL extension is installed and enabled on your server since it is essential for the plugin’s operation.
2. Fill in all required Origin Address fields accurately within the plugin’s general settings to avoid configuration issues.
3. Temporarily deactivate all other plugins except WooCommerce and the FedEx plugin to eliminate conflicts.
4. Temporarily switch your active theme to a default WooCommerce-supported theme like Storefront to rule out theme conflicts.
5. Reactivate the FedEx plugin and test if the critical error still occurs.
6. Review error logs or messages to identify any additional issues.
7. Provide error logs to support if the issue persists for advanced diagnosis.

What troubleshooting steps should I follow if I receive a "Not found any Service Code for the Order" error in the PluginHive FedEx shipping plugin?

1. Double-check that your FedEx account credentials and integration settings are correctly entered in the plugin configuration.
2. Ensure that the shipping services you intend to use are properly enabled and mapped in the plugin.
3. Confirm that the product or order shipping parameters match available FedEx service codes supported by the plugin.
4. If you cannot resolve the issue via documentation, enable “Debug Mode” in plugin settings, try generating the shipment again, and submit a diagnostic report from the "Help & Support" page for detailed analysis by support.

What troubleshooting steps should be taken if the phGetInternalEndpoints method fails with a "Forbidden" error when calling the PluginHive proxy server endpoint for FedEx carriers?

1. Ensure your plugin license is correctly activated and linked to your FedEx account via FedEx Shipping plugin settings.
2. Verify your API keys are valid and active on the FedEx developer portal and configured correctly in the plugin.
3. Confirm your server or website URL is whitelisted if FedEx requires any domain-level restrictions.
4. Update the plugin to the latest version to ensure compatibility with PluginHive’s proxy service.
5. Deactivate and reactivate your PluginHive license via the backend menu to refresh authorization tokens.
6. If the issue persists, provide detailed error logs and your FedEx login credentials to PluginHive support for re-registration and deeper investigation.

What troubleshooting steps can I take if I receive an "Invalid Customs Value" error even after setting Custom Declared Value on products?

1. Verify in the WooCommerce product edit page that the "Custom Declared Value" under FedEx Details is properly populated and greater than zero.
2. Check the PluginHive FedEx plugin configuration setting for "Price Value to be passed invoice":
3. Temporarily disable all third-party plugins except WooCommerce and PluginHive FedEx to rule out plugin conflicts or customizations affecting the customs value.
4. Switch to a default WordPress theme during testing to ensure no theme customizations interfere with shipping details.
5. Attempt label generation again after these changes.
6. If the error continues, review the order details for any customizations or code modifications that might be forcing customs value to zero.

What technical information should I provide to my hosting provider to help them fix the "Forbidden" error with the FedEx plugin?

• The POST request is being blocked when saving FedEx plugin shipping settings in WooCommerce.
• The blocked request pattern involves nested array keys like `boxes[FEDEX_SMALL_BOX:2]` in POST data.
• This is causing ModSecurity or firewall rules to prevent saving changes, resulting in a "Forbidden" error.
• Example blocked request URI: `POST /wp-admin/admin.php?page=wc-settings&tab=shipping§ion=wf_fedex_woocommerce_shipping`
• Request to exclude or whitelist this specific pattern in ModSecurity or any other web security rules.

What steps should I take when the PluginHive FedEx plugin returns persistent errors such as "Service is invalid" despite following common troubleshooting?

1. Enable “Debug Mode” in the PluginHive FedEx plugin settings and reproduce the error to generate detailed logs.
2. Submit a Diagnostic Report from the plugin’s “Help & Support” page to the PluginHive support team for deeper analysis.
3. Provide PluginHive support with access to your WP-Admin, product configurations, and detailed order information where errors occur.
4. Maintain active communication with PluginHive support as they coordinate directly with FedEx technical teams using your account credentials and error logs.
5. Confirm and double-check that your FedEx Freight account is validated and the shipping addresses match exactly (case-sensitive) with FedEx records.
6. Avoid making random configuration changes; instead rely on guided troubleshooting steps provided by PluginHive and FedEx until the issue is resolved.

What steps should I take when getting the FedEx "Create Shipment" error related to delivery service mismatch to generate labels in bulk successfully?

1. Ensure all ShipTo addresses in your orders are accurate and properly classified (commercial or residential).
2. In the plugin settings (WooCommerce > Settings > Shipping > FedEx > General):
3. For return shipments, set "Ship From Address Preference" to "Shipping address" so labels are correctly generated from customer to your business.
4. For affected orders, verify the correct service is selected manually if needed.
5. Generate labels for a few test orders to confirm configuration is correct before bulk label generation.
6. If errors persist, gather order details and submit them with diagnostic reports to PluginHive support for deeper investigation.

What steps should I take if updating the shipping address on the cart page does not reflect changes, and I encounter a 500 server error related to wp-includes JavaScript files?

A 500 server error during address update usually indicates server-side or compatibility issues. To resolve this:

1. **Update WordPress Core:** Confirm your WordPress installation is updated to the latest stable release.

• Temporarily deactivate all plugins except WooCommerce and the FedEx plugin.
• Switch to the default Storefront theme.
• Test again to see if the issue persists.

• Add or verify in wp-config.php:
• Replicate the error and check the `wp-content/debug.log` file for detailed error messages.

4. **Review Server Error Logs:** Access your web hosting server logs for any related errors indicating server configuration or resource issues.

5. **Check Custom Code:** If you have custom code or overrides, ensure their compatibility with current plugin and WordPress versions.

6. **Contact PluginHive Support:** Provide the debugging logs and server error details for precise troubleshooting assistance.

Following these steps helps identify and fix the root cause preventing the shipping address update and eliminating the 500 error.

What steps should I take if the FedEx shipping rates and address change feature work fine for the support team, but the issue persists on my end?

1. Verify the WooCommerce version and update it to at least 7.7.0 or higher if not already done.
2. Provide the exact product link and shipping address you used when the issue occurred.
3. Record and share a screencast or video recording showing the steps you take on the cart page and the error message or issue you face.

What steps should I take if the FedEx shipping plugin returns a "Forbidden" error?

1. Update the FedEx shipping plugin to the latest version (e.g., 7.1.3).
2. Deactivate and then reactivate your plugin license by going to FedEx Registration → License Activation.
3. Re-register your FedEx account credentials within the plugin settings.

What steps should I take if the "Invalid ShipmentSpecialServiceType" error persists even after disabling Delivery Confirmation and Saturday Delivery options?

1. Verify your plugin and site configurations do not introduce invalid or unsupported special services.
2. Enable Debug Mode and generate a Diagnostic Report to collect detailed logs.
3. Contact PluginHive support and, if requested, provide secure FTP/SFTP access so the support team can directly inspect the configuration and reproduce the issue.
4. Maintain secure practices by providing limited-time access and changing credentials afterward to protect your site.

What steps should I take if PluginHive support reports an “unable to load XMLs” error from the FedEx API?

1. Ensure the FedEx account is registered properly in the plugin.
2. Confirm that your FedEx credentials and billing address are correct.
3. Update the plugin to the latest version.
4. Check server settings, such as PHP version and cURL support, to ensure they meet plugin requirements.
5. If the issue persists, escalate to PluginHive technical support with error logs for deeper investigation.

What steps should I take if I encounter errors while generating packages and creating shipments using PluginHive?

1. Make any recent configuration or data changes related to shipments or labels.
2. Try generating the packages and creating the shipment again after applying the changes.
3. If errors persist, replicate the problem to produce the relevant diagnostic report within the PluginHive system.
4. Share the diagnostic report with the PluginHive support team to assist them in their investigation.
5. Provide additional access (such as FTP or SFTP) if requested by the support team to allow deeper troubleshooting of your site’s shipping integration.
6. Stay in contact with support for updates and further required actions.

What steps should I take if I encounter a “Forbidden” error from FedEx through the plugin?

If you encounter a “Forbidden” error from FedEx, perform the following:

1. Deactivate the plugin license:
2. Reactivate the license by re-registering your FedEx account:

This process resets the license and permissions, resolving API authentication errors like “Forbidden.” Once done, verify by checking live shipping rates on your site.

What steps should I take if automatic package generation is not working correctly for Mix and Match products in the FedEx plugin?

1. Verify that no custom modifications have been made to the FedEx plugin files. Undo any changes or update to the latest official plugin version.
2. Disable any other plugins that may conflict, especially the WooCommerce Product Bundles plugin if it is installed but not in use, as the system does not fully support running it simultaneously with Mix and Match Products.
3. Confirm that all package sizes related to Mix and Match quantities are properly defined under the Packages tab in the plugin settings.
4. Test package generation again after these steps. If still unresolved, provide access to a staging site to support for deeper troubleshooting.

What steps should I follow to troubleshoot why FedEx shipping labels are not generating or printing after PluginHive shipping plugin updates or renewals?

1. Enable “Debug Mode” in the plugin settings to collect detailed logs.
2. Attempt to reproduce the problem by generating a shipping label for a test order, preferably using a new shipping address to avoid cached results.
3. Navigate to the “Help & Support” section within the plugin and submit a Diagnostic Report. This report captures checkout transactions and plugin settings critical for troubleshooting.
4. Reference your support ticket number when submitting the report to facilitate faster assistance.
5. Optionally, prepare a screen recording or detailed description of the issue to accelerate diagnosis.
6. If further help is required, provide temporary admin access and relevant product URLs to support for investigation.

What steps should I follow to troubleshoot the "Failed to get Internal Endpoints" error in PluginHive FedEx Shipping?

1. Confirm you have the latest plugin version installed.
2. Deactivate your plugin license from FedEx Shipping → License Activation.
3. Reactivate the license by re-registering your FedEx account in the same section.
4. Double-check the FedEx account credentials used during registration to ensure accuracy.
5. Enable debug mode if the problem persists, and review the debug logs for detailed error messages.
6. Contact support with the debug information if needed to pinpoint any account or API connectivity issues.

What steps should I follow if I receive a "Forbidden" error when trying to get FedEx shipping rates using PluginHive?

1. Update the PluginHive plugin to the latest available version (for example, version 7.1.5).
2. Deactivate your current plugin license by navigating to FedEx Shipping → License Activation in your WordPress admin.
3. Reactivate the license by following the same License Activation process.
4. Re-register or re-link your FedEx account through the plugin settings to ensure proper account authorization.
5. After completing these steps, test to confirm that shipping rates are now visible.
6. If any difficulties persist, consult support with diagnostic logs for further assistance.

What steps should I follow if delivery methods still do not appear and I encounter a "Forbidden" error, even with an active license?

1. Deactivate the current plugin license under **FedEx Shipping → License Activation**.
2. Re-activate the license after deactivation.
3. Navigate to **FedEx Shipping → Registration** and re-register your FedEx account credentials.
4. Confirm that your FedEx account number is correctly entered during registration.
5. Save all changes, then revisit the checkout page to verify shipping options.

What steps should be taken to troubleshoot and isolate the cause of plugin logo upload failure on my site?

1. Deactivate all other plugins temporarily to check if a plugin conflict is causing the JavaScript errors and upload failure.
2. Change the active theme to a default WordPress theme to see if the current theme is conflicting.
3. Check file permissions on your server to ensure the plugin can retrieve and process the images correctly.
4. Provide PluginHive’s technical team FTP or admin access (preferably on a staging site) so they can add error logging and debug the scripts causing the “Maximum call stack size exceeded” error.

What steps helped resolve the shipping option error for some users in WooCommerce FedEx plugin?

1. Performing FedEx re-registration more than once within the plugin.
2. After a subsequent re-registration, the shipping options began appearing correctly.
3. Users should monitor the issue after re-registration to confirm consistent rate calculation.

What steps can I take to troubleshoot if no FedEx shipping methods appear for shipments to the US after license reactivation?

1. Enable “Debug Mode” in the plugin settings.
2. Reproduce the issue by checking shipping rates on the cart or checkout page for US orders.
3. Submit a Diagnostic Report via the "Help & Support" page within the plugin settings.
4. Review the “Specific Countries” option in the plugin settings to confirm that the US is included as a permitted destination country for the shipping methods. The error message “The selected destination country is not included in the Specific Countries” indicates this setting needs adjustment.
5. After updating the country settings, test again for FedEx shipping methods.
6. If the issue persists, share a new detailed diagnostic report with support for further analysis.

What steps can be taken if the debug logs show a “Forbidden” error when attempting to get FedEx shipping rates?

1. Deactivate the FedEx plugin license from the FedEx Registration → License Activation page within your plugin settings.
2. Re-activate the plugin license to refresh the connection.
3. Re-register your FedEx account credentials in the plugin registration section, ensuring all details are accurate.

What steps are taken by PluginHive support to fix the "Forbidden" error when fetching FedEx shipping rates?

1. Verify the active license key and its link to the FedEx account within the plugin.
2. Re-register the FedEx account on the customer’s WordPress site within the plugin interface to correct any mislinking.
3. Confirm that the license status shows as active and properly connected.
4. Test the cart and checkout pages to ensure FedEx shipping methods and rates appear correctly.

What should I provide to PluginHive support to effectively resolve shipment errors like "Invalid ShipmentSpecialServiceType" or error code 2488?

• Specific order number(s) where the errors occur.
• Permission for PluginHive support to generate test labels or shipments on their end, if requested.
• A clear description of when and how the error occurs (e.g., only with FedEx Ground shipments).
• Submitted Diagnostic Reports and error logs created by enabling "Debug Mode" and reproducing the issue.
• FTP or SFTP access credentials, if requested, so the technical team can review your site’s shipping integration and data files.
• Screenshots of error messages or plugin settings, if available, to assist with visual context (note: mention "screenshot" in communication).

What should I expect if a fatal error is replicated by PluginHive support in the plugin?

When PluginHive support replicates a fatal error caused by the plugin, they typically:

1. Confirm the issue by reproducing the error on their test environment or client site.
2. Inform you that the problem has been verified and that they are working on a fix.
3. Release the fix as part of a plugin update in an upcoming stable version.
4. Notify you once the update is available so you can update your plugin to resolve the issue.

Until the patch is released, temporary workarounds may not be available depending on the nature of the bug.

What should I do if the WooCommerce FedEx Shipping Plugin by PluginHive shows a "Forbidden" error when attempting to generate shipping labels?

1. Deactivate your FedEx plugin license by navigating to the FedEx Registration section and selecting License Activation.
2. Re-activate the license by registering your FedEx account again within the plugin settings.
3. After re-registration, try generating the shipping label again through the plugin.

What should I do if the WooCommerce FedEx plugin shows the error "Something went wrong. Please contact PluginHive Support for assistance" during FedEx registration?

1. Clear your site and browser caches to eliminate any cached conflicts.
2. Verify that you are using the correct plugin versions: the FedEx plugin should be version 8.0.1, and the Royal Mail plugin should be version 2.1.0.
3. Test the plugin on a staging environment with all other plugins deactivated and a default WordPress theme (e.g., Twenty Twenty-Five) to rule out conflicts.
4. Ensure the WooCommerce checkout pages and necessary shortcodes are correctly configured (e.g., the My Account page should contain
   Login

   Username or email address *Required

   Password *Required

   Remember me Log in

   Lost your password?

   Register

   Email address *Required

   Password *Required

   Your personal data will be used to support your experience throughout this website, to manage access to your account, and for other purposes described in our privacy policy.

   Register

   shortcode).
5. Make sure product weights are assigned, as FedEx plugin requires weights to calculate live rates.
6. Enable realtime rates in the FedEx plugin settings to fetch live shipping rates.

What should I do if the UPS plugin shows an error "Missing or invalid ship to StateProvinceCode" and does not create a label?

1. Verify the shipping address details for the order are complete, especially that the state or province code is included and correctly formatted.
2. Update the shipping address to correct or add the missing state/province code.
3. Retry generating the UPS label through the plugin.

What should I do if the shipping rate issue is not resolved and I need direct assistance?

1. Inform the PluginHive support team of the ongoing issue and your availability for a call.
2. PluginHive may offer to schedule a remote session where they can temporarily access your computer to troubleshoot with you in real-time.
3. Confirm the date/time for the session and ensure you have remote access software ready if requested.
4. During the session, you can work together through the problem to achieve a resolution promptly.

What should I do if the PluginHive support team cannot access my WordPress admin area to troubleshoot plugin issues?

1. Check for any IP-based restrictions or firewall settings on your server or security plugins that may block the PluginHive support team's IP addresses.
2. Temporarily whitelist the PluginHive support team’s IP address range or entire country (e.g., India, if their team is located there) until the issue is resolved.
3. Confirm and provide valid admin login credentials securely per PluginHive instructions (never share in unsecured messages).
4. If your hosting provider or security plugins restrict access, add exceptions for PluginHive support IPs.
5. Notify PluginHive support once whitelist/access is granted, so they can proceed promptly.
6. Revoke the whitelist rules after support completes their investigation to maintain site security.

What should I do if the PluginHive plugin shows a "Forbidden" error after updating the API key?

1. Ensure the plugin is updated to the latest version (currently 7.1.5).
2. Deactivate your plugin license by navigating to FedEx Registration → License Activation and selecting the deactivation option.
3. Reactivate the plugin license in the same FedEx Registration → License Activation section.
4. Re-register your FedEx account details through the plugin settings.

What should I do if the PluginHive FedEx shipping rate plugin shows a "Forbidden" error and stops working?

1. Update the plugin to the latest version (at least version 7.0.9).
2. Deactivate and reactivate the plugin license:

What should I do if the PluginHive FedEx plugin stops working after renewing the registration and shows a "Forbidden" error?

To resolve the "Forbidden" error after renewing your PluginHive FedEx plugin registration, follow these steps:

1. Open the plugin settings in your WordPress/WooCommerce admin dashboard.
2. Navigate to the FedEx Registration section and find the License Activation area.
3. Deactivate your current FedEx plugin license.
4. Re-activate the FedEx plugin license by registering your FedEx account again through the provided interface.
5. Confirm that the license reactivation process completes successfully.
6. Test the plugin by checking the shipping rates on your cart or checkout pages to ensure rates are displaying correctly.

This process refreshes the license authentication and typically resolves the forbidden access issue after renewal. If issues persist, consider enabling "Debug Mode" in the plugin settings and submitting a diagnostic report for further assistance.

What should I do if the PluginHive FedEx plugin still does not show live shipping rates on the checkout page after renewing the license and resolving a "Forbidden" error?

1. Verify the product and shipping address you are testing with to ensure all required fields are correctly entered and valid.
2. Clear your browser cache or try using a private/incognito browser window to bypass any cached data that might prevent updated rates from displaying.
3. Confirm that shipping options other than the flat rate method are enabled and visible in your WooCommerce shipping settings.
4. Review the plugin configuration once more to ensure no changes have reverted or settings disabled after license reactivation.
5. If possible, share the exact product URL and complete ship-to address for further troubleshooting or support.
6. Check the cart/checkout page after these steps; live FedEx shipping rates should now display correctly if the setup is intact and the plugin functions as expected.

What should I do if the PluginHive FedEx plugin fails to generate shipping labels even after disabling some document issuances like the USMCA Certificate?

1. Temporarily disable additional optional document issuances in the PluginHive FedEx plugin settings to isolate which document triggers the issue.
2. Confirm that all required shipment details are correctly inputted, including product dimensions, weights, and addresses.
3. Review any error logs or screencasts to identify exact failure points related to document generation or shipment creation.
4. Reach out to PluginHive support with detailed logs and your current plugin configurations for further diagnosis if disabling certain documents does not resolve the problem fully.
5. Keep the disabled document settings only as a temporary troubleshooting measure until the root cause is identified.

What should I do if the FedEx Shipping plugin cart does not clear when testing specific products to troubleshoot shipping rate discrepancies?

1. Manually remove all products from the cart before adding only the product(s) you want to test shipping for.
2. Confirm there are no caching plugins or server-side cache interfering with cart updates—clear caches if needed.
3. Try using a different browser or an incognito window to eliminate session or cookie conflicts.
4. Disable other plugins temporarily that may affect cart behavior to rule out conflicts.
5. After clearing the cart, add the test product(s) and check the displayed shipping rates.
6. If cart clearing issues persist, provide PluginHive support with a screencast showing the steps you take and behavior observed so they can investigate the problem.

What should I do if the FedEx shipment creation returns a "masterTrackingId is invalid" error?

• Confirm that all products in the order have their weight and dimensions accurately set in the product edit page under the shipping section.
• Check that packaging is configured correctly in the plugin settings.
• After fixing product details, regenerate the package for the order and retry shipment creation.

What should I do if the FedEx plugin is causing a critical error during label generation, but the issue does not occur on PluginHive’s demo site?

1. Check for conflicts by temporarily deactivating all other plugins except the FedEx plugin.
2. Switch your site’s theme to the default Storefront theme to exclude theme-related issues.
3. Test label creation after these steps to determine if the problem persists.
4. Verify the product settings involved in the shipment, as specific configurations might trigger errors unique to your store.
5. If issues persist, provide PluginHive support with FTP and WordPress admin access (preferably on a staging site) for further troubleshooting.

What should I do if the FedEx plugin gives a "Forbidden" error despite having an active license?

1. Verify that the plugin license is activated on your site by going to FedEx Registration → License Activation.
2. If the license is active but the error persists, deactivate the license in the same License Activation section.
3. Reactivate the license afterward.
4. Re-register your FedEx account by going to FedEx Registration → Registration and completing the registration steps again.

What should I do if re-registration shows an "Invalid Billing Address" error in the FedEx plugin?

1. Verify your FedEx account billing address directly through FedEx’s contact info or recent invoices.
2. Update the billing address fields in the PluginHive FedEx plugin settings to exactly match the verified FedEx billing address.
3. If multiple addresses exist, use the shipping address associated with your FedEx shipments.
4. Retry the registration process after correcting the address information.
5. Make sure the account number used for registration is correct; if one number causes errors, try an alternate valid FedEx account number linked to your company.

What should I do if PluginHive support requests admin access to my WordPress site for troubleshooting but I am unsure how to grant it securely?

1. Log in to your WordPress admin panel.
2. Create a new user with the email **[email protected]**.
3. Assign the role of **Administrator** to this new user.
4. Confirm creation and share the site login URL along with the username and password with PluginHive support via the ongoing support thread.
5. Ensure you follow best security practices such as changing the password afterward and removing the user once troubleshooting is complete.

What should I do if PluginHive support requests access to my WordPress admin to troubleshoot product shipping configuration issues?

1. Create a temporary WordPress admin user with full access, ensuring they can view and edit plugin settings and product configurations.
2. Share the username and password securely with the support team following their request.
3. Ensure that the user account permissions cover the PluginHive configuration area so the support team can review and diagnose the problem. Without appropriate access, the team cannot verify plugin settings or product shipping setups.

What should I do if PluginHive support is still encountering a 403 error when trying to access the website despite whitelisting IPs and countries?

1. Confirm that the URL provided to support is correct and points to the intended login page (e.g., https://trade.kingstonbrass.com/wp-login/).
2. Validate that no IP or country blocking at the server, firewall, or security plugin level is still preventing access.
3. Test access yourself or have support try accessing from different networks or with VPNs (for example, use a US-based VPN if your site restricts access geographically).
4. Clear browser cache and cookies or have support clear browsing data to rule out client-side caching issues.
5. Ensure there are no web application firewall rules or security modules (like mod_security) blocking access from PluginHive’s IPs or VPN ranges.
6. If the subdomain or folder in the URL (such as “trade.”) is causing issues, test alternate URLs or the main domain to identify configuration problems.
7. Provide clear information back to support, including error codes and any security/log messages, so PluginHive can assist further.

What should I do if PluginHive support cannot access my WordPress admin panel due to IP restrictions while troubleshooting?

1. Identify any IP restrictions or firewall rules that could be blocking access from PluginHive’s support IP ranges, which are primarily based in India.
2. Whitelist all Indian IP addresses or support-related IP ranges temporarily on your hosting/server access control and security plugins to allow their login attempts.
3. Confirm with PluginHive support once whitelisting is completed so they can proceed with accessing the site for diagnosis.
4. After issue resolution, review and tighten IP restrictions again as required for security.

What should I do if PluginHive support cannot access my WordPress admin for troubleshooting?

1. Verify the username and password you shared are correct and active.
2. Ensure there are no IP restrictions or security plugins blocking external login attempts.
3. If direct credentials cannot be shared, request alternative ways to provide access, such as creating a temporary user with limited permissions.
4. Alternatively, share detailed screenshots or video recordings showing the issue and plugin settings to assist remotely.
5. Confirm your hosting environment does not have firewall rules preventing external access.

What should I do if my website had a fatal error due to the theme but now is fixed—how do I proceed to ensure the PluginHive FedEx plugin works correctly?

1. Confirm that the website is fully accessible without errors.
2. Log in to your WordPress admin panel and access the PluginHive FedEx plugin settings.
3. Test the shipping rates by simulating a checkout or using a relevant product page.
4. If needed, enable the plugin’s debug mode to monitor any errors.
5. Generate a shipping label for a test or previously failed order to confirm label generation works.
6. If the fatal error reappears or other issues persist, consider temporarily switching to a default theme (like Storefront) to isolate whether the theme is still conflicting with the plugin.

What should I do if malware warnings were triggered on the PluginHive website?

If you received malware warnings for the PluginHive website, be assured that the PluginHive team monitors and resolves these issues promptly. They confirmed that the malware warning has now been resolved. You can safely check back on the PluginHive website, as the security problem has been addressed and the site is safe to use.

What should I do if I receive the error message "The API Key could not be deactivated" when trying to deactivate the FedEx Shipping plugin API key?

The error "The API Key could not be deactivated" often occurs due to interference from security plugins or server restrictions. To troubleshoot this issue:

1. Temporarily deactivate any security plugins running on your WordPress site.
2. After disabling the security plugins, attempt to deactivate the API key again via the FedEx Shipping Activation page.
3. If you do not use any security plugins or disabling them does not resolve the error, contact your hosting provider to check and adjust any server security settings that may block outgoing requests from your site.
4. Once the security restrictions are lifted or plugins disabled, try the API key deactivation/activation process again.

If the issue persists after these steps, consider providing your admin site URL, License API Key, and Product ID to PluginHive support for direct assistance.

What should I do if I receive the error "Invalid Shipment Special Service Type" when creating a FedEx label?

1. In the FedEx plugin settings, enable the **Debug Mode** option. This allows detailed logging of the label creation process.
2. Reproduce the issue by attempting to create the label again to capture relevant error details.
3. Go to the **Help & Support** page within the plugin settings.
4. Submit a **Diagnostic Report** following the on-page instructions. Include any reference number provided for better tracking.

What should I do if I receive spam-related errors when trying to reply to PluginHive support messages?

If your emails to PluginHive support are being blocked due to spam filters, try resolving this issue by checking your email provider’s spam or junk settings to whitelist the PluginHive support email address. Once resolved, you can continue regular communication with the support team for further assistance.

What should I do if I receive an invalid date error while generating a label, but I are unsure where the incorrect date is coming from?

1. Check the plugin’s International Forms settings for any fields related to dates and certificates and verify if any required dates are missing or incorrect.
2. Review the order data to ensure shipment or customs-related dates are entered properly.
3. If you have enabled options like USMCA Certificate, make sure that all associated date fields (such as Blanket Period Begin and End Dates) are filled correctly.
4. Disable any optional certificate or form settings that you do not need or cannot provide the required information for.
5. Save your changes and test generating the shipping label again.
6. If the problem persists, consider enabling debug mode for detailed logs or submit a diagnostic report to PluginHive support for further analysis.

What should I do if I receive an error while bulk printing labels for multiple orders?

1. Stop attempting to bulk print multiple labels simultaneously to prevent further errors.
2. Print shipping labels one order at a time as a temporary workaround.
3. Monitor communications from PluginHive for updates regarding a fix or patch for this issue.
4. Refer to the screenshot provided by PluginHive support (if available) for visual guidance on the problem.

What should I do if I receive an error while activating the PluginHive addon plugin despite having all required plugins installed and updated?

1. Contact PluginHive support and share details of the error message and your environment.
2. Provide your store’s wp-admin and FTP access if requested, to allow the support team to investigate the issue directly.
3. Alternatively, arrange a call with PluginHive support to troubleshoot the problem collaboratively.
4. PluginHive may identify a needed fix and provide you with an enhanced or updated version of the addon.
5. Install the updated addon provided by PluginHive, which should resolve the activation error.
6. After installation, verify the plugin activates successfully and functions correctly.
7. Report back to PluginHive if any further difficulties arise, so they can assist promptly.

This approach ensures the issue is handled efficiently, with PluginHive’s team providing a tested fix and guidance to get the addon active on your site.

What should I do if I receive an error when trying to generate FedEx shipping labels through the PluginHive plugin?

Since the user mentioned attaching an error picture but no solution was provided in the conversation, there is no complete information to provide a troubleshooting answer for label generation errors. Please provide the error message details or logs for further assistance.

What should I do if I receive an error in logs stating "There are no valid services available" when requesting FedEx rates via PluginHive?

1. Verify that all product dimensions and weights are correctly set, as missing or invalid values can cause this error.
2. Check that the origin/shipper address is accurate and complete.
3. Review product packaging or type settings (e.g., LICENSEE vs Consumer) for consistency with your FedEx account setup.
4. Confirm that you are using an active and valid plugin license.
5. Review your FedEx account settings and billing information to ensure there are no restrictions or suspensions.
6. If using shipping classes or custom packaging, ensure they do not conflict with FedEx service eligibility.
7. Enable debug mode and analyze logs for more details to be shared with support if needed.

What should I do if I receive an "Origin country is not serviced" error in the PluginHive FedEx shipping plugin?

This error indicates that the origin address configured in the plugin does not fall within FedEx's serviced areas. To fix this:

1. Verify the origin address configured in the plugin’s settings, ensuring that the country, state, and postal code are correctly entered.
2. Log in to your FedEx account and check if FedEx provides services from that origin location.
3. If the address is incorrect or unsupported, update the origin address in the plugin to a valid FedEx-serviced location.
4. Save changes and test again to verify if shipping rates are retrieved.

What should I do if I receive a "Forbidden" error when trying to fetch FedEx shipping rates from the plugin?

1. Update the FedEx plugin to the latest version (at least v7.1.0).
2. Deactivate the plugin license. Navigate to FedEx Registration → License Activation in the plugin settings.
3. Reactivate the plugin license and then re-register your FedEx account details within the plugin.

What should I do if I receive a “Forbidden” error from FedEx in the plugin logs and the FedEx shipping prices are not showing?

1. Deactivate the plugin license by going to FedEx Registration → License Activation and disabling it.
2. Re-activate the license by re-registering your FedEx account under FedEx Registration → Registration.

What should I do if I need PluginHive support to troubleshoot a persistent error after reactivating and updating the FedEx plugin license?

1. Prepare an admin user account on your WordPress site for support personnel, granting appropriate access (created with the [email protected] email).
2. Share the website URL, admin username, and password securely with PluginHive support.
3. Provide your FedEx account login credentials, order number, and confirm permission for PluginHive to print labels on your behalf.
4. Share the Diagnostic Report generated from the plugin’s debug mode if available.

What should I do if I have updated my FedEx billing and contact addresses to match perfectly but the plugin still gives the "3002–Invalid Billing Address" error?

1. Verify whether the FedEx sender address is different from these addresses.
2. Attempt registration using the sender address rather than billing or contact addresses, as the plugin requires the sender address for registration.
3. If you do not have this information, log in to FedEx and check the sender address details under your profile.
4. Use these exact sender address details in the PluginHive plugin registration.
5. Contact PluginHive support with your FedEx account details for further assistance if problems continue.

What should I do if I have proof and screenshots showing the GST credit has not been received even after the return filing?

1. Share this evidence with the PluginHive accounts team or the Accounts Manager Bharath to assist in their internal follow-up.
2. Confirm that your GST portal and filing details match the submissions.
3. Maintain communication for regular updates while PluginHive coordinates with their accounts and product teams to resolve the issue promptly.
4. Escalate as needed using provided direct contact details if the problem persists beyond the expected processing time.

What should I do if I get the error "Saturday Delivery is not allowed for this Origin/destination pair" when creating shipments?

1. Go to the WooCommerce FedEx Shipping Plugin settings.
2. Disable the "Saturday Delivery" option.
3. Save the settings and try generating the shipping label again.

What should I do if I get a critical error on my website when clicking "Create Shipment" in the PluginHive WooCommerce plugin?

Follow these steps to troubleshoot the critical error when creating a shipment:

1. Ensure you are using the latest version of the PluginHive WooCommerce plugin (version 7.1.5 or above). If not, update the plugin to the latest version.
2. If the issue persists after updating, navigate to your WordPress admin dashboard.
3. Go to **WooCommerce >> Status >> Logs** and select the most recent **Fatal error** log to review the error details.
4. Share the fatal error log with PluginHive support for further investigation.
5. Provide the order number for which you are trying to create the shipment, so support can replicate and analyze the issue specifically.
6. Await further instructions or fixes from PluginHive support based on the logs and order details.

What should I do if I get a "Forbidden" error when saving FedEx plugin settings, and I have already checked Apache ModSecurity?

• CDN-based WAF or firewall rules
• Third-party security plugins on WordPress
• Server-level custom firewall configurations

What should I do if I get a "Forbidden" error and "Failed to get Internal Endpoints" message when generating FedEx labels using the PluginHive plugin?

1. Deactivate your FedEx plugin license in your WordPress admin panel under FedEx Registration → License Activation.
2. Reactivate the license by re-registering your FedEx account through the same FedEx Registration section.
3. Ensure that your license activations have not exceeded the purchased limit (e.g., if only 1 activation is purchased, ensure no other active instances are using the license).
4. If the problem persists after reactivating, contact PluginHive support to verify if the renewal license key needs manual syncing with FedEx Registration, as it may not have been updated automatically.

What should I do if I get "You are not authorized for registration" error despite having website admin access when re-registering FedEx in the plugin?

1. Reload your website page where the plugin is configured.
2. Clear the website cache to eliminate any stale or corrupted data.
3. Attempt to register the FedEx account again.

What should I do if I face the forbidden error and ModSecurity or firewall rules are blocking the FedEx plugin’s settings from saving?

1. Identify and document the exact error message and blocked request pattern, especially if it includes keys like boxes[FEDEX_SMALL_BOX:2].
2. Share this information with your hosting provider or security administrator. Explain that the blocking rule is interfering with the PluginHive FedEx WooCommerce plugin’s normal function.
3. Ask them to add a ModSecurity exception or disable the conflicting security rule for your website domain or plugin request URLs.
4. Confirm that any other third-party firewalls or custom server firewall rules are also checked for similar restrictions and adjusted accordingly.
5. After the exclusions are applied, try saving the plugin settings again.

What should I do if I experience technical issues with Zoom or Google Meet during a scheduled PluginHive support troubleshooting call?

1. Attempt to switch to the alternative platform provided (e.g., if Zoom fails, try Google Meet) if offered by support.
2. Check your microphone and speaker devices and drivers; test them independently outside the meeting.
3. Use a different browser, restart your device, or try an alternative internet connection.
4. If audio issues persist, ask a colleague or family member to assist in testing and configuration before the next scheduled call.
5. Communicate promptly with PluginHive support via email to inform them of the issue and request rescheduling if necessary.
6. Provide clear availability for the next call with timezone information.
7. Confirm you have a microphone-enabled device for future meetings, as audio is required.

What should I do if I encounter the error "You are not authorized for registration" during FedEx registration in PluginHive?

1. Try the registration process again after a short wait, as the issue might be temporary.
2. Reload the registration site and clear your browser cache to ensure there are no cached errors affecting the process.
3. Make sure that the street address or company name you enter does not exceed 25 to 30 characters. Longer entries can cause errors.
4. Enter your phone number without including the country code; just use the local number format.
5. Verify your shipping address by referencing a previous FedEx shipment invoice and ensure you use exactly the same address details.

What should I do if I encounter the error "looks like we got no XML document" in PluginHive FedEx plugin logs?

1. Ensure the correct FedEx account number used for registration matches your active FedEx account.
2. Provide previous shipment invoices if requested by PluginHive support to verify account ownership.
3. Request PluginHive to re-register your FedEx account within the plugin after verifying your details.
4. Confirm all FedEx API credentials and plugin settings are correct.

What should I do if I encounter an error with the PluginHive FedEx plugin and want to fix it myself?

1. Review your plugin settings carefully, focusing on the shipping origin, FedEx account credentials, and service options.
2. Adjust relevant settings such as package dimensions, weight units, or service preferences that might cause conflicts or errors.
3. Ensure that all required fields are properly configured and valid according to FedEx guidelines.
4. Use the “Debug Mode” to gather error logs and identify specific causes if the problem persists.
5. Test changes by generating a new shipping label after applying adjustments.
6. If the error is fixed, confirm stable operation by repeating the test. If not, consider submitting a diagnostic report for further assistance.

What should I do if I encounter a critical error with a white page after clicking "Create Shipment" using the PluginHive FedEx plugin?

1. Confirm that you are using the latest versions of the PluginHive FedEx plugin (version 7.1.5), WordPress, and WooCommerce (version 9.7.0). Outdated versions often cause compatibility issues.
2. Review if the error started recently and check whether any new plugins were installed just before the issue began, as plugin conflicts can trigger errors.
3. Access the WooCommerce error logs by navigating to WooCommerce → Status → Logs, then open the Fatal Error Log to identify detailed error messages.
4. Share the full error log with support to aid further diagnosis.
5. Provide a specific order number where the error occurs to allow targeted testing.
6. Grant permission for the support team to generate a shipping label using that order to reproduce and resolve the issue effectively.

What should I do if I encounter a critical error on my WordPress site when support tries to access it for troubleshooting?

1. Investigate and resolve the critical error on your website to restore normal functionality.
2. Notify support once the issue is resolved so they can proceed with diagnosis and label generation assistance.

What should I do if I encounter a "Forbidden" error when using the FedEx plugin and shipping calculations do not appear?

1. Deactivate your FedEx plugin license by navigating to **FedEx Registration → License Activation** in the plugin settings.
2. Re-activate the license by re-registering your FedEx account credentials within the same section.
3. Ensure this process completes without errors before proceeding.

What should I do if I cannot save FedEx shipping plugin settings because Apache’s mod_security triggers a “403 Access Denied” error with pattern matches on parameters like `boxes_name[FEDEX_SMALL_BOX:2]`?

1. Identify the specific mod_security rule causing the block (often rule 922130).
2. Request your hosting provider or server administrator to whitelist your IP or disable this specific rule for your site temporarily to test.
3. For a permanent fix, configure the mod_security to exclude the plugin’s parameters from blocking—essentially creating an exclusion rule for the predefined FedEx standard boxes parameter structure.
4. Confirm that you cannot disable the security module entirely for security reasons; therefore, customizing rules for your application’s normal operation is necessary.
5. After making these adjustments, the plugin settings should save without triggering mod_security.

What should I do if I cannot access the staging site admin because of a 404 error after sharing the URL?

1. Verify that the URL you provided is correct and accessible externally.
2. Ensure that no IP restrictions, maintenance mode, or security plugins are blocking external access.
3. Provide the correct login URL and access credentials separately if necessary, along with any HTTP authentication details.
4. Confirm that the staging environment is live and accessible from outside your internal network or VPN.

What should I do if I am unable to provide PluginHive support access to my live website to investigate an issue?

If you cannot provide access to your live site for security or privacy reasons, you can create and provide access to a WordPress admin staging site instead. This allows the support team to safely examine the issue and assist without impacting your live environment. Share the staging site URL, admin username, and password with the PluginHive support team for assistance.

What should I do if I am testing FedEx shipping rates and only see error messages because debug mode is active?

1. Complete your testing and identify any issues using the debug logs.
2. Once resolved, disable the “Debug Mode” option in the plugin’s General Settings tab.
3. Refresh your cart and checkout pages; error logs will no longer be visible.

What should I do if I am encountering technical issues with saving settings and do not want to share admin access or do a screen share?

1. Describe the exact error message or behavior you encounter in detail (e.g., "Forbidden" message on a blank page when saving settings).
2. Include any relevant information about your hosting environment, such as hosting provider and any security features you know are running.
3. PluginHive can provide targeted troubleshooting advice based on your description and suggest server-level fixes you can request from your hosting provider.
4. If the issue persists and you prefer no remote troubleshooting, you may proceed with a refund request by following the official refund process.

What should I do if bulk printing shipping labels with PluginHive triggers the "Invalid service type" error on multiple orders?

1. Review your shipping method configurations in your e-commerce platform to ensure only valid FedEx service types are assigned by default to shipping methods used in orders.
2. Adjust or add FedEx services in your shipping settings if necessary to match the services supported on your FedEx account.
3. Identify orders causing errors through the PluginHive logs or error messages.
4. For problematic orders, manually select a valid FedEx service by editing the order shipping method or performing a shipping cost recalculation selecting correct services.
5. Consider automating shipping method assignment via shipping rules or carrier service integrations to minimize manual intervention.
6. After adjustments, retry bulk label generation. This approach helps clear bulk order backlogs efficiently while resolving service type errors.

What should I do if after activating the plugin license I still get the error "There are no shipping options available"?

1. Enable **Debug Mode** in the plugin settings under **FedEx Shipping > Settings**.
2. Attempt to reproduce the issue by checking shipping rates on the cart or checkout page.
3. Go to the **Help & Support** page within plugin settings and submit a **Diagnostic Report** referencing your support ticket number.

What should I do if activating the FedEx WooCommerce plugin after registration causes a critical error on my website?

1. Confirm that all Origin Address fields in the plugin’s general settings are fully and accurately filled out. Missing information often triggers errors.
2. Temporarily deactivate all other plugins except WooCommerce and the FedEx plugin to rule out plugin conflicts.
3. Switch your site theme temporarily to the default WooCommerce Storefront theme to exclude theme-related conflicts.
4. Reactivate the FedEx plugin and test if the critical error persists.
5. If the issue continues, provide detailed logs or error messages for further diagnosis. This systematic isolation helps identify compatibility issues causing the critical error.

What should I do if activating a gear item and adding it to the cart causes a critical error on my WooCommerce shop using PluginHive plugins?

If adding a gear item to the cart triggers a critical error on your WooCommerce shop, follow these troubleshooting steps:

1. Identify any potential plugin conflicts by temporarily deactivating all non-PluginHive plugins, especially those related to product display or cart functionality.
2. Since a critical error was traced to the PowerPack Elements plugin in this case, try deactivating PowerPack Elements and test if the issue persists.
3. Confirm whether the error occurs only when your shipping logic or PluginHive’s plugins are enabled together with PowerPack Elements.
4. Reach out to the PowerPack Elements support team for assistance on the compatibility issue, as their plugin appears to cause the conflict.
5. Meanwhile, test with default WooCommerce shipping methods like Flat Rate to isolate the problem.
6. Ensure your PluginHive plugins and WooCommerce are updated to the latest versions for optimal compatibility.
7. After PowerPack Elements is resolved, re-enable your PluginHive shipping logic and verify normal cart and product page operations.

This approach helps isolate plugin conflicts causing critical errors on product pages and carts, enabling you to resolve incompatibilities affecting your WooCommerce store stability.

What should I communicate to Hostinger support to help them troubleshoot and fix the "Forbidden" error related to the PluginHive FedEx Shipping Plugin?

1. Explain that the PluginHive FedEx Shipping Plugin uses nested array parameters in POST requests (e.g., `boxes_name[FEDEX_SMALL_BOX:2]`) which are essential for managing FedEx shipping box configurations.
2. Clarify that these array-like request parameters are being mistakenly flagged and blocked by ModSecurity rules or other server-level firewalls on your hosting environment.
3. Request a whitelist or exclusion of the specific request patterns or ModSecurity rules causing the block to allow the plugin’s requests through without compromising overall server security.
4. Mention that this adjustment will enable saving the FedEx plugin settings without errors or the need to modify the plugin itself, as the array formatting is critical to its operation.
5. Offer to provide examples of the blocked requests or logs received from PluginHive support if necessary, to assist them in accurately identifying the rule to adjust.

What should I check if FedEx returns a “Service is invalid” error during label generation?

1. Confirm the FedEx service codes configured in your plugin match the types supported by your FedEx account and validated freight services.
2. Verify the shipment details (package weight, dimensions, and addresses) meet the requirements of the selected FedEx service.
3. If necessary, contact FedEx to confirm if your account has the required permissions and services enabled. PluginHive support may request your FedEx account login to cross-verify specific account configurations during investigation.

What options do I have if a plugin bug causing a fatal error cannot be immediately fixed?

If a fatal error caused by a plugin bug cannot be resolved immediately, consider these actions:

1. Continue collaborating with PluginHive support to receive updates on the fix timeline.
2. Avoid using the affected functionality (e.g., creating shipments) until the fix is applied to prevent site crashes.
3. Monitor plugin updates regularly and install the patch as soon as it is released.
4. If the issue significantly disrupts your operations, discuss support options directly with PluginHive, but note that refund or credit requests fall outside standard troubleshooting support.

What is the recommended workaround for the TCPDF_PARSER ERROR when bulk printing FedEx shipping labels?

1. Avoid bulk printing a large number of labels at once. Instead, split your label printing into smaller groups.
2. Print labels in batches of about 10 orders per bulk print operation. This significantly reduces the likelihood of triggering the PDF parser error.
3. Regularly update the FedEx plugin to the latest version (7.0.6 or above) to ensure you have all current improvements and fixes.
4. Monitor for plugin updates that will enhance the bulk print label functionality and fully resolve this issue in future releases.

What is the recommended way for PluginHive to perform debugging when unable to replicate the issue on their demo site?

• Add error logs directly into the plugin’s code stack
• Monitor runtime errors causing recursive JavaScript failures
• Test modifications and fixes in real-time without requiring repeated manual plugin uploads

What is the recommended method to troubleshoot a currency conversion multiplier error with JPY in the FedEx plugin?

To troubleshoot a JPY conversion multiplier issue in the FedEx plugin, follow these steps:

1. Confirm which multi-currency plugin you are using and verify if it is officially supported by the FedEx plugin. Supported plugins include WooCommerce Multi-Currency, Aelia Currency Switcher, WOOCS Multi-Currency, and FOX – Currency Switcher (Multi-Currency).

2. Temporarily switch to one of these supported multi-currency plugins, such as FOX – Currency Switcher, to check if the issue with JPY persists.

3. If the problem remains, verify your currency exchange rates and any manual adjustments you have made for JPY in your currency switcher or FedEx plugin settings, as incorrect custom values may cause multiplier errors.

4. Adjust or reset any manual exchange rate overrides and retest to see if this resolves the multiplier discrepancy.

5. If the issue is resolved after correcting exchange rate adjustments, then it was caused by the manual changes, not the FedEx plugin itself.

By following this methodical process, you can isolate whether the currency rate issue arises from plugin incompatibility or your exchange rate settings.

What is the “Forbidden” error in PluginHive FedEx plugin and how can I resolve it?

The “Forbidden” error typically indicates an authentication failure due to a mismatch or lack of synchronization between the plugin license activation and FedEx account registration. To resolve it:

1. Update the PluginHive FedEx plugin to the latest version.
2. Deactivate the plugin license key completely within the plugin settings.
3. Reactivate the license key using the correct API credentials.
4. Re-register your FedEx account in the plugin by entering valid FedEx details.

What is PluginHive’s policy regarding backlink requests in customer success stories submitted by agencies or users?

PluginHive welcomes customer success stories to showcase how their plugins help businesses. However, they typically do not provide direct follow-back backlinks to customer or agency websites in testimonials or success story features. Backlink inclusion is considered on a case-by-case basis only after the success story is fully verified and the related issue or collaboration is resolved. Reciprocal backlink requests from agencies writing success stories on behalf of clients are subject to evaluation by the PluginHive product team and are not guaranteed. Interested users or agencies should submit their stories for review first and await official feedback on backlink possibilities.

What information should I provide to PluginHive support when requesting help with plugin errors?

1. Precise plugin and platform versions (FedEx plugin, WooCommerce, WordPress).
2. Description of recent updates or changes made to the website (e.g., theme updates, new plugins).
3. Fatal error logs accessed via WooCommerce → Status → Logs that capture the error event.
4. Admin site access credentials with sufficient permissions to test and debug the issue (shared securely).
5. FTP access to the site files for deeper investigation if needed.
6. Order number related to your purchase of the PluginHive plugin.
7. Permission to perform actions like generating shipping labels for troubleshooting.

What information should I provide to PluginHive support when reporting an error about FedEx shipment labels?

1. Confirmation of the origin and destination countries involved in the shipment causing the error.
2. The admin site URL or access point for your store or system integrating PluginHive.
3. The specific order number(s) related to the shipment error.
4. Explicit permission allowing PluginHive support to generate a shipping label on your behalf for testing purposes.

What information should I provide to PluginHive support when reporting a critical error with the FedEx WooCommerce plugin?

1. The exact error messages and stack traces encountered, preferably copied from WooCommerce logs or error screens.
2. The versions of the PluginHive FedEx plugin, WooCommerce, and WordPress currently in use.
3. Details about when the issue started and if any new plugins or updates were applied recently.
4. Specific order numbers where the error occurs to help reproduce the issue.
5. Confirmation or permission for the support team to access your site or generate test labels on your behalf.

What information should I provide to PluginHive support to troubleshoot FedEx shipping integration issues effectively?

When contacting PluginHive support for FedEx integration troubleshooting, provide:

1. Website URL with the WooCommerce setup.
2. Platform and version details (WordPress, WooCommerce, and PluginHive plugin versions).
3. Description of the issue — e.g., no shipping option at checkout, label printing fails.
4. FedEx account number (do not share sensitive keys or passwords).
5. Screenshots or error logs if available (note: mention ‘screenshot’ if you provide).
6. Details about any recent changes or updates applied.
7. Steps already taken to troubleshoot.
8. Availability for calls with your development team if deeper technical discussion is needed.

This information helps PluginHive diagnose problems quickly and recommend precise solutions.

What information should I provide to PluginHive support to help troubleshoot issues related to generating shipping labels or order processing?

1. WordPress admin login URL for your site.
2. A newly created WordPress user with Administrator role specifically for support access, using [email protected] as the email.
3. The username and password for this support user.
4. The specific WooCommerce order number(s) associated with the issue.
5. Explicit permission to generate shipping labels on these orders within your WooCommerce and PluginHive plugin settings.

What information should I provide to PluginHive support to help investigate shipping calculation errors?

To assist PluginHive support in troubleshooting shipping errors, provide:

1. Specific dates and times when the errors occurred.
2. Detailed descriptions of the error messages your customers receive.
3. Screenshots from customers showing the shipping error during checkout (label as "screenshot" in communications).
4. Your current plugin version and license status.
5. Any recent changes made to your WooCommerce store or plugin settings.

Providing these details enables faster investigation and resolution of the issue.

What information should I provide to PluginHive support to expedite resolution of FedEx shipment errors such as "Invalid ShipmentSpecialServiceType" or error code 2488?

• Specific order number(s) experiencing the errors to enable precise replication and investigation.
• Permission for PluginHive support to create test shipments or labels using your store data if requested.
• Detailed descriptions of when and how the errors occur, including whether they happen only with specific shipment types like FedEx Ground.
• Diagnostic Reports and error logs generated after enabling Debug Mode and reproducing the error.
• FTP or SFTP access credentials, if requested, to allow support to examine your store’s files, configuration, and shipment data payloads directly.
• Screenshots of error messages or relevant plugin settings, if available, to provide visual context (noted as “screenshot” in communication).

What information should I provide to PluginHive support if the coupon code is not working as expected?

1. A screencast or screenshot showing the full process you followed during purchase and where the error occurs.
2. The exact coupon code you attempted to use.
3. Details about your order, including the number of licenses you intend to renew or purchase.
4. The email address used for the purchase, especially if the coupon is restricted to certain email addresses.

What information should I provide to my hosting provider to help them fix the "Forbidden" error caused by security rules?

1. Explain you are using the PluginHive FedEx WooCommerce plugin that sends POST requests containing nested array keys like `boxes[FEDEX_SMALL_BOX:2]`.
2. Inform them that the requests are being blocked by ModSecurity or another security firewall due to these special keys in the request payload.
3. Share the example blocked request pattern from the plugin:
4. Ask them to exclude this specific pattern or rule from security checks on your domain to allow the plugin requests to pass through.
5. Mention that similar issues were resolved by other customers by whitelisting or disabling the specific ModSecurity rule causing the block.
6. Provide PluginHive’s domains for whitelisting if their firewall controls outgoing service connections: `pluginhive.com` and `pluginhive.io`.

What information or files should I provide to PluginHive support to help resolve a "Forbidden" error during plugin settings changes?

1. A screencast or screenshots showing the exact steps leading to the error and the blank "Forbidden" window.
2. Access details to your WordPress admin area (if securely possible), so they can replicate the issue on your site.
3. Information about your current WooCommerce and PluginHive UPS plugin versions.
4. Details about your hosting environment, such as web server type, PHP version, and any security or firewall plugins or settings you use that might interfere.
5. Any relevant server error logs or security logs that capture the "Forbidden" response during saving.

What information is required to complete the FedEx registration in PluginHive if the ticket shows "Not authorized for registra…" error?

1. Account Number
2. First Name
3. Last Name
4. Company Name
5. Phone Number
6. Email
7. City
8. Postal Code
9. Address Lines
10. Country Code
11. State Code

What information is needed to troubleshoot plugin purchase and support issues for the PluginHive FedEx plugin?

1. The correct email address used to purchase the plugin or the purchase order number.
2. The URL of your WooCommerce store or the specific product page URL where issues are observed.
3. The versions of WooCommerce and the PluginHive FedEx plugin installed on your site.
4. Detailed description of the issues encountered, including any error messages or screenshots (note: mention screenshot but do not submit sensitive info).

What improvements related to shipment packaging and error handling were included in PluginHive WooCommerce FedEx plugin versions 7.1.4 and 7.1.7?

• Version 7.1.4: Introduced a standardized minimum shipment weight of 0.01 lbs/kgs to avoid zero or invalid package weight errors. It also deprecated the Cash on Delivery (COD) shipping option for shipments within and to the US, preventing related errors.
• Version 7.1.7: Implemented a critical fix for FedEx Ground shipments by ensuring the plugin now defaults to "Your Packaging" instead of automatically assigning FedEx Standard Boxes when generating shipment labels. This change rectifies errors caused by FedEx Ground rejecting FedEx packaging types assigned automatically by the plugin.

What immediate action can I take if FedEx customer service provides a general tech support number but cannot explain the “Service is invalid” error on Freight shipments?

1. Call the provided FedEx technical support number (e.g., 800-435-7949) and request escalation to the Freight service specialist or API integration team.
2. Provide detailed shipment and account information, error codes, and PluginHive debug logs if requested.
3. Inform PluginHive support of the FedEx support number and any progress so they can coordinate further if needed.
4. Meanwhile, review your shipment configurations and FedEx account validations to ensure correctness and readiness for Freight shipments.

What if I continue to face the "Forbidden" error even after updating the plugin and attempting license reactivation?

If the "Forbidden" error continues after performing the above steps, PluginHive support may require access to your FedEx account login credentials to complete the registration from their end. You can share these credentials securely with the support team for assistance completing the FedEx account linkage and resolving the error.

What error might cause shipping labels not to be sent due to email issues in PluginHive FedEx Shipping plugin?

1. Ensure each vendor account has a correct, valid email address entered in their profile.
2. Verify that the plugin’s email settings and templates are properly configured to include the recipient’s email address.
3. Check for any email delivery errors reported by your server or WordPress that might block outgoing emails.

Note: If you encounter detailed error messages indicating missing recipient email addresses, review and correct the address data linked to the orders and vendor profiles.

What does the PHP Fatal error related to TCPDF_PARSER mean in the FedEx WooCommerce Shipping plugin, and how can I troubleshoot it?

1. Open the FedEx WooCommerce Shipping plugin settings in your WordPress dashboard.
2. Enable the “Debug Mode” option to capture detailed logs while reproducing the issue.
3. Try to generate the shipping label again to reproduce the error.
4. Navigate to the "Help & Support" page within the plugin settings.
5. Submit a Diagnostic Report from that page, which collects the necessary technical data to investigate the error.
6. Provide the report along with your ticket reference to the PluginHive support team for detailed analysis and further assistance.

What does the FedEx error "The FTR Exemption or AES Citation you provided is not valid for EEI" mean, and how can I resolve it within the PluginHive FedEx plugin?

1. Ensure you are using the latest version of the PluginHive FedEx plugin (at least Version 7.1.3 or later). Update the plugin if necessary.
2. Enable debug mode within the plugin settings to capture detailed logs by reproducing the issue, then generate and submit a diagnostic report via the 'Help & Support' tab.
3. If the error persists, provide your admin access, order details, and permission to generate the label to the PluginHive support team for deeper investigation. Note that earlier versions of the plugin may not fully support shipments requiring valid FTR or AES citations for certain international destinations, like shipments from the US to Ireland.
4. Monitor for plugin updates, as PluginHive released version 7.1.4 which includes fixes and enhancements specifically addressing label printing errors linked to shipments from the US to Ireland and invalid AES citations.

What does the FedEx error "3002 – Invalid billing address" mean and how can I fix it when connecting FedEx to my website?

1. Verify if you have entered different billing and shipping addresses in your FedEx account or during integration setup.
2. Use the shipping address exactly as it appears on your FedEx shipment invoice for registration and integration settings.
3. If unsure about the correct billing or shipping address, contact your FedEx account representative to confirm the addresses associated with your account.
4. Update the billing address in your FedEx account or during the integration process to match the shipping address from your shipment invoice.

What does the FedEx API error "The COMMERCIAL_INVOICE requires an electronic LETTER_HEAD" mean, and how do I fix it in Pluginhive?

1. Navigate to WooCommerce → Settings → Commercial Invoice.
2. Upload your company logo or letterhead image in the provided section.
3. Retry generating the shipping label after uploading the letterhead.

Note: The Commercial Invoice feature is not enabled by default. Your FedEx account must have ETD Upload Image functionality activated to use this service. To get access, contact FedEx directly with your account details to have the ETD Upload Image feature activated. Once enabled and the letterhead is uploaded, the error should no longer occur.

What does the FedEx API error “Special Service COD not allowed at shipment level” mean, and how can I fix errors related to Cash on Delivery (COD) shipping?

1. Navigate to your WooCommerce FedEx Shipping plugin settings.
2. Go to the “Rates & Services” tab.
3. Locate the Cash on Delivery (COD) option and disable (turn off) it to prevent sending COD requests to FedEx.
4. Save the settings and try placing an order again to check if FedEx shipping rates and options appear correctly without this error.

What does the FedEx API error "All Currency Types in the Requested Shipment must match." mean and how can I resolve it when using a multicurrency setup?

1. Ensure your entire order, including product prices, shipping costs, and taxes, are consistently set in the same currency.
2. Verify that your multicurrency plugin or store settings do not mix currency types within a single order shipment request.
3. Check with your FedEx account representative to confirm currency requirements.
4. Confirm that you are using the latest version of the FedEx plugin (version 7.1.8 or later).

What does the FedEx API error "All Currency Types in the Requested Shipment must match." mean and how can I resolve it in a multicurrency setup?

1. Ensure the entire order, including product prices, shipping costs, and taxes, are consistently set in the same currency.
2. Verify your multicurrency plugin or store settings do not mix currencies within a single shipment request.
3. Confirm currency requirements with your FedEx account representative.
4. Use the latest version of the FedEx plugin (version 7.1.8 or later) which handles currency more reliably.

What does the FedEx API error "3002 – Invalid Billing Address" mean when re-registering a FedEx account in PluginHive, and how can I resolve it?

1. Ensure the street address line and company name do not exceed 25 to 30 characters in length.
2. Enter the phone number without the country code (i.e., omit the leading “1” or other country code digits).
3. Verify that you are using the correct address—if your FedEx shipping address differs from your billing address, use the billing address as it appears on your official FedEx shipment invoices.
4. Double-check that no extra elements like “Unit A” cause length issues by testing both including and excluding them, but prioritize accuracy.

What does the error message "COD is not allowed for the origin/destination pair" mean, and how can it be resolved?

1. Disable the COD option in the WooCommerce FedEx Shipping Plugin settings.
2. Save the changes and attempt label generation again.

What does the error "There are no valid services available" mean in the context of the PluginHive FedEx shipping plugin, and how can it be resolved?

1. Check that all FedEx shipping services are activated in the plugin settings.
2. Ensure the "ShipFrom" and "ShipTo" addresses are correct and supported by FedEx services.
3. Verify package weight and dimensions are within FedEx limits for the selected services.
4. Consult the FedEx website or contact FedEx to confirm service availability for your specified shipping routes and package parameters.
5. Adjust configuration as needed and test again to see available shipping services.

What does the error "The Contract Number {0} is not associated with the Mailed on Behalf of Customer Number in the CPC accounting system for the mailing date entered" mean in the Canada Post plugin, and how can I resolve it?

1. Verify if you have a valid Contract account with Canada Post. If you do not have one, leave the "Contract Number" field blank in the plugin settings.
2. Set the "Payment Method" to Credit-card to indicate you are a non-contract user, allowing shipments to be processed without a contract account.
3. If you have a contract, remove your current credit card details from the Canada Post website, re-add them fresh, and check if the issue persists.
4. If the error continues, contact your Canada Post representative to confirm that your contract number is valid, correctly linked to your customer number, and applicable for parcel services.

What does the error "The address entered for FEDEX_FREIGHT is missing one or more required fields: Country code; ; ." mean, and how can I fix it?

1. Ensure the Freight address fields match exactly the address you provided at FedEx when registering your account.
2. Pay attention to case sensitivity in the address details.
3. Configure the freight address by navigating to WooCommerce > Settings > Shipping > FedEx > Freight.

What does the error "Shipper contact – phoneNumber is required" mean and how can I fix it?

1. Go to the plugin settings page.
2. Locate the ShipFrom address section where your shipper’s address is configured.
3. Ensure that all fields, especially the phone number, are correctly filled out.
4. Save the changes and try generating the shipping label again.

What does the error "Rating is temporarily unavailable, please try again later" mean when testing FedEx shipping rates, and how can I resolve it?

1. Verify that you are currently using FedEx test credentials in your PluginHive setup.
2. Understand that the test server environment can sometimes be unstable or offline, causing rating failures.
3. Switch to live FedEx credentials, as this error is generally not seen when using live credentials.
4. Once live credentials are configured, test the shipping rates again to confirm the issue is resolved.

What does the error "Package 1 – Dangerous goods accessibility type is invalid or missing" mean and how can I resolve it in the PluginHive WooCommerce FedEx plugin?

1. Review the hazardous materials (HazMat) information entered for the package in your WooCommerce order or shipping settings.
2. Ensure that the “Dangerous goods accessibility type” field is correctly filled out according to FedEx requirements. This typically involves specifying if the package is packaged for ground, air, or other transportation modes and matching it with FedEx’s accepted values.
3. Consult FedEx’s documentation or the PluginHive knowledge base for the exact allowable values or options for Dangerous Goods accessibility.
4. Check your PluginHive FedEx plugin settings to confirm that HazMat shipment parameters are enabled and correctly configured.
5. Revalidate the shipping details and retry rate calculation or shipment creation.

(Note: Because no direct complete solution was provided in the conversation, the above combines general hazardous material error resolution best practices based on PluginHive FedEx plugin context.)

What does the error "Invalid ShipmentSpecialServiceType" mean when creating FedEx shipments, and how can I fix it?

The "Invalid ShipmentSpecialServiceType" error indicates that one or more special services configured in your WooCommerce FedEx plugin are not valid or eligible for your shipment. Common causes include enabling services that FedEx does not support for your package or destination.

To fix this error:

• Navigate to WooCommerce > Settings > Shipping > FedEx > Special Services.
• Change the Delivery Confirmation option accordingly.

• Go to WooCommerce > Settings > Shipping > FedEx > Label Generation.
• Turn off the Saturday Delivery option.

3. Save the settings and attempt to generate the shipping label again.

These adjustments address unsupported special services and resolve the invalid shipment special service type error.

What does the error "FedEx Create Shipment Error: Number of Commodities exceeds min or max limit" mean, and how can I resolve it when creating shipments using the PluginHive FedEx plugin?

1. Verify that the order you are trying to ship contains valid products that are currently available in your catalog.
2. Ensure that each product in the order has accurate weight and dimension attributes set, as these are necessary for correct package calculations.
3. Confirm that you have added at least one valid package in the plugin settings, as the system needs a package configuration to calculate shipping.
4. Do not manually add packages to international orders on the order page, as manual package addition there can trigger this error.
5. After ensuring the above, go to the respective order and use the "Re-generate Package" option so that the plugin automatically selects the appropriate package based on your plugin settings.