π How SellerLegend Handles Refunds (And Why It Works This Way)
π‘ TL;DR
SellerLegend applies refunds on the date the original order was placed or shipped, not the date the refund was received. This ensures that revenue, fees, and COGS are correctly reversed in the period where the sale occurred. Refunds are reflected across dashboards and the Orders screen β but not in the Profit and Loss report.
π Refund Count Adjustment
If you receive a refund today, you might expect to see it in todayβs dashboard β but you wonβt. Thatβs because SellerLegend does not count refunds on the day they are received.
Instead, the refund count is assigned to the original order date. For example:
-
A customer places an order on March 1
-
The order is refunded on March 15
-
The refund count will appear on March 1, not March 15
π This means tiles like Today and Yesterday wonβt show refunds unless the refunded order was originally placed during that window, which is rare.
π° Revenue, Fees, and COGS Adjustments
SellerLegend adjusts all financial aspects of a refund on the original order date:
-
Revenue: Reduced on the day the order was placed/shipped
-
Fees: Also adjusted on the order date β though not all fees may be refunded
-
COGS (Cost of Goods Sold): Partially returned to your profit, depending on restockability
π Refunds do not affect todayβs revenue, fee, or COGS numbers. They only adjust the financial metrics on the original order date.
π COGS Restock Assumptions
Not all refunded units are returned in sellable condition. Based on historical analysis, we have determined that 68% of refunded units are returned to inventory. Therefore, on refunds, we return the COGS amount of the unit to your profit
π§Ύ Refund Fees and Net Profit Impact
Even when a refund is issued, Amazon may:
-
Not refund all original fees (e.g., fulfillment or referral fees)
-
Charge a Refund Administration Fee for some categories
As a result, a refunded order can still generate a net negative profit, not zero. This is intentional and accurately reflects the cost of doing business on Amazon.
π Dashboards and Reporting
Refunds are:
-
β Reflected in all dashboards
-
β Visible in the Orders screen
-
π« Not included in the Profit and Loss report
Refunds are excluded from the P&L report to keep it focused on realized operational performance. This avoids distorting profitability from post-sale events like returns.
π¦ Why This Behavior Changed
Previously, SellerLegend counted refunded units on the day the refund was received. However:
-
This created confusion β users saw refunded units but no revenue change for that day
-
Revenue and profit changes were still applied to the order date, leading to mismatches
To resolve this and align all refund effects, SellerLegend now:
-
Records refunded units on the order date
-
Adjusts revenue, fees, and COGS on the order date
This approach ensures consistency, clarity, and accounting accuracy across the platform.
π Refund Handling at a Glance
Event | Handled On | Notes |
---|---|---|
Refund received | β Not today | No refund count or revenue impact today |
Refund count updated | β Order date | Shown in historical order tile |
Revenue/fees adjusted | β Order date | Reflects original financials |
COGS reversed (68% assumption) | β Order date | Based on restock probability |
Refund shown in Orders screen | β Yes | Marked clearly |
Refund shown in P&L report | π« No | Excluded for consistency |