Business software · Cholet, France, since 1971

One system follows each piece from its record to its delivery.

Meubles Morinière makes custom furniture in its Cholet workshop and sells it in its own store. Its software ties the workshop, the store and online sales together. The team has its ERP, customers have their storefront, and both share the same database. So a sale online, in the store or from a quote is the same order, and the team follows it through to the invoice.

A project led solo, with Claude Code, by Adrien Poirier, full-stack software developer. I am looking for a role in a product team, in Nantes or Montréal, from March 2027. Contact me

Storefront · /
The storefront’s home page: a workshop piece on the front page, with its dimensions, price and availability.
ERP · /tableau-de-bord
The ERP dashboard: orders to prepare, storefront and store status, incidents, workshop progress, quotes and stock.
The storefront’s home page on a phone.
The live storefront and the ERP dashboard, on desktop and on a phone. Screenshots from the team’s manual, on the demo database. The people, emails and amounts are fictitious, and the numbered markers guide the reader.
Postgres tables
54
schema migrations
169
business modules
40
test files
1,789
Counted in the repository at each build of this documentation.

01Context

A family business with its own workshop and store

Meubles Morinière’s cabinetmakers have built their furniture on site in Cholet, in western France, since 1971. They work in solid wood and steel, to measure or from their own designs. The store shows their pieces alongside furniture, lighting and decor bought from Italian, Spanish and French makers.

The team is small. The same people sell, write quotes, order from suppliers, build, deliver and keep the books. The software is made for them and for their customers.

02The problem

A trade where every sale is a small project

Time
A made-to-order piece takes several weeks to arrive. The promised date depends on the workshop, suppliers and store closures, and it has to be met.
Money in instalments
The customer pays a deposit, then the balance, in the store or online. Sometimes there’s also a refund or a credit note.
Shared stock
A piece sold in the store must no longer be payable on the website.
Purchasing
Each supplier order is checked against what the customer chose, and the customer is served as soon as it arrives.
The law
Invoices that can’t be changed anymore, VAT, withdrawal rights, personal data and timber traceability.

A till, an online shop and a spreadsheet would each cover part of it. The real problem is what happens between those tools.

03Goals

What the software must guarantee

  1. Enter data only once

    Once it’s entered, data is used everywhere: in the ERP, on the storefront, in emails and in PDFs.

  2. Only promise what the store can deliver

    The price, availability and date shown on the storefront come from the rule the workshop applies. Customers pay what they saw.

  3. Let the database protect obligations

    Anything that touches money, the law or stock is protected by the database itself.

  4. Make life easier for a small team

    The ERP is fast, it works on a phone, and every morning it flags what needs a look.

04Users

The team and customers each have their own application

  • ERP

    The team

    They use it in the store, in the workshop, for purchasing and accounts, on a computer and on a phone. Everyone has the same rights. In a small team everyone has to be able to do everything, so the screens are organized by trade.

  • Storefront

    Customers

    They choose, track their order and can withdraw. Paying online and accepting a quote will open once the terms of sale are final. The account is optional, and you sign in without a password.

The accountant gets the fiscal-year export. The ERP prepares it along with the VAT returns.

Read the full overview

05The product

Two applications share the same Postgres database

apps/site

Storefront

The customers’ shop

  • Catalogue, search, collections, favourites
  • Product page with availability and delivery date
  • Cart and Stripe checkout
  • Quotes viewable and payable online
  • Order tracking, optional account
  • Online withdrawal
The storefront

Postgres

Each application has its own role

  • Storefront moriniere_site
  • ERP owner

The ERP owns it. The storefront only has the rights it needs, table by table and column by column.

The storefront’s role

apps/erp

ERP

The team’s tool

  • In-store sales, orders, quotes, customers
  • Picking and delivery planning
  • Supplier orders, receipts, restocking
  • Stock, counts and movement ledger
  • Catalogue, photos, collections
  • Figures, VAT, invoices and credit notes
  • Fisher, the assistant, on every page (⌘J)
The ERP
  • Stripe → ERP

    Stripe confirms payments to the ERP only, by webhook.

  • ERP → Storefront

    A write invalidates the cache of the affected pages.

  • Storefront → ERP

    The storefront sends withdrawals and account deletions as signed events.

Exchanges between the applications

06On screen

Both applications, as they are used

These screenshots show everyday tasks. The storefront is captured as it is live, and the ERP as the team’s manual shows it, on demo data.

Storefront
ERP

Storefront

Choose and order

From the front page to order tracking, as customers see it.

Storefront · /
Storefront, Home
Storefront · /catalogue
Storefront, Catalogue
Storefront · /collections
Storefront, Collections
Storefront · /produit/…
Storefront, Product page
Storefront, On a phone
Storefront · /commande
Storefront, Cart
Storefront, Tracking

Home. The front page shows a workshop piece with its dimensions, price and availability, and whether the store is open.

1 / 7

The live storefront, captured read-only.

08Under the hood

How it is built

It’s a pnpm monorepo with two Next.js applications and shared packages. The guarantees don’t depend on anyone’s discipline, because the database or the code enforces them.

Tech stack

  • Next.js · App Router
  • React 19 · React Compiler
  • TypeScript strict
  • Prisma
  • Postgres · Neon
  • Better Auth
  • Stripe
  • Tailwind CSS 4
  • Anthropic · AI Gateway
  • Vercel · Paris

The project’s choices

The project has no hosted CI. Before a commit reaches production, the pre-push hook checks it in a detached worktree (types, lint, tests, Postgres checks). Quality

Where to start

A reading path for what you are looking for

Go deeper

The documentation, section by section

The project

What is it, and who built it?

The product

What does the software do?

The code

How is it built?

Engineering choices

Why is it built this way?

Contact

Who wrote this software

I led this project on my own, from analysing the business to running it in production, with AI as leverage and engineering as the standard. The repository is private, but I’m happy to walk through the code in an interview.

How I build with AI

Adrien Poirier

Full-stack software developer

I am looking for a role in a product team, in Nantes or Montréal, from March 2027. I have six years of industry experience, four of them in software development. Since 2022 I have been building a Next.js traceability application as part of a team.

Education
French professional certification at master’s level (RNCP, level 7)
Location
Nantes, France. Relocating to Montréal upon hiring.
Status in Canada
Application planned for the 2027 IEC Working Holiday program (open work permit)
Languages
French, native. English, intermediate.