MRPeasy

MRPeasy is a Cloud-Based ERP/MRP system made for small manufacturers and distributors with 10-200 employees. The software offers production planning and scheduling, inventory management, purchasing, CRM, team management, and accounting functionalities to businesses that need a powerful yet affordable and easy-to-use tool for managing their business.

Prerequisites

To connect MRPEasy to Omnata, you need to have an active MRPEasy account on a Unlimited Plan. If you don't have one, you can sign up here.

Authentication

MRPeasy REST API uses Basic access authentication

• api-key - your MRPeasy API key, that can be found in Settings - Integration -> API access;

• access-key - a secret key that can be defined in Settings - Integration -> API access

Inbound Syncs

The following streams are supported:

• user_actions (Full Refresh and Incremental)

• activities (Full Refresh and Incremental)

• units_of_measurement (Full Refresh and Incremental)

• work_stations (Full Refresh and Incremental)

• work_station_types (Full Refresh and Incremental)

• vendors (Full Refresh and Incremental)

• vendor_contact_data (Full Refresh and Incremental)

• bills_of_materials (Full Refresh and Incremental)

• bills_of_material_components (Full Refresh and Incremental)

• customer_orders (Full Refresh and Incremental)

• customer_order_products (Full Refresh and Incremental)

• customer_order_product_sources (Full Refresh and Incremental)

• customers (Full Refresh and Incremental)

• customer_contact_data (Full Refresh and Incremental)

• manufacturing_orders (Full Refresh and Incremental)

• manufacturing_order_parts (Full Refresh and Incremental)

• manufacturing_order_part_lots (Full Refresh and Incremental)

• manufacturing_order_operations (Full Refresh and Incremental)

• manufacturing_order_operation_work_stations (Full Refresh and Incremental)

• manufacturing_order_operation_work_station_workers (Full Refresh and Incremental)

• manufacturing_order_operation_work_station_worker_results (Full Refresh and Incremental)

• manufacturing_order_notes (Full Refresh and Incremental)

• parameters (Full Refresh and Incremental)

• parameter_values (Full Refresh and Incremental)

• product_groups (Full Refresh and Incremental)

• purchase_orders (Full Refresh and Incremental)

• purchase_order_products (Full Refresh and Incremental)

• purchase_order_bills (Full Refresh and Incremental)

• relations (Full Refresh and Incremental)

• relation_lines (Full Refresh and Incremental)

• relation_line_values (Full Refresh and Incremental)

• return_material_authorization_orders (Full Refresh and Incremental)

• routings (Full Refresh and Incremental)

• routing_operations (Full Refresh and Incremental)

• sales_invoices (Full Refresh and Incremental)

• sales_invoice_products (Full Refresh and Incremental)

• serial_numbers (Full Refresh and Incremental)

• shipments (Full Refresh and Incremental)

• shipment_products (Full Refresh and Incremental)

• stock_items (Full Refresh and Incremental)

• stock_item_purchase_terms (Full Refresh and Incremental)

• stock_item_parameters (Full Refresh and Incremental)

• stock_lots (Full Refresh and Incremental)

• stock_lot_locations (Full Refresh and Incremental)

For incremental loads, we utilise the user_actions and the activity codes to determine the changes in the system. The user_actions stream is used to determine the changes in the system and the activity codes are used to determine the changes in the specific stream.

Outbound Syncs

There is currently no outbound sync support for this App, but please let us know if you have a use case in mind.