Case Study · Parking Marketplace

Recovering an incomplete parking marketplace and carrying it to mobile

Pewny Parking connects drivers who need a dependable place to park with owners who have space to offer. In 2020, we inherited a buggy, unfinished application, stabilised the existing work and completed the search, availability, booking, payment and marketplace-management flows. After launch, we extended the same product with REST APIs for its mobile application.

Client: Pewny Parking
Sector: Parking discovery & booking
Our role: Recovery, completion & mobile APIs
Year: 2020

2020the year we took over the application
3connected views for drivers, owners and staff
2languages across the public experience
RESTan API layer added for the mobile application

Explore the working demo

See the bilingual discovery experience and the route from parking search to a detailed, bookable space.

Open the live demo

Opens in a new tab

Want the private-side tour?

We can walk through owner operations, payments, administration and the mobile API surface.

Book a walkthrough

About 30 minutes, no obligation

The product we inherited

The marketplace concept and parts of the codebase already existed, but core paths were unreliable or unfinished. We began by tracing the existing data model, repairing the parts worth retaining and reconnecting screens that did not yet form a complete booking journey.

The finished product had to serve three perspectives without losing a single source of truth: drivers searching and paying for parking, owners publishing spaces and receiving bookings, and staff overseeing inventory, users, transactions, earnings, refunds and withdrawals.

From search to the right space

Parking is useful only when it matches a place and a time. The discovery flow starts with those constraints, then adds the context a driver needs to compare listings and decide whether a specific space will work.

Search starts with the parking need — Pewny Parking — **Search starts with the parking need**Drivers choose a place, arrival, departure and booking mode before entering the marketplace.

A bilingual public experience — Pewny Parking — **A bilingual public experience**English and Polish journeys make the same parking inventory accessible without splitting the product.

Results designed for comparison — Pewny Parking — **Results designed for comparison**Location, dates, price and space details stay visible while a driver narrows the available options.

A space in its full context — Pewny Parking — **A space in its full context**Maps, street view, facilities, nearby places, owner details, availability and pricing support a confident choice.

Booking and payment

The booking flow validates the selected period, calculates the duration and price, connects a vehicle to the reservation and moves the customer into payment without hiding what they are purchasing. The completed booking remains available afterward as a practical record.

Review before committing — Pewny Parking — **Review before committing**The selected space, vehicle, dates, duration and calculated price are brought together before payment.

A clear payment handoff — Pewny Parking — **A clear payment handoff**The reservation remains understandable as the customer moves from confirmation into secure payment.

Every booking remains actionable — Pewny Parking — **Every booking remains actionable**Drivers can revisit reservation details, invoices, cancellation state and the actions available next.

The driver and owner workspace

A member can participate on either side of the marketplace. The account area therefore brings personal bookings and owner operations together while keeping their responsibilities clear: publish and schedule spaces, respond to bookings, follow transactions, manage withdrawals and communicate directly.

One account for driving and hosting — Pewny Parking — **One account for driving and hosting**A shared dashboard connects bookings made, bookings received, spaces, earnings, transactions and conversations.

Incoming reservations at a glance — Pewny Parking — **Incoming reservations at a glance**Owners can follow who booked, which space is involved, the reservation window and payment status.

A manageable parking portfolio — Pewny Parking — **A manageable parking portfolio**Published spaces, status and availability controls remain together for day-to-day operation.

Structured space publishing — Pewny Parking — **Structured space publishing**Owners define location, type, access, facilities, nearby places, photos, rates and available periods in one flow.

Money connected to reservations — Pewny Parking — **Money connected to reservations**Transaction history and invoices make the financial outcome of each booking traceable.

Questions stay with the space — Pewny Parking — **Questions stay with the space**Built-in messaging gives drivers and owners a direct route to resolve practical details.

The parts that were worth getting right

Search grounded in time

Location and booking dates filter the catalogue before a driver spends time comparing spaces.

Availability that prevents conflicts

Owner schedules and existing reservations are checked against the requested period before booking.

Payments follow booking state

Payment, commission, wallet, cancellation and refund records remain tied to the reservation lifecycle.

The same product on mobile

The REST layer exposes the established search, booking and account rules instead of duplicating them.

The back office

Marketplace staff need to see across the boundaries that keep driver and owner accounts focused. The administration area brings users, parking spaces, bookings, transactions, commissions, refunds and withdrawal requests into one operational layer.

Marketplace health in one view — Pewny Parking — **Marketplace health in one view**Users, spaces, bookings, refunds, withdrawals and earnings are surfaced as one operating picture.

User and owner oversight — Pewny Parking — **User and owner oversight**Staff can review participant records and the account information needed to support the service.

All bookings, across both sides — Pewny Parking — **All bookings, across both sides**Reservations can be inspected with their driver, owner, space, timing and current status.

Transaction-level accountability — Pewny Parking — **Transaction-level accountability**Payment records help staff reconcile the booking lifecycle and investigate exceptions.

Platform-wide space management — Pewny Parking — **Platform-wide space management**The team can review listings and keep marketplace inventory useful and trustworthy.

Earnings tied back to activity — Pewny Parking — **Earnings tied back to activity**Commission and owner earnings remain visible beside the transactions that created them.

The figures visible in these screenshots belong to the local case-study environment and are shown only to demonstrate the interface.

Engineering decisions worth explaining

Recover the usable foundation

We mapped the inherited routes, tables and partial flows first, then repaired viable work instead of forcing a costly rewrite.

Model time as inventory

Hourly, daily, weekly and monthly needs all resolve against owner availability and overlapping reservations.

Make payment outcomes explicit

PayU callbacks, pending states, commissions, owner wallets, cancellations and refunds update the underlying order deliberately.

Extend through a service layer

After launch, mobile endpoints covered authentication, discovery, booking, spaces, vehicles, messages, ratings, transactions and withdrawals.

Built with

Platform

PHP
CodeIgniter
MySQL
Apache
REST APIs

Front end

Server-rendered templates
Bootstrap
jQuery
Google Maps
DataTables
Font Awesome

Marketplace workflow

Availability rules
PayU payments
Monthly bookings
Wallets & commissions
Refunds & withdrawals
Messaging & ratings

Inherited a product that needs a dependable route forward?

We can identify what is worth keeping, repair the foundation and complete the web and API flows your marketplace depends on.

Start a Conversation See Technical Support