Multi-customer logistics · Tred Union network
Customers with nothing in common, one WMS
TECHNOPOLE LOGISTIC — Tred Union network · Multi-activity transport and logistics
01The context
TECHNOPOLE LOGISTIC is a transport and logistics provider, a member of the Tred Union network and a TEDIES customer since 2015. Its logistics business serves principals whose needs have almost nothing in common: mail order, packaging manufacturers, alcohol under duty suspension, and high industrial volumes such as Lotus France.
02The problem
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.
03What was put in place
TALK Logistique across all sites, with a configuration per customer rather than a tool per customer: from full pallets to piece picking, multi-site. The interfaces follow each principal’s ecosystem — PrestaShop, Odoo, EBP, and several distinct EDI formats. TALK Interactive gives TECHNOPOLE LOGISTIC’s customers visibility of their own stock.
04The result
A single foundation absorbs trades that do not share the same constraints. Winning a customer whose rules differ no longer calls for development, only for configuration.
We have worked with TEDIES since 2015. TALK Solutions answers our multi-activity needs: the system suits the specifics of all our customers, whether mail order, packaging manufacturers, excise goods, or high volumes such as Lotus France, from full pallets to piece picking across several sites, with multiple interfaces (PrestaShop, Odoo, EBP and several EDI formats).
Going further
When it is the customer’s customer who asks
Seyfert Packaging works with TECHNOPOLE LOGISTIC and wanted closer interfacing with its logistics provider. Its own software could send and receive EDIFACT — DESADV, INSDES, ORDERS.
TALK could not.
We developed it, and we did not invoice it as bespoke development. Only the EDIFACT module appears on the invoice, like any other module. The development costs were not passed on.
The result for TECHNOPOLE LOGISTIC: Seyfert’s receipts and orders are automated, and loading information goes back automatically. Transparency with its principal no longer rests on file exchanges or phone calls.
Why we do not invoice these developments
Because what was written for Seyfert now serves everyone.
The EDIFACT module went into the catalogue. Other customers use it today without having had to ask, and without having had to pay for it as a bespoke development.
That is how TALK has moved forward for twenty-five years: through real needs, voiced by people who run operations, rather than through a roadmap written in an office. A customer who asks us for something we cannot do does not pay for us to learn — they move the product forward, and the product comes back to them.