The cycle count variance report CSV now includes a Bin Location column. If you count at the bin level, you can see which bin each discrepancy came from. You don't need to go back into the app or recount to find it.

Where to export

Use Export variance report in either place:

  • Whole count (batch): On the cycle count batch page, click Export variance report. You get one report covering every warehouse in the count. The button is available at any stage, so if some sessions are still in progress, their rows won’t have final counted quantities yet.
  • Single warehouse session: Open the session and click Export variance report. You get the report for that warehouse only. The button appears once the session is submitted for review (status pending_review or later).

The file downloads as a CSV named cycle_count_variance_report_<date-time>.csv. Session exports from the app are named cycle-count-session-<id>-variance-report.csv.

What the columns look like

In the app export, the columns appear in this order:

  1. Warehouse
  2. Bin Location
  3. Primary Vendor
  4. SKU
  5. Item
  6. Pre-Commit Quantity
  7. Pre-Commit Calculated Cost
  8. Post-Commit Quantity
  9. Post-Commit Calculated Cost
  10. Commit Quantity Variance
  11. Post-Commit Cost Variance

How to read it

  • Bin-level counts: Each row shows the bin that was counted for that line. Filter or sort by Bin Location in your spreadsheet to find which bins have discrepancies. The Bin Location value is the bin recorded on the count line.
  • Warehouse-level counts: Bin Location is blank. The column is still there, so the layout is the same for every count type.
  • Batch exports across warehouses: The Warehouse column tells you which warehouse each row belongs to. Bin Location then tells you the bin within it.

If you pull the export through the API

The External API exports (batch export and single-session export) include the same column, but Bin Location is added as the last column. The original columns stay in the same positions, so existing integrations that read columns by position keep working. Only the position is different from the app export. If you parse by column position, read Bin Location from the end. If you parse by header name, it works either way.

For how to create bin-level counts, see the related article on counting by SKU or bin location.