| 开发者 | jawaid |
|---|---|
| 更新时间 | 2026年6月23日 02:23 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
{manufacturer} {brand} {model_year}Yes. The smart field mapping system auto-detects feed structure and works with any flat XML or CSV export. We have verified compatibility with feeds from vAuto, HomeNet, Dealer.com, VinSolutions, Dealertrack, CDK Global, Reynolds & Reynolds, DealerSocket, DealerCenter, AutoManager, Frazer, Wayne Reaves, DealerCar Search, ELEAD, and any custom DMS that can export an XML or CSV file accessible via URL or server path. No custom development required — just map your fields once.
Yes. The plugin's field structure aligns with Google's required attributes (VIN, make, model, trim, year, mileage, condition, price, image_link, dealership_name, dealership_address). The Pro version adds Schema.org Vehicle JSON-LD markup, making your vehicle detail pages eligible for Google's vehicle rich results.
The plugin imports and stores all the standard fields required by Meta Automotive Inventory Ads and Microsoft Advertising vehicle catalogs. A separate companion plugin, Vehicle Feed Exporter, is in development to push your inventory directly to Google Merchant Center, Meta Catalog, and Microsoft Advertising.
Any standard CSV with a header row and any flat XML with two levels (root > vehicle > fields). Field names don’t matter — you map them in the settings.
Yes. The plugin is fully theme-agnostic. It also provides its own frontend templates (optional) for listing and detail pages that adapt to your theme’s styling.
You can configure the plugin to automatically draft, trash, or mark as sold any vehicle that disappears from your feed. No manual cleanup required.
Yes. All imported fields are editable in the WordPress editor. Note that manual edits may be overwritten on the next sync unless you use the upcoming field lock feature in the Pro version.
Yes. The plugin downloads all images from your feed into the WordPress Media Library, sets the first as the featured image, and displays all images in a gallery on the detail page.
No. The import runs via WordPress cron in the background. Images are downloaded once and cached in your Media Library. Frontend pages use standard WordPress queries.
Yes. The plugin is fully translation-ready, and a complete Italian (it_IT) translation is included out of the box — the admin settings and the customer-facing vehicle pages display in Italian automatically when your site language is set to Italiano. More languages are welcome: anyone can contribute or improve a translation for the free version at https://translate.wordpress.org/projects/wp-plugins/automotive-feed-import/.
Please use the WordPress.org support forum for this plugin, or visit https://ibexoft.com/products/automotive-inventory-import-sync-car-dealer-feeds/ for direct support.
Yes — this is a Pro feature. Go to Automotive Sync → Settings → Feed & Sync and use the Import Vehicles Into dropdown to pick any custom post type registered on your site — for example one provided by Inventory Presser, the Motors – Car Dealership & Listing plugin, AutoListings, WP-CarManager, a dealership theme, or your agency's own setup. The plugin will write feed data into that post type instead of the built-in Vehicles section, so the other plugin or theme can display it using its own templates. (The free version imports into the built-in Vehicles section.)
The plugin tags every post it creates with an internal marker so it can tell its own data apart from posts you created manually. Stale-listing actions and existence checks only ever touch posts carrying that marker, so your manually-created listings are never modified or deleted by the importer. That said, importing into another plugin's post type touches data that plugin owns. Please follow this checklist before your first import into a third-party post type:
afi- to prevent clashes with other plugins. If you wrote custom CSS in your theme targeting classes like .spec-card, .filter-form, .vehicle-archive-card, .view-details-btn, etc., rename your selectors to use the new .afi-spec-card, .afi-filter-form, .afi-vehicle-archive-card, .afi-view-details-btn prefixed versions.