- A sales mix is each product's share of total revenue, so stock targets should follow those shares.
- A 5:3:2:1 ratio gives four products relative shares of 5, 3, 2 and 1.
- Margin matters: the best mix depends on how much profit each product earns, not only on its share of sales.
- In Odoo's average-price example, a product starts at zero units and $0, so its stock has to be built up from records.
Plan stock by each product's share of the sales mix, not by the business total. In the OpenStax example the product mix is 5:3:2:1, so four products take 5, 3, 2 and 1 parts in that ratio, and the first product is the largest share.
Net takeaways
What a sales mix means for stock on hand
A sales mix is the set of proportions in which a company sells its products. The OpenStax managerial accounting chapter defines it plainly: "A sales mix represents the relative proportions of the products that a company sells—in other words, the percentage of the company's total revenue that comes from product A, product B, product C, and so forth" (OpenStax, section 3.4). That definition changes the planning question. Instead of asking how many parts you sold in total, you ask what share of your sales each product represents.
For a small service firm, the products might be parts, consumables, or parts bundled with labor. Whatever the list, the mix is a set of percentages that add up to the whole business. A product that accounts for a large share of revenue deserves more of the shelf space, the reorder budget, and the attention of whoever plans the van loads. A product that brings in only a sliver can be kept lean.
The definition also shows that the shares are not fixed. Mixes shift as jobs change, seasons turn, and customers come and go. Treat the mix as a planning figure you review on a schedule, not a number you memorize once.
A workable habit follows from this. At regular intervals, or whenever your job mix visibly changes, write down each product's share of revenue and rank the products. Then compare that ranking with what is physically on hand. Where the two disagree, you have found a stock problem worth fixing. Where they agree, your reorder levels are probably in roughly the right place.
Reading a 5:3:2:1 ratio as four product shares
The OpenStax example states its mix as a ratio: "This means that our product mix is 5:3:2:1, as shown in Figure 3.11" (OpenStax, section 3.4). A ratio is a compact way to hold shares. Each product's share is its number in the ratio divided by the total of all four numbers, so the ratio tells you the relative size of every line at once.
The source does not name the four products, so the table below labels them by their position in the ratio.
| Product (ratio position) | Parts in ratio |
|---|---|
| Product A | 5 |
| Product B | 3 |
| Product C | 2 |
| Product D | 1 |
Product A is the largest share of sales in this mix, and Product D is the smallest. The four shares together account for all of the sales in the ratio, so no product is left out of the plan.
For stock planning, this means the ratio gives you a relative order. Product A should generally be held in larger quantity than Product B, and Product B than Product C, and so on. The ratio does not tell you the actual quantities, because those depend on lead times, package sizes, and how fast each product moves. What it does give you is a fixed set of proportions to check your counts against every time you review the mix.
Keep the ratio as the reference point. When one product's share grows, the other shares shrink to make room, so a change in one line needs a glance at the rest.
A worked vinyl example: 5, 3 and 2 parts
The second OpenStax example moves from numbered positions to named products. It describes the sales mix for a vinyl seller: "The sales mix for West Brothers is 5 ft2 of builder grade to 3 ft2 of architectural grade to 2 ft2 of restoration grade vinyl (a ratio of 5:3:2)" (OpenStax, section 3.4). Here the three options sit side by side, and each one has its own ratio figure.
| Vinyl grade | Ft2 in the ratio |
|---|---|
| Builder grade | 5 |
| Architectural grade | 3 |
| Restoration grade | 2 |
The three grades together make up the whole of the ratio, so each row reads as a part of that whole. Builder grade is the largest line and restoration grade the smallest. A dispatcher planning stock for this mix would therefore expect builder grade to be the heaviest line, while still keeping restoration grade on hand, since it is part of what customers buy.
The useful habit is to convert the ratio into shares before you order. A ratio like 5:3:2 is easy to misread as three equal-sized needs, but comparing the parts makes the difference visible at a glance. When you reorder, you can check the proportion against the table: if builder grade is taking more of your stock than the ratio allows, the mix or the buying has drifted from the planned ratio.
The example also shows that a line can be small and still matter. Restoration grade is the smallest part of the ratio, yet it is a real share of sales that deserves a deliberate stock level rather than whatever is left over after the other two.
Why margin decides which shares to keep
A share of sales and a share of profit are not the same thing. OpenStax explains why the difference matters: "Sales mix is important to business owners and managers because they seek to have a mix that maximizes profit, since not all products have the same profit margin" (OpenStax, section 3.4). The goal, in other words, is not simply to sell the biggest share of anything. It is to hold the mix that earns the most profit.
For stock on hand, this changes the ranking. Two products can have similar sales shares while earning very different amounts on each sale. If one carries a fatter margin, it may deserve a bigger stock level than its share of sales alone would suggest, because each unit kept on the shelf and sold earns more for the firm. The reverse also holds. A product with a large share of sales but a thin margin may need careful buying, so that its volume does not tie up cash without returning much.
The practical step is to put margin next to share in the same review. For each product, note its share of sales from the mix and its margin on each unit sold. Then ask two questions. Is the stock level matched to the share? Is the stock level matched to the margin? When the answers conflict, the margin should usually settle the decision for products that are otherwise similar in demand.
Margin is also a reason to revisit the mix after prices change. A supplier cost increase can shift which products earn the most, even when customer demand stays the same. The shelf should reflect that shift, not last year's ranking.
Starting a new item at zero units
Every product begins somewhere, and for a new item the starting point is nothing. The Odoo documentation on average-price valuation sets up its example from that point: "Initially, the product stock is 0, so all values are $0" (Odoo 18.0 documentation). Zero units and a value of $0 are the natural opening balance for a product that has not yet been received.
This matters for planning because a new item has no history. Its share of the mix is a forecast, not a record, and its stock value does not exist until units arrive. A firm that adds a new part to its catalog should therefore record its verified physical count as the opening quantity, using zero only when no units are actually on hand, so that the first purchase starts an honest count.
The zero start also prevents a common error. If a new product is entered with an estimated stock figure instead of the actual count, the firm may believe it holds stock it does not have. A dispatcher who promises the item to a customer on that basis will find the shortfall at the worst moment. Starting from zero keeps the record tied to physical units.
Once the opening balance is set, the item can be placed in the mix. Its planned share should be written down at the same time, so that the first review compares actual sales against a target the firm chose in advance.
Tracking a table from zero units in stock
The Odoo example makes the zero start concrete with a single product: "In this example, a company starts with zero units of a product, table, in stock" (Odoo 18.0 documentation). The table below lists the three figures the example gives at that starting point.
| Measure at the start | Figure in the example | Source wording |
|---|---|---|
| Units of the product in stock | 0 units | "starts with zero units of a product, table, in stock" |
| Product stock, initially | 0 | "the product stock is 0" |
| Value of the stock | $0 | "all values are $0" |
With those three figures recorded, the firm has a clean base. Every later movement, whether an incoming delivery, a sale, or an adjustment, is then a change from a known zero rather than from an estimate.
For a small service firm, the routine is short. Record the opening count for each new item. Log each incoming delivery as it arrives and each unit that leaves on a job. At the review point, compare the running count with the planned share from the mix. If a product's count is growing while its share of sales is shrinking, the reorder level is set too high. A count falling well below that target suggests the item is selling faster than planned.
The zero start is a discipline as much as a number. Each count begins from what was physically verified, and each change is written down. That habit is what lets a dispatcher trust the shelf when deciding what to reorder next.
Low-stock alerts at a minimum level
A minimum-level alert is the simplest trigger to set. You choose a quantity, and the system tells you when the count reaches that quantity or falls below it. Sortly's quantity alerts documentation gives this example: "For example, choose At OR Below Min Level and enter 5 to be alerted when the quantity is 5 or fewer" (Sortly, Quantity Alerts). The alert fires at 5 and at every count below it.
For a service firm, this option works best for items you count on the shelf, where an empty bin is the real problem. A dispatcher who sees the alert knows the item is at or near the level the firm chose, and can reorder before a job depends on it. The alert is only as good as the minimum you set. A minimum taken from a guess will either fire too late, leaving the firm short, or fire so often that people stop reading it.
The alert is also a yes-or-no signal. It tells you the quantity has reached a point, not how much to order. The reorder amount still depends on your job plans and the package sizes you buy. Set the minimum from your own usage history rather than copying the example's 5. The source explains how the alert works, not which number suits your items. Once you choose a threshold, write it next to the item's planned share from your sales mix, so the alert and the mix are reviewed together.
Counting stock on order before you reorder
A minimum-level alert looks only at what is on the shelf. An item with a delivery already in transit can trip it even though the shortage is covered. Sortly describes a second option that counts incoming stock: "For example, if you have 3 chairs in stock and 2 more on order, set an alert for Greater than OR Equal 5 to be notified once the total reaches 5" (Sortly, Quantity Alerts).
The arithmetic is simple. Three in stock plus two on order makes five, and the alert fires when the total reaches five.
| Count in the example | Figure | Meaning |
|---|---|---|
| In stock | 3 | Units on the shelf now |
| On order | 2 | Units expected but not yet received |
| Total compared with the alert | 5 | Stock plus on order, against an alert value of 5 |
The alert counts units on order toward its threshold, so an item already on the way may not trigger a new alert. This matters most when a part is reordered often while earlier orders are still arriving. The trade-off is that the total can stay above the alert while the physical shelf is nearly empty. A dispatcher still needs to check what the next job requires today, rather than trusting the total to show what is usable.
Safety stock measured against projected inventory
Safety stock is a buffer kept above what you expect to need. The question is what that buffer is compared against. Microsoft's Business Central documentation on reordering policies answers it: "The planning system uses projected available inventory when monitoring the safety stock level" (Microsoft Learn, Design details - Handling reordering policies). In that system, the safety check uses projected inventory, not only the units counted at that moment.
For a small firm, the lesson is about the comparison, not the software. A shelf count shows what you hold now. A projected figure looks ahead, so it can show whether you will still be above your buffer once expected movements take place. A buffer that looks healthy on the shelf may already be short once the stock arriving and the stock already committed are taken into account. That makes the projected view a sharper question than a count taken on one morning: will we still be covered after the planned activity?
The projected check suits items where you keep a formal safety level and records arrive on a regular schedule. It is less useful for items with no buffer target, where a simple minimum-level alert does the job with less upkeep.
Which one should you pick?
The three approaches answer different questions, so the right choice depends on what your firm needs to know. A minimum-level alert answers "is the shelf low right now?" It suits items that are counted physically and where an empty bin stops a job. An alert that counts stock on order answers "is the total covered?" It suits items reordered while earlier orders are still in transit. A safety-stock check against projected inventory answers "will we stay above our buffer?" It suits items with a planned buffer and steady records.
For most small service firms, a reasonable approach is a minimum-level alert on the fast-moving parts a job cannot do without, plus the on-order count where repeat ordering is a problem. Reserve the projected check for items where you hold a formal safety level. Avoid switching methods for the same item partway through, or the alerts will stop matching each other and nobody will know which one to trust.
Comparing alert triggers and safety stock side by side
The table below sets the three approaches against each other, using only the figures the sources give.
| Approach | What it compares | Figure from the source |
|---|---|---|
| At OR Below Min Level | Units on the shelf against a minimum | Alert when the quantity is 5 or fewer |
| Greater than OR Equal | Stock plus units on order against a target | 3 in stock plus 2 on order reaches the alert at 5 |
| Projected available inventory | Safety stock against projected inventory | No figure given in the source |
The first two rows use the same kind of threshold but count different stock. The third differs in its basis: it checks projected inventory rather than a single count. When you choose a method, you are choosing what the trigger counts, not only how large the number is.
Related guides: Bulk order sales tax: 3 checks before billing · Bundled maintenance plan sales tax: 8 steps to check · Climate normals: 2 periods to compare for dispatch planning.
Reader questions
What is a sales mix? It is the relative proportions of the products a company sells, meaning "the percentage of the company's total revenue that comes from product A, product B, product C, and so forth" (OpenStax, section 3.4).
What does a 5:3:2 ratio mean for vinyl stock? It means 5 ft2 of builder grade for every 3 ft2 of architectural grade and 2 ft2 of restoration grade (OpenStax, section 3.4). Builder grade is the largest part of the mix.
Does a low-stock alert count units on order? It depends on the setting. A minimum-level alert looks at what is on the shelf. Sortly's "Greater than OR Equal" option counts stock plus units on order, so 3 in stock and 2 on order reaches a total of 5 (Sortly, Quantity Alerts).
What number should I set for a minimum-level alert? Sortly's example uses 5, alerting when the quantity is 5 or fewer (Sortly, Quantity Alerts). The source shows how the alert works, not what number suits your items, so set yours from your own usage.
Does a new item start with stock on hand? Not in Odoo's example, which states: "Initially, the product stock is 0, so all values are $0" (Odoo 18.0 documentation).
What does a safety-stock check compare against? Microsoft's documentation says the planning system "uses projected available inventory when monitoring the safety stock level" (Microsoft Learn, Design details - Handling reordering policies).
Why does margin matter when planning stock? Because "not all products have the same profit margin," and owners seek a mix that maximizes profit (OpenStax, section 3.4). Stock levels should reflect margin as well as share.