Review of Vekia, Supply Chain Software Vendor

By Léon Levinas-Ménard
Last updated: December, 2025

Go back to Market Research

Vekia is a French software vendor selling a cloud platform positioned around supply-chain planning for inventory-driven organizations. Its public product surface emphasizes demand/stock forecasting, “AI-generated” replenishment proposals intended to be pushed back into an ERP, proactive shortage-risk alerting, and a logistics “control tower” for monitoring stock movements. The company presents itself as having shifted from early consulting roots into packaged SaaS, with a customer-facing narrative centered on probabilistic forecasting and operational automation—but with limited publicly reproducible technical detail on the underlying models and optimization methods.

Vekia overview

What the product claims to deliver (observable product surface)

Vekia’s platform is presented as a set of tightly related supply-chain capabilities rather than an ERP replacement: (i) forecasting demand/stock and “logistics operations”, (ii) generating replenishment / purchasing proposals prioritized for execution, (iii) detecting and alerting on shortage risks, and (iv) providing a control-tower layer over stock movements for daily monitoring.12345

A consistent thread across Vekia’s own pages is that outputs are intended to be operationalized through the existing IT landscape—explicitly including feeding recommendations into an ERP—rather than creating a new transaction backbone.63 This suggests Vekia positions itself as a planning/decision-support layer whose tangible deliverables are (a) forecasts and risk signals and (b) recommended order proposals.

Technical reading

Most defensible, narrowly stated deliverables (based on documentation):

  • A forecasting layer producing forward-looking estimates and scenario language (Vekia repeatedly frames this as “anticipating scenarios” and “probabilistic forecast” in company materials).27
  • A replenishment proposal layer that outputs suggested purchase/replenishment decisions, filtered/prioritized, with an integration story explicitly framed around pushing recommendations into the ERP ecosystem.36
  • A shortage-risk monitoring layer (global stock views + proactive alerts).4
  • A stock-movement monitoring/control-tower layer (visibility + daily alerts tied to stock movement data).5

Where the public evidence becomes thin:

  • Vekia uses “AI” and “probabilistic forecast” prominently, including quantified performance uplift claims (e.g., “+25% performance vs previous generation” for “forecast probabiliste”), but it does not, in its public marketing pages, provide enough methodological detail (benchmarks, datasets, error metrics, ablations, or decision-quality evaluation) to treat those claims as independently verifiable.78

Company history signals (as stated by Vekia, then triangulated)

Vekia’s own timeline claims: idea in 2007, creation in 2008 (initially as a consulting firm), a 2010 shift toward being a software vendor, early clients using software in 2011, and subsequent financing milestones (Finorpa in 2012; Cap Horn/Pleiade in 2015; “historic fundraising” in 2017; “SaaS for real” in 2018).7 Corporate registry-style sources corroborate that Vekia exists as a long-lived legal entity (SIREN 503 225 716), enabling at least the company’s existence and basic identity to be verified independently.910

Vekia vs Lokad

Vekia and Lokad both market “probabilistic” and “AI” ideas in supply-chain contexts, but the publicly inspectable evidence points to substantially different product philosophies and transparency levels.

  • Product form: packaged application vs programmable platform. Vekia presents a platform with named functional blocks (forecasting, replenishment proposals, shortage management, control tower) designed to plug into an ERP-centric ecosystem.23456 Lokad’s public materials frame its offering as a programmatic platform (Envision DSL) for building bespoke predictive-optimization logic, with heavy emphasis on expressiveness and auditable pipelines.1112

  • Transparency of the “how”. Vekia advertises a “transparent technology” behind its approach, but its public-facing materials (product/technology pages and corporate narrative) provide relatively limited algorithmic specificity (what models, what objective functions, what constraints, what training/evaluation protocol).87 Lokad, by contrast, publishes relatively explicit technology narratives (e.g., named technology “generations” such as probabilistic forecasting (2016), differentiable programming (2019), and stochastic discrete descent (2021)) and supplies technical documentation around the DSL and differentiable programming concepts.131415

  • Optimization claims: decision layer vs explicitly described stochastic optimization. Vekia clearly claims an automated decision-support layer that generates prioritized replenishment proposals.36 However, public Vekia materials do not clearly specify whether these proposals are produced via (a) explicit constrained optimization with an objective function, (b) heuristics/rules, (c) simulation/what-if logic, or (d) learned policy models—nor do they publish a technical description of the decision engine. (This is not proof it is simple; it is a documentation gap.)387 Lokad, conversely, explicitly names a stochastic optimization approach (“stochastic discrete descent”) and ties it to probabilistic forecasts and non-linear constraints, at least at a conceptual/architectural level.1513

  • Evidence posture for “probabilistic”. Vekia asserts probabilistic forecasting and scenario framing as product pillars and even claims quantified uplift, but does not provide public evaluation artifacts sufficient for reproduction.72 Lokad’s public narrative explicitly defines probabilistic forecasting, situates it in supply-chain decision robustness, and ties it to a broader published technology roadmap.1213

