Choose supplier price monitoring software that compares the same product, variant, pack size and cost basis over time. A useful alert explains what changed and which listings may need review. Before acting, check currency, delivery charges and selling costs so a price difference does not become a misleading margin signal.
A supplier changing a displayed price is easy to describe. Understanding the effect on your business is harder. The new amount may apply to a different quantity break, exclude delivery, or appear in another currency. A promotion can end without the underlying standard price changing. Software should help preserve that context.
This buyer’s guide focuses on supplier-backed ecommerce operations. It does not provide current marketplace fee rates or tax advice. Numerical examples are hypothetical calculations for comparing workflows. Zelluvo publishes the guide and has a commercial interest in supplier monitoring; the buying criteria apply when evaluating any tool.
Define which price you need to monitor
Write a definition before importing the first source. Are you monitoring a publicly displayed unit price, your account’s negotiated price, the cost of a pack, or the total amount needed to receive an order? Each can be useful, but comparing them as though they were identical creates false alerts.
A ten-pack priced at 40 currency units and a single item priced at 5 are not competing observations of the same unit cost. Normalising the pack suggests a base cost of 4 per item, before other charges, but only if you can actually buy and sell on that basis. Minimum order quantities and unsold pack remnants can affect the practical decision.
Keep a source record for the exact variant. A medium shirt may carry a different cost from an extra-large version. A product page’s prominent price may represent the cheapest option rather than the one you sell. Ask the vendor to show where the observed amount came from and which selection produced it.
| Field | What it describes | Question to resolve |
|---|---|---|
| Source price | The observed amount on an authorised source | Which variant, currency and quantity does it cover? |
| Unit cost | Cost allocated to one saleable unit | Was the pack conversion appropriate? |
| Acquisition cost | Unit cost plus relevant purchasing charges | How were shared delivery costs allocated? |
| Contribution estimate | Revenue less included variable costs | Which fees and costs are still excluded? |
Distinguish price monitoring from repricing
Monitoring observes and compares. Repricing changes a selling price. A product may offer one capability without the other, and a workflow can deliberately require review between them. Establish that boundary before authorising account access.
For many small teams, the useful first step is a clear exception queue: this source cost increased, these listings are connected, and this assumption needs checking. The operator can then decide whether to accept a lower contribution, change the selling price, reduce exposure, find a suitable alternative source or stop offering the item.
A rule should make the proposed action explainable. If a tool suggests a new selling price, ask which costs and target it used. If it only reports the supplier change, ask whether you can preserve the additional analysis elsewhere. Do not assume that the label “price monitoring” includes complete profitability accounting or marketplace repricing.
Zelluvo’s documented workflow includes supplier-related observations, product mapping and approval-first live eBay stock changes. Treat any particular price-update capability as a separate requirement to confirm. This article does not promise automatic repricing, a guaranteed margin or support for every supplier.
Compare like with like before trusting the alert
Currency is an obvious source of confusion, but the time and basis of conversion matter too. If your source currency changes, preserve the original amount and code. A converted reporting value can move even when the supplier has not changed its own price. The alert should distinguish an observed supplier change from an exchange-rate assumption.
Tax treatment also needs consistency. Do not compare one amount including tax with another excluding it and call the difference a supplier increase. Use a basis appropriate to your business and confirm that basis with your adviser where needed. Keep the monitoring record explicit rather than building hidden tax assumptions into a formula.
Delivery charges can alter the total cost while the headline price stays unchanged. Decide whether you need to monitor that component directly or review it during purchasing. A source tool may not be able to calculate account-specific delivery costs before checkout. That limitation should be visible in your requirements and decision record.
Promotional prices need dates and conditions. If a discount depends on a coupon, membership or minimum purchase, a public price reading may not describe the amount you can obtain. Ask whether the product records the relevant condition, or whether the operator must check it manually before relying on the cost.
Use a transparent contribution calculation
A simple contribution estimate subtracts the included variable costs from the relevant revenue. It is not the same as final business profit. Fixed overhead, tax and other costs may sit outside it. Name the measure accurately so the team does not interpret a positive figure as proof that the business is profitable.
Consider a hypothetical item selling for £40 on a consistent accounting basis. Assume supplier cost of £20, fulfilment cost of £4 and other included selling costs of £6. The illustrative contribution is £10. If supplier cost rises to £23 and everything else stays constant, it becomes £7. That is a £3 reduction and a 30% decline in this contribution amount.
The supplier cost increased by 15%, while the contribution fell by 30%. The percentages answer different questions. An alert reporting only the supplier percentage can understate how strongly a narrow contribution is affected. Show the absolute change alongside the relevant business measure.
| Item | Before | After |
|---|---|---|
| Revenue used in model | £40 | £40 |
| Supplier cost | £20 | £23 |
| Fulfilment cost | £4 | £4 |
| Other included selling costs | £6 | £6 |
| Contribution | £10 | £7 |
For real decisions, obtain the current costs that apply to your account and category. The official eBay business seller fee guidance is a starting point for UK sellers. Australian sellers should use their applicable local fee information rather than copying a UK assumption. Keep the monitoring comparison separate from the calculation of actual charges.
Choose review rules your team can explain
A percentage change threshold is easy to configure, but it should not be your only consideration. A small percentage movement on an expensive item can exceed a large percentage movement on a cheap accessory. A repeated small increase may also matter more than any individual alert suggests.
Consider a combination of conditions: absolute cost movement, percentage movement, the resulting contribution estimate and the age of the supporting data. Use only conditions the tool actually supports; document the rest as manual review steps. Avoid presenting an illustrative rule as a recommended setting for every business.
Decide which previous value is the comparison baseline. Comparing with the immediately preceding observation identifies each step. Comparing with an approved purchasing baseline can reveal accumulated movement. Both can be useful, but they produce different alerts. The operator should know which one they are seeing.
Set a reset policy for resolved alerts. If you accept a new supplier cost, record who accepted it and when the baseline changed. Otherwise, the same event may keep reappearing, or the system may silently normalise a cost that nobody approved. An alert is resolved when the business decision is recorded, not merely when the message is dismissed.
Handle failed readings and implausible values
A missing price, zero amount or unexpectedly large jump deserves investigation. It may represent a genuine offer, an unavailable product, a pack change or a reading problem. The software should preserve the raw observation and its status so the operator can tell which explanation is supported.
Do not let a failed reading overwrite the last valid cost without a visible explanation. Equally, do not continue presenting an old valid amount as current. Keep the last successful value, its time and the latest failure distinguishable. That makes the next purchasing decision more informed.
Try a deliberately awkward record in the evaluation. A source with a crossed-out previous price and a current promotional price is useful. So is a product with several pack sizes. Ask the vendor to show which amount is stored and why. If the answer relies on a source-specific limitation, record that limitation before expanding coverage.
Route unusual changes to review instead of assuming every observed difference should produce a selling-price change. A sudden tenfold increase can arise from a pack conversion mistake. A reliable process makes it easy to reject the interpretation, correct the mapping and recalculate from valid evidence.
Test software with a small, representative cost file
Prepare a compact evaluation set covering your normal sources and difficult cases. Use authorised records and avoid sharing credentials in a sales email. Include a stable cost, a confirmed change, a pack-size difference, a currency difference and an unreadable source. The purpose is to understand handling, not to manufacture impressive savings.
- Record the exact supplier product and variant.
- Write the source currency, pack size and price basis.
- Capture the baseline and its observation time.
- Compare a later observation on the same basis.
- Calculate the effect using your documented cost assumptions.
- Inspect the proposed review task and responsible person.
- Record the decision without claiming an unverified live price update.
- Check that the history explains the result to another operator.
Measure exceptions that required manual correction and time spent understanding them. A short pilot can show whether the workflow fits your records. It cannot establish a universal error rate or revenue uplift. Keep those boundaries clear when reporting the result internally.
Test what happens when a supplier source is removed or remapped. Historical prices should still be understandable in their original context. A new source with a different cost basis should not silently inherit the old comparison baseline as though nothing changed.
Make the buying decision around your operating model
A seller with a few stable wholesale files may need reliable imports and straightforward review notes. A catalogue with many source pages may place more weight on variant selection, failure visibility and ongoing maintenance. A broader inventory suite may be appropriate when purchasing, warehousing and multichannel allocation are the larger problem.
Ask about limits in concrete terms: number of products or variants, supported source formats, retained history, user permissions and available exports. Confirm which capabilities are included in the plan being quoted. Avoid comparing a basic subscription from one vendor with a fully configured service from another.
For the stock side of the same decision, read the supplier stock monitoring guide. For software selection around the whole eBay operation, use the eBay inventory workflow guide. The best fit is the workflow whose assumptions and limits you can explain before an unexpected change arrives.
If you are evaluating Zelluvo, ask about your supplier cost-review requirements. Confirm current source support, account scope and the boundary between observation, a local proposal and any approved live action. Keep a written record of those answers alongside your pilot results.
Questions about supplier price monitoring
Is supplier price monitoring the same as competitor price tracking?
No. Supplier monitoring examines acquisition-cost information. Competitor tracking examines other sellers’ offers. They answer different questions and may use different identifiers, access methods and comparison rules. Keep their data separate in your buying requirements.
Does a supplier cost increase always require a price increase?
No. Review the effect on your costs, contribution and commercial strategy. You may accept a different contribution, change sourcing or stop offering the item. A monitoring alert provides evidence for the decision rather than deciding it automatically.
Can I compare prices in different currencies?
Yes, with a documented conversion basis and timestamp. Preserve the original amount and currency. Distinguish a supplier changing its price from your converted reporting value changing because of the exchange-rate assumption.
What should I do with a zero or missing supplier price?
Investigate the source and record its state. Do not assume zero means free stock or treat a missing amount as a fresh valid cost. Retain the previous valid observation as historical information while the exception is reviewed.