How to Import Products from Excel in EDGEBIC

To import products from Excel in EDGEBIC by User Solutions you build a Product import mask that maps your spreadsheet columns to product fields, decide whether existing records update or stay untouched, then click Do It and read the result counts. The mask is a saved recipe you build once; every later import of the same file shape is two clicks.

This is the specific task of loading products. For what a mask is and how mapping works in general, read import masks explained, and for building any mask from scratch see how to build an import mask.

Before You Start

• Your file is .xlsx, .csv, .txt, or .tsv. These are the formats the readers understand.
• Every row has a filled product id. That is the natural key EDGEBIC matches on, and a blank key fails the row.
• You can see the Settings tab. Import lives inside Settings, which is permission-controlled; ask your administrator if the tab is missing.
• You have decided update or reuse. Reuse (the default) never changes existing products; update overwrites matched records with your file's values.

Building and Running the Product Mask

1. Open the Settings tab and click the 📥 Import tab. The Import Data page opens.

2. Select Product in the Entity Type list on the left.

3. Click ➕ Define New…. The Import Mask Define window opens.

4. Enter a Name such as Weekly Product Sync. Name it after the routine, not this week's file.

5. Click 📂 Get File and pick your spreadsheet. For an .xlsx, choose the worksheet in the Sheet box. EDGEBIC reads the heading row and lists the columns under File Header Titles.

6. Map the columns. Drag a heading from File Header Titles onto the matching row's Source Header cell in the Field Mappings grid. The rows ticked in the Req column are mandatory: for products that is the product id row, which must be mapped before the mask can run.

   Field	Required	Notes
   Product Id	Yes	The natural key; matched case-insensitively
   Product Name	No	Display name
   UOM	No	Unit of measure
   Unit Price	No	Parsed as a number
   Size, Weight, Lead Time, Category, Description, Country Of Origin	No	Optional attributes

7. Set Header Present on if your first row is headings (the usual case). Leave the delimiter on Excel for .xlsx.

8. Click Save. The mask appears under Saved Masks with its name, last file, and format.

9. To control update behavior, select the mask and click ⚙️ Options…. Tick UpdateExistingRecords only if this run's purpose is to change values; leave it off to protect existing products.

10. With the mask selected, click ▶ Do It. If the remembered file path is stale, a file picker opens: choose this week's file. An Importing progress window runs.

What Changes When You Save

Every file row becomes exactly one outcome, and the result dialog shows the totals.

New and updated products appear immediately in the Product grid and in every dropdown that lists products. Nothing about the schedule changes: imports change data, not the plan.

How to Check It Worked

Read the summary line on the Import Result dialog first: Created … · Updated … · Reused … · Failed …. If you expected updates but see all Reused, UpdateExistingRecords is off. If you see failures, the grid shows the offending rows, and 📄 Open Log File gives the exact row numbers and reasons. Then open the Product grid and spot-check a product you meant to change: its new value should be there. Each run writes its own log file to the EDGEBIC import-logs folder, so you always have a record of exactly what that run did.

A Quick Worked Example

The planner at Acme Industries receives a weekly price file. The saved Product mask Weekly Product Sync has UpdateExistingRecords on because the run's purpose is to change prices. She selects the mask, clicks ▶ Do It, and picks prices-week29.xlsx. The result reads Created 0 · Updated 2 · Reused 14 · Failed 0. Widget-A and Bracket-B prices were updated; the other fourteen products matched and were left unchanged. One product, Frame-S, had a blank price cell in the file, and its existing price was preserved rather than wiped, because blank cells never overwrite values on an update. That single behavior is why she maps only the id and price columns for a price run and leaves everything else out of the mask.

Importing from a Delimited Text File

The same mask flow handles .csv, .txt, and .tsv files, with two extra choices. Pick the correct delimiter (Comma, Semicolon, Space, or Tab) instead of Excel, and set Text Enclosed in Quotes if your file wraps text values in quotation marks. If the file has no heading row, untick Header Present and, instead of dragging headings, fill the Col # cell on each mapping row with the column's position (1, 2, 3), which is walked through in how to import a file with no header row. Everything downstream (matching by product id, the Created and Reused counts, the log file) works identically to an Excel import.

Common Mistakes

Leaving a column of zeros in on an update. On updates, a blank cell preserves the existing value, but a cell that literally contains 0 writes 0. Map only the columns you intend to change, and leave the rest out of the mask.

Expecting Reused to change anything. Reused means found and left alone. If you meant to change prices, you must tick UpdateExistingRecords first. This and related traps live in import mask mistakes.

A blank product id. The id is the key. A blank one has nothing to match or create on, so the row fails. Fix it in the source and re-run.

Assuming an import schedules something. Importing products never touches the plan. It only refreshes master data.

Trusting a renamed worksheet. If someone resaves the workbook and the sheet name changes, EDGEBIC can fall back to the first sheet and read the wrong columns. If a run suddenly reads strange data, re-pick the file with 📂 Get File and reselect the correct Sheet.

Next Steps

Work centers follow the same mask pattern with a different key: see how to import work centers from Excel. To take the catalog the other way, out of the grid and into a spreadsheet, see how to export the product list to Excel. For the full task library, see the EDGEBIC how-to hub, and for where import sits in the wider platform, EDGEBIC.