Log In Contact Us

Review of Algonomy, Retail AI Software Vendor

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

Go back to Market Research

Algonomy (supply chain score 4.3/10) is best understood as a retail personalization and real-time customer-data vendor that also sells supply-chain planning modules. Public evidence strongly supports the maturity of the personalization and CDP stack: documented APIs, SDKs, first-party data collection patterns, release notes, and integration guides are all visible. Public evidence is much weaker for the supply-chain side. Forecast Right and Order Right make plausible claims about multivariate forecasting, model selection, and constraint-aware replenishment, but the public record does not expose enough methodological detail to judge the underlying forecasting or optimization science. The result looks like a broad retail AI suite with credible implementation substance and only moderate supply-chain transparency.

Algonomy overview

Supply chain score

  • Supply chain depth: 4.2/10
  • Decision and optimization substance: 4.4/10
  • Product and architecture integrity: 5.2/10
  • Technical transparency: 4.0/10
  • Vendor seriousness: 3.8/10
  • Overall score: 4.3/10 (provisional, simple average)

Algonomy is not a fake AI shell. It clearly operates real software, especially on the digital-commerce side. The issue is product center of gravity. The most inspectable and mature parts of the public product surface are personalization, search, customer data, and engagement. Supply chain exists, but it appears as an add-on planning layer inside a broader retail suite rather than as the company’s deepest technical center.

Algonomy vs Lokad

Algonomy and Lokad overlap commercially in retail supply chain, but they embody very different software philosophies.

Algonomy sells a broad retail stack. The public surface includes personalization, search, customer data, engagement, and activation products alongside Forecast Right and Order Right. The customer is meant to adopt productized modules and integrations rather than program a decision engine. This is especially clear from the developer documentation, which is rich on SDKs, APIs, connectors, and implementation guides for commerce and CDP workflows. (9, 10, 11, 12, 13, 14, 15, 16)

Lokad, by contrast, is much narrower in perimeter and much more explicit in supply-chain doctrine. The relevant contrast is not “who has more modules?” but “who exposes the logic by which supply chain decisions are produced?” On that axis, Algonomy looks like a black-box suite. It shows how to instrument the software and connect data, but it does not publicly explain the mathematics behind replenishment and forecasting decisions.

There is also a difference in product center. Algonomy’s strongest public evidence is around ecommerce and customer engagement. Even its own positioning often frames the company as retail AI spanning ecommerce, marketing, merchandising, and supply chain. That makes the supply-chain story secondary rather than foundational. For buyers seeking a broad retail AI estate, that may be attractive. For buyers seeking transparent supply-chain-native decision automation, it is a limitation. (1, 5, 17, 18, 19)

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

Algonomy is a merged company rather than a clean-sheet software build.

The current brand launched in January 2021 from the combination of RichRelevance and Manthan. That origin matters because it explains the mixed product DNA: RichRelevance brought personalization, search, and merchandising technology, while Manthan brought analytics and planning lineage. The merger was widely covered in the company newsroom, Business Wire, and Indian business press. (1, 2, 3)

The same early coverage also mentioned a plan to pursue a US listing in 2023. No later filing or public-market outcome was found during this refresh, which makes that claim historically interesting but operationally stale. More recent newsroom activity shows continued customer and product announcements, not public-market execution. (4, 5)

The M&A trail is also meaningful. RichRelevance previously acquired Searchandise Commerce, Avail, and Precog. Post-merger, Algonomy announced intent to acquire Linear Squared in 2022 to strengthen demand planning and forecasting. That history suggests a product portfolio assembled through both merger and acquisition rather than an unusually unified technical core. (6, 7, 8, 25, 26, 27, 28)

Product perimeter: what the vendor actually sells

The perimeter is wide, but not evenly deep.

The public site and documentation show at least three substantial product zones. First, there is the personalization layer built around Recommend and related merchandising and search capabilities. Second, there is the real-time CDP with APIs, mobile SDKs, event capture, connectors, audience activation, and CodeFusion/Active Content patterns. Third, there are supply-chain modules such as Forecast Right and Order Right, aimed primarily at retail demand forecasting and replenishment. (9, 10, 11, 12, 13, 14, 15, 16, 17, 19, 20, 21, 22)

