FR Book 30 minutes
Book 30 minutes with a founder

contact@webwize.fr
+33 6 29 40 14 18

FR
All case studies
Equine nutritionBusiness application In service since October 2026

Stock tracked batch by batch up to its expiry date, and synced with the shop

In Normandy, Harmonie Nutrition Équine, an equine nutrition online retailer, kept its stock in a home-made spreadsheet. The application we built tracks each batch from delivery to its expiry date, and deducts each online order from stock. In service since October 2026.

By Thibaut GalbaOctober 20266 min read

The application informs, the team decides.

60days of notice before a batch reaches its expiry date
32 issues raised during acceptance testing, all fixed and checked
1500+ automated tests that check the application

Alert threshold set in the application. Acceptance testing of every user journey, and tests counted on 27 September 2026.

ClientHarmonie Nutrition Équine, Normandy TimelineSigned on 20 July 2026, in service in October SyncWith every order, rechecked every night WebWize teamThibaut Galba, Antoine Gazan ToolsNext.js, PostgreSQL, WooCommerce

Stock kept in a spreadsheet, next to the shop

The company sells equine nutrition products online. Most of what it sells is bought in for resale, and some is made on site. The business software is not built for detailed stock tracking, so the team kept stock in a home-made spreadsheet.

Before
Stock kept separatelyTraceability in an Excel file

The audit of the whole organisation, carried out from April to June 2026, had described these tools and put stock at the top of the roadmap.
Read the audit case study

The client

Harmonie Nutrition Équine

NormandyOnline salesSome products made on site

Every day, the team has to

  1. ship around forty orders
  2. receive deliveries from suppliers
  3. make some of the products on site
  4. keep track of every batch and its expiry date

What the application does

Stock lives in the application. The shop, deliveries, production and counts feed it. The team gets what it needs to decide, on a computer or a phone.

What feeds the stock

In
01Orders from the shop

Each order is deducted from stock, packaging included, with nothing to type. A recheck runs every night.

02Deliveries

On the phone: the item, the quantity, the batch number, the expiry date, and a photo of the delivery note.

03Production

The recipe says which materials to take out. One batch per bag size, numbered automatically.

04Counts

Items to recount without seeing the expected stock. The difference is posted to the right batch.

The rule

The batch whose expiry date comes first goes out first, for sales and production alike.

What the team receives

Out
05Alerts

An expiry date less than 60 days away, a stock-out coming, based on the last 30 days of use.

06Reordering

Suggested quantities, supplier by supplier. The team places the orders itself.

07The traceability sheet

Filled in from production, on the laboratory's template, with the supplier and batch of each material.

08Recalling a batch

What it went into, the customers to warn, then blocking the batch and everything made from it.

Built with the team, then put into service

A first version was running two days after signing. The next two months went into fitting it to the trade, with the team, then testing every user journey.

  1. 22 July 2026

    A first version on staging

    Two days after signing, to test it and adjust it.

  2. August – September 2026

    Fitted to the trade

    The traceability sheet on the laboratory's template, one item per bag size, the warehouse tasks on a phone.

  3. 23 September 2026

    Demonstration to the team

    The application shown to the team, on staging.

  4. 27 September 2026

    Acceptance testing of every user journey

    32 issues raised, all fixed and checked, then a second pass with no blocking defect.

  5. 1 October 2026

    The application presented

    The complete version, before the data was brought across.

Going live, step by step

October 2026
  1. The dress rehearsal

    38 steps, about two hours, on a computer and on a phone.

  2. Bringing the data across

    We provide the file template, the team fills it in, then we import it.

  3. The opening stock

    A stock check on a date set with the team, so that no order is counted twice.

  4. In service

    Orders from the shop feed the stock, and the team works in the application.

It runs on our servers, and it keeps improving

In service sinceOctober 2026

Hosted by WebWize, on its infrastructure.

  1. A request from the team

    A gap or an idea, raised by the company.

  2. The fix

    Written by WebWize, separately, then reviewed before being merged.

  3. The check

    On a test copy kept separate from production, with the automated tests.

  4. In production

    A backup is taken just before, then the team gets the new version.

Every night
A full backup

Kept for seven days, four weeks and three months.

What comes next
The next stages of the roadmap

Costed during the audit, they are still to be decided with the company.

More case studies

586 customers tracked in the application, on 13 September 2026

Hacot & Co, water softener servicing

A custom scheduling application, in service since July 2026.

 335 Google clicks over 28 days, up from 183 before the agents arrived

Nuances, caterer in Bordeaux

Online shop, cost calculation and SEO agents.

 12 mailing lists created and in service

Medical biologists' union

Its lists moved from Ezmlm, which Gmail and Outlook blocked more and more, to Mailman 3 on a dedicated server.

Is your stock still living in a spreadsheet?

Thirty minutes to look at how you track your batches and expiry dates today. Free.

Antoine Gazan Thibaut Galba Antoine and Thibaut
Book 30 minutes with a founder