Listing platform OtoBroń

The platform had to accommodate three perspectives: visitors looking for specific information, authors managing their publications and the operator responsible for reviewing them. Simplifying one path could not overlook the consequences for the others.

Different listing types also required different logic. For a venue, location, facilities and opening hours mattered. For an event, the date and its connection to a place were important. A universal form would obscure these differences, while putting the information in the description alone would prevent its use in search.

Similar dependencies applied to the backend. Allowing a listing to be edited meant defining rules for renewed moderation. A publishing package required connecting user entitlements with an order and a validity period. Seemingly small decisions affected the entire platform.

We based the implementation on WordPress, MyListing and WooCommerce, combining configuration of existing mechanisms with our own extensions. The directory engine handled the basic listing functionality; our role was to adapt its structures and rules to OtoBroń and add functionality where custom logic was needed.

The publication lifecycle was a separate area of work. In line with the client’s requirement, editing a published listing sent it back for moderation. The dashboard distinguished active publications, those awaiting approval, those awaiting payment and expired ones. We connected these states with the system’s communication settings: we enabled 12 notification types covering listing approval, messages, reports and approaching expiry, among other events. We also adapted the messages for the Polish-language website.

For a listings platform, we select indicators showing whether visitors find the information they need and whether authors can use the publishing service. The portal’s package revenue should be distinguished from transactions between listing users.

Search effectiveness

Transitions from results to venue profiles, training and events, together with the proportion of searches returning no results, help assess the usefulness of data and filters. Analysis by listing type shows where visitors need a better path.

Completing a submission

The proportion of started forms that result in a listing submitted for moderation shows whether authors complete the process. Time from submission to the operator’s decision distinguishes form difficulty from waiting for a review.

Package purchase and renewal

Paid package orders and renewals measure use of the portal’s paid service. Comparing them with started orders and expiring publications helps identify stages that need improvement.

Our custom code also covered media and supporting content. We added a mechanism that applies a watermark to JPEG and PNG images uploaded by users other than the administrator. We created a dedicated OtoBroń plugin with Elementor modules, including an editable FAQ with answer search, as well as an automatic table of contents for articles. The extensions therefore addressed daily publishing and content maintenance as well as the website’s appearance.

OtoBroń received a platform where different publication types share a common backend while retaining their own forms, presentation and search criteria. The listing author’s experience was connected with moderation rules, packages and operator communication.

The value of the project lay in translating the portal concept into specific operating rules: what data is collected, where it is used, who can manage it and what happens when a publication’s status changes. These dependencies, supplemented by custom extensions, formed the core technical work behind the OtoBroń interface.