Find the kind of change the request actually needs

The same complaint can lead to very different work. Customers who ask about the wrong product might need clearer identification, a corrected enquiry reference or a different staff review process. Start with the observed gap and compare interventions that could close it.

When the information is present but unclear

A content improvement may be enough when the product facts are correct but hard to interpret. A pack quantity might be hidden in an image, or a button might imply an accepted order when it only sends an enquiry. The change should be tested by asking a reader to explain the item or next step.

The catalogue and bilingual website services address these problems with content structure and meaningful language review. If the underlying record is wrong, clearer wording alone will not repair it.

When an existing capability is not being used well

A current system may already support a useful filter, field or notification. A focused configuration change can be considered when it expresses the business rule clearly and remains maintainable. The account owner needs to confirm the available product capability and access.

Check the result with the operator who will use it. A workaround that only one administrator understands may shift the problem instead of resolving it. Documentation and an agreed owner are part of evaluating whether the smaller intervention is sustainable.

When the behaviour contradicts the intended process

A reproducible fault calls for investigation. An amended quantity appearing correctly in storage but incorrectly in a staff view suggests a different boundary from a quantity never recorded at all. Software repair follows that evidence before committing to a change.

The finding should explain what can be demonstrated, which dependency remains uncertain and how the relevant neighbouring tasks will be checked. A narrow repair can preserve useful parts of the application without pretending that every limitation has been addressed.

When the process needs a relationship the system cannot represent

New development may be appropriate when staff cannot connect revisions, customer questions and acceptance decisions within the existing arrangement. Order workflows and staff views can make those relationships explicit.

Define a complete first exchange and its exception. Identify what must remain available from the current system and who will operate the new feature. The repair-or-replace guide includes transition work in the comparison. Describe the gap, and the relevant options can be reviewed against your actual circumstances.