RLDD

Thank you for your recent suggestion! We’ve released today an optional add-on that comes with this and other advanced features. If a coupon with email restrictions is applied in the cart, the customer will receive a prompt to verify their email address before the coupon is honored.

You can find more details about this upgrade in version 3+. Please explore the possibilities within the latest update and use the support option for questions about the add-on.

Hi Mark,

Thank you for the update! This plugin operates independently of PitneyShip software and order info is not sent to PitneyShip. In comparison, this WooCommerce plugin is free, and PitneyShip may be charging a small monthly fee. However, it is possible for this WC plugin to display live rates that match PitneyShip as long as the client (merchant ID/shipper ID) is the same entity between the plugin and PitneyShip.

The process is to first create a PB developer account. If you are a developer for the client, it will be okay to use your details to set up the account. You might have previously run into an issue setting up the developer account if you were using the client’s details and they already have a PitneyShip account, but this is beyond my expertise. Once the developer account is created, the PB account manager should be able to tie the client’s merchant/shipper account to the developer account so that the live rates are quoted in WooCommerce.

As the developer, the final step once your account is live is paste in the Developer ID, Merchant ID, and API keys into the plugin. The client can set up payment directly with PB if they choose to use their merchant account for purchasing labels directly in WC, but live rates in the WC cart will work without this step. I am more than happy to offer assistance to complete your set up, and I have a few more ideas, but unfortunately I’m unable to share account details in a public thread. Please refer to the second bullet under “Need Help?” banner on the plugins setup page.

In regards to connecting WC and PitneyShip, I have not done this before, although it appears to use the native WC API which is common. I would expect this just allows tracking numbers and shipping status to be exchanged over API. I do not have a PitneyShip account as this is a separate software product. If you are experiencing issues within PitneyShip like the lack of an ‘Add Store’ button, I would direct this to the PB account manager.

Hi Mark,

Thank you for providing the query information. From the tests I’ve conducted, it appears that the echoing of queries isn’t occurring in fresh installs, suggesting that the issue might be related to specific server settings, such as error reporting or output buffering configurations. These settings can influence how PHP handles errors and output, potentially leading to unexpected behavior like the echoing of sensitive information.

Additionally, if your server is utilizing Suhosin, a PHP security extension, certain settings within it could contribute to the display of information in the interface. I’ll be working on addressing these potential issues in the next release to ensure smoother operation across different server environments.

Regarding the developer account, it seems you’re on the right track. If you continue to receive the error on login, please reach out to shipping api support (email address & phone number are at the top of the plugin’s settings page). They are typically very responsive. Be sure to provide them with the email address associated with your developer account. Mention to them that you’d like to link your existing merchant account (client PB account) with the new developer account. If all else fails, you may create a developer account with a different email address than the SendPro account, as this might be a factor.

Once your developer account is functioning smoothly, integrating it with the plugin is straightforward—simply copy and paste the relevant IDs into the plugin settings to facilitate communication between them.

If you have any further questions please don’t hesitate to reply to this thread.

Hi Mark,

Thank you for reporting this. The developer account is free, and usage of the Pitney Bowes API is also free. I have clients that have used this process for years and am not aware of any pricing except the shipping label itself – but if you find this has changed please let me know. You may sign up for a developer account here: https://developerhub.shippingapi.pitneybowes.com/signup/new-account

I am interested to see the query that is echoed on your config screen. I have not yet been able to reproduce this, but if you have an example that will surely help.

Hi @alexliii,

Thank you for this report. It seems to occur when methods are not yet set up in WooCommerce. In most cases, users will install the plugin after shipping methods have been set up. To avoid these errors temporarily, please deactivate the plugin, create a shipping method in WooCommerce, then reactivate the plugin.

Please lookout for a fix today that will prevent these errors. Thank you!

Hi alexliii,

Thank you for your suggestion! To access this enhanced functionality, we’ve recently released an optional add-on that comes with this and other advanced features. You can find more details about this upgrade in version 2+. Please explore the possibilities within the latest update and use the support option for questions about the add-on.

Thank you for confirming. This should now be resolved in v1.6.1 available now.

Hi can you confirm your version number? A similar bug was found in 1.5.2, and resolved in 1.5.3.