Competitor price monitoring: which price changes deserve action?

Set the comparison before collecting prices

Choose a product or variant, the quantity your buyer needs and a destination. State whether you are comparing displayed item prices or an order total that includes the stated delivery charge. Use the same tax basis on both sides. When tax or delivery is unresolved, keep the comparison at the level the evidence supports.

Keep your internal SKU separate from each marketplace’s source identifier. A similar title or image can start a search, but the match also needs model, size, material, condition and pack-count evidence where those attributes matter. Preserve each source record when two listings are linked.

Give every observation a review state

Use the checks below before calculating a price gap. A missing observation is different from an explicit zero, a free delivery statement or an out-of-stock label.

Use comparable for an observation whose required conditions are sufficiently evidenced for this comparison. Use review when evidence is missing or needs checking. Use exclude when a confirmed mismatch makes the observation unsuitable for the chosen comparison. Record the reason and the person responsible for the next check.

Work through a six-unit order

Every figure below is fictional. Assume the buyer needs six identical units, all confirmed offers use the same tax display basis and destination, and the stated delivery charge applies once to that six-unit order. Observations share the same teaching timestamp. These assumptions are supplied for the exercise; a real collection must retain evidence for them.

Your baseline is one six-unit pack at EUR 60 plus EUR 6 delivery: EUR 66 ÷ 6 = EUR 11 per unit. Use that same buyer quantity when reviewing each competing offer.

For an observed price gap, use (comparable competitor unit price − baseline unit price) ÷ baseline unit price × 100. A product confirmed to have the wrong model would be excluded before this calculation.

This example compares a competitor’s current offer with your own offer. To establish an actual price change over time, compare the same competitor record with its previous qualified observation. Keep that historical baseline separate; a gap against your price does not prove that the competitor has reduced theirs.

A comparable price still needs a business decision. Check your own margin, stock position, service terms and the competitor’s promotion window. Set a review threshold with your team; there is no universal percentage that makes a price cut sensible.

Choose how the data will reach your team

A manual sheet suits a small, stable set of links when someone can revisit sources and document each decision. A monitoring product suits repeated checks, history and alerts when its supported sources, matching rules and update timing fit your needs.

Prisync documents URL-based, barcode-based and hybrid monitoring. Apify’s published workflow separates collection, product matching, baseline comparison and alerts. Those are capabilities to evaluate during a trial. This checklist adds an explicit record of the comparison conditions and your team’s decision; it does not establish that other providers lack those controls.

A scoped data delivery suits a research or catalogue task with agreed fields, samples and output files. PandaBuyNow prepares product, listing and variant data from its supported Chinese marketplaces with source references, field definitions and quality notes in an agreed JSON or CSV structure. Collection scope and any repeat batches need agreement. A delivered snapshot is not a running repricing or alert service.

Keep a reviewable record and test the handoff

The download contains a field-notes row and the three fictional observations above. Filter out the field-notes row before treating it as data. Replace example assumptions with your own source evidence; blank fields mean unresolved values. Technical field names are in English so one worksheet can be shared across teams.

Keep raw values separate from calculations. If currencies differ, retain the original currency and amount, then document the exchange-rate source, rate and timestamp. If a conversion is unsupported, keep the normalized result blank. A converted display price alone does not establish the buyer’s payable order total. If delivery is quoted in another currency, retain that currency and require its own conversion evidence before calculating an order total. The worksheet’s single-rate formula applies only when item and delivery amounts share the source currency.

Before accepting a full file, review a confirmed match, a missing-condition row and a confirmed mismatch. Verify the source, selected variant, order quantity, unit, observation time and calculation. For a repeat batch, name the baseline and distinguish a failed observation from a confirmed price change or removal.

To discuss a PandaBuyNow sample, send representative product links, the target market, selected variants, selling units and the fields and observation period your team needs. Agree feasible coverage and acceptance checks before the full JSON or CSV delivery.