Amazon Feed Error 99007: How to Fix Conflicting Column Values in Your Product Listings
Amazon Feed Error 99007 occurs when two columns in a product listing feed contain conflicting values. Amazon silently ignores one value, which can lead to incorrect listing data if not corrected.
Overview
Amazon Feed Error 99007 occurs when two columns in your product listing feed contain values that contradict each other. When Amazon detects this conflict, it ignores the value in the first column and processes only the second, which can lead to unexpected listing data if left unaddressed. Understanding this error is essential for sellers who regularly upload inventory files, flat files, or listing feeds through Seller Central.
Key Points / What Sellers Need to Know
- Error message format - The error reads: "The value in column {0} conflicts with the value in column {1} and was ignored." The placeholders {0} and {1} refer to the specific column names in your feed file where the conflict was detected.
- Automatic resolution by Amazon - When this conflict is found, Amazon does not reject the entire listing. Instead, it silently drops the value from the first column and keeps the value from the second column, which may not be the outcome you intended.
- Root cause - The error is triggered when your input file contains two data points that are logically incompatible with each other, such as contradictory product type attributes, mismatched category-specific fields, or inconsistent variation relationships.
- Required action - You must correct the conflicting value in your feed file and resubmit it to ensure your listing reflects the accurate data you intended.
How This Error Occurs
Error 99007 typically surfaces when sellers populate multiple columns in a flat file or inventory loader that Amazon considers mutually exclusive or logically dependent. For example, certain product type fields dictate which other attributes are valid, and entering a value that does not align with the controlling field creates a conflict. This can also happen when updating listings in bulk if template columns carry over outdated values that no longer match newly assigned attributes. Sellers using third-party listing tools or automated feed systems are especially prone to this error, since those tools may populate fields based on cached or default values that conflict with current Amazon requirements.
Common Scenarios and Examples
One frequent trigger is when a seller specifies a product type in one column but then provides attributes in another column that are only valid for a different product type. Another common case involves variation listings where the parent-child relationship fields contradict the item type or category designation. Size and color attributes can also conflict if the variation theme column specifies one grouping method while individual attribute columns suggest another. Feed migrations from older template versions to newer ones are another source of this error, as column names and valid value sets can change between template versions.
Analysis & Recommendations
Why This Matters
Sellers who upload product data via flat files or bulk feeds need to understand this error to prevent incorrect listing information. Unresolved conflicts can silently corrupt product data across your catalog.
Key Takeaways
- Error 99007 means two columns in your feed have incompatible values, and Amazon silently drops one
- The first column's value is ignored in favor of the second column when a conflict is detected
- Always download the latest flat file template before bulk uploads to avoid outdated field conflicts
- Check your feed processing reports regularly to catch and fix silent data discards
Recommended Actions
- →Review your feed processing reports for Error 99007 and correct any conflicting column values before resubmitting
- →Download the latest category-specific flat file template from Seller Central to verify valid values for each field
- →Run small test uploads before large batch submissions to catch column conflicts early
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!