June 17th, 2026
Thank you for using LISMOA.
Here's a summary of recent updates. This release ships three major features — Reimbursement and Inventory Loss on the P/L, FBA Storage Fee viewing in LISMOA, and Amazon Ads token expiry alerts — alongside many improvements and bug fixes.
We added two dedicated columns to the P/L on the 実績 (Performance) page: 補填 (Reimbursement) — the gross refund amount from Amazon FBA — and 在庫ロス (Inventory Loss) — the purchase cost of inventory lost to damage or returns. These were previously mixed into general expenses, obscuring the true profit structure.
補填 — The gross refund amount from FBA reimbursements (warehouse damage, warehouse loss, customer returns, etc.). It's counted as-is regardless of whether it's tied to a specific order, so it matches the 補填額 (Reimbursement Amount) total on the Reimbursements page. In the Total Cost calculation, it works to reduce cost.
在庫ロス — The purchase cost of inventory lost to warehouse damage, warehouse loss, or damaged customer returns. In the Total Cost calculation, it works to increase cost.
原価 + 注文連動費 + 販促費 + 補填 + 在庫ロス + その他経費
補填, 在庫ロス, and その他経費 each carry their own sign internally (補填 reduces cost; 在庫ロス adds to cost).
Added 仕入単価 / 原価合計 / 収支 (Unit Cost / Total Cost / Profit) columns. Click a 仕入単価 cell to open a side panel where you can edit it inline, or auto-apply the product's default unit cost.
Added a confirmation status badge and filter with three states: 未確認 (Unconfirmed) / 留保中 (Pending) / 支払い実行済み (Confirmed). See at a glance where Amazon is in the refund settlement process.
Added 収支 / 確認済み件数 / 確認済み金額 / 原価合計 (Profit / Confirmed Count / Confirmed Amount / Total Cost) summary cards.
在庫ロス is aggregated on a different basis than other P/L columns:
Customer returns are counted on the return arrival date (返品日)
Warehouse damage / loss is counted on the approval date (処理の承認日)
This may differ from the order date basis used for most other columns.
FBA storage fees, previously only viewable in Amazon Seller Central, can now be browsed in LISMOA through a new tab on the Inventory page.
From the sidebar, go to フルフィルメント (Fulfillment) > 在庫 (Inventory). You'll see two tabs at the top:
現在庫 (Current Inventory)
在庫保管手数料 (Storage Fees)
Click the 在庫保管手数料 tab to see storage fee data per product (ASIN × Fulfillment Center) for the selected month.
Through column visibility settings, you can also display analytical metrics such as 在庫保管使用率, 平均日次在庫数, 30日超平均在庫, 30日超容積 (storage utilization, avg daily inventory, avg inventory over 30 days, volume over 30 days).
Use the month picker at the top right to go back to past months as needed. Defaults to the previous month (the 1st through end of last month).
By default, six cards are shown at the top: 件数, 対象商品数, 平均在庫保管手数料, 合計保管料, 平均日次在庫数, 平均日次注文数 (Count, Number of Products, Avg Storage Fee, Total Storage Fee, Avg Daily Inventory, Avg Daily Orders). These cards can be swapped out for other metrics via card settings.
Storage fee data is fetched daily for the prior month and reflected in LISMOA as soon as Amazon finalizes the data. The current month's data is not available — this is an Amazon API constraint, as month-level data is only finalized after the month ends.
Due to an Amazon Ads API policy change, ad accounts connected on or after June 30, 2026 will have their authentication token expire 365 days after connection. When the token expires, ad data fetching stops automatically. To prevent disruption, LISMOA will proactively notify you via email, in-app banner, and the Settings page so you can re-authenticate in time. When you see the banner or receive the email, head to the Settings page to re-connect the account.
Ad accounts connected before June 30, 2026 are grandfathered by Amazon and will not expire for the time being. The 365-day countdown only starts once they're re-connected on or after that date.
Added a 在庫総額 (Stock Value) column and summary card to the 現在庫 (Current Inventory) page (#589)
Bulk CSV cost updates can now be done from the SKU page (Product / SKU CSV dialogs are unified under tabs) (#701)
Reworked 在庫ロス aggregation into a two-layer model so that inventory loss from damaged customer returns is correctly reflected on the P/L (#713 +1 more)
Skipped alerts for ASINs not registered in LISMOA, reducing unnecessary notifications (#628)
Unified hover styling for in-table links and tooltips across the app (#473)
Fixed an issue where %-based columns (ACOS, ROAS, etc.) couldn't be sorted on the Ads pages (SP / SB / SD / DSP) (#727)
Fixed an issue where filter values were not saved when saving a preset (ad pages and 10 other pages) (#755 +1 more)
Fixed a 403 "Access Denied" error when creating new presets on Monitor-plan accounts (#766)
Fixed an issue where CSV bulk updates silently ignored columns with mismatched header names, leaving the update at 0 rows with no error (added immediate feedback after upload) (#652)
Fixed an issue where partial cancellations could cause incorrect cost and profit calculations (#667)
Fixed an issue where "¥Infinity" was displayed in the shipping unit cost column for order items (#770)
Fixed an issue where the Amazon expense 当月日割り (Prorate to Current Month) setting was overwritten by the next batch with 発生日 (Date of Occurrence) (#776)
Fixed an issue where the update-frequency tooltip on the dashboard incorrectly showed "every 1 hour" on the Standard plan (#660)
Fixed an issue where DB lock contention during FBA reimbursement report fetching could cause reimbursement data to be missed (#810)
If you have any questions, please feel free to contact our support team. Thank you for your continued support of LISMOA.