Log In Contact Us

Review of eLogii, Route Optimization and Delivery Execution Vendor

By Léon Levinas-Ménard
Last updated: April, 2026

Go back to Market Research

eLogii (supply chain score 3.9/10) is a focused last-mile routing and delivery-execution vendor rather than a broad supply chain planning company. Public evidence supports a real SaaS product with meaningful operational substance: configurable route optimization, multi-day and date-range planning, driver mobile apps, tracking links, proof-of-delivery, REST APIs, and a fairly detailed public help center. Public evidence does not support reading eLogii as a full supply-chain optimization platform in the sense of demand forecasting, inventory planning, or probabilistic network-wide decision-making. The company looks competent and comparatively transparent within the routing niche, but narrow in scope and ordinary in technical ambition outside that niche.

eLogii overview

Supply chain score

  • Supply chain depth: 2.8/10
  • Decision and optimization substance: 4.6/10
  • Product and architecture integrity: 4.2/10
  • Technical transparency: 4.8/10
  • Vendor seriousness: 3.2/10
  • Overall score: 3.9/10 (provisional, simple average)

eLogii should be classified first as route optimization and mobile workforce execution software. It clearly solves real operational problems and appears to do so with a richer public product surface than many SaaS peers in the routing niche. The main limit is categorical, not existential. This is downstream delivery optimization software, not an end-to-end supply chain intelligence platform, and the public “AI-powered logistics” language occasionally stretches beyond what the documentation actually proves.

eLogii vs Lokad

eLogii and Lokad are not close substitutes. They overlap only at the broadest level where both can be said to “optimize supply chain operations.”

eLogii operates at the execution edge of the stack. Its public product is about assigning tasks to drivers, generating routes under constraints, reoptimizing during the day, exposing live ETAs, and feeding execution data back through driver apps and APIs. That is a real and valuable optimization problem, but it is a narrow one. The main object being optimized is a route plan for deliveries or field work, not a full economic policy for purchasing, stocking, allocating, or producing goods. (1, 2, 6, 7, 8, 9, 10, 11, 12)

Lokad sits much further upstream. It is concerned with uncertain demand, stock decisions, prioritization under financial tradeoffs, and explicit quantitative decision policies. Compared with Lokad, eLogii is much narrower, more workflow-centric, and more immediately operational. Compared with eLogii, Lokad is far less about dispatch execution and far more about the economics of decisions before the truck ever leaves the depot.

So the practical comparison is simple. eLogii is appropriate if the problem is route construction and delivery execution. Lokad is appropriate if the problem is what to buy, stock, allocate, or produce under uncertainty. The two tools could complement each other in a layered architecture, but they should not be confused as offering the same kind of intelligence.

Corporate history, ownership, funding, and M&A trail

eLogii appears to be a product line and SaaS brand operated by Brisqq Ltd rather than a large standalone enterprise-software company.

The legal anchor is clear. The terms of service identify Brisqq Ltd as the licensor and the UK company registry shows Brisqq Ltd as an active private company incorporated on September 19, 2014. That places the current vendor in a relatively ordinary founder-led software-company profile rather than inside a large corporate group. (3, 22)

The public brand story also matters. Brisqq’s own about page describes a logistics-as-a-service business born out of dissatisfaction with fragmented metropolitan delivery markets. That suggests eLogii likely emerged from operational last-mile experience rather than from abstract software product theory. This is a sensible origin story for a routing product and helps explain why the execution layer is stronger than the broader supply-chain framing. (23)

Funding and scale remain somewhat noisy. Third-party databases describe eLogii as unfunded or at least as lacking public funding rounds, with small-team and low-single-digit revenue estimates. Those sources are imperfect, but they agree on the main picture: this is a small niche SaaS vendor, not a heavily capitalized planning giant. There is no strong public evidence of completed M&A activity involving eLogii itself. (25, 26, 28, 29)

Product perimeter: what the vendor actually sells

