1. Purpose of Import/Export
The Import/Export functionality lets merchants manage catalog data in bulk through CSV files instead of editing entries one by one in the NetWise admin. Merchants can export the current state of a catalog to a CSV, edit it offline (in Excel, Google Sheets, or any spreadsheet tool), and re-import it to apply changes at scale.
Why merchants use this feature
Setting up a new catalog quickly by editing a spreadsheet rather than clicking through every product.
Applying pricing changes across many SKUs at once.
Bulk-populating a Quick Order catalog with the products and quantities a B2B buyer should see.
Keeping an offline backup or audit copy of catalog state.
2. Price List Catalog — Export
Where the Export button is located
On the Price List Catalog page, the Export action is available from the catalog toolbar/actions area.
Steps to export a catalog
Open the Price List Catalog you want to export.
Click Export.
Confirm the export in the popup.
NetWise generates a CSV reflecting the catalog's current pricing state and downloads it.
The csv will be sent to the store owner's email.
CSV file structure (export)
The export CSV includes human-readable context columns (ProductTitle, VariantTitle) in addition to the SKU-keyed pricing fields. These title columns are for merchant readability only — on re-import, matching is done by SKU, not by title.
Product-level vs variant-level export behavior
Each row in the export represents a single variant, identified by its SKU. A product with three variants (e.g. small, medium, large) exports as three rows that share the same ProductTitle but have distinct VariantTitle and SKU values.
Handling of products without SKU
Because SKU is the matching key, a variant without a SKU cannot be reliably re-imported.
Warning messages during export
When the catalog contains products/variants without SKUs, NetWise surfaces a warning so the merchant understands those rows may not round-trip on import.
Exporting despite validation warnings
The merchant can proceed with the export even when a SKU warning is shown; the warning is informational and does not block export.
(Screenshots needed: Price List Catalog page; Export button location; Export confirmation popup; SKU warning popup; Sample exported CSV.)
3. Price List Catalog — Import
Import workflow
On the Price List Catalog page, click Import.
2.Upload a CSV in the supported format.
3.NetWise validates the file and displays any errors before the import is committed.
4.Review the validation results and proceed.
5.Valid rows are applied; invalid rows are skipped (partial import).
6.A result message confirms what was imported.
Mandatory columns
SKU is the only required column. All other columns are optional and may be left blank.
SKU requirements
Every row must contain a SKU.
The SKU must match an existing variant in the store.
A row whose SKU does not match any variant cannot be applied.
Product matching logic
NetWise matches each CSV row to a store variant by SKU (one SKU = one variant). Title columns, if present, are ignored for matching.
Validation process
The file is validated before the import is committed. The merchant sees the list of errors/warnings first, then proceeds. Problems are surfaced up front rather than discovered after a partial write.
Success and failure scenarios
Success: all rows match a SKU and contain valid data → all rows applied.
Partial: some rows are invalid (bad/missing/unmatched SKU, invalid data) → valid rows are applied, invalid rows skipped, errors reported.
Failure: file is unreadable, has no valid rows, or is in an unsupported format → nothing applied.
Partial import behavior
Partial import is allowed. Valid rows are committed and invalid rows are skipped. The relevant error messages are shown to the merchant before importing, so they know which rows will not apply.
Re-importing an exported CSV
A CSV produced by Export can be edited and re-imported. The extra export-only columns (ProductTitle, VariantTitle) are ignored on import; matching relies on SKU.
4. Quick Orders - Export Catalog
Purpose
Exporting a Quick Order catalog gives the merchant the list of products/variants currently associated with the Quick Order portal, so they can edit the set and quantities offline and re-import.
Steps to export
Open the Quick Orders module.
Click Export.
NetWise generates and downloads the Quick Orders CSV.
CSV structure (export)
The Quick Orders CSV is much simpler than Price List and contains no pricing columns:
ProductId — Shopify product ID (numeric)
VariantId — Shopify variant ID (numeric)
SKU — variant SKU
Quantity — quantity value; exports as 0 by default
Included product information
Each row carries the Shopify ProductId and VariantId, the SKU, and a Quantity. On export, Quantity is 0; the merchant sets the desired quantity before re-importing.
5. Quick Orders - Import Catalog
Import process
Open the Quick Orders module and click Import.
Upload a CSV in the Quick Orders format.
NetWise validates and shows errors before importing.
Valid rows are applied; invalid rows are skipped (partial import).
A result message confirms the outcome.
Required CSV format
Comma-separated values with the header: ProductId, VariantId, SKU, Quantity.
Product matching
Matching is done by SKU (one SKU = one variant), the same as Price List.
SKU validations
SKU is required. Rows without a SKU cannot be matched and are skipped, even if ProductId/VariantId are present.
Invalid row handling
Invalid rows (missing/unmatched SKU, invalid quantity) are skipped; valid rows are still applied (partial import).
6. CSV Format Specification
Price List Catalog - Import columns
Required column: SKU only.
SKU (required) - matching key; must match an existing variant SKU. Example: SKU-001
CustomPrice (optional) - merchant-entered absolute custom price for the SKU; overrides the AdjustedPrice discount when set. Example: 22
AdjustedPrice (optional) - the catalog's global discount applied to the SKU (e.g. 20% off the base price); used when no CustomPrice is set. Example: 20
Increment (optional) - step value between MinimumQuantity and MaximumQuantity. Example: 5
MinimumQuantity (optional) - minimum order quantity for the SKU. Example: 5
MaximumQuantity (optional) - maximum order quantity for the SKU. Example: 200
Quantity Break 1 (optional) - quantity threshold for the first volume-pricing tier. Example: 20
Price Break 1 (optional) - price applied at/above Quantity Break 1. Example: 47.99
Quantity Break 2 (optional) - quantity threshold for the second volume-pricing tier. Example: 100
Price Break 2 (optional) - price applied at/above Quantity Break 2. Example: 44.99
Pricing precedence: if a row has both a CustomPrice and the catalog's AdjustedPrice discount, CustomPrice wins for that SKU.
Price List Catalog - Export columns
ProductTitle (export only, ignored on import) - product display name. Example: The Collection Snow...
VariantTitle (export only, ignored on import) - variant display name. Example: small
SKU (required) - matching key. Example: SKU-003
AdjustedPrice (optional) - global catalog discount for the SKU. Example: 524.97
Increment (optional) - step between min and max quantity.
MinimumQuantity (optional) - minimum order quantity.
MaximumQuantity (optional) - maximum order quantity.
7. Validation Rules
For each rule: trigger condition → expected behavior.
Missing SKU - a row has no value in the SKU column → row is skipped; reported before import (partial import).
Invalid SKU - SKU value is malformed/empty after trim → row skipped; reported.
Duplicate SKU - same SKU appears on more than one row → not specified.
Missing mandatory field - required column (SKU) absent from a row → row skipped; reported.
Invalid data type - non-numeric value in a numeric field (price/quantity) → not specified.
Empty row - a row has no usable data → row skipped.
Archived product - SKU maps to an archived product → not specified.
Draft product - SKU maps to a draft product → not specified.
Unlisted product - SKU maps to a product not listed in the catalog/channel → not specified.
Product not found - SKU does not match any variant in the store → row skipped; reported.
Variant not found - SKU matches a product but not a specific variant → row skipped; reported.
8. Error Messages
Missing SKU warning - Add a SKU to the affected row(s) and re-import, or proceed (those rows are skipped).
Invalid CSV - Fix the file structure (header row, delimiter) and re-upload.
Import failed - Review the reported errors and re-import.
Unsupported file - Upload a .csv file in the supported format.
Empty file - Add at least one valid data row and re-upload.
Partial import - Review skipped rows; correct and re-import if needed.