Previous support is unavailable
The former agency no longer responds or the original developer has left. The application still runs, but necessary changes remain unresolved.
Software development and ecommerce engineering from Leipzig
Stabilise established systems. Build new software with purpose.
ProWebSolutions takes over, develops and operates PHP, Shopware and PrestaShop systems—from database and integration work to dependable production operations.
Development from LeipzigPHP, SQL and custom softwareShopware and PrestaShopOperations and ongoing developmentDirect technical responsibility
Typical situations
When an established system becomes a business risk.
Many enquiries start without a finished specification. They start with uncertainty in day-to-day operations: knowledge is missing, errors recur or a connection between systems cannot be trusted.
The application is poorly documented
Business rules, database structures and external services have grown over time. The side effects of a change are difficult to predict.
Updates have become risky
PHP versions, dependencies or store extensions block routine maintenance and security work.
Data flows break
Store, ERP, payment, shipping or internal systems exchange incomplete data and teams repair the result manually.
Manual work consumes capacity
Staff copy data, maintain parallel lists and coordinate status by email although the process could be automated.
A full rebuild is too dangerous
The existing software contains important data, rules and exceptional cases that cannot safely be replaced in one release.
Core services
Technical work where standard answers are not enough.
Each service has a distinct purpose. Together they provide a controlled path from assessment and development to reliable operations.
PHP development
Maintain and extend backend logic, administration, data processing and SQL in established applications.
PHP developmentPHP takeovers and modernisation
Understand unfamiliar code and dependencies, stabilise operations and plan testable improvement stages.
PHP takeovers and modernisationCustom software
Build web applications for workflows, roles, portals, data processing and reporting.
Custom softwareShopware
Extend, integrate, update and technically support established Shopware 6 stores.
ShopwarePrestaShop
Work on modules, themes, upgrades, defects and external integrations in existing stores.
PrestaShopAPIs and integrations
Implement data flows with validation, retries, logging and an explicit recovery path.
APIs and integrationsMaintenance and operations
Coordinate updates, backups, monitoring, deployment, diagnostics and ongoing development.
Maintenance and operationsTakeover and modernisation
Understand and stabilise first. Change deliberately afterwards.
Source code is only one part of an established application. Production data, background jobs, server configuration, email delivery, external APIs, cron tasks, manual workflows and user knowledge are equally important. A responsible takeover therefore starts with a bounded assessment rather than a promise to rebuild everything.
Immediate operational risks are addressed first. The resulting plan separates urgent corrections from dependency upgrades, test coverage, logging, backups and structural changes. Components that still work can remain; risky areas can be isolated and replaced in controlled stages.
- Capture access and production paths
- Make reported failures reproducible
- Assess database and dependency risks
- Prioritise stabilisation separately from modernisation
Established ecommerce
Shopware and PrestaShop are part of a wider system landscape.
A store does not end at the storefront. Product data comes from multiple sources; orders, payments and shipping status must be processed; marketing and analytics need deliberate integration. Operational failures often occur at these boundaries rather than on the visible product page.
Changes are therefore evaluated in context: which extension affects checkout or pricing, which task synchronises stock, which system owns each field and how an upgrade can be tested and reversed. The objective is a commercial platform whose critical paths do not depend on hidden individual knowledge.
- Shopware 6 plugins, storefront, flows, upgrades and integrations
- PrestaShop modules, themes, diagnostics, upgrades and APIs
- Payment, shipping, product feeds, ERP and inventory systems
- Performance along real user and data journeys
Integrations and automation
Data must not only arrive. It must arrive correctly and remain traceable.
A successful HTTP status alone does not prove a consistent business process. Reliable integrations account for validation, duplicates, partial failures, retries and the operational response after launch.
Source systemStage 01
Validation & mappingStage 02
API / queueStage 03
Target systemStage 04
Logging & monitoringStage 05
Recovery pathobservable and repeatable
A product flow may read changes from an ERP, translate fields and units, validate mandatory values and send only valid records to a store. Invalid records are not silently discarded. They receive a clear state and can be processed again after correction.
The same principle applies to orders, customer data, documents, payment status and internal workflows. Good automation removes manual work without introducing invisible dependencies.
Approach
From an uncertain situation to dependable next steps.
The exact scope depends on the system. This sequence prevents change from starting before the relevant operating context is understood.
Clarify the situation
Define the business impact, current issue, participants, access and known deadlines.
Assess the system
Review code, dependencies, database, logs, deployment, backups and external services according to risk.
Secure operations
Immediate failures and missing recovery options take priority over structural improvements.
Deliver the roadmap
Break change into testable packages, document decisions and deploy with a suitable rollback path.
Selected project experience
Current development, technical support and an in-house product.
Three project profiles show current work across ongoing support and end-to-end product development.
Current technical support
HomeCare Studio
ProWebSolutions supports HomeCare Studio with technical maintenance and ongoing development of its existing web presence.
- Role
- Technical support and continuous development by ProWebSolutions.
Current development project
PremiumPlaner.com
ProWebSolutions is the sole technical development partner responsible for the development and ongoing improvement of PremiumPlaner.com.
- Role
- The complete technical concept and implementation are the responsibility of ProWebSolutions.
In-house software product
DMCA Protect
DMCA Protect is a software product developed and operated by ProWebSolutions for automated digital protection and processing workflows.
- Role
- Concept, technical development and ongoing operation are handled by ProWebSolutions.
Personal responsibility
Direct technical responsibility instead of agency hand-offs.
ProWebSolutions is technically led by Norman Kaubisch. Architecture, development and central project coordination remain under direct responsibility.
Requirements, decisions and their impact on the application stay traceable. Responsibilities and any additional specialist work are agreed transparently for each engagement.
Technical leadership and working principlesTrust without theatre
Complex systems still need understandable decisions.
Concrete project experience, direct communication and documented trade-offs create a dependable working basis.
Direct technical exchange
Requirements and risks are not translated through several sales layers.
Reality before an ideal architecture
The production application and its dependencies determine the order of work.
Limits remain explicit
An initial review provides priorities, not unsupported guarantees about an unknown system.
Operations remain part of the solution
Deployment, observability and recovery paths are considered early.
Technical system review
A bounded first step when the priority is still unclear.
Depending on access and scope, the review can cover architecture, codebase, PHP runtime, dependencies, database, logs, performance, deployment, backups, maintainability and visible security risks.
The result is not a generic quality badge. It is a prioritised technical assessment of immediate risks, missing information, useful first measures and realistic next steps. Scope, access and price are agreed before work begins.
Request a technical system reviewFAQ
Frequently asked questions
Does an old PHP application always need a complete rebuild?
No. The first task is to establish which parts work reliably, which risks threaten operations and where a change would create the most value. Incremental modernisation is often more controllable and economical than replacing everything at once.
Can you take over a system you did not build?
Yes. The initial assessment covers source access, runtime, dependencies, database, deployment and available operational knowledge. Unknown risks are documented instead of hidden behind a general promise.
Do you only work with companies in Leipzig?
No. Leipzig is the company location and enables in-person meetings where useful. Assessment, development and ongoing collaboration can also be organised remotely.
What should an initial enquiry include?
The type of system, current problem, business impact and desired timeframe are enough for a first conversation. Credentials and confidential technical data should not be sent through the standard contact form.
What does a technical system review deliver?
The agreed scope produces a prioritised view of risks, missing information and next steps. It is neither a full security audit nor a guarantee that every dependency can be found without adequate access.
Your system does not need to be perfectly documented before we talk.
Describe the current situation. The first step is to identify which information is still needed for a useful technical assessment.