The product perimeter is narrow and well defined.

eLogii sells route optimization, dispatch planning, driver execution, live tracking, proof-of-delivery capture, and related customer-notification and analytics features. The features page, help center, and driver-app documentation all support the same picture: users model tasks, depots, drivers, vehicles, schedules, capacities, zones, and constraints, then run optimization to generate executable routes. (1, 2, 4, 5, 6, 7, 10, 11, 12)

This is a meaningful perimeter, but a constrained one. eLogii is not selling demand forecasting, replenishment optimization, inventory planning, production planning, or network-wide economic optimization. It is selling the operational last mile and closely related field-service dispatch problems. That is not a defect, but it does sharply limit how much “supply chain” depth can be credited in the broader sense.

The integration surface is respectable. Public documentation shows REST APIs, API collections, webhooks, CSV imports, and external navigation-map integrations. That suggests a real attempt to be embedded into an existing operational stack rather than to operate as a standalone dashboard toy. (13, 14, 15, 16)

Technical transparency

eLogii is more transparent than many SaaS vendors in its category.

The strongest positive is the help center. It documents optimization flows, the two engines, optimization options, custom optimization, ETA logic, driver-app behavior, API setup, and related operational mechanics. This is not deep algorithmic openness, but it is real product transparency and enough to let a technical buyer understand much of the operating surface without talking to sales. (4, 6, 7, 8, 9, 10, 11, 12, 13, 15)

The limit is that transparency stops where the harder solver questions begin. Public evidence does not explain the underlying algorithm families in meaningful detail, does not expose benchmark methodology, and does not document how the ML-enhanced ETA layer is constructed beyond high-level descriptions. So the product is transparent at the operational and API level, but still opaque at the algorithmic-core level.

That is a respectable result for this kind of vendor. It is not enough for a high score, but it is materially better than pure brochureware.

Product and architecture integrity

The product looks coherent and structurally well focused.

Everything publicly visible points to one core system rather than to an acquisition-shaped sprawl. Routes, tasks, drivers, depots, capacities, and execution events all belong naturally inside the same product. The dashboard, driver app, tracking links, and API also fit that single-product story. This gives eLogii a more coherent product shape than many broader enterprise suites. (1, 2, 6, 12, 14)

The system boundaries are also fairly legible. eLogii appears to assume that upstream order creation, customer management, and many master-data processes live elsewhere, while eLogii focuses on planning and executing visits and routes. That is a sensible boundary and a healthier posture than pretending to be the system of record for everything.

The main caution is that the product remains workflow-heavy by design. This is normal for dispatch software, but it means a substantial part of the value still depends on interactive use, status handling, notifications, and mobile execution rather than on deep standalone decision logic. So the integrity is solid, while the architecture remains ordinary for a well-made routing SaaS.

Supply chain depth

This is the weakest dimension because eLogii is narrow by construction.

Route optimization for last-mile delivery is a real supply-chain problem, and in some businesses it is economically central. eLogii deserves credit for addressing that problem directly rather than hiding behind generic analytics language. The product clearly understands depots, drivers, shifts, time windows, capacities, pickup and delivery tasks, and execution feedback loops. (1, 5, 6, 7, 8, 10)

Still, there is no way around the category limit. Public evidence does not support treating eLogii as a broad supply-chain intelligence vendor. It does not engage with purchasing, inventory, production, multi-echelon planning, or the economics of stock and service across a network. It remains a routing and dispatch product with some adjacent field-service scope.

So the score here must stay low despite the product being real and useful. eLogii is strong in a narrow downstream slice of the stack, not deep across the broader discipline.

Decision and optimization substance

This is where eLogii is most credible.

The company clearly exposes route optimization as the product’s core computational function, and the help center gives enough detail to conclude that the system is doing genuine constrained route construction rather than superficial sequencing. The existence of a default engine and a more configurable advanced engine, plus route balancing, route limits, reoptimization, date-range planning, and multiday support, all point to a real OR core. (6, 7, 8, 9, 17)

