Importing from CSV
Bulk-load your items, contacts, and transactions from a spreadsheet
How CSV import works in Ardent Seller
Most list pages — inventory (Ingredients, Packaging, Components, Products, and the rest), Vendors, Customers, Locations, Transactions, Recipes, and several Settings registries — have their own Import from CSV action. Import happens right in your browser: you select your file, map its columns to Ardent Seller fields, and confirm. Ardent Seller validates every row and creates the records — nothing saves until the whole file passes. This guide walks through the inventory import end to end; for the column reference of every other import (vendors, customers, transactions, recipes, and more), see the complete import reference.
Where to find Import & Template
On any importable list, open the actions menu — the ⋯ ("more") button in the table's action bar — and choose Import from CSV. The same menu offers a Download Template option.
- Download Template — gives you a CSV containing the exact header row for that section. On a new account the template has the headers only (no data rows); fill in one row per record beneath them.
- Import from CSV — pick your filled-in file, map its columns to Ardent Seller fields, and confirm. Ardent Seller checks every row and reports what it finds before your data changes.
For example, go to Source → Ingredients, open the ⋯ menu, download the template, add your rows, and import it back.
Map your CSV columns to Ardent Seller fields
After you select a file (it must be a .csv and no larger than 10 MB), Ardent Seller shows a mapping step: each Ardent Seller field gets a dropdown where you pick the CSV column that contains it, next to a preview of the first five rows of your file. Fields marked with * are required and must be mapped before you can continue; anything you don't need can stay on — Ignore —.
- Suggestions pre-fill automatically — when your headers match the template (or a close variant like "product name", "qty", or a small typo), the mapping is filled in for you. Starting from the downloaded template is still the easiest path, because every field pre-fills and you only review.
- One CSV column per field — the same column cannot feed two different fields. If it does, the importer reports it and you adjust the mapping.
- Continue validates the file — after mapping, the importer checks every row and shows either "N records to import" or a row-by-row error list. Nothing is saved until every row passes.
- Read the grey notes too — errors in red stop the import; notes in grey do not. Dates get a note when they look wrong rather than invalid: rows more than ten years old, rows dated in the future, or a whole file of separate orders sharing one date, which usually means the date column was filled down by mistake. These import exactly as written, and your reports by month, vendor price history and tax year are all built on them, so it is worth a look before you continue.
- Dates can be day-first or month-first — the transaction and recipe imports read 2026-09-23, 9/23/2026, 23/09/2026, 23.09.2026 and Sep 23, 2026. They work out from the whole file whether your dates put the day or the month first: any day after the 12th settles it. If every date in the file could be read either way, such as 05/09/2026, they are read month first and a grey note says so. Writing dates as YYYY-MM-DD avoids the question entirely.
Inventory column reference
These are the fields the inventory import accepts — the downloaded template has one column per field. Only Name is required and must be mapped to a column. A blank SKU is generated from the name, a blank Category takes the category of the page you imported from (Ingredients, Products, and so on), a blank State becomes active, and a blank Unit becomes "unit" (each). Every other field is optional and can be left unmapped or blank. Whatever was filled in for you is listed in the dialog before you confirm.
| Column | Required | Description | Valid values / example |
|---|---|---|---|
Name | req | The item name. | e.g. Vanilla Extract |
SKU | opt | A unique identifier for the item. Leave it blank and one is generated from the name (a number is added if two names collide). | e.g. VAN-001 |
Category | opt | The item type. Blank rows take the category of the page you imported from; on the all-inventory page it must be filled in. For a component, write "subassembly", "component" or "components"; an export writes "subassembly". "finished" (or "finished good") is still accepted: Finished Goods were retired in November 2026, so a row with a Price or VariantPrice above 0 imports as a product (keeping its ProductType), any other row imports as a component with no product type, and the import summary says which. | raw, food, subassembly (or component), packaging, finished (a priced row imports as a product, otherwise a component), mro, equipment, labor, product, service |
UsedIn | opt | Ingredient or material rows only. Enter "Food" for an edible ingredient; leave it blank for everything else. A row that names a food in the Food column is tagged Food even without it. | Food, or blank |
ProductType | opt | Product rows only. Blank leaves the type Not set; Ardent Seller sets it when you save a recipe or production run with ingredients for the item (Food if the recipe uses a Food ingredient, otherwise Other). The import summary counts these products (the variant rows of one item count once), for example "3 products have no product type yet. On Products, filter the Product type column to Not set, select them and use Product type to set Food or Other. Then clear the filter." | Food, Other, or blank |
State | opt | The item lifecycle state. Blank means active. | draft, active, archived |
Unit | opt | The tracking unit. Full names and common abbreviations both work ("gram" or "g", "ounce" or "oz", "pound" or "lbs", "each"). Blank means "unit" (each). | unit, gram, kilogram, milligram, ounce, pound, milliliter, liter, teaspoon, tablespoon, cup, inch, foot, meter, hour |
Description | opt | Optional free-text notes about the item. | e.g. Pure Madagascar bourbon |
BinLocation | opt | Where the item is physically stored. | e.g. Shelf A3 |
DefaultEntity | opt | The Supplier on the item: must exactly match the name of an active vendor, or be left blank. A column headed Supplier, or Default Vendor as in older files, is read as this one. | e.g. Valley Flour Co. |
Food | opt | The name of the entry in the built-in food list to link the item to, matched exactly as it appears there (an export writes it for you). Required only on rows whose Category is the older "food". A row tagged Food without it still imports, tagged Food with no food link, and the import shows a notice so you can choose the closest food afterwards. When the name matches, the item also gets that food's allergens, the same list the item sheet fills in when you link a food. | the exact name of an entry in the food list |
Price | opt | The item's SELLING price (not purchase cost). Leave blank for pure raw materials. | numeric, e.g. 6.00 |
Quantity | opt | Opening on-hand stock, in the item's Unit. Pairs with UnitCost to set opening stock and average cost. Cannot be negative. | numeric, 0 or more, e.g. 100 |
UnitCost | opt | Purchase cost per unit in your account currency. Pairs with Quantity for the opening balance. | numeric, 0 or more, e.g. 3.50 |
Allergens | opt | Comma-separated list of allergens present in the item. These are added to the allergens of the food named in the Food column, if it matches. With no allergens here and no matched food, a food item imports with its allergens Not set (never as allergen-free) until you set them or confirm it contains none in the app. | milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, sesame |
MinimumOrderQuantity | opt | The smallest quantity you can order for this item. | numeric, e.g. 12 |
OrderIncrement | opt | The step size in which the item is ordered. | numeric, e.g. 6 |
LeadTimeDaysOverride | opt | Overrides the default lead time, in days. | numeric, e.g. 14 |
ReplenishPoint | opt | Low-stock reorder trigger, in the item's Unit. On-hand at or below this flags the item as low stock. | numeric, 0 or more, e.g. 10 |
ReplenishQuantity | opt | Suggested top-up amount to reorder when the item runs low, in the item's Unit. | numeric, 0 or more, e.g. 50 |
Tags | opt | Semicolon-separated list of EXISTING tag names. Import never creates new tags — define them first. | e.g. bestseller;fall-collection |
VariantSKU | opt | SKU for a variant. On a variant row, repeat the item Name and SKU and fill this in. | e.g. SOAP-100-LG |
VariantDescription | opt | A description of the variant. | e.g. Large bar |
VariantPrice | opt | The selling price for this variant. | numeric, e.g. 9.00 |
VariantQuantity | opt | Opening on-hand stock for this variant, as a number of packs, whatever the item's Unit is. Put it on the variant's row (leave the item-level Quantity blank). Pairs with VariantUnitCost. | numeric, 0 or more, e.g. 25 |
VariantUnitCost | opt | The cost of one pack of this variant, in your account currency. Pairs with VariantQuantity to set the variant's opening balance and average cost. An export writes the same figure, so the file imports back unchanged. | numeric, 0 or more, e.g. 3.50 |
AttributeName | opt | Name of an item-level attribute. Must already exist under Settings → Attributes. | e.g. Scent |
AttributeValue | opt | The value for that attribute. Must be one of the attribute's defined options. | e.g. Lavender |
VariantAttributeName | opt | Name of a variant-level attribute. Must already exist under Settings → Attributes. | e.g. Size |
VariantAttributeValue | opt | The value for the variant attribute. Must be one of the attribute's defined options. | e.g. Large |
A worked example
The file below imports two items. The first is a raw material with opening stock but no selling price. The second is a product whose stock is held at the variant level: to add a variant, repeat the item's Name and SKU on an additional row and fill in the Variant* columns.
Name,SKU,Category,State,Unit,Price,Quantity,UnitCost,VariantSKU,VariantDescription,VariantPrice,VariantQuantity,VariantUnitCost
Vanilla Extract,VAN-001,raw,active,milliliter,,500,0.08,,,,,
Lavender Soap,SOAP-100,product,active,unit,6.00,,,SOAP-100-SM,Small bar,6.00,40,1.10
Lavender Soap,SOAP-100,product,active,unit,6.00,,,SOAP-100-LG,Large bar,9.00,25,1.60- Vanilla Extract — a raw material tracked in
milliliter(the full unit name, not "ml").Priceis blank because it isn't sold on its own.Quantity500 withUnitCost0.08 sets both on-hand stock and average cost. - Lavender Soap — a product sold in two variants. The item-level
QuantityandUnitCostare left blank because the stock lives on the variants. - The variant rows — each repeats
Lavender Soap / SOAP-100and adds a variant with its own opening stock viaVariantQuantityandVariantUnitCost: the Small bar starts at 40 units (1.10 each) and the Large bar at 25 units (1.60 each).
Together, Quantity and UnitCost create an opening-balance transaction on import, so both your on-hand quantity and your average cost are set in one step.
Variants & attributes
Each variant is an additional row that repeats the parent's Name and SKU, then fills in VariantSKU, VariantDescription, and VariantPrice. To give a variant its own opening stock, add VariantQuantity and VariantUnitCost on that variant's row (and leave the item-level Quantity / UnitCost blank so stock isn't counted twice). A variant is counted in packs, so VariantQuantity is a number of packs and VariantUnitCost the cost of one pack, even when the item's Unit is a weight such as gram. In a transaction CSV, a row with a Variant needs a count PackageUnit, such as unit, 1 per pack.
Attributes work through the AttributeName / AttributeValue columns for the item, and VariantAttributeName / VariantAttributeValue for a variant. Import does not create new attribute definitions — the attribute must already exist under Settings → Attributes, and the value you supply must be one of that attribute's defined options.
Importing other sections
The same select-map-validate flow applies across the app — every importable list has its own template and its own set of fields. The complete import reference documents the columns for every surface:
- Inventory — Ingredients, Packaging, MRO (maintenance, repair, and operations), Components, Products, and more (covered on this page).
- Vendors, customers, locations, and charities — contact details plus vendor ordering terms and customer groups.
- Transactions — purchases, sales, and other transaction records.
- Recipes and production runs — including ingredient and step rows.
- Settings registries — tax categories, transaction methods, referral sources, pricing tiers, attributes, and custom fields.
Switching from another tool? Import opening stock or purchase history, not both. The Quantity column on an inventory import is a snapshot of what is on your shelves today, and it already includes everything you bought to get there. On-hand is a running total with no date filter, so importing your old purchase history on top of that snapshot counts the same goods twice — back-dating the purchases does not separate them. If you want the history, set the opening quantities to zero (or subtract the imported purchases from them) and let the transactions build your stock. The import dialog warns you when it spots this, but it cannot tell which of the two you meant.
Troubleshooting common errors
The importer validates every row and shows errors row-by-row. A single error aborts the whole import — nothing is saved until every row is valid — so fix the reported rows and re-upload. Once the rows pass, large files are saved in batches of 100 with a running count in the dialog, so give a long file a moment to finish.
Missing Name
Name is required on every item row. A blank SKU is fine — one is generated from the name.
Duplicate SKU
Each item SKU must be unique across your items. Change the duplicate, or if it is meant to be a variant, move it onto a variant row that repeats the same Name and SKU.
A required field is not mapped ("... is required. Choose the CSV column that contains it.")
Every field marked with * on the mapping step must point at a CSV column. Pick the column from the dropdown, or add the column to your file if it is missing.
A column is mapped to more than one field ("Each column can only be used once.")
One CSV column can only feed one Ardent Seller field. Set the extra field back to Ignore, or split the data into separate columns.
File rejected before mapping
The importer only accepts .csv files up to 10 MB ("Please select a CSV file." / "File is too large"). Save spreadsheets as CSV first, and split very large files.
Invalid Category or State
Use one of the accepted values — Category: raw, food, subassembly (or component), packaging, finished, mro, equipment, labor, product, service; State: draft, active, archived. Values are matched case-insensitively, and near-misses get a "Did you mean?" suggestion. "food" is still accepted and imports as Ingredient or material tagged Food. "finished" is still accepted too: a priced row imports as a product, otherwise a component.
Unrecognized Unit
Common abbreviations such as "g", "oz", "lbs", "ml", "fl oz" and "each" are understood. For anything else use the full unit name, for example "gram" or "milliliter". A blank Unit imports as "unit" (each).
Invalid allergen
Allergens must come from the supported list: milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, sesame.
DefaultEntity not found
The DefaultEntity value must exactly match an existing location or vendor name, or be left blank.
Attribute not defined / invalid value
Import does not create attributes. Define the attribute and its options under Settings → Attributes first, then use one of its options as the value.
Non-numeric Price, Quantity, or UnitCost
These must be plain numbers (Quantity, UnitCost, VariantQuantity, and VariantUnitCost must be 0 or more). Remove currency symbols and thousands separators. Stray spaces, a leading + or ., and scientific notation are cleaned up for you, and extra decimal places are rounded to what the field stores — costs to 4 places, quantities to 6.
A date we can't read, or one that "puts the day first" (transaction and recipe imports)
Write the date as YYYY-MM-DD, for example 2026-01-31. A file has to use one order throughout: if some dates can only be month-first (09/23/2026) and others only day-first (23/09/2026), the importer cannot tell which order the rest are in, so it names the day-first rows. Spreadsheet serial numbers such as 46288 are not dates. Format the column as a date before saving the CSV.
A transaction with too many lines ("... make one transaction of 1,250 lines; the limit is 1,000.") (transaction imports)
Rows that share a date and a TransactionNumber, or a date and a blank TransactionNumber, are imported as one transaction, and a single transaction can hold at most 1,000 line items. The importer checks this before importing anything, so nothing is saved. Give some of the rows a different TransactionNumber to split them into smaller transactions, then upload the file again. Saving more than 1,000 lines in the transaction sheet is refused the same way: "A transaction can have at most 1,000 line items. Split it into smaller transactions."
A Variant that doesn't match, or a purchase row with none (transaction imports)
A transaction file has an optional Variant column, which matches the variant's full label, then its description, then its SKU, ignoring case. A value that doesn't match that item's variants is reported on any row, and a purchase row for an item with variants needs a valid Variant; other categories may leave it blank. Any reported row holds the whole file until it's fixed. A purchase recorded earlier with no variant exports with a blank Variant, so re-importing that file reports the row until you name one. The message lists the item's variants.
Negative opening Quantity
Opening stock cannot be negative. If an item is already overdrawn in your old system, import it with a blank or 0 Quantity, then import an adjustment transaction for it with a negative QuantityInPackage and a matching negative PackageCost — PackageCost is the total for the line, so both signs must agree.