Changelog
Coodra changelog.
Latest updates to the Coodra website, docs, dashboard, AI, privacy, and operational foundation.
Updates
Major updates to the public website, docs, signed-in dashboard, Ask Coodra, privacy controls, and operational foundation.
June 2026
Deeper Ask Coodra answers now finish the job
Complex inventory, margin, forecast, and recommendation questions use a deeper review path. We fixed a generation limit that could stop those answers halfway through a sentence.
Quick questions still take the faster path. Deep reviews still show an expandable summary, keep hidden reasoning private, and now return the complete grounded answer instead of an accidental cliffhanger.
- Deep reviews finish with a complete answer when store data is missing or unavailable.
- Quick connected-system checks remain fast and clearly labeled.
- Prompt extraction, cross-retailer data requests, and unsupported live-write claims remain blocked.
Dashboard refresh prompts now stay dashboard-specific
The signed-in dashboard now checks a dashboard build fingerprint instead of treating every public website deployment as a reason to interrupt the user.
That means a copy tweak on the marketing site should not ask a retailer to refresh their dashboard. Dashboard changes still get surfaced quickly when a tab opens, regains focus, or returns online.
- Fewer noisy update prompts for changes that do not affect signed-in work.
- Cleaner release behavior when public pages and dashboard code ship at different speeds.
Login moves to email-code verification faster
The login flow now gets users to the verification-code step sooner by preloading the auth path, skipping unnecessary MFA status checks when no trusted device token exists, and starting the email-code send without extra waiting in the form UI.
Dashboard access still waits for verified account access and the protected backend session exchange. Faster should not mean looser.
Ask Coodra can show what it checked
Ask Coodra now has a client-facing work summary pattern for deeper questions. The goal is to show the useful breadcrumbs: the kind of question asked, the retail context checked, and the tools or paths used.
This is not raw chain-of-thought, hidden prompts, provider internals, or a private scratchpad. It is a short, expandable summary that helps a retailer trust the answer without exposing things that should stay behind the wall.
- Recommendation questions that need more than a quick reply.
- Forecasting, margin, inventory, and operational questions where context matters.
- A calmer chat experience: useful transparency, not a wall of model noise.
Public docs became a real product handbook
Coodra now has public docs for the review workflow, data use, decision scoring, Ask Coodra, connector authorization, security, operations, troubleshooting, product boundaries, and common questions.
The docs are route-based, searchable, included in the sitemap, and written to be useful for people and answer engines. They explain what exists today without pretending Coodra is a public API platform or an autonomous ordering system.
Privacy-first analytics went live
Product analytics was added with consent gating and allowlisted events. Autocapture, session replay, surveys, dead-click tracking, feature flags, exception capture, and private retail data capture remain off unless a future privacy review deliberately changes that boundary.
The cookie banner was updated to say what people are actually choosing: accept cookies or keep necessary-only behavior.
Error monitoring and release trails were tightened
Frontend and backend errors now have cleaner release attribution and safer defaults around private data. Source-map upload support is documented for production releases when the required build-time variables are available.
The goal is boring in the best way: when something breaks, the team should know which release changed it and where to look first.
The v2 website became the source of truth
The public Coodra website moved onto the cleaned v2 frontend as the primary source of truth. Old v1 files and temporary artifacts were removed so the repository better matches the live product.
The public docs now keep product boundaries, operations, security posture, pricing, and access details in one place, so readers do not have to piece the product together from old notes.
Early access replaced public signup
Public self-signup now routes to early access. That is intentional while Coodra is guided, connector-sensitive, and still proving the first-review workflow with real retailers.
Pricing calls to action also point to early access, so the product does not accidentally promise self-service onboarding before the data and connector path can support it.