# Custom development

> A marketplace module doesn't always cover a specific business need. When that's the case, I build the missing feature, internal tool or application, in PHP/Laravel, in Node.js, or directly in the relevant e-commerce platform's code.

- Source canonique : [https://allaux.fr/en/services/developpement-sur-mesure](https://allaux.fr/en/services/developpement-sur-mesure)
- Langue : EN
- Dernière mise à jour : 2026-08-03

## When custom development makes sense

Before building anything, I check that no existing module already covers the need properly: reinventing a standard component costs time and adds code to maintain for no reason. Custom development comes in when the need is specific to your business, or when existing modules force unacceptable compromises on data or process.

That could be a particular pricing rule, an internal management tool that isn't meant to be public, or a feature that touches both the site and an external system.

## Types of development delivered

- **Internal business applications** — Management tools, dashboards or back offices built for internal use, outside the public site.
- **Specific storefront features** — Pricing, discount or availability rules that don't match any existing module.
- **Custom extensions and modules** — Building a PrestaShop module, a WordPress plugin or a Shopify app for a specific need.
- **Connectors and API** — Bridges between the site and external software, when no marketplace connector covers the use case.
- **Rebuilding existing features** — Rewriting a feature that's become too rigid or too costly to maintain, without necessarily touching the rest of the site.

## How a custom build comes together

1. **Scoping the need** — A precise description of what the tool needs to do, the data it handles, and the users involved.
2. **Technical specification** — Choices on architecture, stack and scope, put in writing before development starts.
3. **Development in deliverable batches** — Work progresses in checkable stages, to avoid months of development with no interim feedback.
4. **Testing and going live** — Checked on a separate environment before release, then monitored under real conditions.
5. **Documentation and handover** — A minimum of technical documentation so the code stays understandable, including to someone else later on.

## FAQ

### What technologies do you use?

Mainly PHP and Laravel server-side, Node.js for certain standalone tools or services, and the platform's native language when the development integrates with PrestaShop, WooCommerce or Shopify.

### Do I own the code once it's delivered?

Yes. Unless otherwise agreed in writing, code developed for you belongs to you and stays accessible on your own environments.

### How long does custom development take?

It depends entirely on the scope. A targeted feature takes a few days, a full application several weeks. The timeframe is estimated after scoping, not before.

### Do you provide maintenance after delivery?

Not automatically. I can offer it separately if you want, through occasional follow-up or a maintenance contract, but delivery doesn't imply an ongoing commitment by default.

### Do you work from a spec that's already written?

Yes, if you have one. Otherwise, I work through the need with you as a technical specification before starting, to avoid misunderstandings along the way.