Update: New ineligibility code for getItemEligibilityPreview
On 14 August 2024 Amazon adds a new ineligibility enum FBA_INB_0342 to the getItemEligibilityPreview API, flagging offers that cannot use manufacturer barcodes (UPC/EAN/ISBN) for inbound shipments. The response includes a clear message and replaces the generic FBA_INB_0300 code for barcode issues.
Overview
On 14 August 2024 Amazon will add a new inbound‑ineligibility code—FBA_INB_0342—to the JSON response of the getItemEligibilityPreview API. The flag indicates that a product cannot be shipped to Amazon fulfillment centers using the manufacturer‑issued barcode (UPC, EAN, or ISBN). Sellers who depend on barcode‑based inbound shipments need to recognize the new code, understand how it is returned, and adjust their preparation processes to keep inventory moving.
Key Points
- New enum value — The API now includes FBA_INB_0342, a dedicated identifier for barcode‑related inbound restrictions.
- Effective date — The change becomes active on 14 August 2024, so any eligibility request made on or after that day may contain the new code.
- Message payload — When the code appears, the response carries a clear text such as “This offer is no longer eligible to use manufacturer barcodes for inbound shipments.”
- Targeted scope — The flag applies exclusively to offers that attempt to use a manufacturer‑provided UPC, EAN, or ISBN for FBA inbound; other eligibility reasons (size, weight, hazardous material, etc.) continue to use existing codes.
- Granular preview — The eligibility preview continues to give sellers a pre‑shipment health check, now with finer granularity that separates barcode issues from generic ineligibility.
- Remediation options — Amazon advises sellers to switch to a brand‑registered barcode, obtain a GS1‑issued identifier, or generate Amazon‑specific FNSKU labels to resolve the restriction.
How getItemEligibilityPreview Works (What’s Changing)
- Submit eligibility request — A seller calls the endpoint with a SKU, ASIN, or product identifier and indicates the intended inbound method. Example: The seller sends a request for ASIN B07XYZ1234, specifying that units will be shipped using the existing UPC 123456789012.
- Backend evaluation — Amazon’s eligibility engine cross‑checks the supplied barcode against the current inbound policy list, which now includes the new barcode restriction rule. : The engine detects that UPC 123456789012 is on the prohibited list for FBA inbound and marks it as ineligible.
Analysis & Recommendations
Why This Matters
Sellers relying on manufacturer barcodes will see FBA_INB_0342 in eligibility checks after 14 Aug 2024, causing inbound plan rejections unless they switch to Amazon‑generated FNSKU or a GS1‑registered barcode. Early detection prevents shipment delays and inventory holds, preserving fulfillment performance.
Key Takeaways
- New enum value FBA_INB_0342 is added to getItemEligibilityPreview responses for barcode‑related inbound restrictions.
- Effective date is 14 August 2024; any eligibility request on or after this date may contain the new code.
- The response now includes the message "This offer is no longer eligible to use manufacturer barcodes for inbound shipments."
- FBA_INB_0342 replaces the generic FBA_INB_0300 code, giving sellers precise insight into barcode ineligibility.
Recommended Actions
- →Update your SP‑API integration to parse ineligibilityReasonCode and add handling for FBA_INB_0342 (Seller Central > Settings > API Integration).
- →Add a pre‑shipment check: run getItemEligibilityPreview for each new SKU; if FBA_INB_0342 appears, switch to Amazon‑generated FNSKU in Seller Centr...
- →Create an automated alert (e.g., AWS Lambda + CloudWatch) that flags any API response containing FBA_INB_0342 and posts a notification to the fulfi...
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!