This breadth should not be mistaken for a unified supply-chain thesis. The suite appears retail-centric first, with supply chain positioned as part of a wider algorithmic decisioning story. The supply-chain modules themselves are also retail-specific, especially grocery replenishment and merchandise planning, rather than general-purpose industrial planning tools. (17, 18, 19, 20, 24)

That said, the perimeter is commercially coherent. Personalized commerce, customer data, merchandising, and replenishment can sensibly live under one retail AI umbrella. The weakness is not random sprawl; it is that the deepest public evidence clusters around customer-facing retail software, not around supply-chain decision science.

Technical transparency

Technical transparency is uneven but non-trivial.

On the positive side, Algonomy publishes much more operational documentation than many peers. The personalization side exposes concrete API behavior such as recsForPlacements, first-party instrumentation domains, integration-versus-production patterns, release notes, and behavior logging. The CDP side exposes developer guides, mobile SDKs, authentication flows, event APIs, product catalog APIs, data model extensions, and connectors such as Shopify and Amazon S3 destinations. This is real implementation substance. (9, 10, 11, 12, 13, 14, 15, 16, 21, 22, 23, 24)

On the negative side, the supply-chain modules remain black boxes. Forecast Right and Order Right use phrases such as multivariate forecasting, ensemble model selection, and proprietary optimization algorithms, but no meaningful public technical brief explains model families, reconciliation methods, uncertainty treatment, objective functions, or solver classes. The company is transparent about integration mechanics and opaque about decision science. (17, 18, 19, 20)

So the correct judgment is not “transparent” or “opaque” in absolute terms. Algonomy is operationally inspectable on its retail engagement stack and methodologically opaque on its supply-chain stack.

Product and architecture integrity

There is a real product estate here, but it reflects layered portfolio construction.

The stronger signals come from the CDP and personalization documentation. Those areas show a live software platform with maintained guides, concrete endpoints, SDKs, first-party capture migration, release cadence, and separately operated application surfaces such as RCDP and TargetOne logins. The legacy RichRelevance GitHub organization also hints at a historically industrial Java and data-infrastructure foundation. These are not signs of a company pretending to have software. (9, 10, 11, 12, 21, 22, 23)

The weaker signal is architectural unity. The overall company is a merger, with additional acquisitions and a product line that now spans personalization, search, engagement, CDP, analytics, and supply-chain planning. That can be commercially effective without being technically elegant. The public record supports a functioning suite more than a parsimonious system.

This is why the integrity score lands in the middle. Algonomy clearly ships and operates real software, but the portfolio logic looks broader and more assembled than sharply bounded.

Supply chain depth

Algonomy has real retail supply-chain relevance, but the depth is moderate rather than strong.

Forecast Right and Order Right are not trivial module names. Their public materials discuss SKU-store forecasting, cannibalization and substitution, merchandise planning, shelf-life, lead times, minimum order quantities, expiry, display stock, and ordering cadence. The grocery replenishment material also shows awareness of volatile retail categories such as fresh, seasonal, and promoted products. This is genuine supply-chain vocabulary rather than generic AI verbiage. (17, 18, 19, 20, 24)

The limitation is doctrinal depth. The public record does not show a strong theory of supply chain decisions beyond better forecasting and constrained replenishment. There is little public discussion of uncertainty as a first-class decision object, of economic tradeoff design, or of the pathologies of common planning KPIs. The suite looks useful for retail planning, but conceptually mainstream.

This places Algonomy above generic analytics vendors and above pure marketing-AI vendors. It does not place the company near the top tier of supply-chain-native software thinking.

Decision and optimization substance

There is credible substance here, but very little public proof of originality.

The positive case is straightforward. Forecast Right claims multivariate and hierarchical modeling, cannibalization and substitution handling, and large-scale model selection. Order Right claims algorithmic replenishment under multiple operational constraints with ERP handoff. These are serious functional claims, and the Linear Squared lineage makes them more believable than if they appeared out of nowhere. (6, 7, 17, 19, 20)

The negative case is just as clear. The public materials do not disclose what “ensemble” means in forecasting, how models are selected, how uncertainty is represented, or what optimizer class drives replenishment. This is exactly the level at which a technical buyer would want detail, and it is missing. Even the stronger claims remain at datasheet level rather than at engineering or research-note level.