The weakness is that the ambition remains ordinary. eLogii looks like a competent commercial VRP platform with ETA refinements, not like a frontier optimization system exposing unusually novel algorithmic contributions. The “AI-powered” language seems mostly tied to ETA adjustments and analytics rather than to a qualitatively different decision engine. That is enough for a decent score, but not for a standout one.

Vendor seriousness

eLogii looks real, but small and somewhat marketing-inflated.

The good news is that the product is clearly live, documented, and commercially deployed enough to have public help-center material, case studies, mobile apps, and software reviews. That already separates it from many thin SaaS claims. The UK public-sector listing and Companies House record also reinforce that this is a normal operating company rather than a purely promotional shell. (21, 22, 30)

The weaker side is conceptual sharpness and hype discipline. eLogii repeatedly leans on “AI-powered” and “most accurate ETAs” style language, but the public evidence behind those claims is modest. The company looks more like a competent route-optimization SaaS than like a sharply argued technical outlier. That keeps the seriousness score only moderate.

Supply chain score

The score below is provisional and uses a simple average across the five dimensions.

Supply chain depth: 2.8/10

Sub-scores:

  • Economic framing: eLogii clearly understands that route planning affects delivery cost, fleet utilization, customer service, and labor productivity. Those are real economic levers. However, the product frames them mostly through operational efficiency rather than through a broader theory of supply-chain economics, which is expected for this niche but still limits the score. 3/10
  • Decision end-state: The software does produce real operational decisions in the form of routes and task assignments, which deserves credit. At the same time, the decision domain is narrow and still embedded in dispatcher-driven workflow and exception handling rather than unattended broad supply-chain automation. That keeps the score low-moderate. 4/10
  • Conceptual sharpness on supply chain: eLogii has a crisp point of view on last-mile routing and field execution. What it does not have is a strong theory of supply chain beyond that execution slice. The conceptual sharpness is real inside routing and weak outside it, which supports a restrained score. 3/10
  • Freedom from obsolete doctrinal centerpieces: The product is not built around old S&OP orthodoxy, service-level theater, or stale planning workflows. It attacks a concrete dispatch problem directly. That deserves a modest positive score, even though the vendor does not really engage with the broader doctrinal debates of supply chain. 3/10
  • Robustness against KPI theater: eLogii’s public story is grounded in actual operational outputs such as routes, ETAs, completed jobs, and proof-of-delivery rather than in abstract corporate scorecards. That is a healthy sign. Still, the public material says little about how performance metrics are protected against gaming or how the product behaves when operational incentives distort route quality. 1/10

Dimension score: Arithmetic average of the five sub-scores above = 2.8/10.

This low score is mostly about scope, not about product reality. eLogii solves a real downstream optimization problem, but it remains a narrow execution tool rather than a broader supply-chain decision system. (1, 2, 6, 7, 10)

Decision and optimization substance: 4.6/10

Sub-scores:

  • Probabilistic modeling depth: Public evidence for true probabilistic modeling is thin. ETA updates and traffic-aware travel-time handling suggest some dynamic estimation, but not a deeply probabilistic decision engine. That leaves the score below average despite real operational forecasting elements at the ETA layer. 3/10
  • Distinctive optimization or ML substance: eLogii clearly contains real optimization logic and exposes multiple optimization modes. However, nothing in the public record suggests unusually distinctive algorithms beyond competent commercial routing software, and the ML story appears narrow. That supports a moderate score rather than a high one. 4/10
  • Real-world constraint handling: This is one of eLogii’s strengths. The documentation shows support for capacities, time windows, zones, schedules, multiday routes, selected-resource optimization, depot behavior, and balancing modes. That is meaningful real-world constraint coverage and warrants a stronger score. 6/10
  • Decision production versus decision support: The product really does output routes and assignments rather than only dashboards or recommendations. This is a substantive positive. The score is still capped because human dispatchers remain central to the operating loop and because the product solves a narrow decision class. 5/10
  • Resilience under real operational complexity: Date-range planning, multiday routing, reoptimization, and route-locking features all indicate some resilience to messy day-to-day operations. Still, the public evidence does not let us judge how well the engine holds up under very large or highly pathological routing instances. That supports a moderate-positive score. 5/10

