Finance Tools

When to use

Read Amazon’s stored catalog-wide fee estimates for existing SKUs, including referral and fulfillment components, prices, dimensions, weight, size tier, fulfillment channel, and currency.

Tips

• Use view="current" for the latest report-backed fee facts already stored for the seller’s catalog.
• Use view="changes" to return added, removed, or changed product rows with changed_fields and numeric fee deltas.
• Read source_contract and source_report in the response; both identify this as the all-SKU estimated-fees report snapshot.

Watch out

• This is not the live Product Fees API. It cannot estimate a caller-supplied candidate price.
• Amazon report columns labeled future fees can arrive as raw strings; the response preserves those source values instead of guessing a numeric contract.

Related tools

When to use

Use this for financial-event fee components, order-level fee exports, or ASIN economics keyed to when Amazon posted the financial event. Use get_payment_transactions for pre-settlement Transaction View rows and get_settlement_economics for finalized settlement report rows.

Tips

• Use view="fee_breakdown" plus order_id for raw fee component rows on a known order.
• Use view="fee_breakdown" with grain="order_item" for bulk weekly order-level exports that need order_id, ASIN, SKU, revenue, fees, tax, and net by posted_date.
• Use view="fee_breakdown" with grain="raw_component" when the agent needs every component row instead of pivoted fee columns.
• Use view="fee_breakdown" without grain or with grain="asin" for the existing ASIN fee pivots across the posted_date range.
• Use view="profitability" for ASIN-level shipment_principal, refund_principal, refund_net, revenue, fees, tax, net profit, units, and the date-basis disclosures.

Watch out

• Profitability shipment_principal, refund_principal, refund_net, revenue, fees, tax, and net_profit use financial-event posted_date, not order date. refund fields preserve Amazon’s signs; revenue remains shipment_principal + refund_principal. order_item_revenue uses purchase_date, so the two cutoffs can represent different orders.
• Profitability includes ASIN-attributed Shipment/Refund events only. Account-level Adjustment/ServiceFee events are excluded from ASIN profitability but remain available with view="fee_breakdown" and grain="raw_component".
• Profitability excludes all advertising spend, FBA storage fees, inbound freight, and COGS. Read excluded_costs for the machine-readable list.
• Money is scoped to the marketplace currency by default. Amazon posts non-home-currency rows (CAD/MXN) under the same marketplace, so set include_all_currencies=true only if you handle mixed currencies yourself.

Related tools

When to use

Inspect ASIN-level profitability signals across posted financial-event net, order-date Business Reports, SP/SD product ad spend, returns, and reimbursements. Set include_sponsored_brands when account-level SB campaign spend must be visible alongside the ASIN review.

Tips

• Sorts by issue score so negative contribution, ad drag, high fees, return pressure, and reimbursement reliance surface first.
• Use review_focus to isolate one issue type when you already know what you are investigating.
• Pair with get_financial_events, get_returns, and get_tacos to inspect the highest-risk ASINs in detail.
• Set include_sponsored_brands=true when SB campaign spend matters to the account-level picture; read summary.account_level_costs.sponsored_brands once for the selected date window.

Watch out

• Contribution is ASIN-attributed Shipment/Refund financial-event marketplace net + FBA reimbursements - SP/SD product ad spend.
• Financial-event revenue, fees, tax, and marketplace net use posted_date. Business Reports use their order-date basis; ads, returns, and reimbursements use their own source dates. The same window can therefore contain different transaction cohorts near its cutoffs.
• Account-level Adjustment/ServiceFee financial events are excluded because they cannot be deterministically attributed to an ASIN.
• Sponsored Brands spend is excluded by default. With include_sponsored_brands=true, it appears once as a separate unallocated account-level cost and is never assigned or repeated across ASINs. DSP ad spend, FBA storage fees, inbound freight, and COGS remain excluded.
• Money is scoped to the marketplace currency by default (financial events, reimbursements, and ad spend); set include_all_currencies=true to include all currencies.

Related tools

When to use

Analyze finalized settlement-report data by effective-date window for per-ASIN economics, storage fees, promotions, or raw report rows. For exact finalized disbursement reconciliation, use get_payment_transactions with financial_event_group_id and transaction_status="RELEASED".

Tips

• Use summary mode to read order_item_price, refund_item_price, and refund_net separately; revenue keeps the existing all-ItemPrice definition.
• Use detail mode with amount_type or amount_description filters to inspect specific rows present in the V2 settlement report.
• Use summary mode fields fba_per_unit_fulfillment_fee, fba_per_unit_fulfillment_fee_quantity_purchased, and fba_per_unit_fulfillment_fee_per_unit for fulfillment-fee audits by ASIN. The per-unit value is signed like the settlement fee amount.
• commission is Amazon's referral fee (amount_description Commission); item_fees is the full item-level fee bucket that contains it. The fee fields (commission, item_fees, fba_fee, fba_per_unit_fulfillment_fee) overlap and are not additive, so use net or total_fees for period totals.
• Storage fees appear in the summary mode, unlike get_financial_events which only has transaction-level fees.
• Summary mode also returns unattributed_fees: account-level fees present in the V2 settlement report that carry no SKU and are excluded from the per-ASIN pivot. These complete the selected report-row window, not an exact disbursement statement.
• For recent refund, deferred, or payment rows before settlement close, use get_payment_transactions instead.

Watch out

• Settlement refund fields preserve Amazon’s signs. refund_item_price contains Refund transaction ItemPrice rows; refund_net contains every attributed Refund settlement row.
• Settlement reports can lag live Payments transactions until Amazon finalizes the settlement period.
• A settlement_effective_date window can contain multiple settlement IDs, and transaction families present in Payments may be absent from the V2 settlement report. Do not treat this tool as an exact disbursement statement.
• Settlement rows carry no reliable per-row currency, so marketplace_currency is asserted from the marketplace and amounts are not currency-filtered. For a North America unified account, settlement amounts may combine currencies; use get_financial_events (marketplace currency by default) to isolate one.

Related tools

When to use

Use financial_event_group_id with transaction_status="RELEASED" for exact finalized disbursement-group reconciliation. Use the date-window mode for recent payment, refund, or deferred rows before settlement reports finalize, or order_id for one order.

Tips

• Use transaction_type="Refund" for recent refund rows that may not appear in settlement reports yet.
• Use transaction_status to separate DEFERRED, RELEASED, and DEFERRED_RELEASED payment transactions.
• For a finalized disbursement, pass financial_event_group_id with transaction_status="RELEASED" and continue with page_token until pagination.has_more is false.
• Set detail=true when you need transaction identifiers, related order/refund/settlement/financial-event-group IDs, or item-level ASIN/SKU context.

Watch out

• Amazon notes financial events might not include orders from the last 48 hours.
• postedBefore is capped to more than three minutes before request time when the selected end date reaches the current time.
• transaction_type is filtered locally because listTransactions does not expose a transactionType query parameter.
• order_id and financial_event_group_id are mutually exclusive. Date filters are not sent in either related-identifier mode.
• The tool fails closed if the account has no configured marketplace or if a supplied marketplace_id differs. There is no US/default fallback.

Related tools