The result is a middle score. Algonomy deserves more credit than a vendor with no planning modules at all. It does not deserve strong credit for transparent or distinctive decision science from what can currently be inspected.

Vendor seriousness

Algonomy looks commercially serious and technically mixed.

The positive case is that the company has real product history, real documentation, real customer-facing assets, and real software surfaces in production. The developer materials are too detailed to be theater, and the M&A history is at least coherent with the current product breadth. (1, 5, 9, 12, 21)

The negative case is familiar: the public product language leans heavily on proprietary AI, algorithmic decisioning, retail-native intelligence, and broad outcome claims without matching methodological disclosure where it matters most. There is also a noticeable asymmetry between the deep documentation for customer-engagement plumbing and the thin documentation for supply-chain decision logic. That asymmetry matters because it reveals where the company’s real operational confidence appears to be.

So the vendor seriousness score stays below the middle. Algonomy is clearly real and competent, but its public technical posture on the supply-chain side is still too opaque and too marketing-shaped to merit a higher score.

Supply chain score

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

Supply chain depth: 4.2/10

Sub-scores:

  • Economic framing: Algonomy’s supply-chain pages do discuss inventory risks, wastage, stock-outs, shelf availability, and store-level tradeoffs, which is better than generic planning language. However, the public doctrine is still mostly framed around forecast improvement and replenishment constraints rather than an explicit economics-first decision framework. The score is therefore below the middle. 4/10
  • Decision end-state: Order Right is presented as generating order plans and pushing them to ERP, which is materially more decision-oriented than dashboard-only software. At the same time, the public materials still read like guided planning tools rather than like a deeply automated decision engine. This justifies a middle score. 5/10
  • Conceptual sharpness on supply chain: The supply-chain story is retail-specific and not trivial, especially around grocery replenishment. Still, it does not reveal a particularly sharp or distinctive supply-chain philosophy. The conceptual center remains mainstream retail planning. 4/10
  • Freedom from obsolete doctrinal centerpieces: The suite is not entirely trapped in old APS vocabulary, but it still leans heavily on forecast accuracy, replenishment planning, and merchandise-facing planning logic. There is no strong public break with older planning doctrine. 4/10
  • Robustness against KPI theater: Public materials emphasize improvement metrics and operational outcomes, but say little about how local KPIs distort behavior or how optimization avoids proxy traps. That leaves a meaningful doctrinal gap. 4/10

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

Algonomy clearly understands retail planning realities better than generic BI or generic CDP vendors. The public record still does not support a stronger score because the supply-chain doctrine remains conventional and under-explained. (17, 18, 19, 20, 24)

Decision and optimization substance: 4.4/10

Sub-scores:

  • Probabilistic modeling depth: The forecasting materials imply sophisticated modeling, but they do not expose a probability-centric architecture or a first-class treatment of uncertainty. Without public evidence on distributions, reconciliation logic, or decision-making under uncertainty, the score must stay low-to-middle. 4/10
  • Distinctive optimization or ML substance: There is enough evidence to believe the company does more than rules-only planning, especially given the multivariate forecasting and replenishment claims. But the public record does not show clearly distinctive methods. The substance appears credible, not exceptional. 5/10
  • Real-world constraint handling: Shelf-life, expiry, lead time, MOQ, display stock, order cadence, and ERP pushback are all meaningful operational constraints. That gives the replenishment story real weight and supports a score above the middle on this specific axis. 6/10
  • Decision production versus decision support: Forecast Right and Order Right do appear designed to produce concrete planning outputs, not just reports. Yet the public story still feels planner-mediated, and the execution depth is not richly exposed. This justifies a moderate score. 4/10
  • Resilience under real operational complexity: The retail and grocery framing suggests exposure to difficult categories and noisy data. But the absence of public detail on model behavior and optimization mechanics makes it hard to score this highly. 3/10

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

Algonomy earns real credit for claiming and apparently delivering non-trivial planning functions. It loses points because nearly all the interesting technical questions remain unanswered in public. (6, 17, 19, 20, 24)

Product and architecture integrity: 5.2/10

