Expertise

You are comparing, and rightly so

An expertise page gets read at a particular moment: the project is still open, several people are in the running, and someone has to decide who gets the work. At that stage, what separates candidates is not the length of a skills list — anyone can write "PrestaShop expert". What separates them is precision: does the person describe the problem like someone who has met it, and do they say where the difficulties are rather than smoothing them over.

These twenty pages are therefore written in the present tense and in the first person, with no client reference. Each sets out a category of assignment: what it covers, how I go about it, what governs feasibility, and what falls outside the scope. A stated refusal is part of the useful information.

How the section is organised

The twenty skill areas fall into five domains. PrestaShop modules and payment: bespoke payment module, bespoke carrier module, point-of-sale payment integration. Performance and migrations: large catalogues, platform changes, multilingual sites and international search.

Integrations and APIs, the largest domain: connecting to B2B supplier APIs, reverse-engineering undocumented APIs, API-first full-stack architecture, generating code from an OpenAPI specification, real-time multi-platform syncing, stock shared between several shops. Applications: bespoke Shopify apps, a controllable MCP server, a programmatic site generator. And applied AI and media: generated product FAQs, generated product video, agent orchestration, media extraction and processing, social distribution from a CRM.

What this section is not

It is not a portfolio of references. None of these pages says "I built this for such-and-such a brand": that register belongs to the delivered work section, which tells the story of projects actually built and put live. The separation is deliberate and strict. Mixing the two produces the most common pitch in the trade — theoretical skill presented as experience — and that is exactly what an informed buyer is trying to see through.

In practice: if you want to know what I can handle, stay here. If you want to see what already exists, go to the delivered work. The two sections answer each other, and several expertise pages link to a project in the same domain.

One more useful point: I work alone, on the code, the database and the server. That naturally bounds the kind of commitment possible. An assignment that assumes several people working in parallel does not fit, and I say so before the quote rather than after.