MRPeasy Customer Order Entry From Customer Purchase Order PDFs

Your customers email purchase orders as PDFs, and someone retypes each one into CRM, Customer Orders.

PDF, JPG, PNG, BMP, HEIC, TIFF

Submit your purchase orders

Any layout, any length
One row per line item
Excel, CSV or JSON
Plans from $49 a month

Overview

Your customers email purchase orders as PDFs, and someone retypes each one into CRM, Customer Orders. Upload one here and get the customer PO number, dates and every line with item, quantity and price as a spreadsheet you can key from in minutes, or feed to the API.

Why customer orders still get retyped into MRPeasy

MRPeasy documents CSV import for items, customers, vendors, stock, bills of materials, routings and price lists. We found no public import page for customer orders, which are added from the CRM module.

The PDF is not a loadable file

A customer PO is a document. Before anything can be loaded or keyed quickly, every line has to exist as a row.

Buyer item codes do not match your items

A customer prints their own part number. Your MRPeasy item code is different, so each line needs a lookup before it can be entered.

Typos reach production

A wrong quantity on a customer order flows into planning, purchasing and shipping. A credit memo later costs more than the keying saved.

Seats are paid per user

MRPeasy is priced per user per month. Paying a seat for a person who mostly retypes PDFs is an expensive way to enter orders.

From customer PO to clean order rows

Upload the purchase order your customer sent. The AI reads the header and every line on every page and returns one clean row per line item.

No template per customer

A one page reorder and a six page order come back in the same column layout, so one routine serves every buyer.

Buyer item numbers kept apart

The item number the customer printed and the description land in separate columns, so one cross-reference maps them to your item codes.

Order number on every line

The customer PO number sits beside every line, which ties the rows to one customer order.

Spreadsheet or JSON

CSV and Excel suit quick keying and review. JSON suits a script that calls the API on a paid MRPeasy account.

Where MRPeasy order entry still costs you hours

MRPeasy is a manufacturing system used by small and mid-sized US shops. Trade customers usually send a PDF purchase order by email. Someone opens it, finds the customer in CRM, adds each product and types the quantity, price and delivery date. With ten orders a day and a dozen lines each, that is a large share of one person's day.

Reading the PDF into rows first gives you a checked list to key from, or a file a script can send through the API that MRPeasy lists for paid accounts. Either way the retyping and the transposition errors go away.

Customer PO field to MRPeasy customer order

What comes off the customer document and where it belongs on an MRPeasy customer order. Field names on your account may differ, so confirm in your own system.

From the customer PO On the MRPeasy order Note
Customer company Customer Match to an existing customer record
Customer PO number Customer reference Repeat on every line of the order
Buyer item number mapped to your item Product Map through a cross-reference sheet
Quantity Quantity Check the unit of measure
Requested delivery date Delivery date One date per line or per order
Unit price Price Compare with your price list

How the workflow runs

Four steps from the customer attachment to a new customer order in MRPeasy.

1

Upload the customer PO

Drop in the PDF, the scan or the email attachment. Up to 50 files per bulk upload, with no per-customer setup.

Tip: Multi-page orders work the same way.

2

Review the lines

Check the header and every line on screen, including the buyer item number, quantity and price.

Tip: Sort by item number to spot codes missing from your cross-reference.

3

Map to your records

Add your item codes next to the buyer codes and save as CSV or Excel.

Tip: Keep the column names the same every time.

4

Enter and check

Create the order in MRPeasy from the sheet. Compare the total with the customer PO before you confirm it.

Tip: Start with one customer for the first week.

Why order desks use this in front of MRPeasy

1
Row per line item
3
Export formats, Excel, CSV and JSON
50
POs per bulk upload

Security and privacy

  • Bank-grade TLS encryption in transit
  • Your PO data is never sold or shared
  • US-based cloud infrastructure

MRPeasy customer order entry questions, answered

Not directly. The public MRPeasy user manual describes adding customer orders from the CRM module. PurchaseOrders reads the PDF and returns the rows as CSV, Excel or JSON, so you key from a clean sheet or send the rows through the API.

We did not find one. The user manual lists CSV import for items, customers, vendors, stock, bills of materials, routings and price lists. Confirm with MRPeasy support for your plan before you plan a bulk order load.

The MRPeasy pricing page lists API and webhooks for paid accounts. Check which plan includes the limits you need before you build a script that creates customer orders.

The pricing page shows $49, $69, $99 and $149 per user per month for Starter, Professional, Enterprise and Unlimited, with Unlimited needing at least 2 users. From the 11th user, each bundle of 10 users is $79 a month.

Yes. It reads whatever the buyer printed and puts their item number and description in separate columns on every line. You map those to your item codes once with a cross-reference sheet, then repeat orders map in seconds.

No. PurchaseOrders reads the customer purchase order and returns Excel, CSV or JSON. It does not connect to MRPeasy or create orders. You key the rows or load them with your own script.