Dimension score: Arithmetic average of the five sub-scores above = 4.6/10.

eLogii deserves real credit here. The product appears to solve a genuine combinatorial problem rather than merely visualizing tasks. The limit is that the public record supports competence, not unusual depth. (6, 7, 8, 9, 17)

Product and architecture integrity: 4.2/10

Sub-scores:

  • Architectural coherence: The product perimeter is tight and coherent, with a believable connection between the optimization engine, planning screen, driver app, and API surface. This is a real strength. The score stops short of high because the architecture itself appears standard for a modern routing SaaS rather than especially original. 5/10
  • System-boundary clarity: eLogii seems to understand its role as an execution-layer planning system that integrates with upstream enterprise applications instead of replacing them. That is a strong and sensible boundary. It deserves one of the better sub-scores in this review. 6/10
  • Security seriousness: Public evidence for security is limited mostly to standard SaaS posture and the existence of formal terms and public-sector listing. There is no strong architectural security story visible in public. That keeps the score modest. 3/10
  • Software parsimony versus workflow sludge: The product solves one fairly specific problem class, which keeps it naturally more parsimonious than broad enterprise suites. Even so, it is still workflow software with dashboards, notifications, app states, and dispatcher interactions. That warrants a moderate score. 4/10
  • Compatibility with programmatic and agent-assisted operations: The REST API, API collection, and webhook surface are meaningful positives. They make the product more programmatically usable than UI-only SaaS. The score is capped because the product still looks primarily configured and operated through the application rather than through explicit versioned logic. 3/10

Dimension score: Arithmetic average of the five sub-scores above = 4.2/10.

eLogii looks like a coherent single-purpose SaaS with healthy boundaries and reasonable integration surfaces. It does not look architecturally weak, but neither does it look unusually deep or opinionated at the system-design level. (1, 12, 13, 14, 15)

Technical transparency: 4.8/10

Sub-scores:

  • Public technical documentation: The help center exposes more operational detail than many peers disclose publicly. There are separate articles for optimization, engines, custom options, ETA behavior, driver-app usage, API setup, and API collections. This is still not deep algorithmic documentation, but it is strong by SaaS standards. 6/10
  • Inspectability without vendor mediation: A technical buyer can infer a lot about how the product works without a sales call. The main workflows, object model, and optimization behavior are reasonably visible. This is one of the better transparency signals in the review. 6/10
  • Portability and lock-in visibility: The API surface, webhook support, CSV import flows, and external navigation integrations give some visibility into how the system fits into a larger stack. However, there is still limited public information about export semantics, migration effort, or deeper data-model portability. That supports a moderate score. 4/10
  • Implementation-method transparency: The onboarding and getting-started material makes the implementation flow fairly legible, from master-data setup through optimization and driver execution. This is more transparent than many enterprise products. It is still lightweight operational guidance rather than a deep delivery methodology, which keeps the score moderate-positive. 5/10
  • Evidence density behind technical claims: Most of eLogii’s claims are tied to product documentation rather than pure brand copy, which is good. The weak spot is the “AI-powered” layer, where evidence thins out sharply. That mix supports a moderately strong score overall. 3/10

Dimension score: Arithmetic average of the five sub-scores above = 4.8/10.

For a small routing SaaS, eLogii is relatively transparent. The documentation is good enough to support a substantive review, even if it still stops short of exposing the actual solver internals. (4, 6, 7, 10, 13, 14, 15)

Vendor seriousness: 3.2/10

