Overview & north star
What E-FACTS is, why it exists, and how product work stays aligned
Product overview
E-FACTS turns point-of-sale and paper receipts into a durable digital record for the shopper — returns, warranties, spend insight, and sustainability signals in one consumer experience, with retailer-facing systems behind the scenes.
Audience
Write for a mixed company audience (Founder, Exec, Design, Dev). Link to Engineering for implementation detail and Design language for UI rules.
North star
Digital receipt infrastructure from POS → consumer wallet — accurate, private, and useful every time someone needs proof of purchase.
If a feature does not make the receipt owner faster, clearer, or safer, it is not on the critical path.
What we are
| Layer | Job |
|---|---|
| Capture | Retail POS / receipt events become structured digital receipts (line items, UCI, returns windows, warranties). |
| Consumer | Shoppers see receipts, bills, analysis, and offers without hunting paper. |
| Impact | Surface paper saved, CO₂ offsets, and eco-receipt milestones where they are real — not decorative greenwashing. |
Product surfaces (at a glance)
| Surface | Primary job |
|---|---|
| Consumer iOS app | Daily shopper product (AppTab: Home · My Bills · Analysis · Offers) |
| Marketing website | Public narrative + entry points (efacts.ca) |
| Backend / APIs | Source of truth for auth, receipts, wallet bind, warranties |
| Internal docs | Company handbook (dev.efacts.ca — this site) |
| Portal / ops | Retail / internal access — separate session boundaries |
Deep dive: Surfaces map · Information architecture.
How we decide
- Start from the shopper job (find a receipt, return an item, understand spend).
- Prefer structured data over screenshots or opaque PDFs.
- Ship on the surface that owns the job (marketing ≠ app ≠ API).
- Measure with metrics; kill or revise what does not move them.
Full framework: Product principles · Feature lifecycle.
Domains
| Domain | Role |
|---|---|
| efacts.ca | Public / marketing presence |
| dev.efacts.ca | Internal docs (this site) — gated access |
| Local | localhost for website, docs, and API during development |
Exact API base URLs and secrets live in each repo’s env docs — never in this handbook.
In this section
| Page | Use when you need… |
|---|---|
| Users & personas | Who we design for |
| Principles | Decision framework |
| Surfaces | Which product owns which job |
| Information architecture | 4-tab consumer app |
| Feature lifecycle | Propose → ship → measure |
| Metrics | Success criteria |
| Writing for product | Tone for execs & shoppers |
| FAQ | Common PM / founder questions |