[Nabachandar]

Upgrading to version 3.00.273 did not solve the problems.

[Nabachandar]

100% problems with beta edition 3.00.272. One of our client machines had a previous edition loaded on it 3.00.244. Everything on that version is working properly everyone else that updated 3.00.272 is having problems. I recommend those that have yet to upgrade to this version to hold off until Sixbit team fixes the problems.

[Nabachandar]

Just got IAF token error as well.

[Nabachandar]

is there status update on: support for listing non-ASIN items on Amazon

[Nabachandar]

John,

I am looking at latest orders. I honestly did not expect the older orders to have an updated date. As of build 3.00.241 the issue still exists. The Latest delivery date for Amazon is 1 day ahead. For instance “BRAND NEW” order from Amazon came in today shows Deliver by: Wed, Sep 20, 2017 to Mon, Sep 25, 2017 in Amazon Web Portal. But in Sixbit shows: Earliest Delivery 9.20.17 to Latest Delivery Date: 9.26.17. To be clear I am talking about brand new order, that came in today 9.14.17 (and running build 3.00.241 as of yesterday. Previous builds had same problem with only exception in the past also included Ship Date that was wrong, that seems to have been fixed but as far as DELIVERY DATE, problem still exists on our end.

[Nabachandar]

John,

Please provide response on the following:

1) When the issues started with 3.00.240 several eBay orders were marked as shipped. The log showed that the “Complete sale failed” and tracking# did not upload to eBay. Order got transferred to status “Fulfilled”. This could create problems as unless we were to go into logs we would not have caught that and clients would not see their tracking# on eBay, thus affect our eBay performance ratings. I think this needs to be changed to work similar like you had done with Amazon. Since it’s critical for the tracking# to upload to eBay and order to have “Complete sale success” status, that in the event it fails to upload trackin# to eBay, the order should not change to status fulfilled upon clicking marked as shipped. In this case it should remain under in process so that we can attempt to resubmit the tracking#. Or perhaps have it go into confirmation errors status like you do with Amazon orders whenever tracking# does not upload.

2) Amazon Latest Delivery Date is not accurate. As of build 3.00.241 still not fixed. Latest delivery date for Amazon is 1 day ahead. For instance an order from Amazon came in today shows Deliver by: Wed, Sep 20, 2017 to Mon, Sep 25, 2017 in Amazon Web Portal. But in Sixbit shows: Earliest Delivery 9.20.17 to Latest Delivery Date: 9.26.17. Note this is brand new order that just came in today 9.14.17 (and running build 3.00.241, same problem existed in previous builds). Only exception in the past Ship Date was wrong, that seems to have been fixed but as far as DELIVERY DATE, problem still exists.

3) eBay wants UPC code assigned to all “NEW” condition items, we updated items product ID field and selected UPC in drop down under “Identifiers” section. When we tried to click send revision to site under check listings, it did not update UPC field. Next we tried to add UPC to Item specifics section of the item and click on send revisions to site, still did not update. Final attempt when to check listings, selected item, clicked go to items for selected listings, then selected edit – batch edit items, selected update running listing and pressed ok. Finally UPC field for running listing got updated. Is this normal behavior? We noticed that if we made changed to description we did not have to go through same steps, and instead go simply click on send revision under check listings but for some reason it didn’t update UPC whether we had it under product ID field or item specifics field. For UPC to update only way was to do it through the batch edit items. Please confirm if normal and finally whether UPC must be assigned to item specifics or product ID field. When we list new items we don’t assign to item specifics and everything shows up correctly so surprised that during revision it did not work and forced us to add it to item specifics.

[Nabachandar]

We updated to release 3.00.241, so far things appear to be working.

Several questions/suggestions:

1) How do we import an old eBay auction that does not appear to be in Sixbit. There are several running listings which we can’t seem to find in Sixbit and they do not import. Even prior release before 3.00.240 did not show them.

One of the ads on eBay has a start time on: Start time: Aug 17, 2017 12:57:17 PDT but we don’t see it in running or even completed listings.

2) When the issues started with 3.00.240 several eBay orders were marked as shipped. The log showed that the “Complete sale failed” and tracking# did not upload to eBay. Order got transferred to status “Fulfilled”. This could create problems as unless we were to go into logs we would not have caught that and clients would not see their tracking# on eBay, thus affect our eBay performance ratings. I think this needs to be changed to work similar like you had done with Amazon. Since it’s critical for the tracking# to upload to eBay and order to have “Complete sale success” status, that in the event it fails to upload trackin# to eBay, the order should not change to status fulfilled upon clicking marked as shipped. In this case it should remain under in process so that we can attempt to resubmit the tracking#. Or perhaps have it go into confirmation errors status like you do with Amazon orders whenever tracking# does not upload.

3) Amazon Latest Delivery Date is not accurate. I am not sure if this issue has been resolved in latest release 3.00.241 but as of release 3.00.240 it was 1 day ahead. For instance an order from Amazon came in today shows latest delivery date as 9.23.17 but on Amazon web portal shows as 9.22.17.

4) eBay wants UPC code assigned to all “NEW” condition items, we updated items product ID field and selected UPC in drop down under “Identifiers” section. When we tried to click send revision to site under check listings, it did not update UPC field. Next we tried to add UPC to Item specifics section of the item and click on send revisions to site, still did not update. Final attempt when to check listings, selected item, clicked go to items for selected listings, then selected edit – batch edit items, selected update running listing and pressed ok. Finally UPC field for running listing got updated. Is this normal behavior? We noticed that if we made changed to description we did not have to go through same steps, and instead go simply click on send revision under check listings but for some reason it didn’t update UPC whether we had it under product ID field or item specifics field. For UPC to update only way was to do it through the batch edit items. Please confirm if normal and finally whether UPC must be assigned to item specifics or product ID field. When we list new items we don’t assign to item specifics and everything shows up correctly so surprised that during revision it did not work and forced us to add it to item specifics.

[Nabachandar]

After completing all steps in post# 9. Just had the users with listing submission errors, exit sixbit and then launch sixbit again, now appears that new listings are posting.

[Nabachandar]

Listings are not submitting for us either.

[Nabachandar]

Reauthorizing did not seem to work earlier today when we did it on client machine (client has it’s sixbit agent disabled, which is strange as in past whether agent enabled for client machine or not, used to seem to work).

I just tried to reauthorize again this time directly on the server which has the agent running. Re-authorization seemed to have been successful this time around.
I am currently refreshing all eBay listings, which so far appear to refresh successfully.

Once refresh is complete I will confirm if items being posted import as well as new orders from earlier today.

[Nabachandar]

John, I don’t mean to push, but is there any sort of ETA when new release will come out? Trying to plan ahead.

[Nabachandar]

I am getting the IAF token expired error as well now.

EDIT: Tried reauthorizing. We are seeing same problem that BOB is reporting.

Can someone from Sixbit acknowledge that you’ve seen this post and working to resolve. This is a series problem.

[Nabachandar]

After manually selecting and refreshing all running listings the errors initially experienced appear to have been resolved.

[Nabachandar]

We just installed build 3.00.135 and the issues seemed to have been resolved. Will continue to monitor and update if we find any problems.

[Nabachandar]

Received notification from the super prompt Sixbit support team that the issue has been identified and fix is coming out in build 3.00.135. I’ll update once we test it out. To rest, I recommend holding off on 3.00.134.

[Author]

Posts