Amazon Seller Fulfilled Prime speed requirements: July 2026 checklist

Amazon's late-May Seller Fulfilled Prime update raises the US delivery-speed bar from July 6, 2026. The reported thresholds move standard-size Prime offers to 40% of Prime customer page views showing one-day delivery, 75% showing two-day delivery, and 90% showing five-day delivery; oversize and extra-large tiers also get higher speed targets.

For US sellers, and for UK sellers running Amazon.com operations, this is not only a logistics planning issue. A weak SFP file can become a Prime badge pause, a disenrollment problem, a late-delivery performance case, or a confused appeal if the seller cannot explain dashboard data, size tier, warehouse coverage, cutoffs, and carrier capacity clearly.

Short answer: pull the SFP evidence file first

Start in the Seller Fulfilled Prime performance dashboard, not in a broad shipping-template edit. The question is whether each Prime offer can support the promise Amazon is showing customers, by size tier and by geography, without creating a delivery or customer-experience record the seller cannot defend later.

• Export or screenshot current SFP speed metrics, on-time delivery rate, valid tracking rate, cancellation rate, and any email notices before making changes.
• List each Prime SKU with ASIN, SKU, size tier, shipping template, warehouse or ship-from location, carrier service, cutoff time, weekend handling, and current Prime status.
• Separate standard-size, oversize, and extra-large products because the July 2026 thresholds are different for each tier.
• Mark single-warehouse SKUs that depend on long-zone carrier delivery, because they are most exposed to one-day and two-day page-view requirements.
• Keep Amazon.com SFP evidence separate from Amazon.co.uk seller-fulfilled evidence unless the UK account shows the same requirement in its own Seller Central.

Map size tier and delivery-promise data honestly

The update also points toward a September 2026 delivery-promise tool using shipping times, weekend availability, and cutoff times by delivery ZIP code. That makes the useful preparation more granular than a normal FBM handling-time audit.

• Confirm package length, width, height, weight, and dimensional records before relying on a size tier in the SFP file.
• Do not classify a bulky product as standard-size to make a target look easier; preserve the physical measurement record and correct the catalog or offer data if needed.
• Build a ZIP-code or carrier-zone table showing which customers can realistically see one-day, two-day, and five-day delivery from each ship-from point.
• Record weekday and weekend cutoff times separately, including carrier pickup limits and holiday exceptions.
• Keep evidence for any fulfillment partner or 3PL promise, including service-level terms, pickup schedules, tracking quality, and exception handling.

Separate SFP risk from ordinary FBM handling-time risk

A normal seller-fulfilled SKU can have a handling-time problem, a late-shipment problem, or an OTDR problem. SFP adds a separate program layer: Prime customer page views, Prime badge visibility, Amazon-handled post-order customer service, and program enrollment status.

• Use the handling-time file for ship-by promises, SKU overrides, Automated Handling Time, and Late Shipment Rate evidence.
• Use the SFP file for Prime offer eligibility, delivery-speed percentages, program notices, Prime order volume limits, and dashboard history.
• If Buy Shipping, Veeqo, or Shipping Settings Automation is part of the protection record, save the label source and template state for each affected order.
• If Amazon pauses Prime offers, preserve the notice and dashboard before re-enabling anything.
• If customers already placed Prime orders under an unrealistic promise, isolate those order IDs before writing a general performance explanation.

Decide when to pause Prime offers before the record worsens

Some sellers will be able to adjust carrier coverage, warehouse distribution, order caps, or weekend staffing before July 6. Others may need to pause selected Prime offers rather than keep a badge that the operation cannot support. That decision should be documented, not guessed during a bad metric week.

• Set a threshold for pausing Prime on SKUs that cannot meet the displayed delivery promise with current carrier coverage.
• Reduce Prime order exposure for constrained warehouses instead of letting the dashboard show avoidable misses.
• Do not reopen Prime offers during a week when staffing, inventory, carrier pickup, or weather disruption makes compliance unlikely.
• If a notice arrives, answer the specific SFP requirement first before adding broader Account Health or customer-service narrative.
• If Prime eligibility is revoked, preserve the full timeline before starting another trial or appeal path.

The practical closing test is whether the seller can explain one line clearly: this Prime SKU, this size tier, this warehouse, this ZIP-code promise, this carrier handoff, and this dashboard result. If that line is still incomplete, work from the performance issues owner context before another SFP change turns an operational gap into a harder recovery case.