A Question That Surfaces Late in ERP Scoping
A manufacturer with an in-house IT team reaches a point in the ERP evaluation process where the question shifts from “does the system do what we need?” to “how much of the setup and ongoing maintenance can we own ourselves?” The team has technical capacity. They want to use it. The question is where the line sits between what they can configure independently and what requires a vendor quote.
This is a practical and important question. Getting the answer right before signing an implementation agreement affects both the total cost of the project and how much control the business retains after go-live.
Why the Boundary Matters More Than It Seems
When an ERP implementation is priced with a fixed fee for the base engagement and separate quotes for customizations, the definition of “customization” carries real financial weight. If the boundary between included configuration and quoted work is not agreed before requirements collection begins, each department request has to be renegotiated as it surfaces. That slows the project and can produce scope surprises mid-engagement.
The people most affected are the ones doing requirements gathering: the IT lead coordinating across departments, the warehouse manager describing pick list formats, the accountant explaining how financial reports need to be segmented. Each of them may surface a need that lands on one side of the line or the other. Without a clear framework, those conversations stall.
There is also a longer-term consideration. A manufacturer that understands which changes it can make independently is better positioned to adapt the system as the business evolves, without returning to the vendor for every adjustment.
What Stays Unresolved When the Boundary Is Unclear
The practical risk is not a single large cost. It is a series of small decisions made without a shared understanding. A department head asks for a custom field on the sales order to track a product attribute. Is that a five-minute administrator task or a quoted development item? A finance manager wants a report filtered by internal department. Does the IT team build that, or does it go to the vendor? A warehouse supervisor wants the pick list to show different columns. Who owns that change?
When these questions do not have clear answers during requirements collection, the project can slow down, scope can drift, and the fixed-fee assumption can erode. The business may also underestimate how much ongoing maintenance it can realistically own, which affects staffing decisions and long-term support costs.
What a Manufacturer Needs to Know Before Finalizing Scope
A useful framework for evaluating this question has two parts. First, what can a Firm Administrator do independently within the ERP, without vendor involvement? Second, where does that self-service capability end, and what triggers a vendor quote?
The answer should be specific enough to use during requirements collection by role. The warehouse manager’s needs, the accountant’s needs, and the manufacturing supervisor’s needs each map differently to the configuration boundary. A manufacturer with IT capacity wants to know which of those needs it can address internally and which ones require a conversation with the vendor before the project starts.
How Versa Addresses This in Practice
Versa documents what administrators can configure themselves, which is the practical starting point for scoping what still needs a vendor quote.
On the administrator-configurable side, a user with Firm Admin permission can add custom fields to supported records, including products, orders, invoices, and other supported models. These fields support text, numeric, date, boolean, and select-list types. The same administrator can create and maintain custom form templates that control supported printed-document layouts. Permission structures and financial dimensions are also administrator-managed, meaning the IT team can define how users access the system and how financial reports are segmented by department, region, or other business-relevant categories. Dimensions are defined and assigned in Setup and can be used to break down financial reports, all without vendor involvement.
The documented boundary is equally important. Custom fields extend supported records but do not create new transaction behavior or automatic workflow by themselves. Certain firm-wide configuration options lock once transactions exist against related master data, so structural decisions made early in implementation cannot always be reversed later. Work outside those tools is what you would discuss and price with the vendor.
This means a manufacturer’s IT team can realistically own the ongoing maintenance of fields, forms, permissions, and dimensions. During requirements collection, each department’s needs can be mapped to one category or the other, giving the project a clear and defensible scope before the fixed fee is committed.
One practical note on timing: some configuration decisions, particularly those involving shared master data across entities, need to be made before records are imported. The IT team’s involvement in early setup is not just efficient. In some cases it is necessary to preserve options that would otherwise close.
What Requirements Collection Looks Like With This Clarity
Return to the manufacturer’s IT lead coordinating across departments. With a clear configuration boundary in hand, the conversation with each department head becomes more direct. The warehouse supervisor’s request for a specific pick list layout maps to a printed document controlled by a form template, where that form type is supported in Versa. The product attribute the department head wants to track maps to a custom field where that record type is supported. The accountant’s request for a financial report filtered by internal department maps to Versa’s dimension system, which the administrator configures.
In each case, the IT lead can give a clear answer during requirements collection rather than deferring to the vendor. The items that genuinely require a vendor quote are identified early, not discovered mid-project. The fixed-fee implementation proceeds with a shared understanding of who does what, and the business enters go-live with the skills to maintain its own configuration.
See This Workflow in a Versa Demonstration
If your team is in the process of scoping an implementation and wants to understand exactly where the administrator-configurable boundary sits in Versa, the most useful next step is a focused walkthrough. A representative session can show how a Firm Admin adds a custom field to a product or order record, how a printed document template is maintained, and how dimensions are assigned for financial reporting. That walkthrough clarifies what your IT team can own from day one, without requiring any preparation on your part before the conversation.
Request a Versa demonstration focused on administrator-configurable scope to see these workflows with a representative product or order record relevant to your business.
If you prefer to explore the topic before speaking with the team, ask Versa AI Advisor about this workflow. The Advisor can answer questions about configuration scope and implementation boundaries and help you decide whether a sales conversation makes sense for your situation.
Request a Versa demonstration focused on administrator-configurable scope at https://www.versaclouderp.com/contact-us
