SellerLegend

Appearance

Troubleshooting Common COGS Issues ​

This guide addresses the most frequent problems users encounter when managing Cost of Goods Sold (COGS) data in SellerLegend.

1. Products Showing $0 COGS ​

When profit appears inflated with 100% margins, four primary causes exist:

  • No cost definition has been created for the product
  • Sales dates fall outside the defined cost period window
  • Incorrect marketplace region selected during entry
  • SKU spelling mismatches between systems

Solutions ​

  • Manually define costs for the product
  • Extend coverage periods to match sales dates
  • Verify marketplace selection
  • Confirm exact SKU matching

2. Excel Upload Failures ​

The system returns three main response states:

  • FAILED — Complete file rejection requiring template/formatting review
  • DONE_WITH_WARNINGS — Partial uploads with row-level feedback available
  • No response — Indicates empty file or header-only content

Common Mistakes ​

  • Using extra worksheet tabs (file must have only one tab)
  • Incorrect date formatting (must use YYYY-MM-DD)
  • Overlapping cost periods
  • Unknown SKUs
  • Currency code errors
  • Missing required fields like Total Paid or Units

3. Date Period Problems ​

Overlapping Cost Periods ​

Overlapping cost periods trigger validation errors. You must adjust either the start date of the new period or the end date of the previous one to eliminate overlap.

Coverage Gaps ​

Periods without defined costs result in $0 cost treatment. Filling gaps requires inserting new periods, even for single-day stretches.

Verification Steps ​

Two methods confirm proper COGS application:

  1. Navigate to Product Dashboard Order List and examine the Unit Cost column for each transaction
  2. Review Sales Per Day Per Product or P&L reports, selecting the product and date range to verify alignment

Best Practices ​

  • Download fresh template copies before bulk uploading
  • Include explicit start and end dates for each cost period
  • Use Notes and Provider fields to document audit trails
  • Maintain a master spreadsheet tracking all product cost changes

When issues persist, isolate problems by testing single products with one cost period, verify marketplace selection, and contact support with Excel files and affected SKUs.