Corum Health

If a buyer requires strong third-party review validation upfront

• The vendor has limited discoverable presence on common B2B review platforms in accessible searches; organizations that rely on peer review volume as a gating criterion may prefer alternatives with larger, independently verifiable review footprints.

If a buyer needs published line-item pricing

• The vendor uses a demo- and quote-driven procurement model; buyers needing online published pricing may find this model a mismatch.

If procurement requires formal public security attestations

• SOC 2 and ISO 27001 claims were not clearly published in accessible vendor materials; regulated buyers may prefer vendors that publish trust centers and certifications.

If only a narrow point solution is required

• Organizations that only need a single function (for example, dispensing only or POS only) may find a suite vendor increases implementation scope and cost.

Current limitations acknowledged by the vendor

• No dedicated public “known issues” page for the overall platform was found in accessible materials; release notes are available and should be reviewed during diligence for recurring defect patterns.

Roadmap (not publicly available)

• No detailed public roadmap with release dates was located in the material reviewed.

Scale limitations

• No explicit published scale boundaries (for example, maximum stores supported, maximum transactions per day, or infrastructure sizing guidance) were found; buyers requiring scale assurances should request sizing documentation.

Security/compliance gaps

• Public-facing security assurance documentation is limited; the absence of publicly posted SOC 2 or ISO certifications should be treated as a gap until vendor-provided documentation is obtained.

API limitations or integration constraints

• The vendor references embedded third-party integrations, but publicly accessible materials did not enumerate integrations, APIs, or a partner catalog sufficient for technical validation; buyers should request an integration and API specification.

• The vendor positions its products as modular and interoperable, enabling customers to adopt components rather than a single monolithic solution.

• Product set includes medication packing functionality, dispensing modules, POS/retail integration, remote access tools, backup/resilience capabilities, and payment integration features.

• Vendor statements indicate ownership by a larger software group, which the vendor frames as providing longer-term operational stability; procurement should still validate roadmap and support commitments contractually rather than relying solely on ownership statements.

• No detailed public case studies with independently verifiable quantitative metrics were found in the sources reviewed for this report.

• Vendor-published documentation (help articles, manuals, release notes) indicates product breadth and operational maturity but does not substitute for outcome-based case studies with validated ROI figures.

• The absence of third-party-verified ROI or time-savings case studies suggests buyers should construct internal business cases using measured baselines (for example, scripts per hour, packing error rates, stock adjustments, and downtime metrics) and validate improvements during a pilot period.