Our marketplace methodology for Munich addresses B2B-specific technical requirements, German industrial standards, and the complex product data that defines industrial marketplace commerce. Marketplace model design (weeks 1-2): defining the B2B marketplace architecture. Key considerations: how does pricing work (fixed, volume-tiered, customer-specific, RFQ-based, auction), what is the procurement workflow (simple add-to-cart vs formal RFQ/quote/PO/receipt cycle), what integration is needed with buyer systems (punchout catalogs for SAP Ariba, OCI for SAP ERP, cXML for other procurement systems), and what seller systems need to connect (ERP integration for inventory and pricing, PIM for product data). Technical architecture: Next.js (buyer and seller front-ends with German-standard UX — clear, functional, information-dense), Node.js/TypeScript (API layer with B2B-specific logic — pricing engines, approval workflows, RFQ management), PostgreSQL (multi-tenant with B2B-grade data management — customer-specific pricing, contract terms, volume history), Elasticsearch (industrial product search — parametric search across technical specifications, cross-reference by manufacturer part number, DIN/ISO standard matching), and Redis (session management, real-time inventory, pricing cache). B2B payment infrastructure: European B2B payment is fundamentally different from consumer payment. Invoice payment: the default B2B payment method in Germany — buyers receive an invoice (Rechnung) with payment terms (typically 30 days net, 2% Skonto for payment within 10 days). The marketplace must handle: credit assessment (evaluating buyer creditworthiness before extending terms — integration with Creditreform or Schufa for German businesses), invoice generation (GoBD-compliant electronic invoices with proper Rechnungsnummer, USt-IdNr, and Leistungsdatum), payment tracking (monitoring outstanding invoices, sending reminders, escalating overdue payments), and payment matching (matching incoming SEPA payments to outstanding invoices). Alternative: Billie or Mondu (German B2B buy-now-pay-later — extending payment terms to buyers while the marketplace receives immediate payment). SEPA Direct Debit: for recurring B2B purchases. Credit card: available but less common in German B2B (typically only for small orders or international buyers). Product data management: industrial product data requires structured, specification-driven catalogs. Classification: eCl@ss (the German/EU standard for product classification — essential for B2B marketplace interoperability), ETIM (for electrical products), and UNSPSC. Product data: structured specifications per product category (dimensions, materials, performance characteristics, certifications, drawings/3D models, safety data sheets). Data quality: validation rules ensuring completeness and accuracy of technical data (mandatory fields per category, unit validation, range checking).