MRPeasy pricing: plan features and the user-bundle rule

The first ten users and later user bundles follow different pricing rules, while required production features determine the edition.

Kartik Deshpande··6 min read

A five-person production team and a twelve-person team do not follow the same straight per-seat calculation in MRPeasy. MRPeasy pricing charges the first ten users at the selected edition’s rate, then adds fixed-price user bundles. Choose the production features first, because a lower seat price is irrelevant when the required workflow needs another edition.

MRPeasy is worth evaluating when its production, inventory, and planning workflow fits the operation and the team can maintain the required records. Keep the current system when it already handles those requirements and a move would mainly recreate working BOMs and routings. The prices below were checked November 10, 2026; confirm currency, billing, and tax in the offer.

Choose the production requirements before the edition

List the operation you need to complete: receive materials, release a manufacturing order, record consumption, inspect output, and complete the customer order. Name the roles involved and the evidence each must retain. A production manager and an occasional shop-floor participant may need different access arrangements, which the vendor should confirm before seats are purchased.

Include the hard constraints, such as expiry tracking, quality review, multiple sites, approvals, or a custom data connection. Assign each to an acceptance task rather than a feature label. For expiry tracking, the useful test is whether the required lot can be traced through receipt, use, and shipment with the needed date information.

The ERP versus MRP comparison addresses the broader system decision. Use it if the purchase scope is still unclear. A planning requirement and a financial-system replacement can overlap, but they carry different migration and ownership work that a single subscription amount does not explain.

Match the published rates with their feature gates

MRPeasy’s official plans list Starter at $49, Professional at $69, Enterprise at $99, and Unlimited at $149 per user per month. Unlimited has a two-user minimum. The table summarizes selected published differences rather than every feature; verify the exact requirement in the offer before purchasing.

EditionPublished user rateSelected plan requirement
Starter$49/monthProduction planning, BOMs, lot traceability
Professional$69/monthAdds expiry dates, quality control, serial numbers
Enterprise$99/monthAdds approvals and multiple production sites
Unlimited$149/month; two-user minimumLists API and webhooks for paid accounts

Do not assume a lower edition covers a feature because a general product page describes it. Retain the edition, requirement, and source reference in the evaluation. When a requirement depends on configuration or a connected accounting system, ask for that dependency in writing and include it in the acceptance scope.

Calculate the first seats and later bundles separately

Assume a hypothetical five-user Professional subscription billed at the displayed monthly rate. Five × $69 = $345 per month, or $4,140 over twelve unchanged monthly payments. That example excludes tax, implementation, external services, and any annual-payment discount; it is not an annual-plan quote.

The pricing page’s bundle explanation charges the first ten users at the edition rate and adds $79 per month for each further bundle of ten. Under that rule, twelve Professional users cost (10 × $69) + $79 = $769 per month. Do not multiply all twelve users by $69 or treat the bundle as replacing the first ten.

Use the expected production audience at launch and during the next review period. A pilot run by the implementation team may have fewer users than the released workflow. Ask which kiosk or reporting roles require a paid seat, and budget the named maintainers as well as the people doing daily transactions.

The edition and audience are separate decisions
Workflow
Required production task
Edition
Feature and access scope
Audience
Base users and bundles
Expanding access changes the seat calculation, while a new operating requirement can change the edition.

Budget the opening data as part of the move

MRPeasy’s inventory setup instructions describe initial quantities and costs, with site and storage information where applicable. Build an opening-data register with the item identifier, unit, quantity, cost basis, location, and approved cut-off. A successful import is not proof that those balances agree with the accepted opening stock.

Count and reconcile the stock population that will be loaded. Keep obsolete items and held stock in their approved categories rather than importing every spreadsheet row as usable inventory. Finance should approve the opening cost basis; operations should approve the unit and physical quantity.

Prepare the BOM versions and operations needed for one representative product family before moving every item. Record component units, yield assumptions, scrap treatment, and effectivity. The bill of materials article covers that record structure separately from the subscription decision.

Prove a complete production path with permitted sample data

Use a trial to receive a partial material order, create the intended manufacturing order, record consumption, and inspect the resulting balances. Include a lot or serial requirement if it affects the edition. These are proposed checks for the buyer, not claims that a hands-on MRPeasy test has been performed.

Use an operator account and a manager account to check the actual role boundary. Verify which fields can be changed and what evidence remains after a correction. Do not let the implementation administrator’s broad access stand in for the permissions people will have after release.

Reconcile the sample output to the accepted inputs and record each difference. An imported BOM can be structurally valid while using the wrong unit or version. A completed manufacturing order should be reviewed for the exact material, output, and timing behavior the business needs, rather than being accepted because its status changed to complete.

Price the accounting and reporting handoffs

Identify which system owns the sales order, purchasing record, item master, and accounting entry. Decide the direction and timing of each approved connection. A vendor listing an integration does not establish which record types or corrections are included in your configuration.

Ask how partial receipts, returns, cancelled orders, and changed item codes pass through the proposed connection. Retain a recovery process for a failed handoff and a way to identify records already processed. Replaying the same transaction without checking identity can create duplicates even when the original connection works as documented.

The Katana pricing evaluation gives another manufacturing-software budget to compare. Use the same staff, production path, inventory scope, and period when comparing totals. Separate the subscription from the cost of migrating and maintaining the connections in either option.

Where Permute fits alongside production software

Permute sells connected business data, custom applications, and governed analysis. We can scope a reporting workflow from permitted accounting records and approved production exports. Declared item and cost mappings connect those sources without assuming that a production-system migration has already resolved every reporting definition.

We can reuse the definitions in a recurring operations report and a custom review application. A manufacturing manager can inspect which source records explain a material or output variance under current permissions. This is separate from licensing MRPeasy, and no native MRPeasy connector is promised here.

Inspect a production reporting handoff

Use permitted production output and accounting records behind one recurring variance.

Keep production operation and accounting policy in their systems

We are not a forecasting engine and do not promise to replace MRPeasy’s planning or transaction workflow. This reporting scope reads source records; it does not promise to release manufacturing orders or revise stock in the source. Confirm source access and refresh intervals before scoping an ongoing report.

The manufacturer owns BOM approval, routing, quality decisions, and opening balances. Finance owns accounting treatment. Keep the subscription decision conditional on those acceptance requirements (including recovery from a failed connection), and retain an unknown cost where the vendor has not supplied the relevant terms.

Approve a production scope and its corresponding price

MRPeasy pricing starts with the edition that covers the required production path. Calculate the first ten users and later bundles under their separate rules, and keep billing assumptions visible. Budget stock preparation, BOM validation, and connection ownership alongside licensing. Stay with an existing workflow when the proposed change cannot justify that work.

Review a manufacturing data and reporting scope

Bring the production and accounting reports that still need reconciliation after the system decision.

Questions about budgeting MRPeasy

Can Unlimited be budgeted for one user?

The published offer states a two-user minimum for Unlimited. Use the applicable minimum when requesting the quote. Do not apply the single-user rate alone to describe the smallest available subscription.

Does the monthly example include annual-payment savings?

No. It uses twelve unchanged monthly payments to make the period explicit. Request the selected billing option and payment terms before comparing it with another vendor’s annual commitment.

Should every employee be included in the initial seat count?

Count the roles that need access and confirm the appropriate access arrangement with the vendor. Keep the expected rollout audience separate from the smaller implementation team. Do not reduce the budget by sharing a login that prevents individual responsibility from being recorded.