French Disorder. E-commerce support

French Disorder is a French clothing brand with a PrestaShop store. The store sells every day, so any failure in checkout, payments or customer emails hits revenue immediately.

The client needed a permanent technical team for the whole chain: storefront, checkout, payments, warehouse and shipping, returns and accounting documents. We didn't write the codebase - we took it over as is: PrestaShop with custom modules, payment integrations and a warehouse link. We've been on board since November 2025.

The heart of this project is fixing bugs. The store came to us with a lot of accumulated baggage: over nine months we've cleaned out a huge number of bugs, from broken maths in invoices to emails that never arrived, and we keep working through new ones every week so the system stays correct.

74% of the cards arrive flagged critical or urgent. That's the profile of supporting a live store: most requests are about something failing right now, for a customer or in the accounting.

A few examples: private-sale prices were calculated by outdated rules, ApplePay charged customers twice, and some buyers stopped receiving order emails.

About half of the tasks involve money. The payments side is PayPal, Payplug with ApplePay, Edenred and Kadéos gift cards, and pay-in-four. This is also where we handled incidents such as a double charge through ApplePay.

The other half is accounting routine: credit notes, invoices and tax corrections for dozens of customers. These tasks recur weekly and go through us.

The store is tied to a physical warehouse: MWS integration, stock synchronisation, shipping label generation for US orders, delivery cost rules.

Data exports are a separate track. When standard PrestaShop reports are not enough, we write SQL queries against the database: returns, sales, reconciliations by period.

When we took the project over, the store lived on expensive infrastructure, with bills well above what the site actually needed. We ran an audit: measured the load, worked out how many resources the store really consumes, and picked a platform where the same power comes with headroom - for noticeably less money. The client lost nothing in performance.

We did the move from scratch and end to end: set up and configured the server, the web stack and the database, migrated the store, ran the checks and switched the traffic over so smoothly that shoppers never noticed.

Speed was a separate job. This generation of PrestaShop is a hungry platform: heavy database queries, faceted filters that crawlers adore, a full page render at every turn. We built caching in several layers, from compiled templates to ready-made pages on the web server, cut off the junk bot load and brought response times to consistently fast. The store flies, even though it's still the same PrestaShop inside.

A live store is always being probed. In July the subscription form was hit by list bombing: bots were signing up other people's addresses by the thousand, and the mailing service threatened to cut the account off for a ruined sender reputation. A code review found the cause: the captcha in the subscription module had been quietly broken - a single character in a condition turned the check into a no-op.

We closed the loophole and moved all four of the site's forms - registration, both subscription forms and the contact form - to Cloudflare Turnstile with server-side token verification. Cloudflare got rules against botnet networks and request rate limits, and a country filter runs on the server: together they cut off around 22 thousand junk requests per hour. We purged 448 fake subscribers from the database, and the sender reputation recovered.

Along the way we worked out why a major catalogue category had been unreachable from search and bookmarks for a month and a half: it was caught by an overly strict server filter left over from a previous bot wave. We had no access to the server config, so we bypassed the restriction with a Cloudflare rule - the section is available again and back in Google.

Tasks flow through a Trello board with priorities: the client files a card, we assess the urgency and take it on. Over nine months the cards have gathered 281 comments with clarifications and sign-offs.

The peak came at the start - 88 tasks in the first three months while the store was being stabilised. After that the flow settled down to a steady maintenance pace.

The collaboration continues: tasks come in and get closed every week. The format is unchanged - Trello with priorities, urgent requests jump the queue.