Websites · WordPress
WordPress development for catalogues and connected systems.
WordPress development for catalogues and portals that need structured content, controlled editing and connections to a CRM or stock system. Our plugins do the decisive parts: redirects that survive a migration, images as WebP, appropriate structured data from the content, and the integration that reads your system. From €3 000.
What it is made of
The panel of our plugin, as the client sees it
Illustrative data. Click a tab; the panel does one job per tab.
| Old address | New address | Status |
|---|---|---|
| /oferta/mieszkania/ | /estate/mieszkanie-na-sprzedaz/ | 301 |
| /o-nas.html | /about/ | 301 |
| /blog/2019/nowe-osiedle | /news/nowe-osiedle/ | 301 |
| /kontakt.php | /contact/ | 301 |
| /pdf/cennik.pdf | /pricing/ | 301 |
272 old addresses mapped for our own migration · 0 chains · 0 dead ends
- hero-kitchen.jpg
2.4 MB186 KB WebP - plan-parter.png
1.1 MB92 KB WebP - team-photo.jpg
3.8 MB240 KB WebP - logo-partner.png
410 KB18 KB WebP
converted on upload · original kept · served by size of screen
optional resource summary · not a Google AI-search requirement
- Dom na sprzedaż, MogilanyCRM #LOK-DS-278published
- Mieszkanie na wynajem, KrakówCRM #LOK-MW-102updated: price
- Działka, SkałaCRM #LOK-GS-391published
- Hala, NiepołomiceCRM #LOK-HW-014sold: page removed
illustrative import · update interval and removal rules agreed per project
What you get
Designed for your catalogue, built without a page builder or a marketplace theme. Performance checked with the real catalogue and integrations.
Agreed redirects, image handling, structured data and connections to your CRM or warehouse. The implementation and maintenance responsibilities are documented.
An agreed import can publish and update listings or products from supported sources. We define field ownership, update intervals, removal rules and failure handling; the team remains responsible for source accuracy and exceptions.
Who this is for
Sites with more pages than a team can type
Properties from the CRM to the site, filters, property pages. Lokalizacja is this case.
Thousands of products with variants, prices from a spreadsheet or an ERP, dealers by region.
Developers and their buildings, clinics and their doctors: one structure, many sources.
WooCommerce where the store shares data with the catalogue and needs custom logic.
Price
From €3 000 for a catalogue or portal. Scope and date per project.
A smaller company site on WordPress is priced after a short call. Hosting on your account.
A catalogue needs a data model before it needs a theme
A WordPress catalogue is often the public view of a larger business process. Products may come from a warehouse system, properties from a CRM and technical documents from an internal library. The first question is therefore what each record means and which system owns it. Without that decision, a website can display an attractive catalogue while quietly publishing conflicting prices, availability or specifications.
Records and relationships
We describe the main objects and their relationships before importing data. A development may contain buildings, apartments and downloadable plans. A supplier may have product families, variants, certificates and compatible accessories. Some relationships belong in the database; others are editorial links. Getting this distinction right makes filters more useful and reduces manual repairs when the catalogue grows.
What editors control
The editing boundary matters just as much. Your team might control descriptions and photographs while the stock system controls availability. An automated update should not overwrite a carefully edited introduction unless that behaviour was agreed. We record the source of each field and decide what happens when a source value is missing, invalid or temporarily unavailable.
Compare the ongoing work, not only the initial build
WordPress can support a small company website as well as a substantial catalogue. Page count alone does not choose the platform. A useful comparison includes the publishing workflow, unusual features, data ownership, hosting responsibility and the cost of keeping the system healthy. The right choice is the one your organisation can operate consistently after launch.
A managed marketing site
If the requirement is a marketing website with straightforward collections and a team that wants managed hosting, we compare Webflow. If the priority is standard ecommerce, we also evaluate Shopify against the actual payment and fulfilment needs. These comparisons should use the required functionality rather than a general argument about which platform is more professional.
A system you control
WordPress is a candidate when control of hosting and application code matters, or when the catalogue requires a specific integration or editorial workflow. That control comes with responsibility for updates, backups and compatibility. A custom theme does not eliminate those tasks. We include them in the decision so the website is affordable to operate as well as possible to build.
Design an import that can be corrected safely
Inspect a sample
We first inspect a representative export or API response, including awkward records. Stable identifiers, image locations, units and status values matter more than how clean the first five rows look. A useful sample includes a deleted listing, an unavailable product, a variant and a record with incomplete information. These show whether the proposed mapping works beyond the happy path.
Reconcile changes
The import needs rules for creating, updating and retiring entries. Running the same feed twice should not create two versions of every product. A removed source record needs an agreed outcome: unpublish, mark unavailable or retain a useful archive. We distinguish a genuine empty catalogue from a temporary connection failure before applying destructive changes.
Handle exceptions
Errors should be visible to the person who can fix them. A report might identify an unknown category, an image that could not be downloaded or a price that failed validation. We plan a safe retry and keep a record of the last successful update. Silently skipping errors leaves the website looking current when it is not.
Make filters and detail pages useful to a buyer
- Browse
- Filters should use criteria buyers actually know: size, compatibility, location or availability. Internal product codes can remain searchable without becoming the main navigation. We check combinations that return no results and give the visitor a clear way to broaden the selection. On a phone, filtering should not cover the entire result set with controls that are difficult to dismiss.
- Evaluate
- A detail page needs enough information to support the next decision. That may include dimensions, delivery restrictions, a downloadable drawing and related alternatives. Images should have a purpose and an appropriate size. For complex products, a well-structured specification table can answer questions that a generic promotional paragraph never reaches. Missing information should be visible rather than replaced with invented copy.
- Enquire
- The enquiry should preserve context. If a visitor asks about a specific listing, the form can carry its identifier and title so the sales team knows what was viewed. We decide which fields are essential and how the request reaches the responsible person. A complete catalogue is commercially useful only when someone can act on the interest it creates.
Maintenance and migration are part of the architecture
Recovery
A backup is useful when it can restore the database and the files required by the site. We agree who manages backups, where copies are kept and how recovery is tested. The same plan should cover hosting access and the credentials needed to restore integrations. A folder of theme files alone will not recreate a catalogue with its content and uploads.
Updates
WordPress and its extensions require maintenance. Before significant updates, take a current backup and use a staging environment where the risk justifies it. Test imports, forms, checkout and custom functionality after changes. Plugin count is not a reliable quality score: a small collection of poorly maintained extensions can be more troublesome than a larger, well-managed set.
Search continuity
For a migration, preserve useful addresses where practical and map changed URLs to relevant replacements. Review metadata, canonical addresses, internal links and indexing controls before launch. Redirects reduce avoidable breakage; they cannot guarantee unchanged rankings. We compare crawl and enquiry data after the move so errors are found while the migration context is still clear.
What we need to estimate your WordPress project
Bring one realistic sample
Send a sample of the data that will populate the site, the current website address, the expected number of records and the systems that must exchange information. Include the features your current platform cannot handle and the tasks your staff repeat manually. A small, representative sample usually answers more technical questions than a long feature wishlist.
Catalogue and portal projects start at €3,000; smaller WordPress sites are scoped separately. The quote separates design, data migration, custom behaviour and ongoing operation. Paid extensions, hosting and external services should be visible before approval. We also identify dependencies such as access to a supplier API, because a missing permission can affect the schedule more than the number of page templates.
A useful first delivery is a working slice: one imported record, its public detail page, the relevant filter and the enquiry path. Reviewing that slice validates both the data and the design before the full catalogue is loaded. It gives your team something concrete to test and gives the project a clear acceptance standard.
Questions
Questions people ask about WordPress
When is WordPress the right choice for a catalogue or a portal?
WordPress is an option when a catalogue needs structured content, integrations or control of the application and hosting. It can also serve smaller sites. We compare the editorial workflow, required features and maintenance responsibilities instead of choosing by page count alone.
What do your own WordPress plugins do?
The boring, decisive parts: a redirect map that survives a migration, images converted and served as WebP, page titles and structured data from the content, optional public resource summaries, and the integration that reads listings or products from your system. Extensions and custom code are chosen for the agreed requirements and documented for maintenance.
Do you build WooCommerce stores?
Yes. WooCommerce can suit a WordPress catalogue or a business needing control over hosting and application code. Shopify also supports wholesale and B2B workflows on eligible plans, so wholesale pricing alone does not decide. We compare required features, integration access and operating costs; The Beast Beauty is a published WooCommerce example.
Is WordPress slow, and how do you handle speed and SEO?
Performance depends on hosting, implementation, images, extensions and the work each page performs. A custom theme alone does not guarantee speed. We measure representative pages, identify bottlenecks and test changes with the real content and integrations in place.
How do you reduce search disruption during a WordPress migration?
We map changed addresses to relevant replacements and preserve useful URLs where practical. Removed content without an equivalent can return an appropriate 404 or 410 response. Redirects, important content and Search Console are reviewed before and after launch. Rankings can move when structure changes; the map and the measurements make it a controlled move.
How much does a WordPress catalogue or portal cost?
Catalogue and portal work starts at €3 000. Record volume, data preparation, templates, custom extensions and supported integrations are named in the quote. A smaller company site on WordPress is priced after a short call. Hosting is on your account; we recommend and set it up.
Get a fixed quote
Tell us where the data lives
Hundreds of pages and a system behind them?
Tell us where the data lives. We say how the site reads it and what it costs.