Publishing listings from the CRM, to Bayut, Property Finder and Dubizzle
A property is entered once, with photographs, attributes and price, then published to the portals you choose. Enquiries from the listings arrive straight in the pipeline, with the portal they came from recorded.
From $2,900one-time payment, no monthly subscription
Publishing property listings from the CRM. One description, publishing and withdrawal across several portals, enquiries returned to the pipeline.
Works together with: Connectors and API, Lead management, Automation and AI.
What happens when the same property is entered three times
Three interfaces, the same photographs, three chances to get it wrong.
- The same property is entered separately into each portal, with the photographs uploaded again each time.
- When the owner drops the price, the agent has to remember everywhere it was published.
- A sold property stays live on a forgotten portal and generates pointless calls.
- Enquiries land in three different inboxes.
- Nobody knows which portal brings real buyers and which only browsers.
- A listing rejected by a portal is discovered late, if at all.
What portal publishing includes
From a single description to an assigned enquiry.
Described once
Attributes, areas, layout, photographs and price are entered on the property record in the CRM.
- Full attributes
- Photographs in one place
- Price and history
- No duplication
Published to chosen portals
You select where the listing goes. Each portal has its own required fields, mapped to the CRM record.
- Selection per portal
- Field mapping
- Validation before sending
- Publication status
One change, updated everywhere
A new price or new photographs propagate at the next synchronisation, across every active portal.
- Price propagated
- New photographs
- Description updated
- No manual work
Withdrawn when sold or let
When the property is marked unavailable, the listings are withdrawn automatically.
- Automatic withdrawal
- No pointless calls
- Reputation protected
- Agents freed up
Enquiries arrive with their source
Messages from the listing become pipeline enquiries, with the portal recorded, so budget can follow evidence.
- Enquiry in the pipeline
- Portal recorded
- Assigned to an agent
- Cost per enquiry
The same mechanism in Romania
On the Romanian edition the connected portals are OLX, Storia and Imobiliare.ro, on the same flow.
- OLX
- Storia
- Imobiliare.ro
- Same flow
What changes in the first month
It shows up within the first few dozen listings.
Publishing time drops
One entry, not three.
- No retyping
- Photographs once
- Live in minutes
Prices stop disagreeing
A change propagates on its own.
- Consistent data
- Fewer complaints
- Credibility
Pointless calls disappear
Listings for sold properties are withdrawn.
- Agents freed
- Less customer frustration
- Better reputation
Enquiries reach the right agent
Assigned by area or by rota.
- Nothing lost
- Faster reply
- Clear ownership
Portals become comparable
Cost per enquiry on each one.
- Budget on evidence
- Weak portals dropped
- Return measured
Rejections get fixed immediately
The reason arrives in the CRM.
- Visibility
- Fast correction
- Listings stay live
How a property travels, step by step
From entry to an assigned enquiry.
Each portal has its own content rules, photograph limits and required fields. The integration follows their interface, but the acceptance criteria remain theirs.
- Content rules are theirs
- Photograph limits are theirs
- Required fields differ
- Paid promotion is theirs
- Ranking in listings is theirs
- Publishing access is granted by them
A rejected listing is corrected and resubmitted, with the reason received from the portal. The CRM cannot force publication.
- 1
The property is entered in the CRM
With all attributes and photographs.
- 2
Portals are selected
Where the listing should appear.
- 3
The listing is published
With fields mapped to each portal’s requirements.
- 4
Changes propagate
At each synchronisation.
- 5
Enquiries enter the pipeline
With the originating portal recorded.
- 6
The listing is withdrawn on sale
Automatically, when the status changes.
What reduces the administrative load on listings
Configurable rules, no programming.
Publish when available
With no manual step.
Withdraw when sold or let
Across every active portal.
Propagate a price change
At the next synchronisation.
Assign the enquiry
By area or by rota.
Alert on rejected listings
With the reason received.
Report per portal
Listings, enquiries, cost per enquiry.
Access to properties and portal accounts
Owner details stay in your own installation.
- Portal credentials stay with you In your own installation, not with an intermediary.
- Owner details do not leave Only the listing content goes to the portal.
- Publishing can be limited by role Not every agent needs to publish.
- Every publication leaves a trail Who published and when.
- Withdrawals are recorded With author and time.
- Exclusive mandates can be held back Sensitive properties are not published automatically.
What to prepare before the first publication
Matters to settle with the portals.
A professional agency account
With publishing access through an interface or feed.
Field mapping
Which CRM attribute matches each portal field.
A photograph standard
Resolution and count, within each portal’s limits.
The enquiry assignment rule
By area, by rota or to the listing agent.
The list of active portals
Where you publish by default and where only on request.
Scheduled server job
For synchronisation and enquiry collection.
The limits of portal publishing, stated plainly
What the module does not do.
- The portal decides what it accepts. A rejected listing is corrected and resubmitted; the CRM cannot force publication.
- Publishing access is obtained from the portal. Not every account has it; it usually requires a professional agency subscription.
- Paid promotion stays with the portal. Featured packages and ranking are managed in your own portal account.
- Synchronisation runs on an interval. Between runs, the listing reflects the state at the last synchronisation.
- Historic duplicates are not cleaned retroactively. Listings published manually before the integration do not become CRM-managed on their own.
- Photographs follow the portal’s limits, not ours.
When publishing from the CRM makes sense and when it does not
Stated plainly.
A good fit if
The situations in which the module pays for itself quickly.
- You publish to at least two portals in parallel.
- Your portfolio changes often.
- You want enquiries assigned to agents automatically.
- You care about cost per enquiry on each portal.
Not a fit if
The situations in which we recommend not buying it now.
- You have a handful of properties, listed once a year.
- You work purely on referrals, without listings.
- You have no professional account with any portal.
- You publish only on your own website.
Which package the connectors and API module belongs to
The module is licensed together with external integrations.
Two modules, one package
The programming interface, keys and events are part of the API and integrations module. Connectors to external services and data feeds form the connectors module. The package that includes each of them is shown on the pricing page.
What every package includes
Every package includes users and roles, clients and contacts, a lead and sales pipeline, custom fields and 15 interface languages.
Invoicing and payment connectors
They are used together with the invoicing module and the payments and collections module.
Pricing and configurations
Package composition and prices by edition are on the pricing page.
Companies that have trusted Zarina CRM
Portal publishing: what it costs and what you get
You pay once. Everything that follows is written here, not in hidden conditions.
The Portal publishing module is included from the PRO package: $3,480, paid once, for the whole company.
The same CRM, in 3 packages. Each package includes everything in the one before it:
- STARTDoes not include this module$2,900
- PROIncluded$3,480
- BUSINESSIncluded$4,640
One-time payment, unlimited users. What each package contains is on the pricing page.
What you pay over time for a subscription CRM
Over 3 years, the subscription costs $9,000; the Zarina PRO licence costs $3,480, once.
An indicative comparison: enter the subscription price you pay now. The licence does not grow with the number of users.
What you get
- A lifetime licence, with no subscription and no per-user charge
- Unlimited users, on the same licence
- 6 months of warranty on correct operation: fixing errors and inconsistencies
- Implementation, configuration and team training, included in the price
- The licence is verified locally, on your own server: the application does not depend on our servers to work
How long it takes and what is needed
- 48 hours in the standard configuration; up to 14 working days with customisation around the company’s workflow
- Your own server or web hosting with cPanel, with an SSL certificate
- PHP 7.4 or newer (8.x recommended) and MySQL / MariaDB
- The PHP extensions mysqli, json, mbstring; curl, gd and zip for integrations, PDF and exports
- One cron task, for reminders and automations
Where data lives
- The data stays on your server and does not pass through ours
- Roles and rights per user, two-factor authentication
- An audit trail and limits on login attempts
- Consents and data subject requests, managed in the application
- Digitally signed updates and backups from the application
Do you have a question about portal publishing?
We answer in writing, with the exact price for your configuration.
Questions about publishing listings to property portals
Can I publish to several portals at once?
Do enquiries from listings arrive in the CRM?
What happens when the property is sold?
Do I need a special account with the portal?
Can the portal reject a listing?
Is paid promotion managed from the CRM?
Does it work for the Romanian market too?
Get the complete product sheet by email
A six-page document with everything you need to know before a sales conversation. No obligation and no sales call.
- All the modules of the platform and the package that includes each one
- The features and modules of the edition you choose, plus available integrations
- Full pricing and what it includes: installation, training, data import, warranty
- The native integrations available and the situations where the platform is not a good fit
Take control of your operations, once
We install Zarina CRM on your hosting, configure it around your own workflow and train your team. From that moment on, the application is an asset of your company, not a recurring expense.