Sub-scores:

  • Architectural coherence: The personalization and CDP stack looks coherent and well-instrumented, with documented APIs, SDKs, and connectors. The broader company portfolio is still a merger-built suite, which reduces the impression of conceptual purity. The result is above average but not strong. 5/10
  • System-boundary clarity: On the customer-data and engagement side, boundaries are visible and documented. On the supply-chain side, the internals are much less clear. This split yields a moderate score. 5/10
  • Security seriousness: Public OAuth flows, first-party data capture patterns, MFA-protected application surfaces, and GDPR-related APIs indicate a baseline of operational seriousness. Public security detail is still limited, so the score remains moderate rather than high. 6/10
  • Software parsimony versus workflow sludge: Algonomy is clearly a broad suite, and broad suites accumulate surface area. The portfolio spans personalization, search, CDP, analytics, engagement, forecasting, and replenishment, which suggests some product mass. 4/10
  • Compatibility with programmatic and agent-assisted operations: The documented APIs, SDKs, connectors, and data-model extension surface are a real advantage. They suggest a product that can at least be integrated and manipulated programmatically rather than only through opaque UIs. 6/10

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

Algonomy looks like real software with real runtime and integration surfaces. The score stops in the middle because the portfolio is broad and assembled, not because the software appears fake. (9, 10, 12, 13, 21, 22, 23)

Technical transparency: 4.0/10

Sub-scores:

  • Public technical documentation: There is substantial public documentation, but it is concentrated in personalization and CDP integration rather than in supply-chain science. This is materially better than average, though still incomplete for the most important planning questions. 5/10
  • Inspectability without vendor mediation: A technical reader can inspect many operational details of the retail engagement stack, including endpoints, event structures, and connector behavior. The planning internals remain hidden. On balance, inspectability is partial rather than strong. 4/10
  • Portability and lock-in visibility: The public docs make integrations, connectors, and event APIs visible enough that a buyer can infer part of the lock-in shape. Still, the deeper data and model portability boundaries are not well exposed, especially on the planning side. 4/10
  • Implementation-method transparency: The implementation method for CDP and personalization is unusually legible, with guides for web, mobile, and connectors. By contrast, the rollout method for forecasting and replenishment is barely exposed. This split again yields a middle score. 3/10
  • Security-design transparency: Algonomy exposes some concrete public security and privacy surfaces through OAuth flows, MFA-protected application access, GDPR-related APIs, and first-party data capture guidance. That is more operationally useful than generic enterprise-grade assurances. The public record still says much more about integration and data handling than about secure-by-design boundaries or failure containment, so the score remains moderate. 4/10

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

Algonomy is one of the few peers here with genuinely useful public developer documentation. The score is held back because that transparency fades exactly where the supply-chain decision logic begins. (9, 10, 12, 13, 14, 15, 16, 21, 22, 23)

Vendor seriousness: 3.8/10

Sub-scores:

  • Technical seriousness of public communication: Algonomy communicates like a real enterprise software vendor with substantial docs and long-running products. However, it also relies heavily on polished AI-marketing language where the hardest technical substantiation is missing. This produces a middling result. 5/10
  • Resistance to buzzword opportunism: Terms such as proprietary AI, algorithmic decisioning, and retail-native intelligence are used freely throughout the public materials. The language is not absurd, but it is more confident than the public evidence warrants. 3/10
  • Conceptual sharpness: The company has a reasonably coherent retail-AI thesis, but not a sharply defined supply-chain doctrine. The product feels commercially broad rather than intellectually precise. 4/10
  • Incentive and failure-mode awareness: Public materials say very little about failure modes, bad incentives, degraded forecasts, or planner misalignment. This silence matters on the supply-chain side. 3/10
  • Defensibility in an agentic-software world: The documented APIs, SDKs, retail connectors, and installed suite breadth all provide some defensibility. The lack of transparent planning science weakens that moat, but the company is still better positioned than a pure presentation-layer vendor. 4/10

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

Algonomy is a serious commercial vendor with real product mass. It is not especially serious in public about exposing the most difficult technical details behind its supply-chain claims. (1, 5, 11, 17, 19)

Overall score: 4.3/10

Using a simple average across the five dimension scores, Algonomy lands at 4.3/10. That reflects a real and broad retail software estate with credible planning features but weak public transparency on the supply-chain science itself.

Conclusion

Public evidence supports the view that Algonomy is a mature retail software vendor with a substantial personalization and CDP stack plus credible retail planning modules. The company clearly operates real software, publishes real developer documentation, and has a coherent retail-suite story connecting customer engagement, merchandising, and some planning functions. That already puts it above many vague AI vendors.