Sub-scores:

  • Technical seriousness of public communication: eLogii’s product communication is more concrete than many SaaS marketing sites, especially once the help center is taken into account. The company clearly sells a real product. The score remains moderate because the top-level marketing still leans heavily on generic superiority claims. 4/10
  • Resistance to buzzword opportunism: The vendor repeatedly uses “AI-powered” language for a product whose publicly documented ML layer seems relatively narrow. That is a meaningful deduction. The hype is not extreme, but it is clearly present. 2/10
  • Conceptual sharpness: The company has a clear point of view on route optimization and delivery execution. Beyond that, the messaging becomes generic and interchangeable with many last-mile SaaS players. This supports a middling score. 3/10
  • Incentive and failure-mode awareness: The documentation shows practical awareness of routing constraints, schedules, route locking, reoptimization, and execution behavior. That is real operational awareness. What remains weak is any public discussion of deeper product failure modes, gaming, or model limitations. 4/10
  • Defensibility in an agentic-software world: eLogii solves a real hard problem class, and the operational routing domain is more defensible than generic CRUD software. Even so, much of the visible value also depends on standard SaaS workflow, mobile execution, notifications, and integrations that become easier to commoditize. That leaves only a moderate score. 3/10

Dimension score: Arithmetic average of the five sub-scores above = 3.2/10.

eLogii looks like a real but modest vendor. The product itself is more serious than the buzzword layer suggests, while the broader company posture remains that of a small niche SaaS rather than a sharply distinctive technical shop. (1, 2, 20, 21, 22, 23)

Overall score: 3.9/10

Using a simple average across the five dimension scores, eLogii lands at 3.9/10. That reflects a real and reasonably transparent optimization product in a narrow execution niche, with respectable OR substance but limited breadth and only moderate technical distinction.

Conclusion

eLogii is a legitimate routing and delivery-execution vendor. The product appears to solve real combinatorial planning problems with enough constraint richness and enough public documentation to merit respect. Within the last-mile niche, it looks more substantial than the average “AI logistics” marketing shell.

The main limitation is that this niche remains just that: a niche. eLogii is not a broad supply-chain planning platform, and the public record does not justify reading it as one. Its strongest claims are about route optimization and operational execution, and that is where the review should keep it.

For organizations that need better route construction, live execution control, and delivery visibility, eLogii looks credible. For organizations seeking upstream, uncertainty-aware supply-chain decision optimization, it belongs in a different category from vendors such as Lokad.

Source dossier

[1] eLogii home page

  • URL: https://elogii.com/
  • Source type: vendor homepage
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The home page presents eLogii as route optimization and delivery-management software with planning, execution, tracking, and analytics layers. It is the best starting point for the current public product thesis and the vendor’s core market positioning.

[2] eLogii features page

  • URL: https://elogii.com/features?hsLang=en
  • Source type: vendor features page
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The features page describes single-day, same-day, date-range, and multiday planning, along with execution and analysis features. It is useful because it makes the current operational scope more explicit than the homepage alone.

[3] eLogii terms of service

  • URL: https://elogii.com/terms-of-service
  • Source type: vendor legal page
  • Publisher: eLogii / Brisqq Ltd
  • Published: unknown
  • Extracted: April 30, 2026

The terms identify Brisqq Ltd as the legal entity licensing the service. This is one of the cleanest sources for tying the eLogii product brand to its operating company.

[4] Getting started collection

  • URL: https://help.elogii.com/en/collections/2275595-getting-started-guide
  • Source type: vendor help-center collection
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This collection documents the initial setup flow for the product. It is useful because it shows the product is supported by a structured public knowledge base rather than by surface marketing alone.

[5] Getting started guide for delivery business

  • URL: https://help.elogii.com/en/articles/5161845-getting-started-guide-delivery-business
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This guide explains the operational setup model for depots, drivers, vehicles, tasks, and planning. It is a core source for understanding the product’s execution-layer data model.

