Change control in online store development: how to approve new requirements
The store is already in development when sales asks for wholesale prices, marketing wants a gift in the cart, and the warehouse requests a separate reservation method. Each request looks small, but together they change the agreed launch. Change control in development helps an online store owner see what additional work they are commissioning, what it displaces from the plan, and who authorized the spending.
The answer is neither to ban new ideas nor to approve every button at a meeting. Separate a proposal from permission to carry out the work: first describe the change, assess its consequences, choose an option, and only then update the tasks and budget. Below is a practical process for clients who want to change their store deliberately rather than discover the new scope on an invoice.
Record exactly how the new request differs from what was agreed
Without an agreed baseline, it is difficult to distinguish a new feature from an unfinished existing one. That baseline could be a version of the requirements specification, a list of features for a phase, or agreed tasks with examples of behavior. What matters is not the document's name, but being able to show what the parties actually agreed.
Keep the agreed development scope with its date, version, verification criteria, and exclusions. Do not rewrite the old version as though the new rule had always been there. The change should refer to the previous requirement, and the updated requirement should refer to the decision that introduced it.
The Association for Project Management describes project change control specifically as recording, assessing, and approving, rejecting, or deferring requests concerning an approved plan. For a store, this means something simple: a new priority must receive an explicit decision, rather than quietly becoming another promise.
Classify the request before discussing payment
The same message, “the discount is not working correctly,” can describe different situations. A task's title does not determine its commercial status. First compare the expected result with the agreed rule and what actually happens when reproducing the issue, and only then discuss how to account for the work.
| Situation | What to establish | How to record it |
|---|---|---|
| The implementation violates an agreed requirement | Which rule is not being met and how to reproduce the issue | A defect referencing the requirement and expected result |
| The business requests different behavior | What is being added to or replaced in the current scope | A change request with an impact assessment and decision |
| The agreed description allows different interpretations | Which materials support each party's understanding | An open question, a person responsible for clarification, and an agreed rule |
If the requirement stated that a dealer discount could not be combined with a promo code, but the site applies both, there is a basis for logging a defect. If the business now wants to allow them to be combined for a particular product group, that is different behavior. Where compatibility was not described at all, the situation should not automatically be called either a free fix or an additional feature.
A defect and a new requirement need different records, but payment arrangements are determined by the terms of your working relationship, not by the label in the task system alone. If there is a disagreement, retain the facts, identify the disputed part, and agree on further action. This management process does not replace a legal analysis of the contract.
Commission an impact assessment, not just programming
A useful change request answers the question “what should become different for the business?” “Add a field” is a weak description. “Allow the buyer to specify a separate invoice recipient without changing the delivery address” is already a basis for a substantive discussion.
Start with a short request record. It should include the initiator and reason, the current and desired rule, the buyers affected, related pages and systems, the desired point of use, and an example of the result. Add a reference to the original requirement version. Mark unknown conditions as questions rather than hiding them inside a confident estimate.
What the development team should provide
Ask for more than a price or a number of hours. You need a list of work, dependencies, changes to checks, estimating assumptions, and the impact on the current plan. If answering requires investigating the business management system, agree the boundaries of that investigation separately. Permission to estimate a task is not yet permission to implement it.
The estimate should cover rule analysis, the interface, server-side logic, integrations, data preparation, and testing where needed. For an external module, also check the license and ongoing support. Otherwise, an inexpensive button change may conceal a more costly redesign of data exchange.
At GL.ua (Glyanets), online store development covers requirements specification, design, programming, and integrations. A new feature is therefore worth discussing in terms of its full impact on the store, not just the screen where the buyer sees it. This is a way to frame a request for an estimate, not a claim about a universal price or timeline.
Separate effort from the calendar
Assessing the impact on budget and timelines must distinguish working hours from waiting time. A small modification may depend on a response from an ERP supplier or an accountant's availability. An additional developer will not remove that dependency. Ask the team to state what it can start now, what it is waiting for, and when the forecast needs to be reviewed.
Who can change priorities and authorize spending
A problem arises when the store manager has approved the interface, the finance manager has not approved the spending, and the contractor has already started work. Before starting, determine who clarifies business rules, who confirms technical feasibility, and who is entitled to change the budget or date. These roles may be combined, but authority must be clear.
Establish which changes the team can decide within the already agreed scope and which require new authorization. The triggers might be budget limits, a change to a business rule, or an impact on another system. No thresholds are equally right for every store: agree them to suit the way you work and the consequences of an error.
Keep a record of the authorized client's decision: the selected option, approved scope, financial terms, impact on the date, and the name and time of approval. A meeting link without a conclusion is weaker than a short, unambiguous record. “See whether it is possible” should not have the same status as “I approve implementation based on this estimate.”
Example: a new pickup rule midway through development
Consider a hypothetical store, not a GL.ua case study. Delivery by a carrier was agreed for the first phase. After a demonstration, the owner requests pickup from several stores, with location selection and confirmation that the order is ready. Calling this “one more delivery method” can obscure new stock availability rules and work for staff at the pickup location.
The change record first captures the desired result: the buyer selects an available location, sees the pickup terms, and receives a notification after preparation. Next, clarify whether stock figures for that specific location are required, who confirms readiness, and what happens if the product is unavailable. Until these questions are answered, a final estimate is premature.
The client should compare alternatives. Add the full scenario now, revising the budget and date. Replace another feature that has not yet been implemented with it after assessing dependencies. Or defer automation, retaining a separately agreed simpler process for the first phase. Each option entails not just development costs but also a workload for staff.
Swapping features does not mean a one-for-one exchange. Removing a recommendations block and adding pickup are not equivalent tasks merely because each occupies one line in the plan. Account for work already completed, new connections to the business management system, and the necessary checks. Record which feature has actually been removed and which has only been moved to the next phase.
The criteria for the new requirement must also change: the buyer cannot select an unavailable location; the readiness notification is sent after an authorized staff action; the collection method is saved in the order. These are examples for clarifying scope, not a complete pickup testing program.
Agile development does not remove the need to approve new scope
When working in short iterations, requirements naturally become more precise. This does not mean that every request can be added to the current phase without consequences. The Scrum Guide allows scope to be clarified and renegotiated with the Product Owner without endangering the Sprint Goal or reducing quality. This is a rule for organizing work, not permission for unlimited spending.
If the store is being developed at a fixed price, new behavior needs to be compared with the agreed boundaries. When billing for actual time spent, it is important to show where the budget is going and which work has changed priority. Neither model eliminates the need to agree decisions; the specific financial arrangements are determined by the parties' agreements.
Maintain one list of requests with clear statuses: proposed, clarification needed, estimated, approved, rejected, or deferred. Track implementation and verification separately from permission to start. For a deferred request, specify the condition for returning to it: data readiness, the next phase, or the owner's decision, rather than an indefinite “later.”
Test the process on one request before a major modification
Before introducing the new process, you do not need to move the entire correspondence history into a complex system. Take a real, unfinished change and check whether someone outside the daily discussion can understand its status. The sequence could be as follows:
- Find the agreed requirement and identify the specific difference in the new request.
- Confirm the classification or openly flag the disputed interpretation.
- Check the estimate against all affected work, dependencies, and checks.
- Obtain an explicit decision from a person with the necessary authority, including the financial terms.
- Update the plan, requirements, and tasks so that they refer to this decision.
- After implementation, check the result against the new rule and actual costs against the agreed accounting arrangements.
Keep control proportionate to the task
For a text change within the agreed interface, a task record may be enough. A new payment method, pricing model, or data exchange with the warehouse needs broader analysis. An excessive form for every small detail slows the team down; the absence of a record for a significant change makes spending and accountability unclear.
The practical result is traceability from a request to approved work. The client sees not only what changed, but why, under what conditions, and in place of what. For the next discussion, it is useful to keep the original estimate, clarifications, and the record of completion rather than reshaping the history to fit the final outcome.
Planning a new feature while your store is being built? Prepare the current rule, desired behavior, and budget or date constraints, and discuss online store development with GL.ua, including an assessment of this change. That way, the conversation starts with a concrete business decision rather than a promise to “add just a little more” without defined boundaries.
Just one step to your perfect website



