Cascade ordering software: supplier rules, fallback choices and basket checks

What is a medicine ordering cascade?

A purchasing cascade follows a sequence of eligible suppliers or decision rules. It might prefer a contracted wholesaler, try another when stock is unavailable and hold a line for review when neither meets the practice’s rules. Price-led routing instead begins by comparing eligible quotations. A platform may combine the two approaches.

Choosing the first supplier with stock can be useful for continuity, but it is a different objective from choosing the lowest total acquisition cost. The right rule depends on the practice’s terms, stock needs, delivery timetable and approval process.

Supplier routing should start with a verified product

The fallback must still be the requested medicine. A supplier sequence must not quietly change a specified brand, release formulation, device, concentration or pack quantity. If no exact eligible product is available, record the exception and ask for review rather than treating a similar name as a successful match.

Read exact medicine pack matching before defining automatic supplier rules. The list of connected wholesalers and the list of products verified for purchase are separate things.

Work out the whole-basket effect

Consider an illustrative order with £92 already in a supplier basket, a £100 delivery threshold and £8 delivery below the threshold. An eligible pack costs £10 there and £8 from another supplier. Buying the £10 pack brings the first basket to £102; buying it elsewhere leaves £92 plus £8 delivery plus £8 for the pack, totalling £108, assuming no additional charges. The higher line price produces a lower combined cost in this example.

That calculation does not justify buying an unnecessary pack to reach a threshold. It compares two ways of buying stock already required. Use the basket threshold calculator with your actual terms and confirm any scheme exclusions.

Rules to discuss with your dispensary team

• Product eligibility: exact product, acceptable pack quantity and any brand restrictions.
• Account evidence: current price, available quantity and when it was checked.
• Commercial rules: supplier priority, delivery charges, minimum values and valid scheme terms.
• Exceptions: uncertain matches, unavailable items, unexpected price changes and quantity limits.
• Approval: who can accept exceptions and who submits the final order.

Scheme comparisons should use current manufacturer discount eligibility, rather than applying a blanket rebate to every pack.

Suggested, selected, staged and ordered are different states

A suggested supplier is a recommendation. A selected line is a buying decision recorded in the application. A staged basket is a plan prepared for the supplier workflow. A verified supplier basket contains the actual items and quantities at that supplier. An order requires confirmation from the supplier.

Ask an ordering platform to show these states separately. If a supplier rejects a line, the workflow should preserve the reason and distinguish a safe retry from a completed purchase. A positive counter in a buying screen is not a supplier order confirmation.

How PharmShop fits into the decision

PharmShop’s buying workflow brings exact-pack evidence, connected supplier searches and basket planning together for review. Use it to evaluate supplier decisions and purchasing costs. Do not infer a fully unattended cascade service from this guide: verify current routing, staging and ordering capabilities against the suppliers you actually use.

Its scope is procurement support. It does not authorise clinical substitutions, replace a PMR or guarantee medicine availability. A supplier’s current account terms and final order response remain essential evidence.

Questions to ask during a demonstration

Try an unavailable pack, a brand-specific request, a partial quantity and an order close to a delivery threshold. Ask which rule selected the supplier, what evidence was retained and what happens if the supplier basket differs from the plan. The software comparison checklist sets out a repeatable evaluation.