Purchase profile / 47.92s

One order becomes personalization.

An immutable order fact becomes a reusable customer-product profile, then combines with later browsing intent on HOME.

Silent film with burned-in narrationOpen WebM directly

What You Will See

  1. One real orderThe purchase creates a durable line-level fact rather than a transient recommendation click.
  2. A later product viewBrowsing adds short-term intent without rewriting purchase history.
  3. Two signals meetHOME presents a strip built from purchase-derived and view-derived candidates.
  4. Seeds stay excludedThe products that supplied context do not return as their own recommendations.

Why It Matters

Per-order history and customer preference are related facts, not the same data structure.

BlueShop keeps every order-product fact for traceability while maintaining a recomputable customer-product summary for serving.

The System Underneath

Order product factOne line from one non-cancelled order
Transactional inboxEnvelope identity prevents duplicate effect
Purchase summaryCount, quantity, first and last purchase
PERSONAL_HISTORYBlended with recent-view similarity
Cancellation recomputes the summary from remaining active facts and removes it when nothing remains.

What This Story Proves

Visible proof

The order, later view and resulting HOME strip are visible in one journey.

Executable proof

The acceptance response requires one PERSONAL_HISTORY result, one SIMILAR_CONTENT result and exclusion of both seeds.

Read how order facts become profiles.

AI engineering connectionExecutable feedback constrains autonomous change