Recover Featured Offer Eligibility Without Guessing

The fastest way to recover a missing Featured Offer is to identify the failed gate first: account eligibility, price health, or competition among eligible offers. The agent reads the live Fulfillment by Amazon (FBA) inventory offer for the Amazon Standard Identification Number (ASIN) through the Amazon Selling Partner MCP, applies a reusable Skill, and uses Amazon Agent Atlas to ground the diagnosis in Amazon's Featured Offer rules. The same evidence can flow through Amazon Agent Flow and the Amazon Agent Data layer when the recovery check spans selling and advertising signals.

That distinction matters because “we lost the Buy Box” describes two different situations. An offer can be ineligible before Amazon ranks it, or it can be eligible and still lose the placement to another offer. Amazon also announced a gradual July 2026 rollout removing the seller-eligibility step, so a historical rule cannot be treated as universal across every store yet. If the offer's demand context matters, the Amazon Ads MCP can add campaign-side evidence without turning a plain chat into a live data connection.

Why not ask ChatGPT or Claude? A disconnected chat has no access to your data, no way to take action, and generic knowledge, not Amazon's. It cannot read the live offer, inspect a PRICING_HEALTH notification, or verify which eligibility rollout applies to your store. The human can paste facts into a chat, but the result is still manual and easy to misclassify. The workflow below keeps the MCP, Skill, Atlas, and your approval step connected.

Eligibility is a gate, not proof of placement

The first check is whether Amazon currently allows the offer to compete. The Atlas-grounded Featured Offer Eligibility playbook says a Professional selling account and performance-based requirements have historically been part of that gate, while Amazon's July 2026 announcement says the seller-eligibility step is being removed gradually. The agent should therefore read the current account state and store rollout status instead of returning a fixed yes/no from old rules.

{
  "asin": "B0EXAMPLE12",
  "account_type": "Professional",
  "store": "US",
  "eligibility_gate": "verify_current_policy",
  "performance_evidence": {
    "status": "read_live_account_metrics",
    "source": "Seller Central account health"
  },
  "rollout_note": "Eligibility rules are changing during the July 2026 rollout"
}

PRICING_HEALTH isolates a price-driven ineligibility

When the agent receives PRICING_HEALTH, the immediate question is not “did a competitor undercut me?” Amazon says the notification means the offer is ineligible at its current price, independent of competitor changes. Compare the offer's total price, including shipping, with the Competitive External Price and the referencePrices values such as averageSellingPrice, msrpPrice, and competitivePriceThreshold.

{
  "status": "price_ineligible",
  "notification": "PRICING_HEALTH",
  "total_price": 32.98,
  "competitive_external_price": 29.99,
  "reference_prices": {
    "averageSellingPrice": 30.49,
    "msrpPrice": 34.99,
    "competitivePriceThreshold": 29.99
  },
  "recommended_action": "review price and shipping; approval required"
}

Eligible offers still compete on price, shipping, and experience

Passing the gate does not win the placement. The Atlas playbooks describe the next stage as a competition among eligible offers; Amazon evaluates competitive price and compelling shipping options, and the detail page can show one New and one Used Featured Offer where applicable. The Get to Know the Product Detail Page playbook is the reference for how those offers appear and compete. The recovery artifact should label this state eligible_not_featured, not eligibility_failure.

# Skill: featured-offer-recovery
read:
  - offer: live price, shipping, condition, fulfillment
  - account: current eligibility and performance state
  - notifications: PRICING_HEALTH, ANY_OFFER_CHANGED
compare:
  - total_price_plus_shipping
  - competitive_external_price
  - reference_prices
  - delivery_and_availability
classify:
  - account_gate
  - price_ineligible
  - eligible_not_featured
  - insufficient_evidence

The recovery artifact should recommend, not silently reprice

The Skill turns the evidence into a small decision plan. It names the failed gate, cites the notification or account evidence, proposes the narrowest next step, and keeps approval on any price or fulfillment change. If evidence is incomplete, it returns insufficient_evidence instead of guessing. For related operational context, compare the same evidence-first pattern in the FBA inventory health guide and use Agent Crawl only when the workflow explicitly needs current external-market evidence.

{
  "asin": "B0EXAMPLE12",
  "status": "price_ineligible",
  "evidence": [
    "PRICING_HEALTH",
    "total price $32.98 > competitive threshold $29.99"
  ],
  "recommended_action": "review price and shipping options",
  "requires_approval": true,
  "monitor": ["PRICING_HEALTH", "ANY_OFFER_CHANGED"]
}

What happens next

Once the artifact identifies the gate, the team can approve one narrow change, continue monitoring, or route an account issue to Seller Central support. The Skill rechecks PRICING_HEALTH and ANY_OFFER_CHANGED after the decision so a recovered offer is measured instead of assumed.

Featured Offer recovery is a diagnosis problem before it is a pricing problem: verify the gate, read the evidence, then approve the smallest action that addresses it.

Next in the series: diagnosing a listing that is suppressed or stranded before its inventory keeps accruing storage cost.