Fulfillment Inbound API v0 being deprecated, new Fulfillment Inbound API v2024-03-20 not ready for Small Parcel Delivery (SPD)
We are currently using Fulfillment Inbound API v0 to create shipments and print labels for Small Parcel Delivery (SPD) shipments.
Amazon is deprecating Fulfillment Inbound API v0 on December 20, 2024. However, the new version Fulfillment Inbound API v2024-03-20 does not yet support Small Parcel Delivery (SPD) shipments, for the carton-level information not known upfront option.
Amazon's docs say "the process for creating a shipment when the carton-level information is not known upfront is only available for LTL shipments at this time"
https://developer-docs.amazon.com/sp-api/docs/fulfillment-inbound-api-v2024-03-20-use-case-guide
Our question is, when will support for Small Parcel Delivery (SPD) shipments be available in the new API (for the carton-level information not known upfront option).
Will it be before December 20, 2024? We are worried that we won't have a workable API alternative by December 20th.
Fulfillment Inbound API v0 being deprecated, new Fulfillment Inbound API v2024-03-20 not ready for Small Parcel Delivery (SPD)
We are currently using Fulfillment Inbound API v0 to create shipments and print labels for Small Parcel Delivery (SPD) shipments.
Amazon is deprecating Fulfillment Inbound API v0 on December 20, 2024. However, the new version Fulfillment Inbound API v2024-03-20 does not yet support Small Parcel Delivery (SPD) shipments, for the carton-level information not known upfront option.
Amazon's docs say "the process for creating a shipment when the carton-level information is not known upfront is only available for LTL shipments at this time"
https://developer-docs.amazon.com/sp-api/docs/fulfillment-inbound-api-v2024-03-20-use-case-guide
Our question is, when will support for Small Parcel Delivery (SPD) shipments be available in the new API (for the carton-level information not known upfront option).
Will it be before December 20, 2024? We are worried that we won't have a workable API alternative by December 20th.
19 replies
Seller_TTG0TX5GOhqmW
Not only that -- there seems to be serious issues with this new API version.
We switched to v0 (from MWS) back in like March 2024 -- a week later we were told "v0 is outdated, you need to switch to v2024-03-20 which came out a week ago" and were given a deadline.
We are trying to switch from v0 to v2024-03-20 and it's a nightmare. What use to be a single call now takes 3 -- and the API does not return any results (or errors). We are trying to get inbound plans and it just returns empty results.
I opened a case and they said:
"Currently there is no option for defining prep category from API, in this case you have to go to seller central shipment's step 1 page. In step 1 of the page you will see error beside the problematic skus. Currently, our tech team is planning to add defining prep category from API with the next release."
So we are being forced to use a new API by a specific deadline that isn't even complete??
We were then sent to some page:
https://sellercentral.amazon.com/fba/sendtoamazon/confirm_content_step
To manually set prep types for items. We re-tested our API code for the new version using specific SKU(s) that had prep types selected, and we are getting the same results (empty results) with no errors.
This new version of the API is *NOT* ready for prime-time. I have no idea why we are being forced over to it.
Seller_WY1FDS1qTfG3S
Would an Amazon mod be able to shed more light on this?
Jameson_Amazon
Hi @Seller_WY1FDS1qTfG3S,
Thank you for reaching out about this and for your patience here!
Unfortunately, I do not have additional insights regarding the timeline and details of this update besides what has been provided within the doc. That said, I can reach out to internal teams to see if I can get further information regarding your question here.
Have you opened a case with Seller Support asking for clarity on this? If so, can you please send me that case ID so I can reference that correspondence?
Thanks again,
Jameson
Seller_WDo6kiNNjgqZ6
Hi,
Just wondering if you've managed to get any further with this issue? Looking at the second use-case tutorial on the page you linked to ("Creating a shipment when the seller does not know the carton level information up-front"), the section on using generateTransportationOptions and listTransportationOptions includes Ground Small Parcel and Air Small Parcel among the "shipping modes", with no mention of being restricted to only LTL.
Seller_TTG0TX5GOhqmW
The new version of the API is a mess and still not word on if it will be pushed back.
It's full of bugs -- I've had cases open for over a month just to get the most basic first few calls to work and return results.
We are using "path #2" which is when you want placement options with only quantity information, which is clearly defined in the documentation. I was told by two different support people I had to supply box content information and I had to keep showing them the alternate path.
The ListPlacementOptions command kept returning empty results -- no errors, just empty results. It turns out that you have to "wait" a certain amount of time for the prior commands to internally process -- even if they return successfully ... you can't just make one call after another. And if you get to that command to quickly, it just returns empty data.
So I've been testing a command they suggested to get the command status to make sure it has completed before moving ahead -- and that has bugs. If you call multiple commands then use that status check, it gets stuck on prior commands. And it seems if you do the status check too rapidly, you can get command failure responses as well.
All of these test results came from having to troubleshoot with support --- and all of these are just testing the first few commands to get placement options for a shipment. Until today I have not even been able to move further in the process and create a shipment... now I at least have some data being returned, but I have to put these long repeating "status checks" in to make sure the former commands completed properly and fully.
This whole API is strange. Single commands have been turned into multiple -- and now require long status checks in between. It's going to take like 7+ calls just to get a list of centers based off some SKUs and QTY... or a long wait to make sure it completes.
I'm not sure how we are expected to use this API by December 15th when it's still in troubleshooting phase and with little support. It's also at the worst time of the year.
Suggest those who have reps reach out to request this transition be pushed back.
@Jameson_Amazon @KJ_Amazon
KJ_Amazon
Hello @Seller_TTG0TX5GOhqmW @Seller_WY1FDS1qTfG3S @Seller_V64vFDcfYsdRa and other sellers asking about the new Fulfillment Inbound AP. I received an update from our partner team about an extension to the migration to the new Fulfillment Inbound API v2024-03-20:
To ensure a smooth transition during this holiday season, we are providing a grace period for migration to the new Fulfillment Inbound API v2024-03-20, until January 21, 2025. If you have already begun the transition, we strongly recommend completing it as soon as possible to benefit from enhanced performance and new features. For those who haven't begun their migration, this extension provides additional time to implement the necessary changes without any business disruptions.
What action is required?
If you use the Fulfillment Inbound API v0, you must migrate to Fulfillment Inbound API v2024-03-20 as soon as possible to avoid service disruption. For help with this, refer to:
- Fulfillment Inbound API v2024-03-20 use case guide
- Fulfillment Inbound API v2024-03-20 reference
- Migrating Fulfillment Inbound workflows
For more information, contact Developer Support for further assistance. Refer to the Fulfillment Inbound API FAQ for more information on features that are supported with the general availability launch. You can also check out the GitHub forums for discussions.
