Case study · Qrinly
From idea to a live, multi-tier QR SaaS platform
How Push to Commit designed and built Qrinly, a QR code and link management platform for restaurants, events and packaging brands.
01 · Overview
Project overview
Qrinly is a QR code and short-link management platform. Its promise is simple: create a QR code, then keep managing what it opens. The code stays the same; the destination behind it can change at any time.
It serves restaurants and cafés putting menus, reservations and WiFi on the table, event organisers handling registration and schedules, and packaging brands linking physical products to setup guides and promotions.
- Client
- Qrinly
- Scope
- Product design, web app and backend
- Platform
- Responsive web app
- Plans
- Free, Starter, Pro and Premium
- Website
- qrinly.com
02 · The challenge
A printed QR code can't change. Qrinly's had to.
Menus change, events move and promotions end, but the code on the table, poster or box stays the same. Qrinly needed codes whose destination stays editable after printing, scan data owners can act on, and plans that grow from a free tier to routing and A/B testing, all in one product a café owner can use without training.
03 · Solution
Our approach
We designed and built Qrinly end to end: the product design, the Next.js web app and the backend behind it.
Every code resolves through a redirect layer, so destinations, routing rules, schedules and A/B splits change instantly without reprinting anything. Scan events feed the analytics dashboard, and features unlock by plan, from a free tier for one-off codes up to Premium for routing and testing.
04 · Features
What we built
The core of Qrinly: creating codes, routing scans and measuring what happens next.
- 01
Editable QR codes
Change where a code points after it's printed, without reprinting it.
- 02
Visual customization
Patterns, corner styles and an embedded logo to match the brand.
- 03
Matching short links
Every QR code comes with a short link for places a camera can't reach.
- 04
Multiple content types
Website, calendar event, app download, messaging, WiFi and contact card (vCard).
- 05
Scan analytics
Scans by country, device, operating system and browser, over any date range.
- 06
Smart routing
Target visitors by country or language and schedule destination changes ahead of time.
- 07
A/B testing
Split scans from one code between destinations and compare the results.
- 08
Folders, hosting and export
Organise codes in folders, host linked files such as PDF menus, and export as PNG or SVG.
05 · Tech stack
Built with
The building blocks behind Qrinly.
- Next.jsWeb app framework
- ReactInterface and dashboard
- Redirect layerDynamic QR codes and short links
- Scan analyticsEvent tracking and reporting
- Routing rulesGeo, language, schedule and A/B
- Subscription plansFree tier plus three paid plans
06 · Process
How the project ran
Our four-phase delivery process, applied to Qrinly.
Phase 01
Discovery
Workshops to define users, core flows and the scope of the first release.
Phase 02
Design
Wireframes and UI for QR creation, customization and the analytics dashboard.
Phase 03
Build
Development in short sprints, with a working demo for the client at the end of each.
Phase 04
Launch
QA, deployment and handover, with support through the first weeks live.
07 · Results
Where Qrinly is today
Public facts about the live product. Usage figures will be added once there is verified data to share.
Live
In production
Qrinly is live at qrinly.com and open for sign-ups.
4
Plans
Free, Starter, Pro and Premium, from €0 to €29.99 a month.
6
QR content types
Website, calendar, app download, messaging, WiFi and vCard.
3
Core audiences
Restaurants and cafés, events, and product packaging.
Related reading
Building something like Qrinly? Let's talk.
Book a call with the team that built it.