Processing Profiles Launch

[openapi-support[bot]]

We're excited to announce that Processing Profiles are now the source of truth for processing times across Etsy. This is a breaking change and you must update your applications. Processing Profiles is a new feature that changes how sellers manage their processing times. This update allows sellers to set processing times at a more granular level, either per listing or at the product level.

If you have not migrated your application to use processing profiles you can consult the migration guide to guide you through the required changes you need to make.

As a reminder, the legacy=false query parameter is no longer required. This is now the only way to to manage processing times.

We appreciate your cooperation and thank you for your continued partnership. Please let us know if you have questions or need assistance by opening a new issue or emailing [email protected].

[amphelps535]

Hello, I am experiencing an error updating the Inventory of a digital product.

I send:

{
    "products": [
        {
             "sku": "5",
            "offerings": [
                {
                    "quantity": 999,
                    "price": 4.15,
                    "is_enabled": true
                 }
            ]
        }
    ]
}

to /inventory PUT for a digital listing (with type 'download') however I get this error as of yesterday:

{
"error": "All offerings need readiness state"
}

Does this seem appropriate? From the migration guide it seems like these readiness states should only be required for physical products.

Thank you for your support!

And to confirm, I get this from running GET listing for the given listing I'm attempting to update
"listing_type": "download"

[openapi-support[bot]]

A patch for this has been released. Thanks again for the report!

[li1ldrawlah]

Hi,
I'm having an issue of getting error: Server Error (500) when trying to use updateListingInventory with the new processing profiles.

{
  "products": [
    {
      "sku": "32046069474071356480",
      "offerings": [
        {
          "quantity": 999,
          "is_enabled": true,
          "price": 59,
          "readiness_state_id": 1404062437198
        }
      ],
      "property_values": [
        {
          "property_id": 513,
          "property_name": "Phone Models",
          "scale_id": null,
          "value_ids": [
            1401944543077
          ],
          "values": [
            "IPhone 17 Pro Max"
          ]
        },
        {
          "property_id": 514,
          "property_name": "Case Type",
          "scale_id": null,
          "value_ids": [
            1133347599171
          ],
          "values": [
            "Tough Case-Glossy"
          ]
        }
      ]
    }
  ],
  "price_on_property": [
    513,
    514
  ],
  "quantity_on_property": [
    513,
    514
  ],
  "sku_on_property": [
    513,
    514
  ],
  "readiness_state_on_property": [],
}

I'm only include 1 product in the sample and I'm using the same processing profile for all of them. Not a great programmer, am using pre-written python code ( https://github.com/anitabyte/etsyv3 ) and trying to implement the new changes.

Tried to compare with inventory with an existing listing and the format looks identical except for
"listing": null
at the bottom

Appreciate any help.

[matthewtaylor-ops]

We are receiving an error when attempting to update stock on certain listings. Other listings on the account update as expected, now that we GET the readiness_state_id and return it back when updating stock.
These are physical listings to be shipped and they are returning a readiness_state_id of null.

First we GET the listing data and we see the readiness_state_id on the affected listings is null:

"readiness_state_id": null

"readiness_state_on_property": [],

We then PUT this data back to update stock we return this value:

`      "offerings": [
        {
          "price": 13.95,
          "quantity": 70,
          "is_enabled": true,
          "readiness_state_id": null
        }`

The API responds:
{"error":"All offerings need readiness state"}

I cannot understand why we are receiving an error here. Surely the listing should either have a readiness state id value, or the API should accept what is being sent when the value is set to null?

[matthewtaylor-ops]

It seems that the listings in question here were not migrated over to the new system. In this case the listings had to be manually edited and assigned a working shipping profile by the user directly.

We are now receiving the readiness state id and updating stock as expected.

[nrathi]

I believe this launch has create a bug with the rate limit logic. Details here: #1475