The Ops Community ⚙️

Victoria Hodgson
Victoria Hodgson

Posted on

Discount mistakes that erode Michigan dispensary margins

An automatic promotion reduces an item’s price, then a budtender adds a manual discount to resolve a customer question. The receipt looks ordinary. The final price, however, is lower than the manager intended when approving the offer.

For a Michigan dispensary, the problem may lie in the interaction between promotions, staff overrides, product costs, and reporting. Reviewing those connections gives managers something specific to correct.

When evaluating Indica Online cannabis software in Michigan, bring your actual discount scenarios to the demonstration. Ask the vendor to show how permitted combinations, restricted overrides, and partial refunds appear in transaction records. Compare the result with your written promotion rules.

Letting promotions combine without a clear policy

A product offer, a cart promotion, and a customer-group discount can each have a reasonable purpose. Allowing them to combine without reviewing the result can produce an unintended selling price.

Write down which combinations are allowed and which should be blocked. Identify exclusions, including products already carrying a reduced price.

The Shopify documentation on combining discounts illustrates why the details matter: its platform distinguishes discount classes, application order, and manual adjustments. Use those distinctions as questions for your own POS, rather than assuming another platform follows the same rules.

Check the calculation order, not just the labels

Ask what amount each discount uses as its calculation base. Determine whether a later discount applies to the original price or an already reduced subtotal.

Approve the resulting price alongside the promotion rules. Save a test receipt showing the intended calculation so staff and managers can recognize an unexpected result.

Treating manual overrides as harmless exceptions

A manual adjustment may solve a service issue while adding another reduction to an already discounted purchase. If employees cannot see the existing adjustments clearly, they may not realize what they are adding.

Define acceptable reasons for overrides, who can approve them, and what record should explain the decision. Check whether your proposed configuration supports those controls.

An exception process should also be usable during a shift. If approval is difficult to obtain, investigate the workflow before broadening access.

Distinguish discounts, credits, and payment methods

A smaller amount due does not necessarily mean another discount was applied. Review how your system treats loyalty benefits, customer credits, and payment methods actually used by the store.

Follow each component through the transaction and reporting. Avoid deducting an amount again during analysis when the reported selling price already reflects it.

Setting sale prices without reliable product costs

A promotion reviewed against an outdated cost can look healthier than it is. Before approving an offer, confirm where the product cost comes from and whether it represents the inventory being sold.

Inspect unit definitions too. A cost associated with a shipment, package, or individual item needs to be interpreted correctly before it supports a pricing decision.

A margin report is only as useful as its inputs. Resolve missing or uncertain costs before treating a displayed margin as evidence that an offer meets your objective.

Keep margin and markup separate

Gross margin measures sales revenue minus cost of goods sold relative to sales revenue. Markup measures that difference relative to cost. Confusing them can lead staff to approve a price using the wrong benchmark.

Also establish which costs your report includes. Gross margin does not represent the business’s final profit after every operating expense.

Leaving expired or overly broad promotions active

An offer can continue reducing prices after its intended purpose ends. Broad category rules may also pull newly added products into a promotion nobody reviewed for them.

Assign an owner to each offer. Check its active period, eligible products, customer conditions, and exclusions before publishing it and when relevant settings change.

Review the live configuration alongside the advertised terms. An accurate promotional message does not establish that the checkout rules match it.

Applying different rules across checkout channels

An online offer and an in-store offer may intentionally differ. The problem arises when staff cannot distinguish that decision from an incorrect configuration.

Compare the same eligible basket across the channels you use. Inspect the price, applied promotions, and any conditions the customer must meet.

If staff compensate for a channel mismatch with a manual reduction, record the reason. Otherwise, the workaround can obscure the original fault and become another unplanned discount.

Checking the customer total without reviewing tax lines

Separate the discounted merchandise amount, tax components, and final payment. A customer-facing total does not explain how each component was calculated.

Have the person responsible for tax configuration review unclear treatment. Do not change tax settings simply to make checkout match a desired promotional total.

Keep the comparison tied to the actual customer category and transaction conditions. A test basket that behaves as intended does not prove every variation receives the appropriate treatment.

Measuring promotion success by revenue alone

Higher promotional revenue does not establish that the offer improved profitability. Review the actual selling prices, associated product costs, refunds, and items included in the purchases.

Determine what question the offer was meant to answer. Clearing selected stock requires a different review from assessing whether a discount encouraged additional purchases.

Do not credit the promotion with demand your records cannot establish. If you lack a suitable comparison, describe the observed results without claiming the offer caused them.

Test a partial refund on a discounted order

Use demonstration data to refund part of a discounted purchase. Inspect how the discount is allocated, what remains on the order, and how the refund appears in reports.

Ask the vendor to explain any recalculation. Do not assume the remaining basket retains its original eligibility or that every system handles the change identically.

Run a discount test before publishing the offer

Write the expected outcome before testing. Keep the basket and customer conditions consistent so a difference can be traced to the rule being examined.

Scenario Result to verify
Ordinary eligible purchase Intended offer applies
Permitted combination Final price matches the approved calculation
Prohibited combination Additional reduction is prevented or flagged
Manual adjustment Authorization and reason remain identifiable
Partial refund Remaining sale and refund can be explained

Check the transaction record as well as the screen. If staff cannot reconstruct the calculation afterward, ask what additional reporting or documentation is needed.

Start with an unexplained low-margin sale

Choose a sale whose result does not match the intended offer. Trace its original price, promotion sequence, manual adjustments, relevant credits, and recorded product cost.

Correct the established cause before changing the entire discount policy. Update the affected rule, permission, or cost record through the appropriate process, then repeat the scenario. Give the promotion owner the verified result and identify any unresolved condition that still needs testing.

Top comments (0)