Public evidence does not support a strong claim that Algonomy is a transparent or especially distinctive supply-chain optimization vendor. The forecasting and replenishment modules appear plausible and useful, but their public technical basis remains largely undisclosed. The best reading is therefore narrow and practical: Algonomy looks strongest when evaluated as a retail personalization and customer-data company with added retail planning capabilities, not as a deeply transparent supply-chain decision engine.

Source dossier

[1] Algonomy launch announcement

  • URL: https://algonomy.com/algonomy-launches-to-power-digital-first-as-the-new-normal-for-retailers-and-brands-across-the-globe/
  • Source type: vendor press release
  • Publisher: Algonomy
  • Published: January 19, 2021
  • Extracted: April 29, 2026

This is the primary source for the Algonomy brand launch. It establishes the combined company story and the initial retail AI positioning spanning customer engagement and broader retail decisioning.

[2] Business Wire launch coverage

  • URL: https://www.businesswire.com/news/home/20210119005161/en/Algonomy-Launches-to-Power-%E2%80%98Digital-First%E2%80%99-as-the-%E2%80%98New-Normal%E2%80%99-for-Retailers-and-Brands-Across-the-Globe
  • Source type: press coverage
  • Publisher: Business Wire
  • Published: January 19, 2021
  • Extracted: April 29, 2026

This coverage corroborates the launch timing and framing from a major press-distribution channel. It is useful as an independent confirmation of the merger narrative.

[3] Times of India merger coverage

  • URL: https://timesofindia.indiatimes.com/business/india-business/manthan-richrelevance-join-to-form-algonomy/articleshow/80354593.cms
  • Source type: press article
  • Publisher: The Times of India
  • Published: January 20, 2021
  • Extracted: April 29, 2026

This article is useful because it shows how the combination was framed in mainstream business coverage. It reinforces the dual heritage of Manthan and RichRelevance.

[4] Economic Times listing-plan article

  • URL: https://economictimes.indiatimes.com/tech/information-tech/manthan-richrelevance-merge-to-form-algonomy-us-listing-in-2023/articleshow/80347512.cms
  • Source type: press article
  • Publisher: The Economic Times
  • Published: January 19, 2021
  • Extracted: April 29, 2026

This source is important mainly because it records the early US-listing ambition. It is useful historical context precisely because that outcome does not appear to have materialized publicly.

[5] Algonomy newsroom

  • URL: https://algonomy.com/newsroom/
  • Source type: vendor newsroom
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

The newsroom is useful because it shows continued product and customer activity well after launch. It supports the view that Algonomy remains an active operating company rather than a dormant brand.

[6] Algonomy intent to acquire Linear Squared

  • URL: https://algonomy.com/algonomy-announces-intent-to-acquire-the-business-of-linear-squared/
  • Source type: vendor press release
  • Publisher: Algonomy
  • Published: January 5, 2022
  • Extracted: April 29, 2026

This is the key source for the Linear Squared transaction. It matters because Linear Squared appears to underpin much of the forecasting lineage now associated with Forecast Right.

[7] PR Newswire coverage of Linear Squared deal

  • URL: https://www.prnewswire.com/news-releases/algonomy-announces-intent-to-acquire-the-business-of-linear-squared-ai-powered-retail-and-cpg-demand-planning--forecasting-provider-301454351.html
  • Source type: press release distribution
  • Publisher: PR Newswire
  • Published: January 5, 2022
  • Extracted: April 29, 2026

This source corroborates the same transaction from a separate distribution channel. It reinforces the seriousness of the announced move into demand planning and forecasting.

[8] Retail Today coverage of Linear Squared deal

  • URL: https://retail-today.com/algonomy-to-acquire-linear-squared-ai-powered-retail-and-cpg-demand-planning-forecasting-provider/
  • Source type: trade press article
  • Publisher: Retail Today
  • Published: January 2022
  • Extracted: April 29, 2026

This article is useful because it shows how the market understood the transaction. It also highlights that third parties often treated the deal as effectively completed even when the vendor phrased it as intent.

[9] Recommend API recsForPlacements

  • URL: https://cdn.richrelevance.com/online_help/public/en/Content/Topics_Recommend/api_guide/recsForPlacements.htm
  • Source type: developer documentation
  • Publisher: RichRelevance / Algonomy documentation
  • Published: unknown
  • Extracted: April 29, 2026

