Implementation traceability
What is standard, what is custom, what is external
Every screen in this demo maps to a buildable implementation. This page is the CEO’s reality check: the experience is ambitious, the technology is ordinary — mostly configuration.
Odoo native
Odoo configuration
Atelier custom
External integration
Future concept
Odoo application map
Proposed stack, using standard apps wherever the fit is honest.
| Odoo app | Used for | Classification | Note |
|---|---|---|---|
| Contacts & CRM | Customer records, leads from website/Instagram/walk-in | Native | Pipelines configured per source |
| Sales & Quotations | Quotes for repairs, approval tracking, conversion to jobs | Config | Quote templates per service |
| Website / eCommerce | Public site, enquiry form, booking page, product list | Config | Branded theme on standard blocks |
| Appointments | Slot booking synced with counter calendar | Native | Service-typed slot types |
| Point of Sale | Counter sales, mixed carts, cash & journal handling | Config | SumUp payment method via integration |
| Repairs (workshop) | Item intake, photos, condition, 9-state lifecycle, QC | Custom | The one real Odoo module to build |
| Project / Tasks | Bench checklists, assignments | Config | Driven by the custom module |
| Inventory & Purchase | Materials, care products, reorder drafts | Native | Two locations: shop & bench |
| Invoicing & Accounting | Invoices, VAT, journals, reconciliation, closing | Native | German chart of accounts (SKR) |
| Employees, Planning, Timesheets | Staff, shift planning, labour per job | Config | Timesheets feed margins |
| Email & Marketing Automation | Status mails, review requests, care reminders | Config | WhatsApp via external provider |
| Reporting / Dashboards | Owner view: revenue, jobs, margins, receivables | Config | Plus custom job KPIs |
SumUp handoff — the exact sequence
Modelled on the public SumUp Cloud API and the Virtual Solo simulator. Odoo commands; SumUp settles the card; Odoo records the result. Responsibility never blurs.
- Odoo POS opens a checkoutEmployee creates/opens the order; customer & items attached (screen POS-2/3).
- Card selected as methodOdoo POS requests payment through the SumUp integration module (payment method “SumUp”, terminal #2).
- Checkout created via Cloud APIAmount, currency EUR, merchant profile, return URL/webhook. Idempotency key from the POS order prevents duplicates.
- Terminal receives the requestSumUp Solo displays the amount — “tap, insert or swipe”. Terminal identity is verified by SumUp, not by us.
- Customer paysCard interaction happens entirely on the SumUp device. Odoo shows “waiting for card”.
- Result returnsWebhook (and fallback status check) delivers the outcome with a transaction id and auth code.
- Odoo records the paymentPayment posted on the order; failed/uncertain outcomes never mark paid (see table below).
- Invoice & accounting updateInvoice RE-2026-1107 marked paid, journal entry created, payout (T+2) registered for reconciliation.
- Everything else followsJob AH-1001 → collected/closed, stock decremented, customer history & follow-ups updated.
| Outcome | System behaviour |
|---|---|
| Successful | Paid · tx id + auth shown · invoice updated · receipt options |
| Declined | Not paid · retry or switch method · no journal entry |
| Cancelled (customer) | Not paid · terminal request closed · retry allowed |
| Timed out | Not paid · terminal auto-cancels · single request, no doubles |
| Terminal offline | No request sent · reconnect flow · cash/transfer remain |
| Result uncertain | Never auto-marked · status re-checked with SumUp · original checkout closed before any retry |
Anti-double-charge rule. Every retry goes through a new Cloud API checkout with a fresh idempotency
key, and only after the previous checkout reached a terminal state. The POS disables the pay button while a
request is in flight — visible in the demo.
Screen-to-module matrix
Every major screen of the demo, its owner, its process, and its implementation label.
| ID | Screen | Role | Business process | Odoo app | Classification | External | Prototype | Demo |
|---|---|---|---|---|---|---|---|---|
| Internal business application — app.html | ||||||||
| INT-D1 | Management dashboard | Owner | Steering & control | Dashboards | Config + custom KPIs | — | Interactive | E |
| INT-C1 | Customers (CRM list) | Front desk | Customer acquisition | CRM/Contacts | Native | — | Interactive | A, E |
| INT-C2 | Customer 360 · Anna Müller | Front desk / Owner | Service history | Contacts | Native + repairs history | — | Interactive | B, E |
| INT-C3 | Customer 360 · Katharina Ott (bespoke) | Owner / Front desk | Bespoke commission | Contacts + Sales | Native + deposit rule | — | Interactive | B |
| INT-I1 | Intake · customer step | Front desk | Intake | CRM | Native | — | Interactive | B |
| INT-I2 | Intake · item, damage, photos | Front desk | Intake | Repairs (custom) | Custom | — | Interactive | B |
| INT-I3 | Intake · services & assessment | Front desk | Quotation | Sales | Config | — | Interactive | B |
| INT-I4 | Intake · confirm & job ref | Front desk | Intake | Repairs (custom) | Custom | — | Interactive | B |
| INT-W1 | Workshop board (9 states) | Workshop | Job lifecycle | Repairs (custom) | Custom | — | Interactive | B |
| INT-W2 | Job detail · checklist, materials, time | Workshop | Job lifecycle | Project/Timesheet | Config | — | Interactive | B |
| INT-W3 | Quality check & rework | Master | Quality | Repairs (custom) | Custom | — | Interactive | B |
| INT-Q1 | Quotations list & editor | Front desk | Quotation → order | Sales | Native | — | Interactive | B |
| INT-A1 | Appointments today | Front desk | Booking | Appointments | Native | — | Interactive | A |
| INT-V1 | Inventory & reorder | Owner | Materials | Inventory/Purchase | Native | — | Interactive | E |
| INT-K1 | Invoices & daily closing | Owner | Finance | Invoicing/Acct. | Native | SumUp payout | Interactive | C, E |
| INT-R1 | Service profitability report | Owner | Steering | Reporting | Config | — | Static sample | E |
| POS & SumUp — pos.html | ||||||||
| POS-1 | Catalogue & search | Front desk | Sale | POS | Config | — | Interactive | C |
| POS-2 | Cart & customer attach | Front desk | Sale | POS | Config | — | Interactive | C |
| POS-3 | Checkout · order review | Front desk | Payment | POS | Config | — | Interactive | C |
| POS-4 | Payment method choice | Front desk | Payment | POS | Config | — | Interactive | C |
| POS-5 | SumUp terminal interaction | Front desk / Customer | Card payment | — | External | SumUp Cloud API | Simulated | C |
| POS-6 | Payment results (6 states) | Front desk | Payment | POS | Integration logic | SumUp | Simulated | C |
| POS-7 | Cash & change | Front desk | Payment | POS cash journal | Native | — | Interactive | C |
| POS-8 | Bank transfer & reconcile | Front desk / Owner | Payment | Invoicing | Native | Bank feed | Simulated | C |
| POS-9 | Completion · records updated | Front desk | Sale → books | POS/Acct. | Native | SumUp | Interactive | C |
| Customer website — website.html | ||||||||
| WEB-1 | Homepage | Customer | Discovery | Website | Config | — | Interactive | A |
| WEB-2 | Service pages ×5 | Customer | Discovery | Website | Config | — | Interactive | A |
| WEB-3 | Portfolio & products | Customer | Discovery | Website/eCommerce | Config | — | Interactive | A |
| WEB-4 | Repair enquiry with photos | Customer | Lead capture | Website → CRM | Config | — | Interactive | A |
| WEB-5 | Appointment booking | Customer | Booking | Appointments | Native | — | Interactive | A, D |
| WEB-6 | Contact & location | Customer | Discovery | Website | Config | Maps (prod) | Placeholder map | A |
| Customer portal — portal.html | ||||||||
| POR-1 | Login / registration | Customer | Access | Portal | Native | — | Interactive | D |
| POR-2 | Overview & action-needed | Customer | Service history | Portal | Config | — | Interactive | D |
| POR-3 | Orders & repair tracking | Customer | Job lifecycle (view) | Portal + custom | Custom view | — | Interactive | D |
| POR-4 | Quote review & approval | Customer | Quotation | Portal/Sales | Native | — | Interactive | D |
| POR-5 | Invoices & receipts | Customer | Payment (view) | Portal | Native | — | Interactive | D |
| POR-6 | Profile, prefs, privacy | Customer | Consent & data | Portal | Config | — | Interactive | D |
| Mobile app (concept) — mobile.html | ||||||||
| MOB-1 | Home & notifications | Customer | Relationship | — (app) | Future | Push service | Interactive | D |
| MOB-2 | Services & detail | Customer | Discovery | — (app) | Future | — | Interactive | D |
| MOB-3 | New request + photos | Customer | Lead capture | CRM API | Future | — | Interactive | D |
| MOB-4 | Appointments | Customer | Booking | Appointments API | Future | — | Interactive | D |
| MOB-5 | Orders & tracking detail | Customer | Job lifecycle (view) | Portal API | Future | — | Interactive | D |
| MOB-6 | Quote approval (replay) | Customer | Quotation | Sales API | Future | — | Interactive | D |
| MOB-7 | Invoice & payment info | Customer | Payment (view) | Invoices API | Future | — | Interactive | D |
| MOB-8 | Profile & preferences | Customer | Consent & data | Portal API | Future | — | Interactive | D |
Prototype assumptions — what is simulated
Simulated behaviours
- · SumUp terminal: no real API calls; outcomes triggered from the clearly-marked simulation box, modelled on the public Cloud API docs and Virtual Solo.
- · Bank feed: “simulate bank receipt” stands in for Odoo’s bank statement import & reconciliation.
- · Notifications: e-mail / SMS / WhatsApp sends are represented by toasts and message rows.
- · Intake & POS replays: AH-1001’s intake and checkout are presented as labelled replays of the week’s real record, so the demo keeps one consistent story.
- · Data: all customers, jobs, amounts are sample data. VAT 19%, EUR, German context.
Design decisions & substitutions
- · Fonts: Cormorant Garamond + Manrope — the site’s actual pairing, no substitution needed.
- · Product tiles: no usable product packshots were available on the site, so care products use labelled placeholder tiles instead of misleading photos.
- · Map: styled placeholder — production uses an embedded map service.
- · Logo on dark: derived lightened wordmark; replace with an official white logo file if one exists.
- · Mobile shell: iOS presentation; the same system is documented for Android conventions.
- · Second persona: Katharina Ott demonstrates the bespoke journey in the app (360 record, commission quote, deposit, fittings); the portal and mobile app remain Anna’s surfaces.
- · Success-green (#2E7D4F) is a semantic state colour added for statuses — not a site brand colour.
Integration dependencies
Must exist
- · Odoo (proposed: current ERP edition) with the apps listed above.
- · Custom “Repairs & Workshop” Odoo module — the single genuine build item: item model, photo attachments, 9-state flow, QC gate, customer-facing status mapping.
- · SumUp merchant account + SumUp Solo terminal (Cloud API capable) replacing the Solo Lite reader.
- · Odoo↔SumUp payment integration (connector module) with webhook + status-check fallback.
Optional / later
- · WhatsApp Business API for status messages (via marketing automation).
- · Google review request automation after collection.
- · Mobile app (concept in this demo) — decision native vs. PWA pending.
Open technical questions for the CEO & implementers
| Q1 | Deposits & partial payments | Require deposits for large jobs (bespoke)? Partial payment at intake vs. full payment at collection? |
| Q2 | German POS fiscalization | KassenSichV / DSFinVK apply to electronic POS: TSE (technical security device) and fiskaltrust or equivalent must be scoped — affects POS hardware & Odoo setup. |
| Q3 | SumUp payout reconciliation | Daily manual match vs. automated import of payout reports into Odoo banking. |
| Q4 | Multiple terminals | One Solo at the counter first; routing rules if a second terminal (workshop?) is added. |
| Q5 | Photo retention | How long do intake photos stay on customer records (GDPR) — with the job, or archived after closing? |
| Q6 | Mobile app commitment | Native (iOS/Android) vs. PWA on the portal API — cost/complexity trade-off for Phase 3. |
| Q7 | Migration of existing records | Which historical customer/job data moves into Odoo at go-live, and from where? |
Preservation note. This branded demo is a separate workspace; the low-fi functional foundation
(personas, journeys, process maps, wireframes) remains untouched and remains the requirements baseline.