[6] Optimization article

  • URL: https://help.elogii.com/en/articles/12353146-optimization
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The optimization article defines route optimization in the product and describes single-day, date-range, multiday, custom, cluster, and reoptimization flows. It is one of the best public sources for the actual planning behavior of the system.

[7] Optimization engines article

  • URL: https://help.elogii.com/en/articles/8842123-optimization-engines
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This article distinguishes the Base and Advanced engines and describes how they use route information, constraints, and balancing options. It is central for evaluating the decision-and-optimization layer.

[8] Optimization options article

  • URL: https://help.elogii.com/en/articles/11064848-optimization-options
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This page covers cost-based optimization and several selectable options that shape the optimization process. It is useful because it shows the product offers more than one fixed black-box routing mode.

[9] Custom optimization article

  • URL: https://help.elogii.com/en/articles/11069691-custom-optimization
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The custom-optimization article documents how users can tune optimization balancing and selection behavior. It matters because it shows the product exposes some control over optimization priorities instead of presenting a single opaque route engine.

[10] ETA scaling and route ETA calculation

  • URL: https://help.elogii.com/en/articles/5352555-eta-scaling-and-route-eta-calculation
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This article explains planned and live ETA logic and how ETA behavior can be adjusted. It is one of the better sources for understanding where the product’s “smart ETA” claims likely sit technically.

[11] Live ETA updates

  • URL: https://help.elogii.com/en/articles/5645498-live-eta-updates
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The live ETA article describes how route ETAs update during execution and how that behavior can be enabled or disabled. It is relevant because it ties the planning engine to real-time execution feedback.

[12] Driver app use

  • URL: https://help.elogii.com/en/articles/10742045-driver-app-use
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This page documents the driver-side execution flow for deliveries and field service, including proof-of-delivery options. It is a key source for the mobile execution layer.

[13] API setup

  • URL: https://help.elogii.com/en/articles/5646436-api-setup
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The API setup article shows that eLogii expects integration into customer systems through an authenticated API. It is a useful transparency signal for the product’s programmatic interface.

[14] API documentation

  • URL: https://api-docs.elogii.com/
  • Source type: vendor API documentation
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The API documentation confirms a real resource-level integration surface for tasks, routes, and related entities. It is important because it proves the product is not purely UI-bound.

[15] API collection

  • URL: https://help.elogii.com/en/collections/6396157-api
  • Source type: vendor help-center collection
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This collection gathers API-related guides and demonstrates that integration support is a first-class public topic. It reinforces the impression of a reasonably mature SaaS integration surface.

[16] General FAQs

  • URL: https://help.elogii.com/en/articles/6983933-general-faqs
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The FAQ page covers mapping-provider and configuration questions. It is useful because it reveals external dependencies and practical implementation details that do not appear on high-level marketing pages.

[17] Auto optimization

  • URL: https://help.elogii.com/en/articles/9842415-auto-optimization
  • Source type: vendor help-center article
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This article describes automatic reoptimization behavior. It is relevant because it provides one of the clearest public views into how the product supports ongoing operational adjustment.

[18] Case studies index

  • URL: https://elogii.com/case-studies
  • Source type: vendor case-study index
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The case-study index shows the sectors and deployment types eLogii publicly emphasizes. It is useful mainly as evidence of commercial positioning across delivery and field-service contexts.

[19] Vergo Pest Management case study

  • URL: https://elogii.com/case-studies/vergo-pest-management
  • Source type: vendor case study
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

This case study gives one concrete field-service deployment example. It matters because it shows the product is not confined to parcel-style delivery alone.

[20] Richburns and Baycorp case-study material

  • URL: https://elogii.com/case-studies
  • Source type: vendor case-study index
  • Publisher: eLogii
  • Published: unknown
  • Extracted: April 30, 2026

The case-study index includes references to Richburns and Baycorp use cases. It provides additional evidence that the product has been used in collection and field-operations scenarios beyond classical retail delivery.

