A product can have several sizes, colors, materials, or bundles, each with its own price. A quick check across those options can catch a swapped value, an unclear promotion, or a listing that is difficult for shoppers to compare. This is a repeatable review method, not a claim that any particular store has a pricing problem.
Start with one product family
Choose one product and list every option a shopper can select on its page. Keep separate products out of the first pass; comparing only like-for-like options makes unusual prices easier to spot. If the same item appears on more than one sales channel, review each channel separately because prices and promotions may differ by channel.
Make a small comparison sheet
For each option, record its displayed name, SKU or other internal identifier, regular price, sale price if there is one, currency, and the page where you checked it. Add a unit or size when it affects what the buyer receives, such as millilitres, number of pieces, or garment size. Note the date and whether the price came from the product editor or the live page.
Use the same price field throughout the comparison. A crossed-out reference price is not the current selling price, and a sale price should not be compared with another option’s regular price without labeling that difference. Keep taxes and shipping separate unless they are included in the displayed price for every option.
Compare the options in a consistent order
Sort options by a meaningful attribute, such as package size or number of pieces. Then scan for:
- Two options that have the same SKU or description but different prices.
- A larger quantity that costs less than a smaller one, when there is no known promotion or bundle explanation.
- A price that appears under the wrong option after changing the selector.
- A sale price that does not match its start or end date, or appears on only one sales channel unexpectedly.
- A unit price that changes sharply when the package size changes.
These are review prompts, not automatic proof of an error. A larger bundle may have a deliberate discount, different sizes may use more material, and a promotion may be limited to one option.
Hypothetical example: Imagine a fictional coffee seller lists a 250 g bag for $12 and a 500 g bag for $19. If the storefront shows $12 after the 500 g option is selected while the product editor shows $19, record the two values and check for a scheduled sale or a selector issue before changing anything. These example values describe no real store and are not findings from a ShelfSparrow audit.
Verify a possible conflict before changing anything
If a value looks unusual, first confirm that the option names and units are being read correctly. Open the product editor and compare its variant, SKU, currency, regular price, and sale settings with the customer-facing page. Select the option on the page, add it to a cart if the store allows, and check the price shown there too. Look for scheduled promotions, channel-specific pricing, bundles, and currency conversion before deciding whether the difference is unintended.
If the product editor and storefront disagree, record the exact option, the value in each place, the page or channel, and the time checked. That gives whoever manages the catalog a concrete issue to reproduce. Change the price only after the intended offer and source of truth are clear; otherwise document the difference as an intentional exception.
Keep the check easy to repeat
Save the comparison sheet with the product record and repeat the same steps after a price update, promotion, or catalog import. A short list of exceptions—such as an approved bundle price or a channel-specific sale—helps the next review distinguish an intentional difference from a possible conflict.
Want a quick second look?
The free listing snapshot reviews one public listing and emails exactly one named finding plus a score. It is separate from the full Store Audit and does not promise a review of every variant in a catalog. Request a free listing snapshot.
How can I test a possible price conflict?
Use a small, fictional example to check the arithmetic without treating a price pattern as an error. Suppose a made-up shop lists a two-piece pack for $18 and a four-piece pack for $32. The simple per-piece amounts are $9 and $8. That difference may be an intentional quantity offer, a promotion, or a mistake; the calculation alone cannot tell you which. Compare the displayed terms, the approved price record, and the dates before you label the result.
Check the option selector with each available combination. If a product offers three sizes and two colors, write down the six combinations you can actually select rather than assuming every option has the same price. Shopify describes each combination of option values as a variant, and its variant documentation notes that price and inventory details can be managed at the variant level. See Shopify’s guide to variants and adding variants. This is why the selected option must be part of the comparison record.
Which edge cases can explain different prices?
Separate regular price, sale price, compare-at price, and unit price in the worksheet. A regular price on one page should not be compared with a sale amount on another without marking that difference. Record currency and market because a number in one currency is not directly comparable to a number in another. Note tax and shipping separately unless the displayed total includes them on both pages.
Bundles need their own row when the quantity or included items differ. A three-piece set and a single item are not the same offer simply because their titles share a product name. Also check whether a promotion is scheduled, whether the public page reflects a selected subscription or purchase option, and whether a channel has an approved price rule. A date-specific sale can make two accurate snapshots differ when they were captured at different times.
What should a review worksheet contain?
Keep one row for each product, variant, channel, and market combination. Useful fields include the SKU or other identifier, exact option values, displayed price type, currency, unit, start and end dates for a promotion, source record, public URL, and check time. Add a short note when an option could not be selected or when the price display was unclear. Do not fill blank cells by guessing.
For a hypothetical review, a row might say “Canvas tote / blue / standard size,” show the public price as $24, record the matching source value as $24, and note that the check occurred on the same date. A second row could show a “two-pack” offer at $42 with a note that the bundle contents differ. These are example values only, not ShelfSparrow pricing or a recommendation. Keep the underlying source alongside the snapshot so another person can repeat the same comparison.
What should happen after the check?
If the public value and approved source disagree for the same variant and time, ask the person responsible for pricing to confirm which value is intended. Record the decision, update through the store’s normal workflow, then reopen the same URL and option. If the records match, keep the review note and move to the next combination. If a price is unexplained, label it unresolved instead of changing it.
This process checks consistency; it does not recommend a price, estimate margin, predict demand, or establish that one variant should cost more than another. A merchandiser or owner still decides the offer. See the Shopify product details guide for the fields Shopify makes available in its product workflow.