# MRPeasy Custom Fields > Source: https://netray.co/erp-help/mrpeasy-custom-fields > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer MRPeasy lets administrators extend records with additional fields in its settings, so you can store information such as drawing revision, customer part number or inspection class on items and documents. Availability by record type and plan varies, so confirm in your account, and remember that a custom field stores data but does not by itself change planning logic. ## Kind how-to ## System small-erp ## Erp MRPeasy ## Module Configuration / Custom Fields ## Query mrpeasy custom fields ## Alternate Queries - mrpeasy add custom field to item - mrpeasy custom attributes customer order - mrpeasy user defined fields - mrpeasy custom field report ## Applies To MRPeasy cloud; the set of records that accept custom fields and how they appear in reports and the API depends on release and plan ## Steps ### How to add and use a custom field **Items:** - Decide the purpose of the field: information only, a filter, a value printed on documents, or a value an integration reads. - Open the settings area as an administrator and look for custom field or additional field configuration for the record type: items, customer orders, manufacturing orders or others. - Choose a name and a data type that matches the use: text, number, date or a pick list when you need consistent values. - Add the field to the record layout and to the grid columns, so users see and filter on it. - Populate existing records by import where possible, rather than by hand, so data is complete. - Add it to printed documents if it must appear on quotes, packing slips or work instructions. - Test whether it appears in exports and in the API response before you build a report or integration around it. ## Sections ### What a custom field can and cannot do **Body:** A custom field is data. It lets you filter, search and print. It does not add planning rules, change a BOM explosion or block a shipment. If you need behavior, such as holding an order until an approval, use the available statuses, roles and workflow settings, or handle the rule outside in your own process. Use pick lists for anything you will report on. Free text produces spellings like Rev A, rev a and A, which are three groups in every pivot table. ### Items, orders and bills of materials **Body:** On items, typical fields are customer part number, drawing revision, material specification, country of origin and inspection class. On customer orders, it is common to keep customer purchase order line references and delivery instructions. For BOMs, fields rarely help, since the structure itself should hold the data; put the information on the item that the BOM line points to. Keep the list short. Each additional field is another thing to maintain, train and clean, and every integration has to decide whether to carry it. ### Reporting and API implications **Body:** Check whether the field is included in the grid export, in standard reports and in the REST API output. If it is exported, a spreadsheet or BI tool can use it right away. If it is not, you may need a different place to store the value, or a support request to the vendor. When you integrate with Xero, Shopify or another system, map the custom field explicitly. Connectors rarely carry it by default. ## Pitfalls - Using free text for values you need to filter or report on. - Creating fields for one-off needs and never retiring them. - Expecting a custom field to drive planning or approvals. - Not checking API and export visibility before building an integration. - Different teams using the same field for different meanings. ## Ai Angle A private assistant can read the exported records, find inconsistent values in a free-text field, such as revision spellings, and propose a pick list and a cleanup file for you to approve. It runs on your own infrastructure, so the item master stays inside your network. ## Faq ### Can I add custom fields in MRPeasy? **Answer:** MRPeasy supports extending records through its settings, though which record types and field types are available depends on your plan and release. Look in the administrator settings and check with support if it is not visible. ### Do custom fields appear in reports? **Answer:** Often in grids and exports, but standard reports and the API may not include every field. Verify in a test before you rely on it for reporting. ### Can a custom field change planning? **Answer:** No. It stores information. Planning uses quantities, dates, lead times, BOMs and reorder rules, so use those standard structures for behavior. ### Should I use text or a pick list? **Answer:** Use a pick list for values you filter or report on, since consistent values are what make the field useful. Use text only for notes. ## Search terms mrpeasy custom fields, mrpeasy add field, mrpeasy user defined fields, mrpeasy item attributes, mrpeasy customize, mrpeasy api fields, mrpeasy customer order fields, mrpeasy reports --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json