Destination
City traffic
Partners can later appear near city routes, country pages, and local destination paths.
Partner Master
Partner with the ELC place network.
Connect cultural venues, hospitality, cafes, print locations, and local offers to the destinations, landmarks, QR routes, and city experiences ELC is building.
Landmark
Place proximity
Nearby cafes, hotels, cultural stores, and venues can connect to landmark discovery.
QR
On-location entry
Future QR paths can open partner profiles, offers, redemption, or city experiences.
Commerce
Local value
Offers, print locations, and partner moments can later connect to Store and dashboards.
Placement system
Partners belong near real places, not in a generic ad directory.
The Partner Master should explain where a business can appear in the ELC product architecture while keeping the actual backend work for later phases.
Route surfaces
Destination pages
City destination pages
Landmark pages
Nearby places panels
QR entry experiences
Store offer handoffs
Partner types
A curated network of places around the ELC journey.
This shell reads a fixed partner type model. Actual partner profiles, media, offers, approvals, and billing remain separate backend phases.
Partner type
Cultural venues
Museums, galleries, heritage spaces, and cultural institutions near destination routes.
Culture
Partner type
Hotels and stays
Hospitality partners that can welcome readers, travelers, and city explorers.
Hospitality
Partner type
Cafes and restaurants
Nearby places for local recommendations, redemptions, and destination moments.
Local dining
QR and offers
QR will become the bridge between place and action.
Future QR routes can open partner profiles, specific landmark experiences, local offers, redemption states, or staff verification. This PR only shows the product model.
1
Apply with place context
2
ELC reviews fit and location value
3
Choose the right visibility path
4
Prepare partner profile and media
5
Attach to city, landmark, or QR route later
6
Track future scans, offers, and redemptions
Plan model
Clear partner tiers without activating billing yet.
The public page can explain the commercial shape now. Stripe, subscriptions, invoices, and partner billing status should stay in a later backend PR.
Profile and discovery
Presence
A curated partner profile with destination visibility and future nearby-place placement.
Billing laterOffers and route placement
Journey
Enhanced story, local offers, QR readiness, and city or landmark journey placement.
Billing laterCampaign and editorial depth
Signature
Curated editorial support, destination campaigns, and future verification workflows.
Billing laterPartner dashboard
Approved partners need a quiet operating room.
The dashboard should stay behind role-based login. It will later manage locations, media, offers, scans, redemptions, and billing status.
Partner loginLocations
Media and profile
Offers
QR scans
Redemptions
Billing status
Cross-system handoffs
Partners should support the ELC journey without taking over it.
Destinations find the place. Landmarks explain the place. Library supports reading. Store handles commerce. Partners connect local businesses to the place.
Destinations
Geography routes users toward countries, cities, landmarks, and nearby partner moments.
Open DestinationsLandmarks
Landmark pages become the place-level layer where nearby partner opportunities make sense.
Preview LandmarkStore
Store can later handle partner offers, bundles, products, and print-related commerce paths.
Open StoreDashboard
Approved partners will use the partner dashboard after auth and role routing are ready.
Partner LoginCurated network
Apply to join places that make the ELC experience more useful in the real world.
The application page is still a draft. Submissions, review workflow, billing, and partner profile creation should be added only when the backend phase is ready.