Amazon Inventory FNSKU Dispute — Yellow Cornmeal (2026-01-07)

Overview

During the ^[1], Mark and Gilbert identified an Amazon fulfillment error blocking approximately 1,000 units of Doodla's yellow cornmeal (1.5lb and 5lb SKUs) from entering FBA. The error was the root cause of Doodla's stalled sales, which had regressed to September-level revenue despite a shipment having been sent in early December.

The shipment was initiated by Carly on December 3rd but remained in an "inbound" state with a defect flag requiring an FNSKU barcode — an incorrect requirement given Doodla's status as the product manufacturer.

The Error

Amazon flagged the cornmeal shipment with a barcode defect, indicating an FNSKU (Fulfillment Network Stock Keeping Unit) was required. This is the standard requirement for resellers, who must apply Amazon-printed sticker barcodes over the original UPC.

However, Doodla is the manufacturer of the product and owns the UPC code registered through GS1. Manufacturers are authorized to ship using their own UPC barcode without applying FNSKU labels. The listing was originally configured to allow manufacturer barcodes, and this had never been an issue in prior shipments.

Amazon's error left ~972 units of high-velocity yellow cornmeal inaccessible in the fulfillment network, directly suppressing sales.

Business Impact

• Sales stalled at September/October levels despite inventory being "inbound"
• ROAS declined from ~3.8 to 3.29
• Yellow cornmeal (5lb) is one of Doodla's highest-selling SKUs; the 1.5lb was also affected
• The inventory shortfall compounded an earlier stockout around Thanksgiving, preventing a full recovery

Resolution Steps

1. Submit a dispute via Seller Central — Gilbert to contact Amazon immediately after the call, citing:
   - Doodla Farms is the manufacturer of this product
   - The product has always been sold using the manufacturer's UPC
   - FNSKU is not required; Doodla is not a reseller
   - The UPC is registered to Doodla through GS1
2. Reference the listing configuration — Amazon should be able to verify the "use manufacturer barcode" setting on the listing itself
3. Escalate if needed — Mark noted this is the first time this error has occurred despite years of selling the product

Related Issues Identified in Same Call

• FBA vs. AWD data discrepancy: The inventory tracking spreadsheet was incorrectly showing shipments going to AWD rather than FBA. Gilbert to clarify with Carly and update the tracker to reflect accurate inbound-to-FBA columns. See ^[2].
• Old World product review: A customer posted a video review showing shipping damage (inadequate packaging). Gilbert to dispute with Amazon, citing carrier damage rather than product defect. Packaging has since been updated.
• Three-way sync needed: Mark sent a note to Carly to schedule a call with Mark, Gilbert, and Carly to fully resolve inventory visibility issues.

Key Principle (Amazon Policy)

Amazon sellers cannot use a competitor's negative review to harm another seller, even if the content is truthful. Manufacturers selling their own products are authorized to use their own UPC barcodes and are not required to apply FNSKU labels.

This distinction — manufacturer vs. reseller — is critical for barcode compliance and should be documented in any future shipment disputes.

Action Items

• [ ] Gilbert: Submit Amazon dispute for yellow cornmeal FNSKU error immediately; cite manufacturer UPC authorization (@Gilbert Barrongo)
• [ ] Gilbert: Clarify FBA vs. AWD discrepancy with Carly; update inventory spreadsheet to remove AWD columns and add Inbound to FBA column with ship dates (@Gilbert Barrongo)
• [ ] Gilbert: Dispute Old World shipping damage review with Amazon; provide evidence of carrier mishandling (@Gilbert Barrongo)
• [ ] Mark: Schedule three-way call with Gilbert and Carly to review full inventory status (@Mark Hope)

Participants

• Gilbert Barrongo (gilbert.barrongo@asymmetric.pro)
• Mark Hope (mark.hope@asymmetric.pro)

Related

• ^[3]
• ^[4]