Import Builder/Guides/MRPeasy import errors
Manufacturing

MRPeasy Import Errors and How to Fix Them

MRPeasy imports items and vendors from a CSV file, and you map each column to a field on screen. These are the problems that garble a file, create duplicate units and vendors, or leave rows out, and how to fix each one.

MRPeasy's import rules

A CSV file, in UTF-8 for non-Latin characters
Up to 3,000 lines per upload
"The first row is heading" ticked when there is one
Every column mapped to the right field, or Do not import
Net cost and quantity at stock given together
Units, groups and vendors spelled the same every time

Where the feed goes

Items are imported in Stock, Items, and vendors in Procurement, Vendors, each with an Import from CSV option. Back up the database first, as MRPeasy recommends, and import items before bills of materials, since a bill of materials needs every item to exist already.

Common errors and their fixes

Names, accents or symbols come through garbled

Cause: MRPeasy reads a CSV file. Saving as an Excel workbook, or as a CSV in the wrong encoding, scrambles non-Latin characters.

Fix: Save as CSV, and for non-Latin characters use UTF-8, or Excel's Unicode Text option, which MRPeasy can also import.

The header row is imported as an item

Cause: MRPeasy reads every row as data unless you tick that the first row is a heading.

Fix: Tick "The first row is heading" on the import screen when your file has a header row.

Columns land in the wrong fields

Cause: You map each column to an MRPeasy field on screen, and the automatic mapping can be wrong when names differ.

Fix: Check every column's field before importing, and set columns you don't want to Do not import.

More than 3,000 lines

Cause: An upload takes at most 3,000 lines.

Fix: Split a larger file into several files and import them one after another.

Units, groups and vendors multiply

Cause: MRPeasy creates a unit of measurement, a product group or a vendor when it doesn't recognise the name. pcs and pc become two units, and Acme Ltd and Acme Limited two vendors.

Fix: Spell units, groups and vendors the same way on every row, and match names already in MRPeasy. The whitespace guide covers stray spaces that make names differ.

Part numbers lose their zeros or turn into dates

Cause: Part No. is how MRPeasy matches items for updates and bills of materials. A spreadsheet turns 00123 into 123 and 1-2 into a date.

Fix: Format the Part No. column as text before pasting. See leading zeros in CSV files.

Items updated when you meant to create them

Cause: When a Part No. already exists, MRPeasy treats the row as an update and shows a confirmation page listing the changes. For vendors, a number that already exists is ignored when creating.

Fix: Check the confirmation page before accepting, and give new items part numbers that aren't in use.

Cost imported as zero

Cause: Net cost per 1 unit and Quantity at stock must be imported together. With one missing, the cost is zero.

Fix: Fill in both for every item that has opening stock. The cost can be edited later on the stock lot, but not by a repeat import.

Stock or vendor terms not updated by a later import

Cause: Inventory quantities and purchase terms can be imported with the item list only when items are first created.

Fix: For later changes use MRPeasy's Inventory import for stock and the Vendors import for purchase terms.

Only one vendor per new item

Cause: A new item can carry one purchase term, and the Vendor, Vendor price per unit and Lead time in days must be given together.

Fix: Import the first vendor with the item and the others from the Vendors import.

Bought and made items mixed up

Cause: Is procured item is 1 for items you buy and 0 for items you make in-house, and it defaults to 0. Marking a purchased part 0 treats it as something you manufacture.

Fix: Set it on every row, and check it before building bills of materials.

Vendor units that don't convert

Cause: If a vendor sells in boxes, the conversion rate is how many of your units are in one box, and the vendor price is per box.

Fix: Enter 200 for a box of 200 pcs, and price the box, not the piece.

Payment period type not accepted

Cause: Payment period type is 0, counting from the invoice date, or 10, counting from the end of the invoice month. Words aren't read.

Fix: Use 0 or 10.

Some rows were skipped

Cause: MRPeasy imports what it can and gives you a skip file listing the failed rows line by line.

Fix: Fix those rows in the skip file and import it again. Back up the database before a big import: the manual expects some trial and error.

After importing

Rows that fail are collected in a skip file you can download, with the error for each line. Fix those in the file and import again, rather than editing records by hand.

Check the units, product groups and vendors MRPeasy created after the first import: a misspelling shows up there as an extra entry.

Checklist before you import

A description on every item
Part numbers as text and used once
Units, groups and vendors spelled consistently
Net cost and quantity at stock together
Vendor, vendor price and lead time together
Is procured item set to 1 or 0 on every row
Payment period type 0 or 10
No more than 3,000 lines
Database backed up

Collecting parts or suppliers from several sources?

Send each location a form instead of a spreadsheet. The MRPeasy items template uses MRPeasy's item field names, flags repeated part numbers and takes the bought-or-made flag only as 0 or 1. For suppliers, the MRPeasy vendors template flags repeated names and numbers.

Try the items template

Import Builder is an independent product and is not affiliated with, endorsed by, or sponsored by MRPeasy. MRPeasy is a trademark of its owner. Import rules as described in MRPeasy's user manual, November 2026.