Net: based strictly on public, sourceable material, Vekia looks like a more packaged, integration-forward planning layer (forecasting + replenishment proposals + alerts) with less publicly inspectable algorithmic detail, while Lokad’s posture is more programmatic and openly technical (DSL + published paradigms), with named optimization mechanisms and conceptual detail made available in documentation.368131115

Product and technology claims, scrutinized

Forecasting: what “probabilistic” seems to mean here (and what is not documented)

Vekia repeatedly uses language consistent with probabilistic/scenario forecasting (“scenarios”, “incertitude”, “forecast probabiliste”).27 This could imply distributional forecasting or multi-scenario generation rather than point forecasts, but Vekia’s public pages do not clearly specify:

  • the statistical form (full distributions vs quantiles vs scenario trees),
  • whether lead-time uncertainty is modeled,
  • the training pipeline (features, model classes),
  • evaluation methodology (metrics, baselines, sampling frames),
  • or whether forecasting is coupled to downstream decision objectives.

Accordingly, “probabilistic” must be treated as plausible but under-specified from public evidence alone.287

Replenishment proposals: decision automation without disclosed decision model

Vekia’s replenishment propositions are described as “generated by AI” and “filtered by priority” with an explicit message that Vekia can feed an ERP with optimized order proposals.36 Public documentation does not clarify:

  • whether “priority” is driven by expected cost/benefit, service level risk, contractual constraints, or operational heuristics,
  • how constraints such as MOQs, pack sizes, truck/load constraints, calendars, or supplier-specific rules are modeled (if at all),
  • what human override workflow exists (approval, exceptions, governance).

Thus, the deliverable is clear (prioritized suggestions), but the mechanism is not.36

Architecture and stack signals from hiring / technical surfaces

Vekia’s hiring materials provide some of the strongest non-product-marketing clues about implementation choices, explicitly naming parts of the stack (front-end frameworks, backend languages, and cloud/data tooling).1617 Separately, Vekia exposes at least some externally reachable API documentation under a Vekia-controlled domain, indicating the existence of authenticated REST-style endpoints and a developer-facing documentation surface (even if this particular API appears adjacent to web-notification tooling rather than core supply-chain planning).18

“AI” as a label: evidentiary grading

High-confidence (directly evidenced):

  • Vekia markets AI-driven forecasting/proposals/alerts as core product pillars.234
  • Vekia markets ERP integration for pushing replenishment proposals.6

Medium-confidence (consistent but not sufficiently specified):

  • Some probabilistic/scenario-style forecasting is likely implemented, because it is central in the narrative and naming (including “forecast probabiliste”).27

Low-confidence (not publicly substantiated):

  • Any claim about specific ML model classes (e.g., gradient-boosting vs deep learning), specific optimization solvers, or end-to-end “autonomous decision-making” beyond the generation of recommendations—because public documentation does not describe such internals in a reproducible way.87

Deployment and roll-out methodology (observable claims)

Vekia’s own integration positioning is strongly oriented around plugging into an existing enterprise IT stack and not requiring ERP replacement: it repeatedly frames itself as “interconnectable” and able to “feed your ERP” with optimized proposals.63 This implies a roll-out pattern that, at minimum, requires:

  • extracting historical sales/stock/supply and master data from ERP/WMS/TMS sources,
  • running forecasting + proposal generation on Vekia’s side,
  • returning recommended orders (and potentially risk alerts) into downstream operational workflows.

However, Vekia’s public pages do not provide a detailed, step-by-step deployment playbook (data contracts, refresh cadence, cutover governance, planner workflow changes) that would allow an external evaluator to assess implementation risk in detail.61

Clients and case studies: named vs weakly evidenced references

Vekia’s website explicitly lists named references and links to business cases (e.g., Okaidi/Okaïdi, Mr Bricolage, Engie Home Services).19 This is stronger than anonymized claims, because names are published and business-case artifacts exist (even if still vendor-authored).19

Additional external references exist, but vary in evidentiary strength:

  • A third-party case narrative exists around Leroy Merlin and a Vekia tool called “ProOrder”; this is an external source but should still be treated cautiously unless it is traceable to primary customer statements or detailed operational metrics.20
  • A Vekia press release describes Martin Brower adopting Vekia after a disruption narrative involving a cyberattack and continuity needs; this is explicit but remains vendor-authored unless corroborated by Martin Brower or independent reporting.21

