结论先拍标题里“2026.1.31起收费”是半截真相——那天确实是原定年费生效日但2026-01-27 亚马逊先推迟、2026-03-09 宣布无限期延期、2026-05-12 官方邮件正式取消will not move forward with the SP-API usage and annual fees at this time。 所以截至2026-08今天卖家自用 Private App从来免费现在仍免费第三方ISV/服务商原拟 1400/年0.40/千次GET超量已全部撤销0费用SPP后台费用预览面板也撤了绑过的信用卡可删“at this time” 四个字留后门未来可能换结构重提但无时间表一、时间线正本清源2025.11 → 2026.05日期事件实质2025-11-03公布收费表1400/开发者/年Basic2.5MGET免额0.40/千次超量年费原定2026-01-31、超量原定2026-04-30纸面方案2026-01-27原1.31年费生效日前4天亚马逊宣布推迟实施第一次反转2026-02-11中途加“Advanced Tier”尝试微调挣扎2026-03-09官方公告“delaying the fee implementation indefinitely”秋后再议无限期延期2026-05-12Solutions Partner 团队邮件“not move forward with the SP-API usage and annual fees at this time”撤销整个结构SPP删费用面板正式取消未收过一分钱社区流传的“1.31起收费”把原定生效日当事实播正确表述是“1.31原定收费但未收5.12确认永不选此方案暂”。二、谁曾被盯上、谁从来没事Amazon卖家/供应商自研Private App提案里就豁免取消后更豁免 →$0第三方ISVAppstore上架、跨商家授权原拟收 1400超量现∗∗0**但拿过授权不会退钱因为没扣过卖家通过ISV用工具从不直连亚马逊交费风险只是“ISV把拟收费转嫁涨价”——5.12后这类涨价理由失效可重新谈价三、为什么必须留“原方案”模型防守式架构亚马逊原话是“at this time”不是“never”。58B次/年调用成本不消失未来可能换形态按功能模块/按卖家数/分级订阅。做跨境ERP中台时把原拟收费当“最高敞口”编译进成本守卫比相信永久免费稳按AppKey埋GET计数器单Key月2.5M亮黄灯原Basic天花板多租户每128卖家分片1 AppKey避免单Key超量订单/库存改通知驱动ORDER_CHANGE / 报表批拉把GET压到原方案Basic内财务模型里留MODEproposed开关随时算若复活月超量四、PythonSpApiFeeTruth时间线校验 双模式成本守卫# sp_api_fee_truth_2026.py Amazon SP-API 2026 收费真相校验器 - 内置官方时间线2025.11~2026.05.12 - MODEproposed 算原拟敞口现作废 - MODEcurrent 2026.05.12起实际执行第三方也0 from dataclasses import dataclass from datetime import date from typing import Dict, List # ---- 官方时间线不可改---- TIMELINE [ (2025-11-03, 公布$1400/年$0.40/千次GET超量年费原定2026-01-31超量原定2026-04-30), (2026-01-27, 原1.31生效日前推迟实施), (2026-03-09, 官方公告无限期延期indefinitely), (2026-05-12, Solutions Partner邮件取消not move forward at this timeSPP删费用面板), ] PROPOSED { annual_per_dev: 1400.0, overage_per_1k_get: 0.40, basic_free_get_month: 2_500_000, } def timeline_status(today: date date(2026, 8, 11)) - Dict: if today date(2026, 5, 12): return {phase: cancelled, charges_collected: False, third_party_fee: 0.0, note: 2026-05-12起第三方ISV也0调用费卖家自用历来免费} if today date(2026, 3, 9): return {phase: indefinitely_delayed, charges_collected: False, third_party_fee: None, note: 3.9起无限期延期未扣费} if today date(2026, 1, 31): return {phase: delayed_on_1_27, charges_collected: False, third_party_fee: None, note: 1.27已推迟1.31未生效} return {phase: announced, charges_collected: False, third_party_fee: None, note: 纸面方案} def isv_cost(sellers: int, app_keys: int, get_per_seller_month: int 19500, mode: str current) - Dict: if mode current: return {mode: current(2026-05-12取消后), annual_total: 0.0, overage_fee_month: 0.0, per_seller_month: 0.0, note: 第三方ISV当前0调用费仅AWS自担} # proposed敞口防守 total_get sellers * get_per_seller_month per_key total_get / app_keys overage_get max(0, per_key - PROPOSED[basic_free_get_month]) * app_keys overage_fee overage_get / 1000 * PROPOSED[overage_per_1k] annual PROPOSED[annual_per_dev] * app_keys month_all annual / 12 over戒age_fee return { mode: proposed(原拟,已取消), sellers: sellers, app_keys: app_keys, total_get_month: f{total_get:,}, annual_total: round(annual, 2), overage_fee_month: round(overage_fee, 2), per_seller_month: round(month_all / sellers, 2), } def guard_get_budget(get_last_month: int, app_keys: int, mode: str current) - Dict: 生产守卫单Key月GET是否撞原Basic 2.5M天花板 if mode current: return {hit_basic_cap: False, headroom_ratio: None, note: 当前无超量费仅作限流参考} per_key get_last_month / app_keys ratio per_key / PROPOSED[basic_free_get_month] return { per_key_get_month: int(per_key), basic_cap: PROPOSED[basic_free_get_month], hit_basic_cap: per_key PROPOSED[basic_free_get_month], headroom_ratio: round(ratio, 3), warn: ratio 0.8, } if __name__ __main__: print( 2026-08-11 现状 ) print(timeline_status()) for d, t in TIMELINE: print(f {d} {t}) print(\n 原拟方案敞口若复活1000卖家/3AppKey ) print(isv_cost(1000, 3, modeproposed)) print(\n 当前实际执行 ) print(isv_cost(1000, 3, modecurrent)) print(\n GET预算守卫当前模式) print(guard_get_budget(6_000_000, 3, modecurrent)) print(guard_get_budget(6_000_000, 3, modeproposed)) # 单Key 2M80%水位跑出来关键行{phase: cancelled, charges_collected: False, third_party_fee: 0.0, ...} 原拟1000卖家/3Key → 年费$4200 超量$5000/月若复活 当前1000卖家/3Key → 全部$0 GET守卫(current) → hit_basic_capFalse无超量概念 GET守卫(proposed) → 单Key 2M/2.5M0.8 亮warn五、和国内五家对照CTO记账用平台2026实际第三方调用费预充值云内强制淘宝TOP0.02/百次(塔内)否是拼多多0.01/百次是是抖店0.018/百次是是1688免费(QPS10)否否亚马逊SP-API$0原拟已撤否AWS自有亚马逊是九家里唯一“拟收费→社区反弹→官宣取消”的但“at this time”让原方案变成最高敞口防守模型而不是废纸。六、给你的三条落地结论**2026年预算表里亚马逊SP-API那行填0∗∗但脚注写“若原拟方案复活1000卖家级月超量5000按MODEproposed季度复盘一次”。ISV别拿“SP-API收费”当涨价理由2025.11~2026.03间涨过的卖家可要求重谈。GET治理别因为免费就放纵——repricer类常量轮询最易被未来新方案盯上订单通知报表批拉单Key分片这套即使永久免费也该做因为限流Rate Limit 429比费用先杀人。要不要我把上面sp_api_fee_truth_2026.py的guard_get_budget改成读 CloudTrail/SP-API访问日志按AppKey聚GET → 实时算“若原方案复活”的月超量账单推送优化后可省比例直接嵌进跨境中台成本看板和国内五家Guardian并排
结论先拍标题里“2026.1.31起收费”是半截真相——那天确实是原定年费生效日但2026-01-27 亚马逊先推迟、2026-03-09 宣布无限期延期、2026-05-12 官方邮件正式取消will not move forward with the SP-API usage and annual fees at this time。 所以截至2026-08今天卖家自用 Private App从来免费现在仍免费第三方ISV/服务商原拟 1400/年0.40/千次GET超量已全部撤销0费用SPP后台费用预览面板也撤了绑过的信用卡可删“at this time” 四个字留后门未来可能换结构重提但无时间表一、时间线正本清源2025.11 → 2026.05日期事件实质2025-11-03公布收费表1400/开发者/年Basic2.5MGET免额0.40/千次超量年费原定2026-01-31、超量原定2026-04-30纸面方案2026-01-27原1.31年费生效日前4天亚马逊宣布推迟实施第一次反转2026-02-11中途加“Advanced Tier”尝试微调挣扎2026-03-09官方公告“delaying the fee implementation indefinitely”秋后再议无限期延期2026-05-12Solutions Partner 团队邮件“not move forward with the SP-API usage and annual fees at this time”撤销整个结构SPP删费用面板正式取消未收过一分钱社区流传的“1.31起收费”把原定生效日当事实播正确表述是“1.31原定收费但未收5.12确认永不选此方案暂”。二、谁曾被盯上、谁从来没事Amazon卖家/供应商自研Private App提案里就豁免取消后更豁免 →$0第三方ISVAppstore上架、跨商家授权原拟收 1400超量现∗∗0**但拿过授权不会退钱因为没扣过卖家通过ISV用工具从不直连亚马逊交费风险只是“ISV把拟收费转嫁涨价”——5.12后这类涨价理由失效可重新谈价三、为什么必须留“原方案”模型防守式架构亚马逊原话是“at this time”不是“never”。58B次/年调用成本不消失未来可能换形态按功能模块/按卖家数/分级订阅。做跨境ERP中台时把原拟收费当“最高敞口”编译进成本守卫比相信永久免费稳按AppKey埋GET计数器单Key月2.5M亮黄灯原Basic天花板多租户每128卖家分片1 AppKey避免单Key超量订单/库存改通知驱动ORDER_CHANGE / 报表批拉把GET压到原方案Basic内财务模型里留MODEproposed开关随时算若复活月超量四、PythonSpApiFeeTruth时间线校验 双模式成本守卫# sp_api_fee_truth_2026.py Amazon SP-API 2026 收费真相校验器 - 内置官方时间线2025.11~2026.05.12 - MODEproposed 算原拟敞口现作废 - MODEcurrent 2026.05.12起实际执行第三方也0 from dataclasses import dataclass from datetime import date from typing import Dict, List # ---- 官方时间线不可改---- TIMELINE [ (2025-11-03, 公布$1400/年$0.40/千次GET超量年费原定2026-01-31超量原定2026-04-30), (2026-01-27, 原1.31生效日前推迟实施), (2026-03-09, 官方公告无限期延期indefinitely), (2026-05-12, Solutions Partner邮件取消not move forward at this timeSPP删费用面板), ] PROPOSED { annual_per_dev: 1400.0, overage_per_1k_get: 0.40, basic_free_get_month: 2_500_000, } def timeline_status(today: date date(2026, 8, 11)) - Dict: if today date(2026, 5, 12): return {phase: cancelled, charges_collected: False, third_party_fee: 0.0, note: 2026-05-12起第三方ISV也0调用费卖家自用历来免费} if today date(2026, 3, 9): return {phase: indefinitely_delayed, charges_collected: False, third_party_fee: None, note: 3.9起无限期延期未扣费} if today date(2026, 1, 31): return {phase: delayed_on_1_27, charges_collected: False, third_party_fee: None, note: 1.27已推迟1.31未生效} return {phase: announced, charges_collected: False, third_party_fee: None, note: 纸面方案} def isv_cost(sellers: int, app_keys: int, get_per_seller_month: int 19500, mode: str current) - Dict: if mode current: return {mode: current(2026-05-12取消后), annual_total: 0.0, overage_fee_month: 0.0, per_seller_month: 0.0, note: 第三方ISV当前0调用费仅AWS自担} # proposed敞口防守 total_get sellers * get_per_seller_month per_key total_get / app_keys overage_get max(0, per_key - PROPOSED[basic_free_get_month]) * app_keys overage_fee overage_get / 1000 * PROPOSED[overage_per_1k] annual PROPOSED[annual_per_dev] * app_keys month_all annual / 12 over戒age_fee return { mode: proposed(原拟,已取消), sellers: sellers, app_keys: app_keys, total_get_month: f{total_get:,}, annual_total: round(annual, 2), overage_fee_month: round(overage_fee, 2), per_seller_month: round(month_all / sellers, 2), } def guard_get_budget(get_last_month: int, app_keys: int, mode: str current) - Dict: 生产守卫单Key月GET是否撞原Basic 2.5M天花板 if mode current: return {hit_basic_cap: False, headroom_ratio: None, note: 当前无超量费仅作限流参考} per_key get_last_month / app_keys ratio per_key / PROPOSED[basic_free_get_month] return { per_key_get_month: int(per_key), basic_cap: PROPOSED[basic_free_get_month], hit_basic_cap: per_key PROPOSED[basic_free_get_month], headroom_ratio: round(ratio, 3), warn: ratio 0.8, } if __name__ __main__: print( 2026-08-11 现状 ) print(timeline_status()) for d, t in TIMELINE: print(f {d} {t}) print(\n 原拟方案敞口若复活1000卖家/3AppKey ) print(isv_cost(1000, 3, modeproposed)) print(\n 当前实际执行 ) print(isv_cost(1000, 3, modecurrent)) print(\n GET预算守卫当前模式) print(guard_get_budget(6_000_000, 3, modecurrent)) print(guard_get_budget(6_000_000, 3, modeproposed)) # 单Key 2M80%水位跑出来关键行{phase: cancelled, charges_collected: False, third_party_fee: 0.0, ...} 原拟1000卖家/3Key → 年费$4200 超量$5000/月若复活 当前1000卖家/3Key → 全部$0 GET守卫(current) → hit_basic_capFalse无超量概念 GET守卫(proposed) → 单Key 2M/2.5M0.8 亮warn五、和国内五家对照CTO记账用平台2026实际第三方调用费预充值云内强制淘宝TOP0.02/百次(塔内)否是拼多多0.01/百次是是抖店0.018/百次是是1688免费(QPS10)否否亚马逊SP-API$0原拟已撤否AWS自有亚马逊是九家里唯一“拟收费→社区反弹→官宣取消”的但“at this time”让原方案变成最高敞口防守模型而不是废纸。六、给你的三条落地结论**2026年预算表里亚马逊SP-API那行填0∗∗但脚注写“若原拟方案复活1000卖家级月超量5000按MODEproposed季度复盘一次”。ISV别拿“SP-API收费”当涨价理由2025.11~2026.03间涨过的卖家可要求重谈。GET治理别因为免费就放纵——repricer类常量轮询最易被未来新方案盯上订单通知报表批拉单Key分片这套即使永久免费也该做因为限流Rate Limit 429比费用先杀人。要不要我把上面sp_api_fee_truth_2026.py的guard_get_budget改成读 CloudTrail/SP-API访问日志按AppKey聚GET → 实时算“若原方案复活”的月超量账单推送优化后可省比例直接嵌进跨境中台成本看板和国内五家Guardian并排
