Amazon slaps 3.5% fuel and logistics charge on sellers because of Iran war
“Elevated costs in fuel and logistics have increased the cost of operating across the industry,” Amazon said in an emailed statement.
Amazon is slapping a 3.5% fuel and logistics surcharge on third-party sellers using its platform starting later this month amid a spike in fuel prices since the war in Iran started.
The temporary charge is effective April 17 for many of the sellers who use Amazon’s fulfillment services, the online behemoth confirmed to The Associated Press in an email Thursday.
“Elevated costs in fuel and logistics have increased the cost of operating across the industry,” Amazon said in the emailed statement.
The Seattle-based company said it has absorbed these increases so far but similar to other major carriers, when costs remain elevated, it implements temporary surcharges to partially recover these costs. It noted the charge is “meaningfully” lower than surcharges applied by other major carriers.
“We remain committed to our selling partners’ success and to maintaining broad selection and low prices for customers,” Amazon added.
Amazon’s fuel and logistics-related surcharge will apply to U.S. and Canadian sellers using its Fulfillment by Amazon option. Starting May 2, the surcharge will take effect with sellers using the Buy with Prime and Multi-Channel Fulfillment options.
Amazon joins a growing list of carriers imposing surcharges to recoup rising energy costs as the Iran war drags on.
United Parcel Service and FedEx have increased their fuel surcharges. The United States Postal Service announced last week it was imposing an 8% fuel surcharge that would apply to packages to be shipped starting April 26. The surcharge would remain in place until Jan. 17 2027, it said.
The Fortune 500 Innovation Forum will convene Fortune 500 executives, U.S. policy officials, top founders, and thought leaders to help define what’s next for the American economy, Nov. 16-17 in Detroit. Apply here.
Fortune Tech
https://fortune.com/2026/04/04/amazon-slaps-3-5-fuel-and-logistics-charge-on-sellers-because-of-iran-war/Sign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Analyst News
ciflow/trunk/179003: Thread compile_region_name through AOTAutograd cache hit path
On AOTAutograd cache hit, _compile_fx_inner is skipped entirely, so compile_region_name was never stamped onto the cached CompiledFxGraph. This caused name-dependent tests to see name=None when a prior test with the same graph shape (but no name) populated the cache first. Thread compile_region_name through fx_config so it reaches the cache hit path in wrap_post_compile. The name is excluded from cache keys since it doesn't affect compiled output — it's just a debug label. This replaces the previous workaround of disabling autograd cache for name visibility tests.





Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!