# Delivered work > Nineteen projects I carried out and put into production. Each page tells a real story: the starting context, the technical constraint that made it hard, what I built and how it fitted into what was already there. No client is named, and none should be identifiable. - Source canonique : [https://allaux.fr/en/realisations](https://allaux.fr/en/realisations) - Langue : EN - Dernière mise à jour : 2026-09-30 ## What you came here to check People look at delivered work for a simple reason: to check that someone has already built something comparable to what they have in mind. A statement of skill is easy to write; a delivered project comes with its constraints, its trade-offs and the places where the elegant solution had to be dropped. That is the material these pages hold. So you will find the past here, not promises. Each page describes something that exists, went live and was used. If you would rather know what I can take on today, independently of what I have already built, the expertise section is there for that: it describes skills I can bring to bear, where this one describes deliveries. ## How the section is organised The nineteen projects group by type of work. Commerce and catalogue: rebuild of a fashion shop, multilingual cosmetics shop, multi-supplier B2B catalogue, B2B site in eleven languages, per-customer configurable margins, product personalisation studio. Hospitality and point of sale: order-at-table by QR code, bridge to a cloud till system, menu syncing to delivery platforms. Automation and feeds: automated PDF quotes, Google Merchant feed for a B2B catalogue, running a Turkish marketplace, a complete Shopify application. Property and media: listing collection, social distribution from a CRM, automated video generation. And booking: appointment booking for an aesthetic clinic, tourist transport reservation. Finally, a bespoke brochure website for a psychology and counselling centre. ## What a project page contains, and what it does not Every page follows the same shape: the starting situation, the point that was genuinely hard, the solution chosen and why that one rather than another, then what the result changed in the team's daily work. Technologies are named — platform, language, kind of API — because that is the information that lets you judge. What you will not find: no company name, no brand, no site address. That is not coyness. A developer who publishes a client list also publishes, without meaning to, a map of their technical dependencies and sometimes of their weaknesses. Projects are therefore described by their nature and their sector, never by their owner. Nor will you find growth percentages or revenue figures. Measured results belong to the clients, not to me, and I do not publish numbers I could not prove. ## For a quick sense of the work - **Fashion e-commerce rebuild** — Taking over an existing shop with its catalogue, its variations and its order history. ([/realisations/refonte-ecommerce-pret-a-porter](/realisations/refonte-ecommerce-pret-a-porter)) - **Multi-supplier B2B catalogue** — Aggregating several suppliers' catalogues into a single shop, with availability rules specific to each. ([/realisations/catalogue-multifournisseurs-b2b](/realisations/catalogue-multifournisseurs-b2b)) - **Bridge to a cloud till system** — Linking online orders to a point of sale till system, in both directions. ([/realisations/passerelle-caisse-cloud-restauration](/realisations/passerelle-caisse-cloud-restauration)) - **B2B site in eleven languages** — A trade catalogue in eleven languages, with the URL and hreflang handling that comes with it. ([/realisations/site-b2b-multilingue-onze-langues](/realisations/site-b2b-multilingue-onze-langues)) - **Brochure website for a psychology centre** — A bespoke Turkish-language site with one page per service, phone callback, WhatsApp and KVKK information. ([/realisations/site-vitrine-centre-psychologie](/realisations/site-vitrine-centre-psychologie)) ## Delivered work or expertise? > This section describes projects delivered, in the past tense. The expertise section describes types of work I take on, in the present. If your need resembles a project listed here, say so: the starting point of the conversation is already set. ## FAQ ### Why is no client named? Because a commercial reference should not be bought at the price of technical information about someone else's site. I describe what I built, the sector and the constraints; the client's name adds nothing a reader needs in order to judge. ### Were these projects done alone or in a team? I work alone on the technical side: design, development, going live. On some projects a designer, an agency or an in-house team was involved upstream, and the page says so when it shaped the technical choices. ### Can I see the code or a demo? The code belongs to the clients and cannot be shown. Depending on the project, part of how it works can be walked through in a conversation, on a neutral environment and with no real data. ### A project close to mine isn't listed, is that a problem? No. These nineteen pages are a sample, not an inventory. What matters is the nature of the technical problem: syncing stock between two systems works the same way whether the shop sells car parts or furniture. ### Which platforms were these built on? Mainly PrestaShop and WooCommerce, plus Shopify for applications, and PHP, Laravel or Node.js development where the need fell outside an e-commerce platform. Each page states the technology used.