Replace all ~1,086 occurrences of Wizamart/wizamart/WIZAMART/WizaMart with Orion/orion/ORION across 184 files. This includes database identifiers, email addresses, domain references, R2 bucket names, DNS prefixes, encryption salt, Celery app name, config defaults, Docker configs, CI configs, documentation, seed data, and templates. Renames homepage-wizamart.html template to homepage-orion.html. Fixes duplicate file_pattern key in api.yaml architecture rule. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
9.9 KiB
Customer Ownership & Marketing Positioning
The Problem
Letzshop owns the customer relationship. Stores:
- Can't export customer emails easily
- Can't send marketing campaigns
- Can't retarget past buyers
- Lose repeat business to marketplace algorithm
Result: Stores acquire customers through Letzshop but can't turn them into loyal, direct customers.
What "Customer Ownership" Could Look Like
Level 1: Data Export (Simple)
What it is: Export customer list with order history to CSV.
┌────────────────────────────────────────────┐
│ Orion Dashboard │
│ ┌──────────────────────────────────────┐ │
│ │ Customers (142) [Export CSV] │ │
│ ├──────────────────────────────────────┤ │
│ │ Marie Dupont 3 orders €245 │ │
│ │ Jean Martin 1 order €89 │ │
│ │ Sophie Weber 5 orders €512 │ │
│ └──────────────────────────────────────┘ │
└────────────────────────────────────────────┘
│
▼ Export
┌────────────────────────────────────────────┐
│ email,name,orders,total_spent,last_order │
│ marie@...,Marie Dupont,3,245,2024-12-01 │
│ jean@...,Jean Martin,1,89,2024-11-15 │
└────────────────────────────────────────────┘
│
▼ Import manually
┌────────────────────────────────────────────┐
│ Mailchimp / Brevo / etc. │
└────────────────────────────────────────────┘
Effort: ~2 days (you already have customer data from orders) Support overhead: Very low Value: Medium - manual but functional
Level 2: Smart Segmentation (Medium)
What it is: Tag customers, filter by behavior, export segments.
┌────────────────────────────────────────────┐
│ Customer Segments │
│ ┌──────────────────────────────────────┐ │
│ │ 🏆 VIP (5+ orders) 23 │ │
│ │ 😴 Dormant (no order 90d) 45 │ │
│ │ 🆕 New (first order) 12 │ │
│ │ 🇩🇪 Germany shipping 34 │ │
│ │ 🎁 Holiday buyers 2023 28 │ │
│ └──────────────────────────────────────┘ │
│ │
│ [Export Segment to CSV] │
└────────────────────────────────────────────┘
Features:
- Auto-tagging based on behavior (VIP, dormant, new)
- Manual tagging (wholesale, problem customer)
- Filter by: country, order count, total spent, last order date
- Export filtered lists
Effort: ~1 week Support overhead: Low Value: High - actionable data
Level 3: Mailchimp Integration (Complex)
What it is: Direct sync with Mailchimp - customers auto-sync, segments sync, tags sync.
┌─────────────┐ ┌─────────────┐
│ Orion │ ──────► │ Mailchimp │
│ │ Sync │ │
│ Customers │ ◄────── │ Audiences │
│ Orders │ │ Tags │
│ Segments │ │ Campaigns │
└─────────────┘ └─────────────┘
API Integration Required:
- Mailchimp Marketing API v3
- OAuth 2.0 for account connection
- Webhook for unsubscribes (GDPR)
- Audience sync (create/update members)
- Tag sync (apply tags from segments)
Effort: ~2-3 weeks Support overhead: MEDIUM-HIGH
- "Why aren't my contacts syncing?"
- "My tags aren't showing up"
- Mailchimp API changes / deprecations
- GDPR compliance (unsubscribe sync)
Value: High - but is it 2-3 weeks of value?
Level 4: Built-in Email Marketing (Very Complex)
What it is: Send emails directly from Orion.
Required:
- Email template builder
- Email sending infrastructure (SendGrid, SES, Postmark)
- Deliverability management (SPF, DKIM, DMARC setup)
- Bounce/complaint handling
- Unsubscribe management
- Open/click tracking
- A/B testing
- Scheduling
- Campaign analytics
Effort: 2-3 months (to do it well) Support overhead: VERY HIGH
- "My emails go to spam"
- "Why didn't my campaign send?"
- Deliverability issues
- GDPR compliance
Value: Very high - but you're building Mailchimp
Verdict: Don't do this. Use existing tools.
Comparison: Back-Office vs Marketing Positioning
Option A: Back-Office Focus (Invoicing, Inventory, Operations)
| Aspect | Assessment |
|---|---|
| Core message | "Run your business better" |
| Primary features | VAT invoicing, inventory truth, locations, incoming stock |
| Target emotion | Fear (compliance), relief (organization) |
| Competitive moat | VAT expertise, Letzshop-specific |
| Support overhead | Low (self-contained systems) |
| Development effort | ~2-3 weeks for MVP |
| Revenue model | Subscription (necessary tool) |
Customer type: Operations-focused, compliance-worried
Option B: Marketing Focus (Customer Ownership, Retargeting)
| Aspect | Assessment |
|---|---|
| Core message | "Grow your business" |
| Primary features | Customer CRM, segmentation, Mailchimp sync |
| Target emotion | Ambition (growth), frustration (Letzshop limits) |
| Competitive moat | Weak (many CRM tools exist) |
| Support overhead | Medium-High (external integrations) |
| Development effort | ~3-4 weeks for meaningful features |
| Revenue model | Subscription (growth tool) |
Customer type: Growth-focused, marketing-savvy
The Strategic Question
Who is easier to sell to?
| Customer Type | Buys Because | Objection |
|---|---|---|
| Operations person | "I need this to not mess up" | "Is it really necessary?" |
| Growth person | "This will make me money" | "Will it actually work?" |
Which has stickier retention?
| Tool Type | Stickiness | Why |
|---|---|---|
| Back-office | HIGH | Your invoices, inventory data - hard to migrate |
| Marketing | MEDIUM | Customer list is portable, can switch tools |
Which is simpler to support?
| Tool Type | External Dependencies | Support Risk |
|---|---|---|
| Back-office | None | LOW |
| Marketing | Mailchimp API, email delivery | MEDIUM-HIGH |
My Recommendation
Start with Back-Office, Add Customer Export
Phase 1 (Now): Back-office tools
- VAT invoicing (differentiator, compliance fear)
- Inventory management (already built)
- Product locations (simple, useful)
- Incoming stock/PO (nice to have)
- Customer export to CSV (satisfies marketing need without complexity)
Phase 2 (Later, if demand): Marketing enhancement
- Smart segmentation
- Mailchimp sync (only if customers ask for it specifically)
Why This Order?
- Back-office is a "must-have" - stores need correct invoices
- Marketing is a "nice-to-have" - they can use Mailchimp directly with CSV export
- Lower risk - no external API dependencies to start
- Faster to market - VAT invoicing is ~1 week, Mailchimp is ~3 weeks
- Clearer positioning - "The back-office Letzshop doesn't give you"
The Hybrid Pitch
"Orion gives you the tools Letzshop doesn't:
- Correct invoices with proper VAT for any EU country
- Real inventory across all your channels
- Your customers - export anytime for your marketing
EUR 49/month. You focus on selling, we handle the back-office."
The customer export feature satisfies the marketing need without building a marketing platform.
If You Want Marketing Focus Instead
If you strongly feel marketing is the right angle:
Minimum Viable Marketing Product
- Customer list with order history ✓ (you have this)
- Basic tagging (manual + auto VIP/dormant)
- Segment filtering
- CSV export with segments
- Mailchimp sync (this is the "magic" feature)
Skip: Built-in email sending, campaign builder, analytics
Effort: ~3 weeks total
The pitch becomes:
"Own your Letzshop customers. Sync them to Mailchimp automatically. Build repeat business without copy-pasting spreadsheets."
But: This competes with many existing tools. Back-office is more defensible.
Final Comparison Table
| Factor | Back-Office (Invoicing) | Marketing (Customer CRM) |
|---|---|---|
| Uniqueness | HIGH (VAT expertise) | LOW (many CRM tools) |
| Development time | ~2 weeks | ~3-4 weeks |
| Support overhead | LOW | MEDIUM-HIGH |
| External dependencies | NONE | Mailchimp API |
| Stickiness | HIGH | MEDIUM |
| Emotional driver | Fear (compliance) | Ambition (growth) |
| Price sensitivity | LOW (necessary) | HIGH (nice-to-have) |
| Recommendation | START HERE | Add later if demanded |