Guac

• Organizations that require published formal security/compliance certification (e.g., SOC 2/ISO) before engaging in a pilot if the vendor cannot provide evidence quickly under NDA.
• Organizations that are strictly standardized on an enterprise planning suite and will not consider point solutions.
• Environments where item-level data quality is insufficient (unreliable on-hands, missing promotion capture).

• The vendor emphasizes retailer-specific customization, which implies deployments are not fully plug-and-play and may require project work.
• The solution depends on ingesting internal data plus external data; data availability and quality can be gating factors.

No explicit public product roadmap with dates was found in the reviewed materials.

Not publicly documented. Buyers should request:

• Maximum validated store/SKU scale in production
• Latency of forecast generation
• Uptime and incident history

No public trust center or published certifications were found on the vendor site during this research.

The vendor describes integrations as custom; no public API documentation was found on the reviewed pages. Buyers should request API specifications, integration templates, and connector inventories during diligence.

• Fresh-category specialization rather than a generic demand-planning approach.
• Modeling that incorporates local external variables (weather granularity, school district calendars, demographics, local events), which can be important for short-horizon fresh forecasting.
• Operationalization focus: converting forecasts into ordering and production recommendations that can be embedded into store and DC workflows.

• Vendor-reported comparative forecasting performance and numeric claims (waste reduction, sales lift, MAE) require disclosure of methodology for independent assessment.
• Vendor statements about large-scale data usage and complex model architectures should be validated during technical due diligence and pilot work.

• RELEX / Blue Yonder: deeper suite integration, established reference base, mature integration frameworks, and more publicly documented enterprise security posture.
• Freshflow: more transparent pricing and packaging for mid-market buyers.
• Crisp (with Shelf Engine): broader data collaboration capabilities across the retailer–CPG interface and a wider ecosystem.

Because direct end-user reviews are scarce, public evidence is mainly vendor-published materials, Y Combinator profile information, press coverage (industry tech and trade outlets), and LinkedIn posts or partner content.

• Press coverage reported a founder comment that larger retailers often struggle to predict future demand and can both overstock and understock inventory.
• The vendor’s profile reports a specific accuracy metric for current customers and links that to a material reduction in food waste (these are vendor-reported figures without publicly available independent validation in the reviewed materials).

• There are no accessible G2/TrustRadius-style negative user reviews specifically about this vendor in the accessible public record. Therefore, the balanced view must rely more on vendor material, press coverage, and general patterns observed in demand forecasting deployments.

• Focused approach to fresh-category forecasting rather than a generic retail planning approach.
• Use of external and local variables (weather, events, school calendars) to inform short-horizon forecasts.
• Willingness to customize and provide hands-on rollout support, according to vendor materials.

• Preference for integrated suites (larger retail planning vendors) to reduce point-solution proliferation.
• Lack of publicly documented security/compliance materials may slow enterprise procurement.
• Customization approaches that create vendor-specific dependencies may increase long-term maintenance risk.

Likely best fit (inferred):

• Mid-market to enterprise grocery retailers — regional to national chains with dozens to many hundreds of stores depending on complexity and ROI thresholds.
• Retailers where fresh shrink materially affects margins and where a modest but financially meaningful sales lift or comparable shrink reduction is possible.

• Grocery retailers, regional chains, and specialty grocers with substantial perishables mixes.
• Potential adjacency: convenience chains with meaningful fresh assortments and commissary-driven prepared foods.

• Economic buyers: VP Fresh Operations, VP Merchandising, VP Supply Chain/Replenishment.
• Champions: Fresh category managers, replenishment planners, store operations leaders.
• End users: store order writers/managers, DC buyers, commissary planners.

• High spoilage/shrink and frequent stockouts in fresh categories.
• Manual ordering processes (spreadsheets, ad hoc heuristics) and inconsistent store execution.
• Difficulty incorporating local demand drivers such as events, school calendars, and weather.

• Accessible internal data (POS, inventory/on-hand, deliveries, promotions).
• Willingness to run a controlled pilot and operationalize process changes at the store level.
• A financial profile where shrink reduction or sales lift is material to the business.