open-api
open-api copied to clipboard
[ENDPOINT] Proposed design change for Shop Receipt (add ship by timestamp)
What in the current endpoint design do you think is missing or find confusing?
To calculate the ship by date for an order, we currently have to use processing_min and processing_max from getListingInventory, calculated from the greatest processing_max item in the order. This is undesirable because the time cutoff in the ship-by dates calculated by Etsy for our timezone is not documented or clear (and also not midnight or configurable to our local close of business), nor are the adjustments for shipping on weekends and federal holidays, so our estimation is often inaccurate.
Proposed Endpoint Design Change Expose the required ship by timestamp in the Receipt
Why are you proposing this change? This is important because of Etsy's new "Star Seller" requirements. We had an order, for example, that was scheduled to ship on July 4th (a Sunday), ahead of a US federal holiday July 5, so was considered late by Etsy, but was within our estimated shipping schedule based on our hours of operation and the days we cannot physically ship. While I understand that this team has no control over the business rules, exposing the required ship by date will both save us some awkward code and help us meet the new requirements.
+1 for this
This is crucial
+1