Overall: Vekia does publish verifiable client names, but many performance claims appear to remain primarily vendor-reported unless independently corroborated.1921

Corporate maturity and market presence

Registry sources support that Vekia is a long-lived French entity (SIREN 503 225 716), consistent with the company’s own origin narrative (creation around 2008).9107

Funding and financing signals (with source limitations)

Accessible public sources document at least one major later-stage fundraising round (2015/2017 era) and name venture investors; however, for several early rounds, the most detailed reporting is either in sources that are not reliably accessible or in aggregator-style databases, reducing confidence in exact amounts without better primary coverage.22237

Acquisition activity

A concrete, externally published acquisition event exists: ASYS announced acquiring VekiaPlan Solutions in 2016 (VekiaPlan being described as a company/product line distinct from Vekia’s core supply-chain platform).24 Beyond that, no additional acquisition activity was confirmed in the accessible source set.

Financial distress / restructuring signals

Public legal-notice sources report that Vekia entered a French “procédure de sauvegarde” (safeguard procedure) in 2023 and later had a plan referenced in 2024—an important maturity/risk signal because it indicates court-supervised restructuring rather than straightforward growth trajectory.25

Conclusion

What Vekia’s solution delivers (most defensible statement): a cloud-based supply-chain planning layer focused on forecasting, generating prioritized replenishment proposals intended to be integrated back into ERP workflows, and monitoring/alerting (shortage risk + stock-movement “control tower”).23456

How it achieves these outcomes (what can be evidenced): Vekia documents the functional blocks and integration intent clearly, and hiring/technical surfaces expose parts of the engineering stack. But public materials do not provide enough detail to independently verify the specific forecasting form (“probabilistic” implementation), the decision logic behind prioritized proposals (objective functions/constraints/solver family), or any claimed performance uplift, beyond vendor-authored assertions.781617

Commercial maturity: Vekia appears to be an established (non-early-stage) vendor by longevity and named customer references, with at least one publicly announced fundraising history and an externally documented divestiture (VekiaPlan). That said, the 2023 safeguard procedure is a material counter-signal that should be considered in any diligence process.9192425

Sources

  1. Vekia — “Solution de Gestion Supply Chain” — accessed 2025-12-24 ↩︎ ↩︎

  2. Vekia — “Prévision de la demande, du stock et des opérations logistiques” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  3. Vekia — “Propositions d’approvisionnement” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  4. Vekia — “Gestion de la pénurie” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  5. Vekia — “Tour de contrôle logistique” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎

  6. Vekia — “Intégration” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  7. Vekia — “À propos” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  8. Vekia — “Technologie” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎

  9. Pappers — “VEKIA (503225716)” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎

  10. Annuaire des entreprises (French government) — “VEKIA” — accessed 2025-12-24 ↩︎ ↩︎

  11. Lokad Technical Documentation — “Envision Language” — accessed 2025-12-24 ↩︎ ↩︎

  12. Lokad — “Probabilistic Forecasting (Supply Chain)” — Nov 2020 ↩︎ ↩︎

  13. Lokad — “Forecasting and Optimization technologies” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎

  14. Lokad Technical Documentation — “Differentiable Programming” — accessed 2025-12-24 ↩︎

  15. Lokad — “Stochastic Discrete Descent” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎

  16. Vekia (recruiting) — “Nos technologies” — accessed 2025-12-24 ↩︎ ↩︎

  17. WeLoveDevs — “Vekia” (stack / hiring signals) — accessed 2025-12-24 ↩︎ ↩︎

  18. push.vekia.ar — API Documentation (“Websites” endpoint) — accessed 2025-12-24 ↩︎

  19. Vekia — “Clients” — accessed 2025-12-24 ↩︎ ↩︎ ↩︎ ↩︎

  20. BestPractice AI — “Leroy Merlin: Inventory Management with Vekia ProOrder” — accessed 2025-12-24 ↩︎

  21. Vekia — “Martin Brower x Vekia : 8 jours…” — 28 Mar 2025 ↩︎ ↩︎

  22. Maddyness — “Vekia lève 2,4 millions d’euros” — 06 Oct 2015 ↩︎

  23. Stratégies — “Vekia lève 12 millions…” — 07 Sep 2017 ↩︎

  24. PR Newswire — “ASYS completes the acquisition of the company VekiaPlan Solutions” — 05 Apr 2016 ↩︎ ↩︎

  25. ActuLégales — legal notice on Vekia safeguard procedure — accessed 2025-12-24 ↩︎ ↩︎