Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter rrrrobb

    (@rrrrobb)

    Please mark this complete. It has been fixed in v2.0.2

    I am seeing the exact same issue as you.

    Plugin has not been updated in 6 months at this point.

    First post about this issue was 7 months ago, as was the promise to fix it.

    Looks like the last support response, in the main list of issues, was 6 months ago as well.

    Seems its time to find a replacement, Too bad, it is a nice little plugin that did exactly what it claimed.

    Thread Starter rrrrobb

    (@rrrrobb)

    Hello Tamara,

    We purchased both the “WooCommerce Stamps.com API” and the “Sequential Order Numbers Pro” plugins and gave them a test.

    However we determined that the function of the “WooCommerce Stamps.com API” plugin was not for us. We aren’t looking to handle the postage printing from within our individual Woocommerce sites. Having more than one source of orders we prefer to use the Stamps.com interface to manage our shipping labels. It simply makes it more efficient.

    We have found the need for “Sequential Order Numbers Pro”.

    I am not sure why…. but after testing…. using the FREE version of the Woocommerce plugin (Plugin Name: “WooCommerce – StampscomEndicia Integration”) supplied by Stamps.com and the payed plugin “Sequential Order Numbers Pro”, everything seems to finally be working.

    I know there have been updates to plugins and WordPress. I don’t believe any of those updates were specifically related to this issue or these plugins. I can say at this time that we are finally functioning correctly. I do not know if the free version “Sequential Order Numbers” is working. I am hesitant to try it now that I finally have the site functioning.

    Thanks again for all of your help.

    Take care.

    Thread Starter rrrrobb

    (@rrrrobb)

    Hello Tamara,

    So far Stamps.com’s position is “sense this is related to a third party plugin”, this is a “Feature Request” not a “bug”. Thus they have no time to do anything about it.

    Funny, it is their code that has the problem in it. It is their code that causes the “fatal-error”. It is their code that is reading the “Order Number” created by “Sequential Order Numbers” and incorrectly uses it in place of the “Order ID”. If their plugin wasn’t written to use the “Sequential Order Numbers – Order Number” it would simply use the “Order ID” and work.

    But somehow this is a “Feature Request” not a “bug”.

    Currently we have reached out to WooCommerce and asked them to verify that the Pro Plugins work together correctly and don’t have this same issue. We have waited all week for their response. We finally got it, but they didn’t bother to understand the question before they gave us a canned response. So I have again responded to them, again requesting them to verify that the Pro plugins actually work correctly. We need to install this on two different sites and the cost becomes more than $200.00 to do this. We do not want to waist any more time and money before we know that the plugins actually work.

    So here we are another week later, and still no answer.

    Thread Starter rrrrobb

    (@rrrrobb)

    Hello,

    I’d be happy to share the link. The file is offered directly from Stamps.com. When Stamps.com customers add WooCommerce as a source they are presented with a link to this plugin. So sense Stamps.com is presenting this plugin, for FREE when the customer adds WooCommerce to their account, I would beg to differ that it is the Official plugin “stampscomendicia“. The other is a Pro or third party upgrade.

    Thread Starter rrrrobb

    (@rrrrobb)

    I just got off the phone with another customer service rep from Stamps.com who is claiming this is not a bug it is a feature request.

    First
    Plugin Name: “WooCommerce – StampscomEndicia Integration”
    is provided to Stamps.com customers via their two interfaces. Either the web interface or the Windows app interface.

    Second
    This “Plugin Name: WooCommerce – StampscomEndicia Integration” has been written to acquire the “Order Number” created by the “WooCommerce Sequential Order Numbers” plugin.

    Third
    When “WooCommerce Sequential Order Numbers” plugin is activated This “Plugin Name: WooCommerce – StampscomEndicia Integration” gathers the “Order Number” provide by the “WooCommerce Sequential Order Numbers” plugin and uses it for the “Order ID”.

    Fourth
    When the “WooCommerce Sequential Order Numbers” plugin is active, generally, the “Order Number” and the “Order ID” are not equal.

    Fifth
    If the “Order Number” and the “Order ID” are not equal and one tries to use the “Order Number” as the “Order ID” the system creates a “fatal-error”.

    Sixth
    If the code for the “WooCommerce Sequential Order Numbers” plugin was not present in the “WooCommerce – StampscomEndicia Integration” plugin provided by Stamps.com it would not acquire the “Order Number” in the first place, it would acquire the “Order ID”, and would always work.

    Seventh and Finally
    This is not a feature request, this is a partial implementation that is causing “fatal-errors” and the possibility of the wrong shipping information being passed on to the wrong customer. If the order number of one customers order matches the Order ID of another customers order the wrong information could potentially be passed.

    The code for acquiring the “Order Number” created with “WooCommerce Sequential Order Numbers” plugin is clearly inside the code of the “WooCommerce – StampscomEndicia Integration” plugin provided by Stamps.com. If you look at the code you can clearly see it is implemented to acquire the “Order ID” and it does. It just isn’t fully implemented correctly. Because it tries to use that same “Order Number” as both the “Order Number” (correct) and the “Order ID” (incorrect – causes the fatal-errors).

    Thread Starter rrrrobb

    (@rrrrobb)

    Thank you for your response. It has become quite apparent that the problem is that Stamps.com is only retaining one number for a given order.

    If the “WooCommerce Sequential Order Numbers” plugin is installed and active:
    Stamps.com, via their “Plugin Name: WooCommerce – StampscomEndicia Integration”, collects the “Order Number” created by the “WooCommerce Sequential Order Numbers” plugin.

    If the “WooCommerce Sequential Order Numbers” plugin is NOT active:
    Stamps.com, via their “Plugin Name: WooCommerce – StampscomEndicia Integration”, collects the “Order ID” created by the WooCommerce installation.

    When Stamps.com processes ones information it is based upon which ever number it has. If one is NOT using the “WooCommerce Sequential Order Numbers” plugin the entire process works because the “Order ID” is correct.

    However if the “WooCommerce Sequential Order Numbers” plugin IS active the process breaks because the Stamps.com system tries to use the “Order Number” as the “Order ID” and this is not correct.

    From what we have been told, what we are trying to do should work. That we should not have to use the Pro versions of either plugin in order to achieve our end results. That it is/was intended to work.

    We would pay for and use both Pro versions of the plugin’s if we had use of the functions which make them the Pro versions. However we have no need and no intention to use these Pro features. All we need and desire is the basic functionality which we have been assured should work. We have a hard time paying approximately $120 (per year) for the Pro versions that we are not supposed to need in order to do what we have been told we should be able to do for FREE.

    It is becoming a principal thing. Why pay money for something that should be working for FREE. If it is supposed to work using the FREE version then they should make it work.

    Otherwise they should openly admit that it costs $120 per year to do what we are supposed to be able to do for FREE.

    What keeps happening is:
    We call in, tell them what is happening, what we are trying to do.
    Then we are told we should be able to do what we are trying to do, that it should work using the FREE versions, that someone will contact us.
    Then no one contacts us. Not a peep. No emails, no phone calls. Silence.

    The errors generated by WooCommerce actually show the “Order Number”=“Order ID”. On the orders created using the “WooCommerce Sequential Order Numbers” plugin. It is blatantly obvious that the system is not working correctly. They need to fix their problem. The users should not have to pay an additional $120 per year to make something work that is supposed to work for FREE.

    I appreciate that the Pro versions may work. But if we have no need for the additional functions that make it a Pro version we shouldn’t have to pay to make the FREE functions work.

    Put Simply, Stamps.com needs to fix their interface to recognize the fact that the “Order ID” and the “Order Number” aren’t necessarily the same number.

    Thank you again for your response, hopefully it will not fall on their def ears.

    Thread Starter rrrrobb

    (@rrrrobb)

    Thank you for the response. You confirmed my suspicion, this plugin has nothing to do with their issue. We have confirmed what their issue is, can repeat it, and know what the fix for it is. Now we just have to get them to admit they have the problem and get them to fix it.

    Thanks again for the information.

Viewing 8 replies - 1 through 8 (of 8 total)