SCPro common mistakes
SCPro · Understand the traps and how to avoid them.
On strategy items, the candidate evaluates each option against general 'best practice' (e.g., 'always collaborate', 'always reduce inventory') instead of the competitive priority the scenario explicitly states, and selects the option that sounds most modern.
Habit from general business reading and from exams that reward universally 'good' answers; the stem's stated priority (cost leadership, responsiveness, risk mitigation) gets skimmed as background rather than treated as the decision criterion.
What to do instead
Before reading the options, write down the stated competitive priority and the one or two performance dimensions it implies. Then eliminate any option that improves a dimension the scenario does not value, even if it is a legitimate practice elsewhere.
The candidate answers an S&OP scenario with an action belonging to a different step of the cycle - for example, prescribing an executive reconciliation decision when the stem is asking what happens in the demand review, or collapsing S&OP into 'the forecasting meeting'.
S&OP is remembered as a single monthly meeting rather than a sequenced cycle with distinct inputs, owners, and outputs; the wording of the options is plausible at any step, so the step boundary is never checked.
What to do instead
Memorise the cycle as input -> owner -> output for each step (demand review, supply review, reconciliation/financial alignment, executive review). For every option, name the step it belongs to; only options from the step in the stem survive.
The candidate treats lowest purchase price as the correct sourcing answer, or defaults to 'award to the lowest bidder' when the scenario mentions quality problems, long lead times, or warranty exposure.
Price is the only number visible in the stem, so it becomes the anchor; total cost of ownership requires adding freight, duty, quality, inventory carrying, and failure costs that the candidate does not think to construct.
What to do instead
Force a TCO build before choosing: list the cost buckets the stem actually supplies (price, freight/Incoterms, duty, defects/rework, lead-time inventory, switching cost) and sum per supplier. If an option names a cost the stem supplies and another option ignores it, the ignoring option is wrong.
The candidate applies a single relationship style to every supplier - usually 'build a strategic partnership' - regardless of the item's spend and supply risk, or assigns a partnership approach to a leverage item and arms-length competitive bidding to a bottleneck item.
Relationship language is emotionally appealing and the candidate has not practised classifying the item first; the quadrant logic is known as a diagram but not as a decision rule.
What to do instead
Classify before answering using two axes the stem gives: spend/importance and supply risk/availability. Then apply the fixed mapping - strategic: partnership and joint development; leverage: competitive bidding and volume leverage; bottleneck: secure supply, buffer, and qualify alternatives; non-critical: simplify and automate.
The candidate selects a contract type or incentive structure by 'fairness' instinct rather than by who can best control the risk - for example, recommending a firm-fixed-price contract for development work with high technical uncertainty, or a cost-reimbursable contract for a mature, well-specified commodity.
The candidate evaluates the contract from the buyer's desire for cost certainty rather than from risk-bearing capability, and does not check whether the specification is stable enough for a fixed price to be meaningful.
What to do instead
Run a two-question test: is the requirement well-defined, and can the supplier control the cost outcome? Well-defined plus controllable -> fixed price. Uncertain or buyer-controlled -> cost-reimbursable or time-and-materials with incentives. Match the answer to that test, not to which party you would prefer to hold the risk.
The candidate plugs numbers into EOQ, reorder point, or safety-stock formulas using mismatched time units (annual demand with a weekly holding cost, or daily demand with a monthly lead time) and then picks the closest-looking option.
The formulas are recalled as shapes rather than as dimensionally consistent equations, and the urge to finish the calculation fast under exam time pressure suppresses the unit check.
What to do instead
Before computing, write the unit of every input and every output next to it, and convert everything to one period (usually annual for EOQ cost terms, lead-time period for reorder point). Sanity-check the answer's magnitude - a reorder point larger than annual demand means a conversion error.
The candidate applies forecasting-and-safety-stock logic to dependent-demand items in an MRP environment, or conversely applies MRP explosion logic to independent end-item demand, and picks the option consistent with the wrong demand type.
Forecasting is learned first and dominates recall; the stem often mentions a forecast, which triggers forecast-driven answers even when the item is a component whose demand is derived from a parent schedule.
What to do instead
Classify the item before answering: if demand is derived from a parent item or a schedule, it is dependent and is calculated by BOM explosion - no independent forecast and no independent safety stock. If it is an end item sold to the market, it is independent and forecast-driven. State the classification in one word, then answer.
The candidate answers a scheduling or master-production question as if capacity were unlimited - accepting a plan because the material is available and due dates line up, without checking that work-centre hours or run time fit the horizon.
Material availability is the visible constraint in the scenario, and infinite-loading assumptions are the default mental model; capacity is treated as a later 'execution' problem rather than a feasibility filter.
What to do instead
For any plan or MPS option, compute a rough capacity check: required hours = quantity x run time + setups, compared to available hours in the period. If the option requires overtime, outsourcing, or a missed date that the stem forbids, it is infeasible regardless of material availability.
The candidate assigns Incoterms responsibilities from memory of a single familiar term, giving the buyer or seller the wrong obligation - for example, treating an F-term as if the seller pays main carriage, or assuming insurance is always the seller's duty.
The three-letter codes are learned as a list rather than as a structured progression of transfer points, and the exact cost/risk split is rarely rehearsed under time pressure.
What to do instead
Recover the structure rather than the list: E (buyer does everything from seller's premises), F (buyer arranges main carriage), C (seller pays main carriage but risk passes on shipment), D (seller delivers at destination). Then apply the specific term's two data points - point of delivery/risk transfer and who pays main carriage and insurance.
The candidate computes or interprets customer service using the wrong fill-rate definition - reporting a case fill rate as an order fill rate, or treating cycle service level (probability of no stockout per cycle) as equivalent to a fill rate.
The metrics are used interchangeably in practice and differ in the denominator and in what counts as 'filled'; the candidate recognises the term and stops reading which unit of measure the stem defines.
What to do instead
Anchor on the denominator before computing: case/unit fill rate = units shipped / units ordered; line fill rate = order lines filled completely / lines ordered; order fill rate = orders shipped complete / orders placed; cycle service level = probability of no stockout in a replenishment cycle. Perfect-order metrics multiply on-time, complete, damage-free, and documentation accuracy - do not report a single component as a perfect order.