Use relevant costing, pricing, contribution, and operational evidence to support decisions.
Costing and pricing questions ask which financial information matters for a management decision. In a Day 3 short case, the goal is not to build a full cost system. The goal is to identify the decision, separate relevant from irrelevant costs and revenues, perform the calculation that supports the decision, and explain the operational consequences.
Relevant information changes the future decision. Sunk costs, unavoidable fixed costs, and arbitrary allocations often do not change the decision. Incremental revenue, avoidable cost, variable cost, capacity constraints, opportunity cost, quality risk, customer effect, and strategic fit often do. The answer should explain which facts matter and why.
| Decision type | Relevant focus | Recommendation should address |
|---|---|---|
| Special order | Incremental revenue, variable cost, capacity, and customer impact. | Accept, reject, price differently, or add conditions. |
| Make-or-buy | Avoidable internal cost, supplier price, quality, capacity, and risk. | Source internally, outsource, or use a hybrid approach. |
| Pricing | Cost floor, margin target, market constraints, capacity, and strategy. | Price, minimum price, or negotiation approach. |
| Product mix | Contribution per constrained resource and strategic constraints. | Prioritize products or remove bottlenecks. |
| Process decision | Cost savings, implementation cost, quality, timing, and staff impact. | Implement, delay, test, or reject the change. |
A relevant cost differs between alternatives and affects the future. A sunk cost has already been incurred and should not drive the decision. An allocated cost may be useful for reporting or performance tracking, but it may not be relevant if it will not change. A fixed cost may be relevant only if it is avoidable or if capacity constraints create an opportunity cost.
The response should classify costs in the context of the decision. Do not simply label all fixed costs irrelevant or all variable costs relevant. A fixed cost can be relevant if accepting a project requires new equipment rental. A variable cost can be irrelevant if already committed and unavoidable. Context controls the classification.
When the case gives incomplete cost data, state the assumption and calculate what can be supported. Do not invent missing cost categories. Explain what information would be needed before management acts.
flowchart LR
A["Management decision"] --> B["Alternatives"]
B --> C["Future cash flows"]
C --> D["Avoidable or incremental items"]
D --> E["Capacity and opportunity cost"]
E --> F["Relevant result"]
F --> G["Recommendation with operating caveat"]
Use the map to keep the calculation connected to the choice. A cost is not relevant because it appears in the case; it is relevant because it changes between alternatives.
| Cost or revenue item | Usually relevant when… | Usually not relevant when… |
|---|---|---|
| Variable production cost | Volume changes and the cost will be incurred for the option. | Inputs are already committed and cannot be avoided. |
| Fixed cost | The decision adds, removes, or avoids the fixed cost. | The same fixed cost remains under all alternatives. |
| Allocated overhead | The allocation reflects an avoidable resource use. | The allocation is arbitrary and total overhead will not change. |
| Sunk cost | Rarely relevant; only useful as context for risk or behaviour. | It has already been incurred and cannot be recovered. |
| Opportunity cost | Capacity used by one option prevents a better alternative. | There is idle capacity and no sacrificed alternative. |
| One-time implementation cost | The option requires setup, training, transition, or exit spending. | It is unrelated to the alternatives being compared. |
This classification should be explained in words. A short Day 3 answer can say, “The allocated rent should be excluded because total rent will not change, but overtime is relevant because accepting the order requires additional labour cost.”
Contribution analysis is useful when the decision depends on incremental profit or scarce capacity. A positive contribution may support accepting an order, but only if capacity exists, quality can be maintained, and the order does not damage regular pricing or customer relationships.
Capacity constraints change the calculation. If machine hours, labour hours, storage, cash, or supplier availability is limited, contribution per constrained unit may be more useful than contribution per unit sold. The response should identify the constraint and explain how it affects the choice.
Do not stop at the number. If a special order has positive contribution but uses capacity needed for higher-margin regular sales, accepting it may still be poor advice. If outsourcing saves cost but increases quality or supply risk, the recommendation should mention that risk.
When capacity is constrained, the best option is not always the highest contribution per unit sold. The useful measure is contribution relative to the constrained resource.
| Constraint | Better analysis | Recommendation focus |
|---|---|---|
| Machine hours | Contribution per machine hour. | Prioritize products that use scarce machine time best. |
| Labour hours | Contribution per labour hour and overtime feasibility. | Balance margin with staffing, training, and quality. |
| Materials or supplier supply | Contribution per scarce input unit. | Allocate scarce input to the best-supported order or product. |
| Storage or delivery capacity | Contribution after storage or logistics constraint. | Avoid orders that create bottlenecks or customer service risk. |
| Cash availability | Contribution timing and working-capital need. | Consider whether the option is profitable but cash-constrained. |
If there is no constraint, contribution per unit may be enough. If there is a constraint, state the constraint before recommending.
Pricing advice should balance cost, market, capacity, customer expectations, and strategy. A minimum price may be based on relevant cost, but a recommended price may also consider demand, brand position, competitive response, customer relationship, and long-term margin.
When the case asks for pricing, clarify whether the goal is to set a minimum acceptable price, evaluate a proposed price, or recommend a pricing strategy. A cost-based price may be insufficient if the market will not accept it. A market-based price may be dangerous if it does not cover relevant costs or creates precedent for regular customers.
Do not confuse the price floor with the business recommendation.
| Price concept | What it answers | What it does not answer |
|---|---|---|
| Relevant-cost floor | The lowest price that avoids incremental loss before qualitative factors. | Whether the price protects brand, capacity, or customer expectations. |
| Target-margin price | The price needed to reach a margin goal. | Whether customers will accept the price or competitors will respond. |
| Market-based price | What the market may bear. | Whether the entity covers relevant cost or preserves strategy. |
| Special-order price | Whether an unusual order is worth accepting. | Whether the price should become a normal customer precedent. |
| Negotiation range | The zone between minimum acceptable price and desired price. | Which non-price terms should be required. |
Management accounting is not only arithmetic. Operational constraints often change the recommendation. Supplier reliability, employee training, bottlenecks, quality control, customer service, inventory space, technology, and implementation timing may all matter.
Use qualitative facts when they affect the decision. If outsourcing saves money but exposes the company to unreliable delivery, state that risk. If a low-price order fills idle capacity without affecting regular customers, explain why the qualitative concern is lower.
| Pitfall | Better approach |
|---|---|
| Including every cost in the decision. | Include costs and revenues that differ between alternatives. |
| Treating allocations as automatically relevant. | Ask whether the allocation changes if the decision changes. |
| Ignoring capacity constraints. | Use contribution per constrained resource where relevant. |
| Ending with contribution only. | Interpret the result and recommend an action. |
| Ignoring quality and customer effects. | Add qualitative constraints that change the decision. |
Use a decision-relevant data-result-recommendation pattern. Name the decision, identify the relevant costs and revenues, calculate the result, then recommend the action with any operational caveat. This gives management a usable answer instead of a disconnected calculation.
Costing and pricing answers are strongest when they show both discipline and business sense: the number supports the recommendation, and the recommendation respects operational reality.