Around ten Google Sheets files, replaced by one database.

The context

Delicorner is a Paris-based company founded in 2015 that delivers fresh fruit and snacks to businesses.

One of its offers is a distribution model: each client has a negotiated product list, a budget and delivery rules, and places an order every week. Delicorner wanted to grow by signing more clients using this same model. It needed a B2B tool that could keep up, quickly.

Three clients were already using this model: Meta, Salesforce and Datadog. More than 500 product references each week, around €200,000 per month.

Around ten files for 3 clients.

Each client had its own Google Sheets for orders, picking and reporting. Some data moved between them automatically; the rest was transferred manually, including entry into the internal CRM for some clients. Discrepancies were common.

55 ≠ 48.

Many products are sold in packs of 6, 12 or 24. Clients, however, ordered individual units. Take cans sold in packs of 12: a client orders 55, and the warehouse picks either 4 packs (48) or 5 packs (60). Either way, the discrepancy carried through to the reporting and had to be explained manually.

Discovering the budget in the meeting.

Every week, customer success spent 1 to 2 hours per client comparing what had been ordered with what had been delivered, line by line. Then came a 1-hour reporting meeting. Until then, clients had no visibility into their budget: they discovered it in the meeting.

Three departments, one person connecting them.

Logistics, purchasing and customer success each worked in their own files. One person in customer success connected everything. If they were absent, the chain stopped.

What I built

I followed an order from end to end: client, customer success, purchasing and warehouse. That fieldwork revealed the mismatch between units and packs. After rapid prototyping, three rules shaped the tool:

• order full packs;
• never overwrite the quantity ordered;
• use one database for all clients.

Airtable becomes the core of operations. Data is entered just once, and the client and all 3 internal departments—logistics, purchasing and customer success—work from the same information.

Clients order through their portal and see their budget update in real time. If they enable recurring orders, their order renews automatically each week.

Customer success validates the order. On validation, the tool creates the following week’s order and generates an import file in the internal CRM’s format for every client. No more manual CRM entry.

In the warehouse, staff flag missing items, purchasing sets restocking dates, and customer success is alerted if a delivery is at risk. After delivery, discrepancies are calculated automatically.

The database adapts to any client using the same model. Onboarding is straightforward: some initial configuration, and the client can start ordering.

The launch included a demo, a client guide, a follow-up after 2 weeks and a feature list documented for each role.