Amazon has announced the deprecation of XML and flat file listing data (including pricing and inventory) submitted via the Feeds API. Amazon has also stated that no new features or categories will be introduced in the legacy XML format, and applications must migrate to JSON-based Listings Items APIs or JSON_LISTINGS_FEED via the Feeds API by June 30, 2025.
In response, Celigo has introduced three new JSON-based flows for inventory, pricing, and product data to ensure compliance with Amazon’s latest requirements. We strongly recommend migrating to these new flows as early as possible to ensure a smooth transition. Celigo will phase out existing XML-based flows and fully adopt Amazon’s JSON-based approach.
For more details about Amazon's announcement, refer to Deprecation of Feeds API support for XML and Flat File Listings Feeds.
Key changes
GTIN exemption for listings items API v2021-08-01
If you are selling products using a GTIN exemption, you can create a product on Amazon without an ASIN or product identifier (UPC, GTIN, or EAN) using the Listings Items API v2021-08-01.
To apply for a GTIN Exemption:
- Submit a manual exemption request through your Seller Central account.
- Once approved, you can create a product listing using the Listings Items API v2021-08-01.
- When submitting the listing, ensure that:
- The brand name is set to "GENERIC".
- The supplier_declared_has_product_identifier_exemption attribute is set to true.
- For more details, refer to Seller Central.
Shift to Product-type-based listings
Amazon has transitioned from category-based listings to product-type-based listings. Consequently, Celigo now manages product listings through a single flow using mappings, replacing the previous category and custom category flows.
Flow updates
Enhanced Flexibility with Celigo’s Mapper 2.0: The new product flow leverages Celigo’s Mapper 2.0 framework, which enhances flexibility, efficiency, and scalability in product listing management.
The screenshots below compare the old and new mappings:
Old mapping
New mapping
Deprecating flow
Amazon will discontinue the CSV-based product flow on June 30, 2025. Following Celigo's release update, the product flow, along with the category and custom category flows created using it, will be marked with a "(To be deprecated)" tag.
-
Flows > Product
- (To be deprecated) NetSuite Item to Amazon Product (Add or Update)
New flow
The JSON-based product flow is now available in the Amazon - NetSuite integration app. You can transition to this new flow using the instructions provided below.
-
Flows > Product
- NetSuite Item to Amazon Product (Add or Update)
Migrate to new product flow
Prerequisites
Before you run the flow:
- Review the existing import field mappings (category and custom category flows) that have now been consolidated and auto-migrated as part of a single flow: NetSuite Item to Amazon Product (Add or Update).
- Check for any mappings that were skipped during auto-migration due to multiple source fields (e.g., hardcoded values) mapped to the same destination attribute.
- You can identify the skipped mappings using the table provided in the email with the subject: "Action Required: Migrate product flow mapping in your Amazon – NetSuite integration app".
- To add any skipped mappings, refer to the Add additional or missed mappings section.
The following screenshot displays the new NetSuite saved search, which includes the mandatory criteria for the Product type field. For existing users, it is essential to update the Product type field in NetSuite, as Amazon has replaced the Category field with Product Type.
Important: Ensure that the NetSuite item is configured according to the requirements of the selected product type. The product flow in the integration app will attempt to sync all fields that have data available in NetSuite, as long as a corresponding field mapping exists.
To identify the required fields for each product type, refer to Product type utility, and configure your NetSuite item accordingly.
With Amazon’s recent release of the new Product Feed API, product-type schemas are still evolving and may be subject to instability. As a result, Celigo currently does not perform additional validation or cleanup before submitting the feed. Once the schemas are stabilized by Amazon, validation and cleanup logic will be added to the flow.
Steps to take:
- Open your Amazon - NetSuite integration app.
- Navigate to Flows > Product.
- Turn off the toggle for the flow: (To be deprecated) NetSuite Item to Amazon Product (Add or Update).
Note: Ensure that you don’t turn on the new flow before turning off the old flow. - Turn on the toggle for the flow: NetSuite Item to Amazon Product (Add or Update).
Important:
- After the flow runs successfully, verify that the category mappings from the previous flow have been added to the NetSuite saved search and field mappings. To review these mappings, click the Edit Mappings icon next to the Amazon Item Import Adapter. Once confirmed, you can disable the old flow.
- Before running the flow for a larger set of products, we recommend conducting a few test runs with a smaller item group to ensure everything works as expected.
- Any fields added from the supported list in the Product Feed mappings table will be automatically retained as part of this transition. If additional mappings are required from the available options, you can configure them manually. For more details about the supported list of fields, refer to Product attributes mappings from category XSDs (XML) and flat file feed types.
- Once the flow is enabled, you can schedule it based on your business needs.
Add additional or missed mappings
Prerequisites
For items in NetSuite → eTail → Amazon:
- Ensure that the Product Type field is added for an item, as Amazon Category has been replaced by Product Type.
- Depending on the selected Product Type, update all required fields in the Results tab. The custom labels provided in the Results tab are used in the product flow mappings.
See Amazon's Product Flat File Mappings for product types (catalog).
For example, if the product image and ingredient field mappings were skipped during the auto-migration process, follow the steps below to manually configure and map product attributes:
Find available product-type attributes
You can access the full list of Amazon product-type attributes using the following documentation: Get Amazon Product-Type Attributes
Use the search functionality within the document to quickly locate the attributes relevant to your product type. For example, if you're working with Pet Supplies, you can search for attributes such as images, ingredients, or any other relevant field.
Mapping image attributes
You can map image attributes (like main images or additional images) to your NetSuite custom fields. Here's how:
- Search for “image” in the above doc to identify all image-related attributes.
- In your NetSuite saved search, assign a custom label (e.g., image) to your image export field.
- In the NetSuite Item to Amazon Product (Add or Update) flow, click the Edit Mappings icon next to the Amazon Item Import Adapter.
- If the image field wasn't auto-migrated under Attributes, click Add Mapping (+).
- In the destination field, choose the appropriate Amazon attribute such as:
- main_image_locator.media_location
- other_image_locator[].media_location
- In the source field dropdown, select the NetSuite saved search field (e.g., image) that contains your image URL.
- Preview to ensure the mapping is correctly configured.
- Click Save.
You can add as many image fields as needed and map them to their respective Amazon fields.
Mapping array fields (e.g., Ingredients)
For attributes that accept arrays (like ingredients), you can map them using dot notation:
- In your NetSuite saved search, map a field using a label like: Ingredients.0.value (or) Ingredients.1.value (or) ingredients.2.value.
- Then, in your flow mappings, add a new field and select the corresponding NetSuite saved search field from the dropdown. Make sure the destination field aligns with the structure Amazon expects, as defined in the product-type schema.
Notes:
- You can manually add any supported attribute—even if it wasn't auto-migrated.
- There's no strict requirement to follow a predefined hierarchy; you can map attributes flexibly to fit your business needs.
- Always ensure that your destination attribute name matches Amazon’s schema.
- Plan the transition ahead of time to avoid disruptions after June 30, 2025.