Inventory problems are not always obvious. A reader can return dozens of plausible vehicle cards while skipping later pages, stopping at one thumbnail per car, or pulling recommendation images into the wrong gallery. Those failures matter because every downstream caption, photo review and listing begins with the vehicle record accepted here.
The failure class is not theoretical. Frazer’s own support material includes troubleshooting for many or all vehicles missing, a few vehicles missing and vehicle photos missing from websites. Nexgate’s support material separately covers stock items not visible in its inventory view and photo-upload problems. Those pages describe their own systems—not AutoPosting Pro and not every dealership—but they show why inventory completeness and photo ownership need separate checks. Sources: Frazer vehicle-upload troubleshooting and Nexgate inventory troubleshooting.
Five warning signs and what they usually mean
| Warning sign | What it may mean | Safe response |
|---|---|---|
| The first page looks right, but cars are missing | Pagination, load-more behavior, filters or an alternate inventory route may not have been followed. | Compare distinct discovered vehicles with the source lot count and inspect page-by-page additions. |
| Most vehicles have exactly one image | The reader may be taking the listing-card thumbnail instead of the vehicle detail gallery. | Use the vehicle detail page as the gallery boundary and inspect the full-resolution candidates. |
| A vehicle has 20 photos, but several show other cars | A broad image selector may have crossed into related inventory, recommendations or a page-wide carousel. | Require vehicle identity near the gallery and exclude images outside that vehicle's detail container. |
| The refresh suddenly returns zero or far fewer cars | The site may have changed, returned a challenge, failed to finish loading or exposed a partial view. | Hold the candidate. Keep the last-known-good inventory until the smaller result is explained. |
| Photos are right, but VIN, price or mileage is blank | The visual match alone is not enough to establish a complete posting record. | Treat required-field coverage separately from photo coverage and hold incomplete vehicles for review. |
1. Establish the source-of-truth count
Start with the dealership’s public used-inventory view. Record the visible total when the site publishes one, then count distinct VINs or canonical vehicle detail links across every page or load-more state. Card count alone is weak evidence: the same vehicle can appear twice, and a carousel or featured section can look like part of the main inventory.
- Track new distinct vehicles added by each page or interaction.
- Stop only when the next state adds no new vehicle identities—not merely when the URL repeats.
- Record exclusions such as new inventory, sold units or a location filter so the comparison is reproducible.
2. Bind every record to a vehicle identity
Use the VIN when the website publishes it. A stock number or canonical detail-page URL can help locate a record, but neither should silently replace a conflicting VIN. The year, make and model are useful for human review; they are not unique enough to prove that two records are the same car.
Identity conflict rule
If the listing card, vehicle page and structured data disagree about the VIN or core vehicle identity, hold that record for review. Do not choose whichever value is easiest to extract.
3. Treat the vehicle detail page as the gallery boundary
Listing pages are optimized for browsing the lot, so one thumbnail per vehicle is normal. The detail page is where a full gallery usually lives—but it can also include logos, finance art, recently viewed vehicles and related-car rails. The goal is not “all images on the page.” The goal is “the usable, full-size images owned by this vehicle.”
- Find the vehicle-specific detail region. Confirm the surrounding VIN, stock number or vehicle heading.
- Collect full-resolution candidates. Prefer the image URL intended for display or zoom, not the smallest thumbnail variant.
- Exclude non-vehicle assets. Remove placeholders, logos, navigation icons, banners and related-vehicle cards.
- Normalize and deduplicate. Query-string size variants should not create twenty copies of one photo.
- Review identity evidence. A large photo is still wrong if it belongs to a different car.
4. Score required fields separately from photos
A good gallery cannot compensate for a blank price or wrong mileage. AutoPosting Pro’s baseline acceptance check covers VIN, year, make, model, price, mileage, exterior color, description, a stable vehicle detail URL and usable photos across the complete candidate. Trim, interior color, transmission and other features improve the record but do not hide a failure in those required fields.
- Distinct vehicle count and identity
- VIN, year, make and model coverage
- Price, mileage and exterior-color coverage
- Description and vehicle-detail URL coverage
- Usable photo count by vehicle
- Duplicate VINs or detail URLs
- Identical galleries across different VINs
- One-photo concentration
- Placeholder or thumbnail-heavy galleries
5. Compare with the last-known-good inventory
A refresh is a candidate, not automatically the new truth. Compare it with the last accepted lot: vehicle count, VIN additions and removals, field coverage, and the distribution of usable photo counts. A legitimate sell-down can reduce inventory, but a sudden unexplained collapse should be reviewed before it removes hundreds of usable records.
6. Review the exceptions before Marketplace
The final screen should explain what passed, what changed and what was held. A salesperson does not need to watch every network request, but they should be able to see whether the vehicle they are about to queue has the expected VIN, year, make, model, price, mileage, exterior color, description, vehicle link and gallery. The same record should follow the vehicle into caption and photo review.
Inventory sync questions
Why can an inventory sync find some cars but miss others?
A listing page may paginate, load more cards after interaction, apply a default filter, or link to a different used-inventory route. The reliable check is distinct vehicle identity across every discovered page, compared with the dealership's visible or published total—not whether the first screen looked populated.
Why does each vehicle sometimes get only one photo?
Inventory cards often expose one thumbnail while the vehicle detail page contains the actual gallery. A reader that stops at the listing card can produce a believable vehicle count but still miss most of the photos.
Why do photos from other cars appear in one vehicle's gallery?
Vehicle pages can contain recommendation rails, recently viewed cars, logos, banners and hidden carousel assets. Collecting every image on the page is not the same as identifying the gallery owned by that vehicle. Gallery candidates should stay inside a vehicle-specific detail region and be checked against that vehicle's identity.
Should a smaller refresh immediately remove vehicles from the app?
Not when the drop is unexplained. An empty or sharply smaller result can reflect a temporary website response rather than a real inventory change. Hold the candidate, show the difference and keep the last-known-good inventory until the new result passes review.
Does AutoPosting Pro require a DMS feed or CSV?
No. Public AutoPosting Pro configures a site-specific reader for the dealership's public inventory website and runs it through the signed-in Chrome workflow. The candidate still has to pass its inventory and vehicle-gallery checks before it can replace cloud inventory.
Does verified inventory guarantee a Facebook Marketplace listing will be accepted?
No. Inventory verification covers the dealership-data side of the workflow. Facebook controls Marketplace access, account eligibility, interface availability and final listing acceptance.
Ask for the evidence, not a green badge.
The useful proof is a complete candidate with explainable vehicle count, required-field coverage, VIN-owned galleries and a safe decision about what can replace the last accepted inventory.
See how AutoPosting Pro verifies the candidate