Atelier Hamidi 09 · Technical & design notes Demo hub
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 appUsed forClassificationNote
Contacts & CRMCustomer records, leads from website/Instagram/walk-inNativePipelines configured per source
Sales & QuotationsQuotes for repairs, approval tracking, conversion to jobsConfigQuote templates per service
Website / eCommercePublic site, enquiry form, booking page, product listConfigBranded theme on standard blocks
AppointmentsSlot booking synced with counter calendarNativeService-typed slot types
Point of SaleCounter sales, mixed carts, cash & journal handlingConfigSumUp payment method via integration
Repairs (workshop)Item intake, photos, condition, 9-state lifecycle, QCCustomThe one real Odoo module to build
Project / TasksBench checklists, assignmentsConfigDriven by the custom module
Inventory & PurchaseMaterials, care products, reorder draftsNativeTwo locations: shop & bench
Invoicing & AccountingInvoices, VAT, journals, reconciliation, closingNativeGerman chart of accounts (SKR)
Employees, Planning, TimesheetsStaff, shift planning, labour per jobConfigTimesheets feed margins
Email & Marketing AutomationStatus mails, review requests, care remindersConfigWhatsApp via external provider
Reporting / DashboardsOwner view: revenue, jobs, margins, receivablesConfigPlus 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.

  1. Odoo POS opens a checkoutEmployee creates/opens the order; customer & items attached (screen POS-2/3).
  2. Card selected as methodOdoo POS requests payment through the SumUp integration module (payment method “SumUp”, terminal #2).
  3. Checkout created via Cloud APIAmount, currency EUR, merchant profile, return URL/webhook. Idempotency key from the POS order prevents duplicates.
  4. Terminal receives the requestSumUp Solo displays the amount — “tap, insert or swipe”. Terminal identity is verified by SumUp, not by us.
  5. Customer paysCard interaction happens entirely on the SumUp device. Odoo shows “waiting for card”.
  6. Result returnsWebhook (and fallback status check) delivers the outcome with a transaction id and auth code.
  7. Odoo records the paymentPayment posted on the order; failed/uncertain outcomes never mark paid (see table below).
  8. Invoice & accounting updateInvoice RE-2026-1107 marked paid, journal entry created, payout (T+2) registered for reconciliation.
  9. Everything else followsJob AH-1001 → collected/closed, stock decremented, customer history & follow-ups updated.
OutcomeSystem behaviour
SuccessfulPaid · tx id + auth shown · invoice updated · receipt options
DeclinedNot paid · retry or switch method · no journal entry
Cancelled (customer)Not paid · terminal request closed · retry allowed
Timed outNot paid · terminal auto-cancels · single request, no doubles
Terminal offlineNo request sent · reconnect flow · cash/transfer remain
Result uncertainNever 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.

IDScreenRoleBusiness processOdoo appClassificationExternalPrototypeDemo
Internal business application — app.html
INT-D1Management dashboardOwnerSteering & controlDashboardsConfig + custom KPIs—InteractiveE
INT-C1Customers (CRM list)Front deskCustomer acquisitionCRM/ContactsNative—InteractiveA, E
INT-C2Customer 360 · Anna MüllerFront desk / OwnerService historyContactsNative + repairs history—InteractiveB, E
INT-C3Customer 360 · Katharina Ott (bespoke)Owner / Front deskBespoke commissionContacts + SalesNative + deposit rule—InteractiveB
INT-I1Intake · customer stepFront deskIntakeCRMNative—InteractiveB
INT-I2Intake · item, damage, photosFront deskIntakeRepairs (custom)Custom—InteractiveB
INT-I3Intake · services & assessmentFront deskQuotationSalesConfig—InteractiveB
INT-I4Intake · confirm & job refFront deskIntakeRepairs (custom)Custom—InteractiveB
INT-W1Workshop board (9 states)WorkshopJob lifecycleRepairs (custom)Custom—InteractiveB
INT-W2Job detail · checklist, materials, timeWorkshopJob lifecycleProject/TimesheetConfig—InteractiveB
INT-W3Quality check & reworkMasterQualityRepairs (custom)Custom—InteractiveB
INT-Q1Quotations list & editorFront deskQuotation → orderSalesNative—InteractiveB
INT-A1Appointments todayFront deskBookingAppointmentsNative—InteractiveA
INT-V1Inventory & reorderOwnerMaterialsInventory/PurchaseNative—InteractiveE
INT-K1Invoices & daily closingOwnerFinanceInvoicing/Acct.NativeSumUp payoutInteractiveC, E
INT-R1Service profitability reportOwnerSteeringReportingConfig—Static sampleE
POS & SumUp — pos.html
POS-1Catalogue & searchFront deskSalePOSConfig—InteractiveC
POS-2Cart & customer attachFront deskSalePOSConfig—InteractiveC
POS-3Checkout · order reviewFront deskPaymentPOSConfig—InteractiveC
POS-4Payment method choiceFront deskPaymentPOSConfig—InteractiveC
POS-5SumUp terminal interactionFront desk / CustomerCard payment—ExternalSumUp Cloud APISimulatedC
POS-6Payment results (6 states)Front deskPaymentPOSIntegration logicSumUpSimulatedC
POS-7Cash & changeFront deskPaymentPOS cash journalNative—InteractiveC
POS-8Bank transfer & reconcileFront desk / OwnerPaymentInvoicingNativeBank feedSimulatedC
POS-9Completion · records updatedFront deskSale → booksPOS/Acct.NativeSumUpInteractiveC
Customer website — website.html
WEB-1HomepageCustomerDiscoveryWebsiteConfig—InteractiveA
WEB-2Service pages ×5CustomerDiscoveryWebsiteConfig—InteractiveA
WEB-3Portfolio & productsCustomerDiscoveryWebsite/eCommerceConfig—InteractiveA
WEB-4Repair enquiry with photosCustomerLead captureWebsite → CRMConfig—InteractiveA
WEB-5Appointment bookingCustomerBookingAppointmentsNative—InteractiveA, D
WEB-6Contact & locationCustomerDiscoveryWebsiteConfigMaps (prod)Placeholder mapA
Customer portal — portal.html
POR-1Login / registrationCustomerAccessPortalNative—InteractiveD
POR-2Overview & action-neededCustomerService historyPortalConfig—InteractiveD
POR-3Orders & repair trackingCustomerJob lifecycle (view)Portal + customCustom view—InteractiveD
POR-4Quote review & approvalCustomerQuotationPortal/SalesNative—InteractiveD
POR-5Invoices & receiptsCustomerPayment (view)PortalNative—InteractiveD
POR-6Profile, prefs, privacyCustomerConsent & dataPortalConfig—InteractiveD
Mobile app (concept) — mobile.html
MOB-1Home & notificationsCustomerRelationship— (app)FuturePush serviceInteractiveD
MOB-2Services & detailCustomerDiscovery— (app)Future—InteractiveD
MOB-3New request + photosCustomerLead captureCRM APIFuture—InteractiveD
MOB-4AppointmentsCustomerBookingAppointments APIFuture—InteractiveD
MOB-5Orders & tracking detailCustomerJob lifecycle (view)Portal APIFuture—InteractiveD
MOB-6Quote approval (replay)CustomerQuotationSales APIFuture—InteractiveD
MOB-7Invoice & payment infoCustomerPayment (view)Invoices APIFuture—InteractiveD
MOB-8Profile & preferencesCustomerConsent & dataPortal APIFuture—InteractiveD

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

Q1Deposits & partial paymentsRequire deposits for large jobs (bespoke)? Partial payment at intake vs. full payment at collection?
Q2German POS fiscalizationKassenSichV / DSFinVK apply to electronic POS: TSE (technical security device) and fiskaltrust or equivalent must be scoped — affects POS hardware & Odoo setup.
Q3SumUp payout reconciliationDaily manual match vs. automated import of payout reports into Odoo banking.
Q4Multiple terminalsOne Solo at the counter first; routing rules if a second terminal (workshop?) is added.
Q5Photo retentionHow long do intake photos stay on customer records (GDPR) — with the job, or archived after closing?
Q6Mobile app commitmentNative (iOS/Android) vs. PWA on the portal API — cost/complexity trade-off for Phase 3.
Q7Migration of existing recordsWhich 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.