What the sales import does
A sales import adds destination quantities to your workspace so your team can reconcile them against product and packaging records. You choose a CSV or Excel workbook, map its columns, review the preview and row errors, then confirm the import. PackageReports keeps the original file with the import for later review.
Prepare the spreadsheet
Use one row for each product SKU, destination, and transaction date. Include five required values: SKU (the identifier your product catalogue uses), quantity (number of sellable units, not packaging grams or sales dollars), country (an uppercase two-letter code such as CA or US), region (the destination code, such as ON or QC), and date in YYYY-MM-DD format. Keep the original export unchanged and check that it covers the reporting period you intend to review.
For a Canada-wide report, include Canadian sales from every province and territory in the same source dataset. Keep each row's actual destination region; the national calculation uses Canadian rows together and retains their regions in the underlying records. You do not need a separate provincial form for this Canada-wide workflow.
Upload and map columns
- Sign in and open Imports in your workspace.
- Under Start an import, choose Sales ledger, select your CSV or XLSX file, and choose Upload & preview. The page displays the current file-size limit.
- Open the new import. The preview shows up to the first 100 source rows.
- Under Map your columns, match SKU, quantity, country, region, and date to the corresponding spreadsheet headers. The header names can differ; choose the column that contains each value. If the file has a transaction type column, map it to Transaction type (optional).
- Choose Validate mapping. The import becomes ready only after every row passes its required checks.
Fix row errors before committing
The Row errors table names the source row, field, and what to check. Common causes are a blank SKU, a quantity that is not a number, a country value that is not a two-letter uppercase code, an invalid region code, or a missing or incorrectly formatted date. Correct the source spreadsheet and upload it again, or adjust the column mapping if the values are in a different column. The import screen maps columns; it does not edit individual source rows.
Check your file for duplicate sales rows before confirming. The import validates required values but does not decide whether two similar rows are duplicates. Confirming commits the valid rows to your Sales ledger. Importing the same file again is detected by its file fingerprint rather than adding a second copy.
Reconcile products and review the result
A row can import even when its SKU does not yet match a product in your catalogue. In the Sales ledger, look for Needs product match and link that source SKU to the correct product before calculating. A calculation also depends on an approved packaging specification for the product and the selected reporting period and location. A sales import by itself does not complete those checks or submit a government report.
Sales are kept in the destination country and region recorded in each row. For Canada, provincial and territorial codes describe where the sale went; they do not create separate Canadian reporting forms. If you map a transaction type, use the uppercase values SALE, RETURN, or ADJUSTMENT. A return is subtracted using the absolute value of its quantity; an adjustment uses the sign entered in the source. Review adjustments and reconciliation totals with your team before relying on an output.
Read the sales reconciliation guide for a worked review. When you are ready, sign in to your workspace and open Imports.
