An item can sell frequently and still contribute less margin than expected. When sales, inventory, and accounting teams review activity separately, they may miss an important distinction: the selling price may no longer reflect the relevant cost, or the item data and setup may need to be checked.
OrderTechERP brings sales, orders, inventory, accounting, reporting, and branches into one operating space. This gives teams a way to move beyond the question, “Which items are moving?” and ask a more useful one: “Which sold items should we review first because their margin is low?”
The purpose of the review is not to make an automatic pricing decision. It is to create a prioritized checklist for validating the price, cost, and item setup within the company’s configuration and team permissions.
What is a low-margin item?
Operationally, margin is the difference between the value of a sale and the cost associated with the item. A low margin may result from a low selling price, a cost change, or item data that does not reflect how the company currently records cost. The resulting list should therefore be treated as a review queue, not as a confirmed list of errors.
It helps to separate three questions:
- Was the item actually sold? Start with sales and order activity rather than an inactive item list.
- Is the difference between selling value and cost low? Compare the sale with the available cost data according to the company’s setup.
- Is the cause commercial or data-related? The issue may be a price that needs review, a cost that is not current, or an item setup that requires validation.
Build one reviewable list
Instead of having each team maintain a separate file, bring the items requiring attention into a shared operating workflow. Use sales and order data to identify items that appeared in transactions, then relate them to the available inventory and accounting cost information within the company configuration.
The list does not need to be complicated. For each item, it can include:
- The item name or identifier.
- The period in which the sales occurred.
- The recorded sales value or quantity.
- The cost used for the review.
- The calculated or observed margin.
- The relevant branch or operating context, when that information is available and the team has permission to view it.
- The next status: check selling price, check cost, check item setup, or no action for now.
Prioritize instead of reviewing everything at once
A review may produce dozens or hundreds of items. Teams therefore need a clear prioritization method rather than jumping straight to price changes. A practical starting point is to focus on items that have both actual sales activity and a low margin, then add general operating considerations such as how often the item appears, whether the observation differs by branch, or how important the item is to current orders.
This is not a ready-made pricing policy. It is a way to decide where a qualified team should begin checking. For example, items can be grouped as follows:
- High-priority review: a sold item shows a clearly low margin and requires a timely explanation.
- Medium-priority review: the sales and cost information needs comparison, or the item appears different across branches.
- Monitor: there is not enough reliable information yet, or no immediate decision is needed before validation is complete.
Check the selling price before proposing a change
A low margin does not automatically mean the selling price should increase. The sales or commercial owner should first confirm that the recorded price is the intended price for the item and that the review covers the correct period and transaction. The team should also account for cases where the price differs by branch or order context, if those differences are part of the company’s configuration.
Any possible change should then go to the appropriate owner for review. Document the question first: does the recorded selling price reflect the current commercial decision? If the answer is unclear, keep the item in a validation state rather than changing data based on an automated conclusion.
Check cost and item setup
The selling price may be correct while the cost used in the review is outdated or unsuitable for the company’s context. This is where inventory and accounting teams should check the cost source and recording approach according to the approved company configuration, without assuming an accounting method or policy that has not been defined.
Review the item’s underlying data as well: its unit, classification, inventory relationship, and any setup that affects how sales or cost are read, subject to the team’s permissions. If the issue is data-related, correct the source or setup through the appropriate approval path, then repeat the review. Changing the selling price to compensate for a data problem can create a second problem.
Use the operational assistant for the next step, not as a substitute for review
OrderTechERP includes an AI-powered operational assistant that connects an order and its data to the next step according to the company’s configuration and team permissions. In this workflow, its operational guidance may help direct a case toward “check selling price,” “check cost,” or “review item setup” when the available data and configuration support that direction.
That guidance is not a final decision. Its usefulness depends on data quality, the completeness of the company setup, and the permissions assigned to the team. A responsible owner should review the information behind the observation and confirm the action before making any change.
Assign clear responsibilities
- Sales: confirm that the selling price reflects the approved commercial decision.
- Inventory: check item data, quantities, and the operating context connected to inventory.
- Accounting: review cost information according to the company’s configuration.
- Reporting: present the review queue clearly, maintain its priority, and track its status.
- Branches: explain relevant operating or price differences visible in the data they are permitted to review.
- Orders: provide the transaction context in which the item appeared, so the result is not interpreted separately from the original order.
A practical conclusion
Reviewing low-margin sold items starts by connecting sales with cost, but it should not end with a list. The practical value comes from turning that list into a clear validation priority: should the team check the selling price, the cost, or the item setup?
OrderTechERP provides a shared operating space that connects sales, orders, inventory, accounting, reporting, and branches. Its operational assistant can connect data to a next step within the company’s configuration and team permissions. The quality of the result still depends on data quality, sound setup, and appropriate human review. In this way, a low margin becomes a useful signal for investigation—not an automatic reason to change a price.

