Your supplier raises a cost, but your repricer is still trying to beat a competitor. Before approving the next batch, check the lowest price you can accept for that exact item, using a current cost and an agreed calculation. Keep repairs to underpriced products separate from competitive price changes so you can review each for the right reason.
Why do I keep two pricing jobs?
In BC Supply Ops, the market-pricing view imports competitor research workbooks and resolves a cost-based minimum per supplier. It proposes one cent below the cheapest market listing only when that price clears the minimum. When the market sits at twice our minimum, the row is flagged as suspect and excluded from automatic application.
That threshold is a documented rule in this project, not a universal definition of a bad competitor price. Choose review thresholds with the merchant and test them on actual comparisons. A review flag should ask someone to check the source; it should not declare the source wrong.
The minimum-price audit has a narrower job: classify variants as below minimum, at or above minimum, or missing cost. The case study records one audit of 70,418 variants: 35,869 were at or above minimum, 34,525 had no cost, and 24 were below it. Those are a recorded snapshot, not live counts or a claim about current profitability.
A variant with no cost cannot be marked safe just because the audit found no violation. The checklist and worked example below are my proposed way to review another store's pricing rules, rather than additional claims about the project's implementation.
Which cost should the floor use?
Start with the specific supplier offer that can supply the sellable variant. In this project, suppliers arrive through different APIs and spreadsheets, including different currencies. Keep the source reference and currency beside every cost so a reviewer can trace the proposed price back to its input.
Shopify's Cost per item guidance describes a reseller's cost per item as the amount paid for the product, excluding taxes, shipping, and other costs. A populated field therefore does not prove that every expense your pricing policy cares about is included. Write down which expenses your rule includes before using that field in automation.
For each supplier, record the cost source, how old it may be, the currency conversion rule, pack quantity, and the person responsible for corrections. Agree whether the minimum protects a margin percentage, a markup, or a fixed amount left after the specified costs.
Do not repair an ambiguous product match inside the pricing job. Send it through the supplier barcode matching review first. A perfectly calculated floor attached to the wrong pack or variant is still the wrong price decision.
Does your minimum mean margin or markup?
Ask the person setting up the repricer to calculate one row with you. In this hypothetical example, a fragrance costs €20 per sellable unit. Cost and selling price use the same currency and exclude tax; fees, shipping, discounts, and other expenses are left out to isolate the calculation. The percentage is an example, not a recommended target.
Shopify explains the difference between markup and margin: markup compares the amount added with cost, while margin compares it with selling price.
| Agreed rule | Calculation | Minimum price |
|---|---|---|
| Add a 25% markup | €20 × 1.25 | €25.00 |
| Keep a 25% margin on selling price | €20 ÷ (1 − 0.25) | €26.67, rounded up to cents |
At €25, the €5 left after product cost is only 20% of the selling price. Calling that a 25% margin would approve the wrong floor.
Next, test your price endings. With the second rule, rounding down to €26.49 would put the price below the floor. Ask the repricer to choose an allowed price at or above the minimum, or hold the row if no permitted price works. Keep both the calculated minimum and the final price in the preview.
Finally, check an active discount against the price the customer would pay. A 10% discount on €26.67 leaves about €24.00, below this example's floor. Passing a catalog-price check does not establish that a promotion passes too. Decide who reviews that exception before applying either change.
What should each row do before prices change?
Build a preview that changes nothing in Shopify and gives an action and reason for every row. Keep “cannot check: cost missing” separate from “checked: above minimum.” The operator should be able to see why a row is excluded.
| Condition | Minimum-price audit | Market repricing |
|---|---|---|
| Cost missing or outside the accepted freshness window | Hold; cannot evaluate | Hold; do not guess a minimum |
| Supplier or pack identity unresolved | Hold for mapping review | Hold for mapping review |
| Current price below a verified minimum | Propose a lift to the minimum | Require the same minimum before any proposal |
| Current price at or above minimum | Leave unchanged | Evaluate the verified market comparison |
| Proposed market price below minimum | Not a reason to lower the floor | Reject the undercut; review a floor-level proposal if appropriate |
| Market comparison flagged as suspect | Continue only with independently verified cost | Hold the competitive recommendation |
| Inputs changed after approval | Rebuild the plan | Rebuild the plan |
In BC Supply Ops, repricing produces a reviewable plan before live writes. Typed confirmations and separate write permissions provide additional controls. They help prevent an accidental run, but the operator still needs to understand the prices being approved.
How do you review a competitor comparison?
Ask for a comparison record showing the observed item, its source URL, observation time, price, and the matched store variant. Add the packaging, quantity, and availability evidence used to accept the comparison. Reject a comparison whose item identity cannot be explained.
For example, consider a hypothetical supplier row for a refill and a market result for a retail bottle. Hold the comparison until someone confirms they are the same sellable item.
Review suspiciously high prices as carefully as low ones. The documented twice-minimum guard exists to stop suspect market data from authorizing a large automatic increase. Keep the captured evidence with the hold so a corrected source can produce a new plan.
The output should remain understandable when no change is proposed. “Unchanged because the current price clears the floor” and “unchanged because cost is missing” require different follow-up work. Put them in different queues with an owner for the missing evidence.
What should happen between approval and application?
Save the old price, proposed price, variant ID, cost source, calculation rule, and approval alongside the plan. Immediately before a write, check for changes to the supplier cost, selected supplier, or store price. Any of these can make the earlier approval stale; hold that row for a fresh decision.
For a custom Shopify integration, productVariantsBulkUpdate updates variants belonging to one product and returns userErrors. Its allowPartialUpdates option controls whether valid changes can persist when another variant has invalid data. The default is false; an integration must still inspect the response and reconcile what actually changed.
Record results per variant, then read back the relevant prices. Sending a request does not tell you whether every price changed. Keep the response, observed result, and any retry decision connected to the original plan.
Restoring an old price also needs review. Check that the current price still matches the value this operation applied, then check the old price against today's cost floor. If either check fails, resolve it before applying a correction; an old price may now be too low.
Before enabling writes, test a missing cost, an outdated cost, a packaging mismatch, a rounded price below the floor, a changed store price, and a partial failure. Keep supplier input validation separate, as described in the feed acceptance workflow.
Where should you start?
Choose a small group of variants and calculate one floor by hand before running a read-only audit. Check the preview against that calculation, including rounding and an active promotion. Count rows that meet the agreed rule, proposed increases, and rows you cannot evaluate.
Resolve missing costs before expanding the run, then introduce competitor proposals as a separate reviewed operation. The multi-supplier operations overview shows how pricing fits beside stock and ordering. For implementation scope, see my Shopify supplier integration service.
If you need help making that review part of your automation, send a sanitized pricing example through the supplier automation enquiry page, or book a call. Include the supplier cost, intended rule, and disputed price so we have a concrete place to start.
