Build 3.00.393 resolved sku issue.
Still waiting on response to the following:
Also please review the following thread as this issue has existed for long time without resolution.
Monday is a holiday so perhaps that has an affect on it but still the #s don’t add up.
MOE
strange because the latest stable version .353 is working fine here.
Your late to the party. The issues outlined in this thread have already been resolved.
Seems to be working for us as well.
John, I hope the Sixbit developer team can work on implementing the following asap and ultimately make it a priority:
1) Making sure that Sixbit loads in the event of such issues in the future. Regardless of the market the Sixbit application should load, item editing should work etc… not freeze and crash the application.
2) I’ve mentioned this multiple times, it’s very important that Sixbit checks that the tracking# uploaded to the market. I am not sure how many times I’ve stressed this. This affects our performance metrics. I’ve seen many times whether their was a token authorization issue or other issues where the tracking# did not upload to eBay and order was transferred to fulfilled. This needs to be changed. The application should check that the tracking# went through, perhaps after doing an upload the API should do a check and verify that eBay returns the tracking# that got uploaded. If it’s unable to get a match or unable to connect to verify than the order should go to confirmation errors status just as you do with Amazon.
3) When the token issue arose regular users were greeted with the seller business profile page which also holds various credentials and other data we may not want listing staff to see. If the user doesn’t have permissions they should not have the ability to see this information.
John,
It’s still not working. Authorization worked but nothing is uploading to eBay nor updating etc… Hopefully inventory qty. does not get screwed up and there is some sort of check that the sixbit agent does to verify if a qty. revision request went through. I know it doesn’t currently check if the tracking# uploaded so hopefully it atleast checks if inventory revision went through.
John Manning,
There is another issue that I’ve brought up to you in the past which I thought you guys took care of but apparently still exists as of latest build. In the past I mentioned that when marking eBay orders with tracking# as shipped, in the event that the tracking# does not upload to eBay the order should go to confirmation errors status rather than transfer to fulfilled. In other words there should be a check in place that verifies whether the tracking# uploaded to eBay or not. If it did not than it should not transfer to fulfilled unless we manually do it. You had mentioned that you guys would implement this check. Right now with this latest eBay token issue we just had a user accidentally mark a bunch of eBay orders as shipped and all orders transferred to fulfilled without the actual tracking# uploading to eBay. Had we not been paying attention to this, this could have been a big issue that affects our performance metrics. Please make this a priority. Just like with Amazon if Sixbit is not able to confirm that the tracking# uploaded to eBay, than the order should not transfer to fulfilled but rather go into Confirmation Errors status just as you do with Amazon.
Todd,
AVR-Sales and Nabachandar, refer to THIS TOPIC.
You do realize I am the one that started the thread your referring to? The post above was letting AVR-Sales know why they were having issues. But thanks for pointing me to the thread that I created yesterday!
Users are reporting that they are not able to enter the sixbit application due to this ebay api token issue. Also regular users without admin permissions get presented with the business profile screen showing the eBay/Amazon account info etc…. Can you guys please release an updated version in the future that regardless of eBay token working or not, that we are able to enter into the application since the application is also used for other marketplaces etc… Right now we are not even able to use it for Amazon etc… which is a huge problem. Finally regular non admin users should not be seeing the seller profile screen to reauthorize etc… unless they have permissions on their account.
We’ve contacted eBay and they should be reverting a change on their end to fix this issue.
It should start working again automatically, but we’ll post on the board when we confirm it is.
John is there any updates from eBay on this issue? They should have been working on this throughout the night. Is there more to this than has not been said? We sell on multiple channels and this could cause overselling due to inventory not updating. Please follow up with them so we know how much longer to wait.
There seems to be token authorization issue going on requiring authorization which isn’t working.
I hate to say this but I am glad we are not the only ones. Hopefully Sixbit / eBay gets it fixed soon!
John,
We also seeing issues with random Amazon order tracking#s not uploading to Amazon. This started after updating to this recent build. If we manually upload tracking# through Amazon seller central and then go back to Sixbit and click refresh on order that the order goes to fulfilled. It’s random as we get several orders per day that tracking# is not uploading for some reason.
Delay issue seems to be resolved on our end. We will report back as we continue testing if we notice any further issues.
Brandon,
Is there an ETA as to when the new build will be out? Our users are also reporting various issues which might be tied to the issue you are describing. We wanted to test out the new build ASAP to see if the issue is related or not.