Paste your company ID and API token, press Sync now, and your whole catalogue is on your site - listings, filters, offer pages, photo slider and agents. No ACF. No field mapping. No front end to build.
This is not a mock-up of what you could build. It is the archive the plugin renders on its own, out of the box, on any theme.
The plugin talks to the Esti CRM client API and nothing else. Without an Esti account and an API token there is no catalogue to synchronize.
Offers are read-only here on purpose: Esti CRM is the single source of truth, and each run overwrites imported content. Edit in the CRM, not in wp-admin.
Photos are hotlinked from the Esti CDN so imports stay instant and your disk stays empty. If you need every image copied onto your own server, this is the wrong tool.
No field mapping, no template work, no developer on standby.
Get pluginGet the latest .zip file. Go to Plugins > Add New in your WordPress dashboard and upload the file.
Open the plugin's Settings screen and enter the company identifier and API token issued by Esti CRM.
Import only certain offer types, cities, transactions or a price range - and pick which fields the filter bar shows.
Navigate to the plugin Settings > API Key and paste your license key from this dashboard.
The catalogue imports in the background and your offers are online, under /offers/, with filters, maps and agent cards already working.
Everything below is in the plugin. There is no add-on, no pro tier of the front end and no implementation package to buy.
A WP-Cron chain imports the catalogue page by page in the background, plus a Sync now button whenever you want it immediately. Unchanged offers are skipped, so a run costs almost nothing.
Type, transaction, location, price, area and rooms - each field switched on or off in the settings. Filters travel as plain GET parameters, so results are cacheable, linkable, back-button-safe and indexable.
Every offer gets a real page with a large swipeable gallery, all its parameters, video and virtual-tour links - not a row in a table.
Every run pulls the exported staff list - photo, role, office, phone, e-mail - and each offer page shows the agent who actually owns it in the CRM.
Restrict the import by offer type, subtype, city, transaction and price range - so a branch site can carry only the plots, or only Warsaw, out of the same CRM account.
Every run recorded with its status, duration, pages and counters - created, updated, unchanged, skipped, deleted - and the exact offers that failed. A dead run is flagged as interrupted rather than left spinning.
Other Esti CRM plugins for WordPress map the API to ACF fields, and stop there: the website itself is a separate project, priced separately. That is the part we ship.
Prices quoted for other integrations are the public list prices published by their vendors and may change. Ours are on this page, in full, below.
The bundled front end is a default, not a cage. Offers are a normal public post type exposed to the REST API, so the Gutenberg Query Loop and the Elementor Loop Grid list them with no extra code, and featured images resolve to the CDN thumbnail on their own.
[osfec_offers type="apartment" city="Warszawa" limit="3" columns="3" more="yes"]
// theme/single-osfec_offer.php wins over ours. $price = osfec_field( 'price' ); $rooms = osfec_field( 'rooms' ); $photos = osfec_photos();
No custom database tables. No taxonomies. No images copied into the media library. Offers are plain posts with plain meta, so uninstalling leaves nothing behind and backups stay the size they were.
We're here to help. Can't find what you're looking for? Reach out to our support team directly.
No. Offers are stored as ordinary WordPress posts with post meta - the plugin creates no database tables, registers no taxonomies and needs no ACF licence. Install it, paste two credentials, and it runs.
No, and that is the point. The offer archive with its filter bar, the full offer page with the photo slider, the map and the agent card all ship with the plugin and work the moment the first synchronization finishes. Building your own UI is an option, not a prerequisite.
Every six hours through WP-Cron, plus a Sync now button in the admin. Large catalogues are imported page by page in the background, so the first run finishes a few minutes after it starts and no request ever times out.
It drops out of the API response and its post is removed on the next successful synchronization. Esti CRM is the source of truth: offers are read-only in WordPress, and every run overwrites the imported content.
Nothing is deleted. Cleanup only runs after the last page of a successful run, so a failed run leaves your existing offers exactly where they are. An outage at the CRM can never empty your website.
They are served straight from the Esti CDN and never copied into the media library - the slider uses the large variant, listings the thumbnail one. Your disk usage and your backups stay the same size no matter how many offers you have.
Yes. The offer post type is exposed to the REST API, so the Gutenberg Query Loop and the Elementor Loop Grid can list offers with no extra code, and featured images resolve to the CDN thumbnail. There is also a shortcode, a block and template overrides in your theme.
The usual ones import Esti data into ACF fields and leave the display to you - which means Advanced Custom Fields plus a developer, or a paid implementation package that runs from roughly 699 to 1499 zl net for a single site, one-time. This plugin brings the whole front end with it and costs $35 a year for one domain.
WordPress 6.0 or newer, PHP 7.4 or newer, and the company identifier plus API token that Esti CRM issues for its client API. Nothing else.
Yes. Every paid plan comes with a 14-day money-back guarantee. If the plugin is not right for you, email szymon.zawadzki@llm-automatic-translation.top within 14 days of purchase and we will refund the licence fee in full, no questions asked.
Install the plugin, paste two credentials from Esti CRM and press Sync now. The offers, the filters and the offer pages are already built.
Get plugin