This is one of the strongest technical sources in the dossier. It exposes a concrete recommendation endpoint, response behavior, and event logging, proving real product substance on the personalization side.

[10] JSON Integration Overview

  • URL: https://cdn.richrelevance.com/online_help/public/en/Content/Topics_Integration/json_integ_core_integ_guide/JSON%20Integration%20Overview.htm
  • Source type: developer documentation
  • Publisher: RichRelevance / Algonomy documentation
  • Published: unknown
  • Extracted: April 29, 2026

This page is useful because it documents first-party capture, integration-versus-production endpoints, and instrumentation mechanics. It supports the assessment that Algonomy’s ecommerce stack is operationally mature.

[11] Release Summary 14 Nov 2024

  • URL: https://cdn.richrelevance.com/online_help/public/en/Content/Topics_Release_Summaries/2024/Release%20Summary%2014_Nov_2024.htm
  • Source type: release notes
  • Publisher: RichRelevance / Algonomy documentation
  • Published: November 14, 2024
  • Extracted: April 29, 2026

The release notes are valuable because they show a maintained product with ongoing engineering work. This source also exposes some of the company’s current “Ensemble AI” language in a concrete product-maintenance context.

[12] Release Summary 21 Mar 2024

  • URL: https://cdn.richrelevance.com/online_help/public/en/Content/Topics_Release_Summaries/2024/Release%20Summary%2021_Mar_2024.htm
  • Source type: release notes
  • Publisher: RichRelevance / Algonomy documentation
  • Published: March 21, 2024
  • Extracted: April 29, 2026

This source documents first-party instrumentation migration toward algorecs.com. It is useful evidence of live engineering and privacy-conscious operational change.

[13] Real-time CDP developer home

  • URL: https://developer.algonomy.com/rcdp/en/Content/Home_api_rcdp.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

The CDP developer home is one of the best sources for the scope of the CDP product. It makes the implementation surface immediately visible: SDKs, connectors, clickstream APIs, consent, and references.

[14] Getting Started with Real-time CDP

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_SDK_developer%20guide/Getting%20started.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

This guide gives a concise product-level description of the Real-time CDP and shows that Algonomy exposes practical implementation entry points rather than only marketing pages. It is modest in depth, but still useful because it proves the product has a real onboarding and developer-facing surface.

[15] React-Native SDK guide

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_SDK_developer%20guide/React-Native%20SDK.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

This source is important because it exposes current mobile SDK surface and the bridge to TargetOneMobileSDK. It is another strong signal that the company runs real, maintained software.

[16] Active Content / CodeFusion docs

  • URL: https://developer.algonomy.com/rcdp/en/Content/Home_api_ac.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

These docs are useful because they show how Algonomy expects customers to fuse APIs and rendered content for activation. They reinforce the suite’s engagement and orchestration orientation.

[17] Forecast Right datasheet

  • URL: https://algonomy.com/wp-content/uploads/2022/06/Forecast-Right-Datasheet.pdf
  • Source type: vendor datasheet
  • Publisher: Algonomy
  • Published: June 2022
  • Extracted: April 29, 2026

This is the core supply-chain source for the forecasting story. It claims multivariate, hierarchical, and retail-native demand forecasting with automatic model selection and data-enrichment capabilities.

[18] Forecast Right ebook landing page

  • URL: https://algonomy.com/resource/forecast-right-ebook/
  • Source type: vendor resource page
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

This page is useful because it extends the forecasting positioning beyond the datasheet and reinforces that the supply-chain messaging is targeted at retail merchandise and demand planners. It also shows that the planning narrative is still packaged as a retail business resource rather than as a technical forecasting exposition.

[19] Order Right datasheet

  • URL: https://algonomy.com/wp-content/uploads/2022/06/Order-Right-Datasheet.pdf
  • Source type: vendor datasheet
  • Publisher: Algonomy
  • Published: June 2022
  • Extracted: April 29, 2026

This is the main replenishment source. It is especially useful because it names concrete constraints such as shelf-life, lead times, MOQs, display stock, and ordering frequency, making the module more credible than generic optimization rhetoric.

