Listings will no longer create items when imported
In the past, we would automatically create items when a listing was found on Amazon.
This was acceptable when we supported only a single Amazon channel, but now that we are moving to allowing multiple channels, it creates some syncronization issues.
For example, if there is different data for the same SKU on two channels, then which data should we use?
Or if one channel has a SKU that represents a different item than a SKU on another channel, then the incorrect item could be used and shipped as a result.
Since there is no way to automatically resolve these issues, instead, we are making it easy to find listings, create them as items, or link them to existing items, so that if there is a conflict that needs to be resolved, it can be resolved by a person rather than our system making an educated guess.
This is what that will look like:
Our aim is to make it just as easy to find a listing and add it to a shipment as it was when you just added items.
As a bonus, this will make it much easier to manage FBA vs FBM listings since items will no longer created automatically, so you can either only create an item for the FBA listing, or create one item and link it to both listings. This is a long-standing issue we’re excited to resolve.
If you have any feedback or issues with this update, let us know!
Log in to comment and vote
Comments22
Kal
Apr 15, 2025
But what if the merchant only has 1 channel? Surely it should be automatic, or an option to set the default channel to use for inventory creation would be more efficient
Keith Brink
Apr 15, 2025
@Kal Our thinking here is that it should be just as fast to select a listing to add to a shipment as an item, so there should be no downsides to not creating an item immediately.
Let me know if there’s something we missed here that’s slowing you down.
Kal
Apr 15, 2025
We use the API to create inbound shipments on behalf of our customers. The change has caused massive issues for us, as it’s no longer as simple as searching the merchants inventory and adding it into a shipment.
Keith Brink
Apr 15, 2025
@Kal Ah, I see, that’s true as an API user the experience is quite different now.
In your case, I would default to searching for listings via the API. The listing will return a product_link:
The product_id is equivalent to the item ID, so you can use it to add items to shipments. If there is no product_link, you can use the details in the listing to create an item first, then add that item to the shipment.
That means compared to the old item-based approach, you should only have a single additional API call.
Kal
Apr 16, 2025
Hi Keith,
Thank you for your guidance. I've implemented a solution based on your suggestions, and I wanted to share what I've learned and the approach I've taken:
I successfully find channel listings using the Index listings call. However, I've had to implement pagination through all pages (sometimes 20+ pages) to find specific SKUs because the search functionality doesn't seem to be working effectively. Direct queries for SKUs often return no results, requiring a full scan of all listings.
I've created a process that:
Finds the channel listing by SKU (by paginating through all listings)
Creates an inventory item with the same SKU and title
Adds all identifiers from the channel listing to the inventory item (ASIN, EAN, GTIN, FNSKU, etc.)
Creates an inbound shipment using this inventory item
This approach successfully creates inbound shipments with all the necessary identifiers, including the FNSKU, so we’re able to print during check-in.
However, I'm still unable to establish a product_link between the channel listing and the inventory item. I've tried multiple approaches:
Using the
/channels/{CHANNEL_ID}/listingsendpoint with bothitem_exists=yesanditem_exists=noTrying different payload formats and combinations
Looking for other endpoints that might handle linking
All attempts to create this link result in 500 Server Errors from the API. Establishing a link seems to only work via the UI.
The current solution works for creating inbound shipments, but the channel listings and inventory items remain unlinked (no product_link is established).
Is this expected behaviour, or should the linking process be working? Are there any other approaches you'd recommend for establishing this link?
Thank you for your help!
Keith Brink
Apr 21, 2025
See my comment to Andrew with some more details on filtering, let me know if you continue having issues.
For the product_link, we’ve added that endpoint to the docs:
https://docs.prepbusiness.com/docs/endpoints/channels/listings/
Kal
Apr 21, 2025
Thanks for the new API endpoint. Does this carry over the identifiers & image automatically? Many thanks
Keith Brink
Apr 22, 2025
It does not, those will need to be added to the item individually.
Andre Zimmermann
Apr 15, 2025
“As a bonus, this will make it much easier to manage FBA vs FBM listings since items will no longer created automatically, so you can either only create an item for the FBA listing, or create one item and link it to both listings.”
→ We want to use only FBA products for outbound shipments to Amazon. How can we tell if an item is FBA or FBM? Especially if the merchant has every ASIN multiple times with different conditions for FBA and FBM? Right now we are often selecting the FBM listing which results in an error for the FBA shipment
Keith Brink
Apr 16, 2025
@Andre Zimmermann I’ve moved your comment here so we can work on showing which listing is FBA vs FBM:
https://feedback.prepbusiness.com/p/show-which-listings-are-fba-vs-fbm
Andrew
Apr 18, 2025
@Keith Brink Hi Keith - we’re experiencing the same issues as @Kal with new items and creating inbound shipments via the API. While Kal’s solution seems to partially work (for creating the inbound, but not linking the items), this isn’t working for us. The Amazon account has over 20k listings, so paginating through all of them each time we need to search for an item isn’t practical. Perhaps you can revisit the option to create a setting where a channel can be made the “default” and then items would automatically be created like they were in the past? At the moment, we stuck clicking through listings manually one at a time on the front end and creating the items.
Keith Brink
Apr 21, 2025
@Andrew The search function should work, have a look at the search language docs:
https://docs.prepbusiness.com/docs/search-language/
/api/channels/1/listings?page=1&per_page=20&q=title~"board"Here is an example of searching for “board” in the title, and you can search for the following fields:
sku
title
identifiers.identifier (any attached identifier)
channel_identifier
If you’re not getting results, could you give me an example of your search (you can email support with the details if you prefer, just reference this conversation).
@Kal This should be helpful for you as well.
Keith Brink
Apr 21, 2025
@Andrew Also wanted to link you to the new documentation for creating a product → listing link:
https://docs.prepbusiness.com/docs/endpoints/channels/listings/
Andrew
Apr 21, 2025
Thanks, @Keith Brink To make sure I have this correct. If there’s a new product that hasn’t been linked before, then these additional calls are needed:
Search the channel listings
Create a new inventory item with the listing details
Add the identifiers to the new item (repeat this call for each identifier, at least 2 per item with the UPC and FNSKU)
Link the new item and the listing
So it’s 5+ calls to the api for something that used to happen automatically?
Keith Brink
Apr 21, 2025
@Andrew Yes, that’s right.
In general, our direction with the API is to move away from endpoints that do a lot of things at once (such as automatically copying the listings details to a new item including the identifiers) in favour of a composable API where each individual action is taken as a discrete step.
This has the disadvantage of requiring more API calls to do the same behaviour, but the benefit of allowing exact control of what happens inside the application.
As we’ve grown, a challenge that we’ve faced is that the old approach with more automatic behaviours doesn’t quite fit all the time, and ties a lot of functionality together so that making a change in one place has a ripple effect throughout the application. This slows us down and makes it hard to troubleshoot issues.
I get that it’s annoying to have to change an existing, working codebase to adapt to our new approach here. At some point in the future we will be releasing a stable version of the API where we lock in our core behaviours, but for now I hope the long term results are worth the cost you’re paying today.
Andrew
Apr 21, 2025
Thanks Keith — and the long term strategy makes sense. Will get this updated on our end and email support if any issues.
Andrew
Apr 21, 2025
@Keith Brink One issue with the linking — the call to link only takes in one parameter. Shouldn’t the listing_id be used as well? Also, the terminology seems to change from one call to the next. I assume the product_id from the listings search should be the same as the item_id on the link?
Keith Brink
Apr 21, 2025
@Andrew Yes, sorry for the terminology confusion, item = product, we plan to move towards using “product” over “item”.
The listing is based on the listing ID passed in to the route parameter.
Andrew
Apr 21, 2025
@Keith Brink But is the parameter “listing_id”? The only parameter showing in the doc is “item_id”. And is this endpoint available now? I’m getting a 404 stating that “The route api/channels/listings/link could not be found”. I’ve tried with and without the channel id.
Keith Brink
Apr 21, 2025
@Andrew Apologies, forgot to add that listing_id param to the route. I’ve added it now.
/channels/{CHANNEL_ID}/listings/{LISTING_ID}/linkAndrew
Apr 21, 2025
@Keith Brink Makes sense, but I’m still getting a 404 at that endpoint. Message returned is "The route api/channels/7318/listings/72967247/link could not be found."
Keith Brink
Apr 22, 2025
Apologies, I should have double checked, it’s actually:
/channels/listings/{LISTING_ID}/linkThe channel ID is unnecessary since we have the listing ID already.