Customers

What they changed,
and what it produced

Nobody changes TMS or WMS on a whim. Here are real situations, with what set them off.

Carrier and logistics provider · Auxerre
Eight years, a thousand contracts a day, zero downtime
The business ran on bespoke developments from a third-party publisher, hosted on a VAX server under OpenVMS and reached through terminal emulation. Every change went through that supplier, and was paid for. With no overall view, dispatchers extracted the data and rebuilt it in Excel; some figures were only known after the daily or monthly close.
0days of downtime during the replacement1,000transport contracts a day, and as many in logisticsUPSILON
Multi-customer logistics · Tred Union network
Customers with nothing in common, one WMS
Serving customers that different in a single warehouse means picking, traceability and billing rules of their own for each. The usual answer is to open a configuration per customer, or even a tool per customer — and to pay the price of that divergence with every new contract won.
04/2015went live€0extra development cost for their customer’s EDITECHNOPOLE LOGISTIC
Industrial logistics · Tred Union network
Opening a warehouse for a demanding customer
Pharmaceuticals demand complete traceability: batch number on the pallet and serial number on the product. APTAR therefore demands it of its provider. It runs SAP, and expects receipts and invoicing to flow back with no re-keying. A WMS that does not go down to the serial number, or that has no interface, rules the provider out before the commercial conversation even starts.
07/2022warehouse went liveFIRST TRANSPORTS Logistique
Wine logistics · multi-site
A subsidiary starting up, a group that does not stop
A new tool on a new site raises the question every multi-site owner asks: what happens to the others in the meantime? Changing software at one subsidiary must neither disturb the existing warehouses nor force them to migrate at the same time.
0interruptions at the group’s other sites01/2023Mitjavile subsidiary went livePHM Group
E-commerce and store · omnichannel
One stock, two availabilities
Omnichannel is not a synchronisation problem, it is an arbitration problem. The store and the web shop draw on the same stock but must not see the same availability — what is held for the shop floor is not sellable online. Purchasing is driven by the ERP while stock belongs to the warehouse. And a return may concern a whole batch or a single item identified by its serial number.
01/2016went live2sales channels on a single stockArmurerie-auxerre.com

Eight years, a thousand contracts a day, zero downtime

Customers with nothing in common, one WMS

Opening a warehouse for a demanding customer

A subsidiary starting up, a group that does not stop

One stock, two availabilities