What API2Cart Is Evaluating for MRPeasy Integration
Candidate workflow
Align store demand with customers, products, manufacturing orders, stock, and shipments. Final entity and method coverage will follow verified vendor interfaces and customer requirements.
Operational outcome
The intended result is to preserve site, bill-of-materials, routing, lot, serial, lead-time, and status context. Identity rules and idempotency would be defined before transactional writes are enabled.
ERP safeguards
The design must coordinate customer orders with production planning without assuming immediate availability. Customers, products, sales orders, fulfillments, invoices, and production records would keep their distinct lifecycle roles.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About MRPeasy So Far
Based on MRPeasy’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. MRPeasy offers a REST API, documented via a published OpenAPI/Swagger specification, but access is gated to customers on the "Unlimited" pricing plan rather than available to all accounts. Authentication uses HTTP Basic auth with a paired api-key and access-key generated under Settings > Integration > API access. Bulk reads are capped at 1,000 records per request, and a beta v2 with expanded reporting endpoints is available alongside the stable v1.
MRPeasy integration is not live yet. Authentication, modules, entities, fields, writes, events, limits, editions, and release timing remain subject to technical discovery and demand.
Background. MRPeasy states that its minimum viable product was developed in 2013 and the company was founded in February 2014. It began as cloud production-planning software for small manufacturers and expanded into a manufacturing ERP suite with inventory, purchasing, sales, workforce, and accounting capabilities.
Where it specializes. The service is deliberately designed for small manufacturing businesses that need accessible material requirements planning, production scheduling, bills of material, routings, stock, procurement, customer orders, and shop-floor reporting without enterprise-scale infrastructure.
Integration challenge. MRPeasy provides REST APIs, with a newer v2 introduced alongside the established v1 interface. The published v1 reference uses Basic authentication, Range headers for pagination, partial-content responses, and HTTP 429 when another request is running. API2Cart discovery must confirm the customer’s subscription and API version, available read and write endpoints, credential isolation, concurrency behavior, page ranges, units, BOM and routing identifiers, manufacturing-order states, and accounting integrations. Requests should be queued and retried safely rather than sent in uncontrolled parallel batches.
Technical validation. Engineering must verify API access, keys, rate limits, supported objects, and incremental update options. Unsupported modules and operations would remain outside the public scope.
Roadmap evaluation considers API maturity, sandbox access, operational correctness, commerce relevance, scale, customer demand, maintenance cost, deployment variants, and overlap with existing connectors. This page records a candidate, not a promised release date.
Primary sources: MRPeasy company and product history · MRPeasy product overview · MRPeasy REST API reference
Related planned integrations: Genius ERP integration · xTuple ERP integration · metasfresh integration · Tryton integration
Interested in MRPeasy Integration?
Let us know you’re interested, and we’ll notify you as soon as MRPeasy support becomes available.
