A Centralized, Reusable Architecture
Why This Matters
When working with Sitecore Search (Discover) and OrderCloud, one problem always shows up:
They don’t naturally talk to each other.
- Search knows what to show
- OrderCloud knows who the user is and what they can buy
But neither understands the other.
The result:
Disconnected experiences, duplicate logic, and fragile integrations.
The Core Problem
To deliver a real commerce experience:
Sitecore Search needs:
- User identity (for personalization)
- Store context (for inventory)
- A valid OrderCloud token
OrderCloud needs:
- Proper configuration per site
- Token lifecycle handling
- Awareness of Search making API calls
The Solution: A Centralized Bridge
Instead of connecting things in multiple places,
we introduce one centralized layer in Next.js:
A bridge that connects Search ↔ OrderCloud
Key Design Ideas
Centralization
All communication flows through one bridge
→ no scattered logic
Multisite Ready
- Config-driven setup
- Add new site without changing architecture
Token Control
- Single place for token validation & refresh
- Prevents duplicate API calls and race conditions
Progressive Enhancement
- Show search results instantly
- Enrich with live data in background
What’s Next
In the next blog
- Implementation
- Code structure
- Reusable utilities
Happy Coding 🎉
Leave a Reply