[20] Azure Marketplace listing for Order Right

  • URL: https://azuremarketplace.microsoft.com/en-au/marketplace/apps/algonomysoftwareprivatelimited1672991874831.order_right_01?tab=overview
  • Source type: marketplace listing
  • Publisher: Microsoft Azure Marketplace
  • Published: unknown
  • Extracted: April 29, 2026

This source supports the existence of a packaged market-facing offering for Order Right. It adds modest credibility to the notion that the module is sold as software rather than only custom services.

[21] API Reference Guide

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_am_API/introduction_rcdp_apis.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

The API reference guide is valuable because it enumerates concrete API families such as clickstream, product catalog, GDPR, and customer profile management. It strengthens the case for technical transparency on the CDP side.

[22] Data Model Extension docs

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_dme/data_model_extension.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

This page is useful because it shows that the CDP surface is not entirely rigid and includes a documented way to extend the data model. That is a real product-level signal, not just generic marketing.

[23] Shopify connector guide

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_Integration/Getting_started_with_Connectors.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

The Shopify connector guide is a good example of concrete integration detail. It demonstrates the kind of operational implementation guidance that many peers never publish.

[24] Amazon S3 destination settings

  • URL: https://developer.algonomy.com/rcdp/en/Content/Topics_Integration/Destination_settings%20for%20Amazon%20S3.htm
  • Source type: developer documentation
  • Publisher: Algonomy
  • Published: unknown
  • Extracted: April 29, 2026

This source is useful because it exposes destination channels, connector configuration, and the practical mechanics of moving data out of the system. It adds to the picture of a real integration platform.

[25] Linear Squared FORECAST Squared on Azure Marketplace

  • URL: https://azuremarketplace.microsoft.com/en-us/marketplace/apps/linearsquared.forecaset_squared?tab=overview
  • Source type: marketplace listing
  • Publisher: Microsoft Azure Marketplace
  • Published: unknown
  • Extracted: April 29, 2026

This source helps corroborate the pre-Algonomy existence of a real forecasting product lineage behind the Linear Squared deal. It matters because it makes the forecasting claims less synthetic.

[26] Linear Squared FORECAST Squared on AppSource

  • URL: https://appsource.microsoft.com/en-us/product/saas/linearsquared.forecaset_squared
  • Source type: marketplace listing
  • Publisher: Microsoft AppSource
  • Published: unknown
  • Extracted: April 29, 2026

This second marketplace source reinforces the same product-lineage point. It provides additional independent evidence that Linear Squared was a real product business, not just a thin acquisition story.

[27] RichRelevance GitHub organization

  • URL: https://github.com/orgs/RichRelevance/repositories
  • Source type: public code organization
  • Publisher: GitHub
  • Published: unknown
  • Extracted: April 29, 2026

The public RichRelevance organization is useful because it exposes traces of a historically industrial software stack, including Java and data-infrastructure tooling. It is legacy evidence, but still meaningful.

[28] Searchandise acquisition record

  • URL: https://mergr.com/transaction/richrelevance-acquires-searchandise-commerce
  • Source type: M&A database record
  • Publisher: Mergr
  • Published: unknown
  • Extracted: April 29, 2026

This source documents the Searchandise acquisition and helps reconstruct the earlier product-building path behind the RichRelevance side of Algonomy. It is useful because it shows that the company expanded by bolting on retail-search capabilities rather than building every merchandising component from scratch.

[29] Avail acquisition announcement

  • URL: https://www.businesswire.com/news/home/20130513005555/en/RichRelevance-Acquires-Avail-Europes-Largest-Provider-Online
  • Source type: press release
  • Publisher: Business Wire
  • Published: May 13, 2013
  • Extracted: April 29, 2026

This source is useful because it confirms another important pre-merger acquisition that contributed to portfolio breadth. It supports the view that Algonomy’s current estate is historically assembled.

[30] Precog acquisition coverage

  • URL: https://techcrunch.com/2013/08/14/richrelevance-acquires-precog-to-add-large-scale-analytics-engine-to-e-commerce-personalization-platform/
  • Source type: press article
  • Publisher: TechCrunch
  • Published: August 14, 2013
  • Extracted: April 29, 2026

This source documents the Precog acquisition and highlights the analytics-engine lineage behind the personalization platform. It is useful because it reinforces the long-standing commerce and analytics center of gravity in the broader Algonomy product story.