I have 5 sales on Oct 30 ...
Only 3 show in the "last review period" data.
NONE of them show as being shipped despite all being shipped Oct 31.
---
Look at the "current review period" data ...
All 5 sales show up ... all with tracking data being shipped Oct 31.
---
The "current review period" still doesn't show anything about the sale on Oct 31 (which shipped Nov 1) ... and as far as my school learning goes, is a sale made in the month of October.
---
I called in on Nov 1 when I got the email about the wonderful Customer Service Badge and Speedy Service Badge ... held about an hour while the support "checked on things" ... then was told to wait 24 hours for the shipping data to refresh. Yeah, I'm a web developer ... I know better ... she said she would escalate it and to hold ... then was hung up on and never called back despite the support person verifying my phone number at the beginning of the call in case we got cut off.
Called back ... waited 2 HOURS on hold while this person verified everything again (you can look in the live data and see all the relevant data). Was told I should wait 48 hours for the data to refresh after I explained it's already been 24 hours since the data period ended. See the pattern?
But I waited .. called just now ... didn't wait on hold too long ... but got the same story. And when the support person started telling me how every month I would have a chance to make Star Seller ... I blew up.
Because that's what I was told LAST MONTH when the same thing happened because I'd had too many "pick-ups" which has no tracking number and penalizes the seller and didn't learn that before coming to this forum to read about all the other sellers who'd gotten screwed by the same exact thing.
So are there any real tech support people here who know how to pull data from a database at the correct time instead of the middle of a Sunday?
Believe me when I say this is not a difficult thing to do. I'll write the SQL for you if you need.
Yeah, I'm snarky right now because I always get that way when I deal with illogical systems. Especially when the fix is SOOOOO easy --->
[code]
select * from sales where sales_date >= "2022-08-01 00:00:00" and sales_date <= "2022-10-31 12:59:59"
[/code]
Gets a bit more complicated when you factor in the picked-up stuff ... but I'm not getting paid to write a complex query on a database I haven't seen .. soo ..
---
Seriously, why is this a problem? You guys have an amazing website with so much cool stuff behind the scenes ... why does this program not work correctly? The fees have doubled on us since I opened my Etsy shop .. but I don't mind that if I get the value for it ... and you've delivered quite well on most things ... BUT ...
(disconnected)
- Grumpy Old Programmer
@RCGdesignsETSY: The real problem seems to be Etsy's verbiage. As mentioned by others end of the month is always problematic. Have you checked the applicable CSV files? Based on our analysis of the CSV files, it appears that messages are assigned to the month that the 24 hour reply window ends (not when the message was received or answered) and orders are assigned to the month that they are scheduled to ship by (not when they were placed or shipped). And dates are determined by UTC not the sellers timezone.
It's always been that way. Back when the program started (and I was getting a lot more orders), I had over 20 orders that didn't count during the last three days of a month, even though some of them were shipped and even delivered by the cutoff date.
Basically, it's not worth making a frustrating call to support about this, because it's just how they've decided to calculate things.
What is your time zone? I believe Etsy uses UTC for calculating star seller metrics.
@RCGdesignsETSY: The real problem seems to be Etsy's verbiage. As mentioned by others end of the month is always problematic. Have you checked the applicable CSV files? Based on our analysis of the CSV files, it appears that messages are assigned to the month that the 24 hour reply window ends (not when the message was received or answered) and orders are assigned to the month that they are scheduled to ship by (not when they were placed or shipped). And dates are determined by UTC not the sellers timezone.
@RCGdesignsETSY "the sale on Oct 31 (which shipped Nov 1) ... and as far as my school learning goes, is a sale made in the month of October"
.It may not be as straightforward as you are thinking. Orders on the last day/s of the Month are attached to the Month in which they are "due to ship", not the month in which the Order was made or the Month the Order was actually Shipped. So Orders on 30/31 Oct that were due to Ship 01/02 Nov will be attributed to the November stats. This is obviously set up to cover and not disadvantage people who have not shipped by 31 Oct Orders which were not due to Ship until November,
I understand all the comments here ... but as a database guy for the last 30 years, it really is easy to do. They can run the queries for sellers in their separate timezones, cut off at exactly midnight on the last day of the month for each timezone. That's what is so frustrating ... it's not difficult!
Plus, that's easier on the system to handle because you're grabbing less data instead of *all* the sellers' data.
With a complex query, or a secondary pass, they can filter out the packages that have longer processing times and *not* include them in the data set used to determine Star Seller Status. And in that same query/second pass, they can filter out for items that were picked up and didn't need a tracking number ... at the very least not even count them ever.
I do database stuff like this every day. So it's hard for me to accept "that's the way it is" as a valid answer.
@RCGdesignsETSY And Etsy knows this. They are well versed in databases but they choose what they want to do. We live with their decisions.
I have worked with many a software engineer/ programmer etc. to know that while it may be possible always to do such and such from a technical point of view, the corporate business side always wins out. They decide how the programming will be determined, not the head of the software/programming dept.
@RCGdesignsETSY: Not disagreeing with you, as we have quite a bit of experience with system design and implementation and constantly wonder what some of their decisions are based on. But I still think that the major issue is the way Etsy words things - why don't they just say that "eligible orders" is based on the scheduled ship date instead of implying that it is the order date.
Etsy uses UTC time. So that cut off point is determined by UTC time and Etsy's penchant for 30 days.