Storefronts, portals and the payment plumbing behind them
A web project is rarely just pages. It is a catalogue that has to stay correct, a payment that has to clear through a specific bank, a receipt that has to satisfy a tax authority, and a second language that has to be complete rather than half-translated. We build the whole of that, not the part that photographs well.
Storefronts and catalogues
Product data as data, not as pages. Adding an item is a database row, so the catalogue does not rot as it grows, and search and filters keep working at a thousand products.
Portals and dashboards
The screens your staff live in all day. Built for speed of entry rather than for a screenshot: keyboard first, no modal that hides the row you were reading.
Card payments and fiscal receipts
Local payment rails, not only Stripe. We have shipped MAIB card payments with fiscal invoicing on order completion, which is the part most projects discover too late.
Multilingual, indexable per language
Each language gets its own address and its own meta, so both versions can rank separately. Content lives per locale at the field level, so a page can be complete in one and pending in another without breaking.
Prerendered for crawlers
Every route is rendered to static HTML at build, so a search engine or a social scraper gets a full page instead of an empty shell that fills in after JavaScript.
Online shops and catalogues
Stock, variants, orders and a checkout that clears through the bank your customers actually use, with the receipt the tax authority expects.
Booking and reservation platforms
Availability, pricing rules, confirmations and the dispatcher's calendar — with the notification reaching a phone rather than an inbox nobody opens.
Client portals and internal panels
The screens staff work in all day: orders, documents, statuses, roles, and who is allowed to change what.
Marketplaces with several sellers
Seller accounts, commissions, payouts and moderation — the part that turns a catalogue into a place other people can sell in.
Corporate sites in several languages
Each language a real version with its own address and meta, not a plugin translating over the top of a single one.
CMS and headless publishing
WordPress or a headless CMS behind a fast front end, so marketing publishes without waiting for a developer.
Shops selling in several languages
If your customers do not all read the same language, a translation plugin will cost you every market it touches. A complete version per language costs less than one broken one stretched across all of them.
Businesses with a local payment problem
Card payments through a regional bank, fiscal receipts, invoicing rules that no international platform implements. This is ordinary work here and exotic everywhere else.
Anyone whose site is invisible to search
If your pages are a JavaScript app, a crawler may be receiving nothing at all. That is checkable in a minute and fixable in a day.
A link beside a group means it is running in production in a project you can read about. The rest is what the team also covers.
Front end
In production: Createli Group — custom furniture
CMS and PHP
Back end and data
In production: Bilingual electronics e-commerce
Payments and fiscal receipts
In production: Bilingual electronics e-commerce
Hosting and indexing
In production: Elegance Transfer — booking in four languages
Start with the scope conversation. It costs nothing and it is usually one call.