Why dealer feeds get rejected
Most disapprovals come from the same handful of problems in the source data. A DMS export is written for accounting, not advertising, so it arrives with codes, blanks and duplicates Google will not accept.
- Zero or missing prices on vehicles that are still in prep
- Condition stored as a DMS code (N, U, C) rather than new or used
- The same VIN listed twice after a transfer between rooftops
- Blank image or landing-page links for vehicles without photos yet
- Titles that read “2024 CHEV SLVRDO 1500 CREW 4WD LT”
Fix it once, at the feed
Instead of cleaning a spreadsheet every week, you write each fix once and MiFeed applies it to every vehicle, every day. Fall back to internet price or MSRP when price is empty, translate condition codes with a value map, drop vehicles without photos with a filter, and de-duplicate by VIN. Health checks score the feed before it is published and point to the exact rows that would fail.
Pricing that matches your website
Google compares the price in your feed with the price on your vehicle page. MiFeed’s pricing rules — discounts by make, model or days in stock, aging markdowns, a margin floor and an MSRP ceiling — produce one computed price that every channel publishes, so your Google price, your Facebook price and your marketplace price agree.
Typical Google vehicle fields and where MiFeed finds them
| Channel field | How MiFeed fills it |
|---|---|
| id / VIN | Your VIN column, validated and de-duplicated |
| title | Year, make, model and trim, cleaned up by formula |
| price | Your pricing policy, or internet price → price → MSRP |
| condition | DMS code translated to new or used |
| mileage | Odometer column, with unit added |
| link / image_link | Vehicle page URL and first photo from your photo list |