Monitor supplier stock without an API by using an authorised file, feed, product-page observation or documented manual check. Identify the exact variant, preserve the observation time and treat failed readings as unknown. Review the evidence before changing listed quantities. The absence of an API does not justify bypassing a supplier’s access controls.
Many suppliers do not provide a connection that fits a small seller’s workflow. Some can send a periodic stock file. Others maintain product pages but offer no structured export. The practical task is to obtain usable evidence, understand its limits and connect it to the right listing without pretending it is a live inventory reservation.
This guide describes a supplier-backed eBay process rather than a scraping script. It covers source selection, variant checks, freshness, exception handling and a limited pilot. The example records are illustrative. Zelluvo publishes the guide and has a commercial interest in supplier-monitoring software.
Ask for the simplest authorised source first
Start with the supplier relationship. Ask whether an export, stock sheet, data feed or regular account report is available even if there is no public API. A straightforward file with stable identifiers may be easier to validate than a product page whose layout changes frequently.
Specify the fields you need: product identifier, variant identifier, quantity or availability state, source timestamp and relevant location. Explain whether you need a full catalogue snapshot or changes since the previous file. That distinction affects how you interpret missing rows.
Agree how often the information is produced and how it may be used. Do not assume that a publicly viewable page permits any form of automated access. Use the supplier’s supported methods and account permissions. If a source blocks or challenges the connection, pause and resolve access through the supplier rather than trying to evade the restriction.
| Source | Useful when | Limitation to record |
|---|---|---|
| Supplier CSV or spreadsheet | Identifiers and update times are consistent | The file may be older than the import time |
| Authorised catalogue feed | The supplier distributes structured availability | Missing rows and stock definitions need agreement |
| Permitted product-page observation | No suitable structured source exists | Variant selection and layout changes can affect readings |
| Documented manual check | The catalogue is small or a source needs investigation | Coverage depends on operator availability |
Write down what the source actually tells you
A supplier source may provide an exact number, an availability label or a lead-time message. Keep those meanings separate. “Available” does not tell you how many units are allocated to your business. “Usually dispatched in several days” is not the same as an immediate stock count.
Establish whether the value refers to one warehouse, a combined network or a default delivery region. If the source changes by location, make the selected region part of the observation record. Otherwise, two operators can see different results and assume one of them is wrong when they are checking different conditions.
For numeric stock, ask whether committed orders are already excluded. A number that describes physical stock on hand can differ from the quantity available for a new order. Your exposure calculation should not silently assume a definition that the supplier has not confirmed.
Document what you do not know. An incomplete definition is a reason for a cautious process and a supplier question, not a reason to invent a more precise quantity. A monitoring record is useful when it communicates uncertainty honestly.
Map the exact product and variant
Record the supplier’s identifier alongside your internal SKU and the destination listing or variation. Include the attributes that distinguish the item, such as size, colour, pack quantity or model. A source URL alone may not identify the required variant if the page opens with a default selection.
Open the source through your authorised access and verify the selected option. Then repeat the check from a fresh session or another permitted view where practical. This can reveal a page that remembers a previous selection rather than preserving the intended variant in the saved link.
A parent product being available does not establish that every option is available. If the tool cannot reliably select or identify the exact option, keep that mapping outside routine quantity decisions. A manual check may be a suitable fallback while you discuss a better source with the supplier.
For eBay’s identifier context, consult the developer guidance on managing multiple-variation listings. Your monitoring process needs to preserve enough detail to connect the source observation to the intended variation, rather than merely finding a similar product title.
Preserve both source time and check time
A file imported at 11:00 may have been generated at 06:00. A product page read at 11:00 may not reveal when its underlying stock was last refreshed. The time your system obtained the information and the age of the information itself are different facts.
Store the supplier-provided timestamp when it exists. Store the time of your latest successful observation separately. If the source does not disclose its own update time, say so. A recent observation is still useful, but it should not be described as proof that the supplier’s internal stock changed at that moment.
Use explicit time zones when records cross UK and Australian operations. The important requirement is that another operator can place events in the right order. Avoid unlabelled local times in a shared incident record, especially when a source file arrives overnight for one reviewer.
Set a freshness policy around the business decision. A slowly changing spare-part catalogue may tolerate a different interval from a fast-moving promotional item. Your ability to review and act also matters. A source checked frequently but left unreviewed can still support an outdated selling decision.
Keep failures out of normal stock values
Define three distinct outcomes: available, unavailable and unknown. Unknown covers cases where the source could not be read, the expected variant could not be identified or the result was not interpretable. It should not be silently converted into a confident availability statement.
Retain the last successful observation as history. If yesterday’s record said eight units and today’s attempt fails, the useful record is “latest attempt failed; last successful quantity eight, observed yesterday”. Showing only eight with today’s refresh time would make old evidence look current.
A page redesign may move or remove the information your tool expects. A file may rename a column or change its quantity format. Ask the provider how such changes become visible. An explicit source exception is more useful than a plausible but unverified result.
Decide who investigates the failure and what happens to listing exposure while it remains unresolved. A cautious stock decision may be appropriate, but record the reason accurately. This lets you distinguish an unreliable source from a supplier that genuinely has no stock.
Build a manual fallback that another person can follow
A fallback should name the source, the exact variant to inspect, the information to record and the person responsible. “Check manually” is too vague when several nearly identical options exist. Use a short checklist that can be followed during a busy period.
- Confirm the supplier and authorised account or access method.
- Open the exact product and select the intended variant.
- Record the displayed quantity or availability without adding unsupported precision.
- Record the observation time and any source timestamp.
- Note discrepancies, unavailable options or access problems.
- Compare the result with the relevant listing and pending proposal.
- Record the review decision and verify any separately approved update.
Do not place supplier passwords or private account information in shared article notes, exported examples or support messages. A workflow can preserve product evidence without exposing credentials. Use your approved access arrangements when another operator needs to repeat the check.
The fallback also needs a completion rule. Once the source becomes readable again, review whether the original mapping and interpretation still hold. A recovered connection does not automatically prove that the layout change preserved the same variant or price meaning.
Test one normal case and several difficult ones
Begin with a small observation-only pilot. Choose a stable item, an unavailable item, a product with several variants and a source that cannot currently be read reliably. These cases reveal more about the workflow than a long list of simple successful checks.
| Case | Expected interpretation | Review question |
|---|---|---|
| Readable exact variant | Timestamped availability or quantity | Does the source match the listing? |
| Confirmed unavailable variant | Stockout evidence | Who reviews exposure? |
| Variant selection missing | Unknown or mapping exception | Can the selection be resolved? |
| Unreadable source | Failed attempt with historical context | Who owns the fallback? |
Inspect every pilot result manually using permitted access. Record mismatches and the work needed to explain them. A small sample can establish whether a source format is promising; it does not support a general accuracy claim for the entire supplier catalogue.
Then test a second import or observation cycle. Confirm that unchanged records remain understandable, changed records show a clear comparison and missing records are handled according to the agreed source semantics. Repeatability is more useful than a single successful demonstration.
Connect observations to controlled selling decisions
Keep the source-reading layer separate from the authority to change a listing. An observation can support a local proposal, but the proposal still needs the correct mapping, a valid rule and the relevant review. This separation makes failures easier to trace.
Before an approved update, inspect the current destination state. Recent orders or manual adjustments can make an older proposal unsuitable. After the action, verify that the intended account, listing and variation reflect the decision. A request being submitted is not the same as the destination being confirmed.
Zelluvo’s documented eBay stock workflow keeps live changes approval-first. Evaluate its source compatibility and variant handling using your own approved examples. Do not assume that any arbitrary supplier page can be supported, or that the absence of an API means setup requires no maintenance.
Read the supplier stock monitoring software guide for buying criteria and the supplier-stockout workflow for exposure decisions. These controls work together: obtaining a reading does not complete the operational task.
Know when to change the source or process
If a source fails repeatedly, ask whether maintaining it is still worthwhile. A supplier file, a different authorised feed or a more limited manual catalogue may be more dependable. The best response to repeated ambiguity is not always a more complicated reader.
Track recurring problems by cause: access failure, layout change, missing variant, unclear quantity meaning or stale information. That record supports a specific discussion with the supplier. It also helps you decide whether a software provider’s proposed integration actually addresses the problem.
Budget for maintenance in the buying decision. Product pages and supplier catalogues change. Ask who investigates a broken source, what support is available and how you can keep affected listings under control during the investigation. Confirm terms directly rather than assuming a subscription includes every source repair.
To assess fit, ask Zelluvo about an authorised supplier-source workflow. Share a non-sensitive example and describe the exact variant, available information and intended review process. A clear source specification is more useful than asking whether the tool can monitor an entire website.
Questions about monitoring without an API
Do I need to scrape a website if no API exists?
No. Ask about files, feeds, account reports or a documented manual process first. If page-based observation is permitted, assess its reliability and maintenance needs. Do not bypass access restrictions to obtain stock information.
Can an availability label be converted into a stock quantity?
Not without additional reliable evidence. “Available” describes a state, not a specific allocation. You may choose a conservative listing policy, but label it as your exposure decision rather than a measured supplier quantity.
What if the supplier changes the page layout?
Treat an uninterpretable reading as unknown and investigate. Preserve the last successful observation with its original time. Validate the exact variant and field meaning again before returning the source to routine use.
Will this process remove all overselling risk?
No. Supplier stock can change after observation and may be shared with other buyers. Reliable readings, careful mappings, exposure rules and prompt confirmed actions can support better decisions, but they do not reserve inventory.