Memory
What gets remembered from review.
Review history helps future ranking without becoming a hidden permission system or an automatic write path.
What gets remembered
Coodra should remember review outcomes: approved, skipped, adjusted, investigated, marked incomplete, or corrected. Those outcomes are useful because they show what the retailer found worth acting on.
It can also remember recurring patterns, such as a store that repeatedly skips small reorder suggestions for slow-moving accessories, or a buyer who wants supplier risk shown before margin cleanup.
What memory should not become
- Not a permission system
- Memory should not decide what a user is allowed to access. Roles and account checks handle that.
- Not an automatic write path
- Remembering a preference does not mean Coodra can change stock, orders, or catalogs by itself.
- Not a secret store
- Connector credentials and sensitive account data do not belong in advisory memory.
- Not a customer-proof machine
- Feedback history cannot be turned into public claims without evidence and permission.
How memory changes ranking
Memory should tune the queue. If a team repeatedly approves supplier-risk recommendations before reorder suggestions, Coodra can rank supplier-risk work higher. If a recommendation is often corrected because margin data is stale, Coodra should show the data issue instead of repeating the same confident mistake.