A daily stock monitoring checklist should tell an eBay seller what needs attention, what evidence to inspect and how to record the outcome. It should cover the gap between supplier information and the quantity customers can actually buy. Simply opening a dashboard and checking for red badges leaves too much to memory.
Use this checklist as a starting routine, then adapt it to your catalogue and operating hours. “Daily” describes a planned review, not a promise that one check every twenty-four hours is sufficient for every item. Fast-changing supply, unresolved failures and active orders may require attention sooner.
Prepare a review sheet you can hand over
Keep one row per actionable exception, with the listing and variation identity, supplier source, last successful observation, current concern, owner and next action. Separate the time the source was checked from the time a proposal was calculated and the time a marketplace result was confirmed.
Do not copy private buyer details into a general monitoring sheet. An order or internal reference can connect the reviewer to the authorised system when needed. The monitoring record should contain enough operational context to make the decision without becoming an unnecessary store of customer information.
Before starting, establish who can approve live changes and who provides cover. If the reviewer finds a problem but has no route to an authorised decision maker, the checklist can document risk without reducing it. Make the escalation path part of the routine.
1. Check whether monitoring itself is healthy
Begin with failed checks, stale sources and missing observations. A quiet alert queue can mean stable conditions, but it can also mean that the system has stopped receiving information. Review the last successful activity for the sources and product groups that matter to the day’s operation.
Distinguish a source problem from an item problem. If many products from one supplier become unreadable together, investigate the shared configuration or access issue. Do not assume that every affected item is unavailable, and do not assume that its previous availability remains valid.
Record the affected scope and owner. If an unresolved monitoring failure could leave listings exposed, follow the agreed review policy for uncertain data. The policy should identify a permitted action and decision maker rather than leaving each operator to improvise.
2. Review overnight orders and commitments
Check the order information available through your authorised workflow and identify commitments relevant to stock decisions. A supplier observation does not describe units already promised to customers, and a physical stock count is not the same as stock still available to offer.
Pay attention to products where several orders arrived close together or where the same supply supports more than one listing. The review should establish whether the latest decision accounts for the commitments your process recognises. Do not manually subtract quantities a second time if the authoritative system already handles them.
Escalate orders with unresolved sourcing or identity questions through the appropriate order process. Keep the stock review linked to that work, but avoid marking an order fulfilled merely because a supplier page shows availability. Fulfilment requires its own confirmation.
3. Prioritise unavailable and low-availability items
Inspect items that moved from available to unavailable, crossed a defined threshold or became uncertain. Check the exact variation before deciding what the signal means. A parent product may remain available while the size or colour you sell has disappeared.
Where a source provides only a qualitative label, preserve that limitation. “Low stock” is not a verified count unless the source explicitly gives one and your process can interpret it correctly. The reviewer should not manufacture a numeric quantity to make the spreadsheet look complete.
Compare the signal with the live exposure and the applicable rule. A useful note might say that a specific variation requires quantity review because its last successful observation is no longer reliable. It should not merely repeat the alert title without explaining the decision.
4. Check changed or ambiguous mappings
Review newly imported listings, recently edited variations and supplier pages whose options changed. These are natural points for identity errors to enter the process. Match the relevant attributes, including pack size or compatibility where those affect fulfilment.
Keep ambiguous matches out of routine approval until they are resolved. An apparently sensible quantity calculation for the wrong item is still wrong. Use the SKU mapping guide to document the relationship and the evidence behind it.
When a mapping is corrected, identify which pending decisions relied on the old relationship. They may need to be reconsidered with current evidence. Fixing the mapping alone does not prove that every proposal already in the queue is now appropriate.
5. Review supplier cost changes
Look for significant or unexpected cost movements alongside stock exceptions. Verify currency, unit count and source conditions before assessing margin. A lower displayed price can refer to a different option, while a higher amount can include a charge previously shown elsewhere.
Use the business’s documented cost model. If an input is estimated or outdated, say so. The daily reviewer should not invent tax, shipping or fee assumptions simply to obtain a clean margin result. Route uncertain commercial decisions to the person responsible for those assumptions.
A cost alert does not automatically authorise repricing. Record whether the decision is to investigate, accept the changed contribution, review the selling price through a separate process or adjust exposure. The supplier price monitoring guide explains that distinction in more detail.
6. Inspect proposed quantities before approval
For each proposal under review, inspect the item identity, source observation, observation age and rule applied. Ask whether anything material changed after the proposal was created. A proposal that was sensible yesterday may need recalculation after new commitments or a corrected mapping.
Review unusually large changes separately. A sharp increase could be legitimate, but it could also reflect a source interpretation or unit-count error. A sharp reduction may reveal a real shortage or an unreadable source. The magnitude is a reason to inspect the evidence, not proof of either outcome.
Approve only through the supported process and within the reviewer’s authority. Keep rejection reasons useful: “wrong pack size in source match” helps the next operator, while “looks wrong” does not. Clear reasons also reveal recurring issues in later process reviews.
7. Confirm the result of authorised actions
After an approved marketplace update, establish what the system confirms. Separate a queued action, an attempted action and a confirmed destination state. Do not close the exception because a button was clicked if the outcome remains unknown.
For failures, preserve the intended quantity and last confirmed state alongside the error context. Review current evidence before retrying; the original proposal may no longer reflect the latest situation. Use the supported recovery path instead of creating competing manual and automated changes.
If several tools can write to the listing, determine whether another writer could reverse the action. The daily checklist should refer to a clear ownership policy. Without it, operators may repeatedly “fix” quantities that another system restores a few minutes later.
8. Sample apparently normal items
Do not spend the whole review on alerts. Select a small, rotating sample of products that show no exception, including different suppliers and variation types. Confirm that their observations are recent enough, identities remain correct and the displayed status has the meaning you expect.
This is a practical way to detect silent process drift. It is not a statistically proven assurance programme unless you have designed and validated it as one. Record what was sampled and what was found so the exercise produces evidence rather than a habitual tick.
Use findings to improve the checklist. If repeated samples reveal stale values that never trigger an alert, address the missing control. Adding more manual checks indefinitely can conceal a repairable problem in the monitoring process.
9. Hand over unresolved exceptions
End the review with an explicit list of open items, their owners and the next review point. Include the last confirmed state and the reason the item remains unresolved. A colleague should be able to continue without asking the departing operator to recreate the morning’s investigation.
Separate “waiting for evidence” from “waiting for approval” and “action failed”. Those states require different follow-up. Avoid marking an item complete just because you have sent a message about it; completion should mean the defined outcome has been reached.
Review cover for periods when the usual operator is unavailable. If the next scheduled review is too late for an exposed issue, escalate it before ending the shift. A calendar entry is not a substitute for an owner who can act.
A reusable checklist format
| Check | Evidence | Completion condition |
|---|---|---|
| Monitoring health | Last successful observations and failures | Problems assigned and uncertainty handled |
| Commitments | Relevant order or stock records | Decision inputs reconciled |
| Availability | Exact variant and source time | Exposure reviewed against the rule |
| Mapping | Listing-to-supplier relationship | Ambiguities resolved or held |
| Cost | Price basis and current assumptions | Commercial action recorded |
| Proposal | Inputs, rule and reviewer | Approved, rejected or explicitly pending |
| Outcome | Destination confirmation or failure | Result known or recovery assigned |
| Handover | Open items and named owners | Next review is clear |
Example: a short review with three different problems
Imagine a seller finds three exceptions: a missing blue variation, a cost increase on a separate item and a failed update from the previous review. These should not become three identical “stock problem” tickets. The first needs identity and availability evidence; the second needs a commercial assessment; the third needs the intended action and destination state.
The reviewer resolves the first mapping question, sends the cost decision to its owner and keeps the failed update open until the supported recovery path confirms an outcome. That separation makes the handover useful. It also prevents an apparently cleared dashboard from hiding work that has merely changed queues.
Using the checklist with Zelluvo
Zelluvo publishes this checklist. Its current workflow supports eBay listings, supplier mapping and local stock proposals, while live eBay stock changes remain approval-first. Early access permits one eBay seller account per client organisation. The checklist also includes general operating practices that should be adapted to the tools and permissions you actually use.
It does not imply automatic purchasing, automatic repricing or unrestricted multichannel updates. If you want to assess the workflow, contact Zelluvo with a small set of representative listings and walk through a normal observation, an exception and a confirmed approved result.
Keep the routine proportionate
Time the review occasionally and note which steps consume effort. If most time goes into locating source evidence, improve the record or interface used for that task. If most time goes into waiting for an approver, review cover and authority. These are different bottlenecks and should not receive the same remedy.
Remove checks only when their purpose is covered elsewhere and that coverage has been verified. Adding a new dashboard does not automatically make the old reconciliation unnecessary. Conversely, duplicating the same check in several sheets can create inconsistent outcomes. Give each step a reason to exist, a clear owner and a record that shows whether it was completed or remains open.
Frequently asked questions
Is one daily check enough?
Not necessarily. Set review and escalation frequency around supply uncertainty, commitments and response time. A daily routine is a baseline organisational habit, not a universal protection against changes between checks.
Should I check every listing manually every day?
Use risk-based exceptions and a rotating sample when that suits your operation. If manual review cannot keep up, improve the source, mapping and alert process rather than assuming a longer checklist will solve the workload.
What is the most important field in the review sheet?
No single field replaces the others. Exact identity, evidence time, owner and next action work together. A precise quantity is not useful when nobody knows which variation it describes or when it was observed.
When can an exception be closed?
Close it when its defined decision or action has a known outcome and any follow-up is explicitly assigned. Sending a message, clicking approve or dismissing a notification is not automatically that outcome.