[21] UK G-Cloud terms and conditions

  • URL: https://assets.digitalmarketplace.service.gov.uk/g-cloud-12/documents/714455/752390383583979-terms-and-conditions-2020-04-24-1304.pdf
  • Source type: public-sector procurement document
  • Publisher: UK Digital Marketplace / Brisqq Ltd
  • Published: April 24, 2020
  • Extracted: April 30, 2026

This document lists the service in the UK government cloud marketplace and identifies Brisqq Ltd as supplier. It is useful because it corroborates the SaaS deployment model and the corporate identity from a non-marketing source.

[22] Companies House record for Brisqq Ltd

  • URL: https://find-and-update.company-information.service.gov.uk/company/09226265
  • Source type: company registry entry
  • Publisher: GOV.UK / Companies House
  • Published: unknown
  • Extracted: April 30, 2026

The Companies House record confirms that Brisqq Ltd is an active UK private limited company incorporated on September 19, 2014. It is the cleanest corporate-ground-truth source for the vendor.

[23] Brisqq about page

  • URL: https://brisqq.com/about
  • Source type: vendor company page
  • Publisher: Brisqq
  • Published: unknown
  • Extracted: April 30, 2026

This page explains Brisqq’s logistics-as-a-service origin and says the company serves close to 1,000 brands. It is useful because it suggests an operational origin for the software rather than a purely abstract SaaS genesis.

[24] UK trademark record for eLogii

  • URL: https://www.trademarkelite.com/uk/trademark/trademark-detail/UK00003478187/eLogii
  • Source type: trademark record
  • Publisher: Trademark Elite
  • Published: unknown
  • Extracted: April 30, 2026

The trademark record helps date the branding and ties the eLogii name back to Brisqq Ltd. It is a secondary source, but useful for reconstructing the product-brand timeline.

[25] Tracxn company profile

  • URL: https://tracxn.com/d/companies/elogii
  • Source type: company database entry
  • Publisher: Tracxn
  • Published: unknown
  • Extracted: April 30, 2026

This profile treats eLogii as a small company founded around 2019 and reports no disclosed funding. It is imperfect but useful as one external signal on company scale and age.

[26] CB Insights company profile

  • URL: https://www.cbinsights.com/company/elogii
  • Source type: company database entry
  • Publisher: CB Insights
  • Published: unknown
  • Extracted: April 30, 2026

CB Insights describes eLogii as ML-powered and provides a slightly different founding-year signal. It is useful mainly because it corroborates that external databases also classify the company in the route-optimization niche.

[27] EU-Startups directory entry

  • URL: https://www.eu-startups.com/directory/elogii/
  • Source type: startup directory entry
  • Publisher: EU-Startups
  • Published: unknown
  • Extracted: April 30, 2026

This directory entry describes eLogii as part of the Brisqq group. It is useful as secondary corroboration for the brand-to-parent-company relationship.

[28] IRONPROS company profile

  • URL: https://www.ironpros.com/home/company/22895151/elogii
  • Source type: company database entry
  • Publisher: IRONPROS
  • Published: unknown
  • Extracted: April 30, 2026

IRONPROS places eLogii in the logistics-tech and route-optimization category and gives another rough scale signal. It is weak evidence, but directionally consistent with the other database sources.

[29] GetLatka company profile

  • URL: https://getlatka.com/companies/elogii.com
  • Source type: SaaS metrics entry
  • Publisher: GetLatka
  • Published: unknown
  • Extracted: April 30, 2026

This profile provides rough revenue and team-size estimates and mentions a reported M&A offer. It is noisy evidence, but it supports the picture of a small SaaS vendor rather than a large enterprise platform.

[30] Capterra reviews page

  • URL: https://www.capterra.com/p/202055/eLogii/reviews/
  • Source type: software review page
  • Publisher: Capterra
  • Published: unknown
  • Extracted: April 30, 2026

The reviews page is useful as weak but broad evidence that real users have interacted with the product and discuss usability, implementation, and routing value. It should not be treated as proof of technical depth, but it does support commercial reality.