[{"data":1,"prerenderedAt":1507},["ShallowReactive",2],{"locale-routes":3,"page-\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist":178,"insights-author-\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist":1313},{"home":4,"privacy":7,"framework-focus":10,"framework":13,"framework-principles":16,"imprint":19,"contact":22,"shopware-agency-b2b":25,"shopware-agency-electronics":28,"shopware-agency-development":31,"shopware-agency":34,"shopware-agency-pricing":37,"shopware-agency-migration":40,"shopware-agency-seo":43,"shopware-agency-support":46,"location-hamburg":49,"location-munich":52,"about":55,"about-mission":58,"about-partners":61,"services-consulting":64,"services-development":67,"services":70,"services-optimization":73,"services-growth":76,"insights-ai-sales-channels-shopware":79,"insights-b2b-shop-starten-checkliste":82,"insights-ecommerce-deadlines-2026-27":85,"insights-e-invoice-b2b-shopware-xrechnung-zugferd":88,"insights-handelskoenig-b2b-quotes":91,"insights-shopware-5-eol":94,"insights-shopware-6-7-release":97,"insights-shopware-6-8-outlook":100,"insights-shopware-6-plans-pricing-2026":103,"insights-shopware-6-migration-noetig":106,"insights-shopware-gmv-2026":109,"insights-shopware-vs-shopify-2026":112,"insights-shopware-maintenance-retainer-development":115,"insights-withdrawal-button-shopware-6":118,"whitepaper-agentic-commerce-b2b-beschaffung":121,"whitepaper-compliance-2026-27":123,"whitepapers":126,"whitepaper-kanalverbund-marktplatz-shop-agentic":129,"whitepaper-shopware-6-boutique-vs-grossagentur-tco":131,"case-comspot-focus":133,"case-framily-focus":136,"case-handelskoenig-focus":139,"case-lupa-focus":142,"case-shifter-focus":145,"case-topi-focus":148,"case-xucker-focus":151,"talks-beyond-seo-scuc-2026":154,"talks":157,"talks-shopware-container-hosting-hitc-2026":160,"talks-symfony-cli-docker-scuc-2025":163,"webinars":166,"team-alex-jank":169,"team-benedikt-rillox":172,"team":175},{"de":5,"en":6},"\u002F","\u002Fen",{"de":8,"en":9},"\u002Fdatenschutz","\u002Fen\u002Fprivacy",{"de":11,"en":12},"\u002Fframework\u002Ffocus","\u002Fen\u002Fframework\u002Ffocus",{"de":14,"en":15},"\u002Fframework","\u002Fen\u002Fframework",{"de":17,"en":18},"\u002Fframework\u002Fprinzipien","\u002Fen\u002Fframework\u002Fprinciples",{"de":20,"en":21},"\u002Fimpressum","\u002Fen\u002Fimprint",{"de":23,"en":24},"\u002Fkontakt","\u002Fen\u002Fcontact",{"de":26,"en":27},"\u002Fshopware-agentur\u002Fb2b","\u002Fen\u002Fshopware-agency\u002Fb2b",{"de":29,"en":30},"\u002Fshopware-agentur\u002Felektronikhandel","\u002Fen\u002Fshopware-agency\u002Felectronics-retail",{"de":32,"en":33},"\u002Fshopware-agentur\u002Fentwicklung","\u002Fen\u002Fshopware-agency\u002Fdevelopment",{"de":35,"en":36},"\u002Fshopware-agentur","\u002Fen\u002Fshopware-agency",{"de":38,"en":39},"\u002Fshopware-agentur\u002Fkosten","\u002Fen\u002Fshopware-agency\u002Fpricing",{"de":41,"en":42},"\u002Fshopware-agentur\u002Fmigration","\u002Fen\u002Fshopware-agency\u002Fmigration",{"de":44,"en":45},"\u002Fshopware-agentur\u002Fseo","\u002Fen\u002Fshopware-agency\u002Fseo",{"de":47,"en":48},"\u002Fshopware-agentur\u002Fsupport","\u002Fen\u002Fshopware-agency\u002Fsupport",{"de":50,"en":51},"\u002Fstandorte\u002Fhamburg","\u002Fen\u002Flocations\u002Fhamburg",{"de":53,"en":54},"\u002Fstandorte\u002Fmuenchen","\u002Fen\u002Flocations\u002Fmunich",{"de":56,"en":57},"\u002Fueber-uns","\u002Fen\u002Fabout",{"de":59,"en":60},"\u002Fueber-uns\u002Fmission","\u002Fen\u002Fabout\u002Fmission",{"de":62,"en":63},"\u002Fueber-uns\u002Fpartner","\u002Fen\u002Fabout\u002Fpartners",{"de":65,"en":66},"\u002Fleistungen\u002Fberatung","\u002Fen\u002Fservices\u002Fconsulting",{"de":68,"en":69},"\u002Fleistungen\u002Fentwicklung","\u002Fen\u002Fservices\u002Fdevelopment",{"de":71,"en":72},"\u002Fleistungen","\u002Fen\u002Fservices",{"de":74,"en":75},"\u002Fleistungen\u002Foptimierung","\u002Fen\u002Fservices\u002Foptimization",{"de":77,"en":78},"\u002Fleistungen\u002Fwachstum","\u002Fen\u002Fservices\u002Fgrowth",{"de":80,"en":81},"\u002Finsights\u002Fai-verkaufskanaele-shopware","\u002Fen\u002Finsights\u002Fai-sales-channels-shopware",{"de":83,"en":84},"\u002Finsights\u002Fb2b-shop-starten-checkliste-shopware","\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist",{"de":86,"en":87},"\u002Finsights\u002Fe-commerce-fristen-2026-27","\u002Fen\u002Finsights\u002Fe-commerce-deadlines-2026-27",{"de":89,"en":90},"\u002Finsights\u002Fe-rechnung-b2b-shopware-xrechnung-zugferd","\u002Fen\u002Finsights\u002Fe-invoice-b2b-shopware-xrechnung-zugferd",{"de":92,"en":93},"\u002Finsights\u002Fhandelskoenig-b2b-angebotsanfragen","\u002Fen\u002Finsights\u002Fhandelskoenig-b2b-quote-requests",{"de":95,"en":96},"\u002Finsights\u002Fshopware-5-eol","\u002Fen\u002Finsights\u002Fshopware-5-end-of-life",{"de":98,"en":99},"\u002Finsights\u002Fshopware-6-7-release-update-vorteile","\u002Fen\u002Finsights\u002Fshopware-6-7-release-update-benefits",{"de":101,"en":102},"\u002Finsights\u002Fshopware-6-8-ausblick-roadmap-vorbereitung","\u002Fen\u002Finsights\u002Fshopware-6-8-outlook-roadmap-preparation",{"de":104,"en":105},"\u002Finsights\u002Fshopware-6-lizenzen-kosten-2026","\u002Fen\u002Finsights\u002Fshopware-6-plans-pricing-2026",{"de":107,"en":108},"\u002Finsights\u002Fshopware-6-migration-noetig","\u002Fen\u002Finsights\u002Fshopware-6-migration-necessary",{"de":110,"en":111},"\u002Finsights\u002Fshopware-gmv-berechnung-1-million-grenze","\u002Fen\u002Finsights\u002Fshopware-gmv-calculation-one-million-threshold",{"de":113,"en":114},"\u002Finsights\u002Fshopware-vs-shopify-vergleich-2026","\u002Fen\u002Finsights\u002Fshopware-vs-shopify-comparison-2026",{"de":116,"en":117},"\u002Finsights\u002Fshopware-wartung-retainer-weiterentwicklung","\u002Fen\u002Finsights\u002Fshopware-maintenance-retainer-development",{"de":119,"en":120},"\u002Finsights\u002Fwiderrufsbutton-shopware-6","\u002Fen\u002Finsights\u002Fwithdrawal-button-shopware-6",{"de":122},"\u002Fwhitepapers\u002Fagentic-commerce-b2b-beschaffung",{"de":124,"en":125},"\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27","\u002Fen\u002Fwhitepapers\u002Fe-commerce-compliance-2026-27",{"de":127,"en":128},"\u002Fwhitepapers","\u002Fen\u002Fwhitepapers",{"de":130},"\u002Fwhitepapers\u002Fkanalverbund-marktplatz-shop-agentic",{"de":132},"\u002Fwhitepapers\u002Fshopware-6-boutique-vs-grossagentur-tco",{"de":134,"en":135},"\u002Fcase-studies\u002Fcomspot-focus","\u002Fen\u002Fcase-studies\u002Fcomspot-focus",{"de":137,"en":138},"\u002Fcase-studies\u002Fframily-focus","\u002Fen\u002Fcase-studies\u002Fframily-focus",{"de":140,"en":141},"\u002Fcase-studies\u002Fhandelskoenig-focus","\u002Fen\u002Fcase-studies\u002Fhandelskoenig-focus",{"de":143,"en":144},"\u002Fcase-studies\u002Flupa-focus","\u002Fen\u002Fcase-studies\u002Flupa-focus",{"de":146,"en":147},"\u002Fcase-studies\u002Fshifter-focus","\u002Fen\u002Fcase-studies\u002Fshifter-focus",{"de":149,"en":150},"\u002Fcase-studies\u002Ftopi-focus","\u002Fen\u002Fcase-studies\u002Ftopi-focus",{"de":152,"en":153},"\u002Fcase-studies\u002Fxucker-focus","\u002Fen\u002Fcase-studies\u002Fxucker-focus",{"de":155,"en":156},"\u002Fvortraege\u002Fbeyond-seo-scuc-2026","\u002Fen\u002Ftalks\u002Fbeyond-seo-scuc-2026",{"de":158,"en":159},"\u002Fvortraege","\u002Fen\u002Ftalks",{"de":161,"en":162},"\u002Fvortraege\u002Fshopware-container-hosting-hitc-2026","\u002Fen\u002Ftalks\u002Fshopware-container-hosting-hitc-2026",{"de":164,"en":165},"\u002Fvortraege\u002Fsymfony-cli-docker-scuc-2025","\u002Fen\u002Ftalks\u002Fsymfony-cli-docker-scuc-2025",{"de":167,"en":168},"\u002Fwebinare","\u002Fen\u002Fwebinars",{"de":170,"en":171},"\u002Fteam\u002Falex-jank","\u002Fen\u002Fteam\u002Falex-jank",{"de":173,"en":174},"\u002Fteam\u002Fbenedikt-rillox","\u002Fen\u002Fteam\u002Fbenedikt-rillox",{"de":176,"en":177},"\u002Fteam","\u002Fen\u002Fteam",{"id":179,"title":180,"author":181,"body":182,"citations":1286,"description":1291,"draft":1292,"extension":1293,"image":1294,"meta":1297,"navigation":1298,"ogImage":1299,"path":84,"publishedAt":1300,"readingTime":1301,"robots":1299,"schemaOrg":1299,"seo":1302,"sitemap":1305,"stem":1306,"tags":1307,"translationKey":1311,"updatedAt":1299,"__hash__":1312},"insights_en\u002Fen\u002Finsights\u002Fstart-b2b-store-shopware-checklist.md","Starting a new B2B store: Where to begin? A Shopware checklist","benedikt-rillox",{"type":183,"value":184,"toc":1237},"minimark",[185,189,192,195,203,206,211,214,217,251,254,258,261,264,287,290,294,297,302,305,309,312,316,319,323,326,330,333,340,344,347,370,373,377,380,409,412,416,419,442,445,449,452,455,459,462,488,491,495,498,502,505,508,531,534,537,541,544,547,573,576,580,583,683,686,690,693,719,722,726,729,732,752,755,759,762,765,788,799,808,812,815,818,844,847,851,858,861,885,888,892,895,898,915,918,921,925,928,954,957,961,964,990,993,997,1000,1003,1023,1026,1030,1033,1037,1057,1061,1081,1085,1105,1108,1112,1120,1123,1143,1150,1154,1157,1161,1164,1168,1171,1175,1178,1182,1185,1189,1192,1196,1199,1202,1205,1209],[186,187,188],"p",{},"A new B2B store does not start with design or a specification document. It\nstarts with a clear business goal, real customer processes, and an early\nShopware foundation on which data, prices, and the ERP integration are tested\nwith real examples. The ambitious vision then becomes a manageable MVP with\npilot customers instead of a big-bang go-live.",[186,190,191],{},"Because a new B2B store is expected to personalize prices, automate orders,\nrelieve sales teams, and integrate seamlessly with ERP, PIM, and CRM systems.\nThe first workshop therefore tends to produce a long list: customer groups, approvals,\nbudgets, quotes, quick orders, shipping addresses, payment terms,\ncustomer-specific assortments, and much more.",[186,193,194],{},"This is precisely where many projects stall. Where should a team begin when\nalmost every process appears important and many dependencies are still unknown?",[186,196,197,198,202],{},"The most important recommendation is: ",[199,200,201],"strong",{},"Start working with the commerce\nplatform early instead of waiting until every requirement has been documented\nin full."," This does not mean launching an unfinished store. It means creating\na robust Shopware foundation as early as possible so that processes, data, and\nintegrations can be tested with real examples.",[186,204,205],{},"This article explains how to structure a B2B commerce project, which decisions\nshould be made first, how customer self-service reduces repetitive sales work,\nand how to turn an ambitious vision into a manageable MVP.",[207,208,210],"h2",{"id":209},"why-b2b-projects-start-differently-from-conventional-online-stores","Why B2B projects start differently from conventional online stores",[186,212,213],{},"A B2C store can often begin with one assortment, one price list, and a\nrelatively straightforward checkout. In B2B commerce, the storefront is merely\nthe visible part of a larger sales and procurement system.",[186,215,216],{},"A business customer may expect:",[218,219,220,224,227,230,233,236,239,242,245,248],"ul",{},[221,222,223],"li",{},"individual prices, discounts, or volume tiers,",[221,225,226],{},"an approved assortment rather than the complete catalog,",[221,228,229],{},"several employee accounts within one company,",[221,231,232],{},"roles, budgets, and order approvals,",[221,234,235],{},"different billing and delivery addresses for each organizational unit,",[221,237,238],{},"orders by product number, CSV, or shopping list,",[221,240,241],{},"quote requests and personal price negotiations,",[221,243,244],{},"individual payment and delivery terms,",[221,246,247],{},"access to ERP documents, orders, delivery notes, or invoices,",[221,249,250],{},"repeat ordering with as few steps as possible.",[186,252,253],{},"The store consequently becomes part of the existing organization. Sales,\ncustomer service, purchasing, IT, accounting, logistics, and product management\nare all affected. If the initiative is treated as a web design project, many\ncritical questions emerge only shortly before launch.",[207,255,257],{"id":256},"the-most-common-false-start-specify-everything-first-install-shopware-later","The most common false start: Specify everything first, install Shopware later",[186,259,260],{},"A detailed requirements document creates a sense of certainty. It can only\ndescribe what the project team understands at that moment, however. Many\nassumptions become tangible only when real customers, products, prices, and\norders are visible in a working platform.",[186,262,263],{},"Typical late discoveries include:",[218,265,266,269,272,275,278,281,284],{},[221,267,268],{},"Product numbers and variants are structured differently in the ERP than\nexpected.",[221,270,271],{},"A supposedly simple price list actually consists of numerous exceptions.",[221,273,274],{},"Customer number, debtor account, and delivery address cannot be mapped\nunambiguously.",[221,276,277],{},"Approval processes differ between customers or branches.",[221,279,280],{},"Product data exists but is unsuitable for digital search.",[221,282,283],{},"The ERP can provide data but cannot reliably accept certain changes.",[221,285,286],{},"A process works internally but is too complicated for buyers in the store.",[186,288,289],{},"When the platform is introduced only after months of specification, these\ninsights become expensive. The data model, integrations, and concepts that have\nalready been approved then need to change together.",[207,291,293],{"id":292},"why-the-platform-should-be-available-as-early-as-possible","Why the platform should be available as early as possible",[186,295,296],{},"An early project store turns assumptions into testable behavior. Even a secured\ndevelopment system with a handful of sample customers and products creates more\ninsight than numerous abstract process diagrams.",[298,299,301],"h3",{"id":300},"requirements-become-tangible","Requirements become tangible",[186,303,304],{},"A sales representative can use a real example to demonstrate why customer A\nneeds different prices and customer B requires an approval workflow. Business\nterminology becomes visible fields, rules, and status values.",[298,306,308],{"id":307},"data-problems-become-visible-early","Data problems become visible early",[186,310,311],{},"An initial import of 50 representative products quickly reveals whether media,\nunits, variants, volume prices, accessories, and search terms are sufficient.\nThe complete catalog does not need to have been migrated yet.",[298,313,315],{"id":314},"integrations-can-be-tested-vertically","Integrations can be tested vertically",[186,317,318],{},"Rather than developing every API in full, the team implements one end-to-end\nbusiness case: synchronize a customer, display a product, determine a price,\nplace an order, and return the order status. This vertical slice exposes\ntechnical and organizational gaps early.",[298,320,322],{"id":321},"departments-decide-based-on-the-same-system","Departments decide based on the same system",[186,324,325],{},"Sales, IT, and logistics no longer discuss three different interpretations of\nthe same process. They evaluate one shared, working implementation.",[298,327,329],{"id":328},"training-and-change-begin-before-launch","Training and change begin before launch",[186,331,332],{},"Key users can learn the new way of working early, provide feedback, and later\nsupport colleagues or pilot customers. Adoption does not begin with the launch\nemail.",[186,334,335,336,339],{},"The distinction matters: ",[199,337,338],{},"Starting with the platform early means learning\nearly, not building everything early."," Architecture decisions need careful\nconsideration, while functionality should be delivered according to value and\nrisk.",[207,341,343],{"id":342},"self-service-relieves-sales-teams-when-it-is-designed-end-to-end","Self-service relieves sales teams when it is designed end to end",[186,345,346],{},"One of the strongest arguments for a B2B store is not additional revenue alone.\nIt is a better distribution of work. In many companies, sales representatives\nspend a substantial share of their time on repetitive administrative tasks:",[218,348,349,352,355,358,361,364,367],{},[221,350,351],{},"entering orders from emails or PDF documents into the ERP,",[221,353,354],{},"looking up product numbers and availability,",[221,356,357],{},"confirming customer-specific prices,",[221,359,360],{},"responding to order status and delivery date requests,",[221,362,363],{},"resending invoices, delivery notes, or data sheets,",[221,365,366],{},"reconstructing previous baskets for repeat orders,",[221,368,369],{},"maintaining new contacts or delivery addresses manually.",[186,371,372],{},"These tasks are necessary, but they rarely generate the greatest sales value.\nA well-integrated B2B store makes them independently available to customers\naround the clock.",[298,374,376],{"id":375},"what-customers-should-be-able-to-do-in-self-service","What customers should be able to do in self-service",[186,378,379],{},"Effective self-service does not stop at the basket. Depending on their\npermissions, business customers should be able to:",[218,381,382,385,388,391,394,397,400,403,406],{},[221,383,384],{},"view their approved assortment and conditions,",[221,386,387],{},"check availability, lead times, and packaging units,",[221,389,390],{},"order via search, product number, CSV, or shopping list,",[221,392,393],{},"request quotes and follow their status,",[221,395,396],{},"manage employees, roles, and approvals,",[221,398,399],{},"select delivery addresses and purchase references,",[221,401,402],{},"repeat previous orders,",[221,404,405],{},"retrieve order status and shipping information,",[221,407,408],{},"download invoices, delivery notes, and product documents.",[186,410,411],{},"The benefit depends on reliable and understandable information. A portal with\noutdated stock, unclear prices, or missing documents creates more questions and\nadds to the sales team's workload instead of reducing it.",[298,413,415],{"id":414},"how-the-role-of-sales-representatives-changes","How the role of sales representatives changes",[186,417,418],{},"Self-service does not replace personal sales. It shifts work from order entry\nto customer development. Sales representatives gain more time for:",[218,420,421,424,427,430,433,436,439],{},[221,422,423],{},"advising customers on complex products and applications,",[221,425,426],{},"individual offers and negotiations,",[221,428,429],{},"developing existing accounts and cross-selling,",[221,431,432],{},"reactivating inactive customers,",[221,434,435],{},"acquiring new business,",[221,437,438],{},"analyzing demand, assortment, and buying behavior,",[221,440,441],{},"personal escalation when the digital route is insufficient.",[186,443,444],{},"The store becomes a digital colleague for the sales team. Standard cases run\nautomatically, while exceptions are deliberately transferred to a person. This\nhandover must be visible: customers should always understand when they can\ncontinue on their own and how to reach their established contact for a complex\nquestion.",[298,446,448],{"id":447},"involve-sales-from-the-beginning","Involve sales from the beginning",[186,450,451],{},"When a store is introduced as a pure IT initiative, it may be perceived\ninternally as competition or a control mechanism. Selected sales\nrepresentatives should therefore help choose sample data, pilot customers, and\nself-service workflows.",[186,453,454],{},"Their experience shows which exceptions are genuinely business-critical. In\nreturn, the objective must be explicit: the digital channel removes repetitive\nwork and supplies better information for personal account management.\nCommission, targets, and account ownership must not put digital orders in\nconflict with the sales representative responsible for the customer.",[298,456,458],{"id":457},"how-to-measure-the-actual-relief","How to measure the actual relief",[186,460,461],{},"Useful metrics before and after the pilot include:",[218,463,464,467,470,473,476,479,482,485],{},[221,465,466],{},"share of orders reaching the ERP without manual entry,",[221,468,469],{},"internal processing minutes per standard order,",[221,471,472],{},"number of status, price, and document requests per 100 orders,",[221,474,475],{},"share of successful repeat orders in self-service,",[221,477,478],{},"active customer accounts and employee accounts,",[221,480,481],{},"abandonment rates in search, basket, and approval workflows,",[221,483,484],{},"time from quote request to submitted offer,",[221,486,487],{},"share of sales time spent on advice rather than administration.",[186,489,490],{},"These KPIs belong in the initial objectives. They demonstrate whether the B2B\nstore genuinely releases capacity or merely creates another channel that sales\nmust maintain in parallel.",[207,492,494],{"id":493},"the-b2b-store-checklist-in-which-order-should-you-begin","The B2B store checklist: In which order should you begin?",[186,496,497],{},"The following sequence works well because it clarifies business objectives\nand processes first (steps 1–4: business goal, customer observation, system\nlandscape, data sample), creates a technical learning environment next (steps\n5–9: early Shopware platform, customer organization, pricing logic, MVP,\nintegrations), and expands functional scope and rollout only after that\n(steps 10–12: UX, security and operations, pilot customers).",[207,499,501],{"id":500},"_1-define-the-business-goal-and-decision-ownership","1. Define the business goal and decision ownership",[186,503,504],{},"\"We need a B2B store\" is not yet a measurable objective. The first problem to\nbe solved needs to be explicit.",[186,506,507],{},"Possible objectives include:",[218,509,510,513,516,519,522,525,528],{},[221,511,512],{},"move standard orders from inside sales to self-service,",[221,514,515],{},"reduce errors from email, phone, and spreadsheet orders,",[221,517,518],{},"allow existing customers to order at any time,",[221,520,521],{},"connect new markets or dealers digitally,",[221,523,524],{},"accelerate quoting processes,",[221,526,527],{},"support sales with a digital sales channel,",[221,529,530],{},"generate insights into demand and repeat purchasing.",[186,532,533],{},"Each goal needs a baseline, target value, and date. Examples include digital\norder share, processing time per order, error rate, repeat order rate, and\nactive business customers.",[186,535,536],{},"The project also needs a person with genuine decision authority. Without a\nproduct owner, conflicts between sales, IT, and operations are merely deferred.",[207,538,540],{"id":539},"_2-observe-customers-and-core-processes","2. Observe customers and core processes",[186,542,543],{},"The best requirements do not originate solely in internal meetings. Interview\nfive to ten representative customers and observe how they actually place\norders today.",[186,545,546],{},"Questions include:",[218,548,549,552,555,558,561,564,567,570],{},[221,550,551],{},"Who searches for products and who submits the order?",[221,553,554],{},"Who needs to approve it?",[221,556,557],{},"Do users search by product number, name, or technical attribute?",[221,559,560],{},"Which information is regularly missing?",[221,562,563],{},"Which orders repeat?",[221,565,566],{},"When is a quote required instead of a direct purchase?",[221,568,569],{},"Which documents and status information are needed after ordering?",[221,571,572],{},"Why do customers currently resort to phone or email?",[186,574,575],{},"Not every exception belongs in the first release. The interviews identify the\ntwo or three workflows that create the greatest value.",[207,577,579],{"id":578},"_3-document-systems-and-data-ownership","3. Document systems and data ownership",[186,581,582],{},"Before designing integrations, clarify which system owns each piece of\ninformation. A simple matrix prevents ambiguity later.",[584,585,586,602],"table",{},[587,588,589],"thead",{},[590,591,592,596,599],"tr",{},[593,594,595],"th",{},"Information",[593,597,598],{},"Typical source",[593,600,601],{},"Question to resolve",[603,604,605,617,628,639,650,661,672],"tbody",{},[590,606,607,611,614],{},[608,609,610],"td",{},"Customers and debtor accounts",[608,612,613],{},"ERP or CRM",[608,615,616],{},"Who may change master data?",[590,618,619,622,625],{},[608,620,621],{},"Products and variants",[608,623,624],{},"ERP or PIM",[608,626,627],{},"Where are sellable copy and media created?",[590,629,630,633,636],{},[608,631,632],{},"Prices and terms",[608,634,635],{},"ERP or pricing engine",[608,637,638],{},"Real-time lookup or synchronization?",[590,640,641,644,647],{},[608,642,643],{},"Stock and lead times",[608,645,646],{},"ERP, WMS, or OMS",[608,648,649],{},"How current must the display be?",[590,651,652,655,658],{},[608,653,654],{},"Orders",[608,656,657],{},"Shopware and ERP",[608,659,660],{},"At which status does the ERP become authoritative?",[590,662,663,666,669],{},[608,664,665],{},"Invoices and documents",[608,667,668],{},"ERP or DMS",[608,670,671],{},"Are files copied or merely made accessible?",[590,673,674,677,680],{},[608,675,676],{},"Users and roles",[608,678,679],{},"Shopware, CRM, or IAM",[608,681,682],{},"Who manages joiners and leavers?",[186,684,685],{},"Every field needs a business owner, technical source, and rule for failure\ncases. \"It comes from the ERP\" is not a solution without an accountable process\nand specific interface.",[207,687,689],{"id":688},"_4-build-a-realistic-data-sample","4. Build a realistic data sample",[186,691,692],{},"The first project store should not contain only three particularly simple demo\nproducts. Use a small but representative selection:",[218,694,695,698,701,704,707,710,713,716],{},[221,696,697],{},"simple products and variants,",[221,699,700],{},"small and very large assortments,",[221,702,703],{},"different units and packaging sizes,",[221,705,706],{},"volume prices and customer-specific conditions,",[221,708,709],{},"products with documents or complex attributes,",[221,711,712],{},"spare parts, accessories, or alternatives,",[221,714,715],{},"one active and one blocked customer,",[221,717,718],{},"companies with one buyer and with several buyers.",[186,720,721],{},"This sample becomes the shared test set for the data model, search, prices,\npermissions, and integrations.",[207,723,725],{"id":724},"_5-establish-shopware-as-the-project-platform-early","5. Establish Shopware as the project platform early",[186,727,728],{},"Create a permanently available development or integration store with version\ncontrol, a deployment process, separated environments, access protection, and\ntraceable configuration.",[186,730,731],{},"The first stage does not require the final design. It should:",[218,733,734,737,740,743,746,749],{},[221,735,736],{},"contain the representative data sample,",[221,738,739],{},"model at least two different business customers,",[221,741,742],{},"support one complete ordering process,",[221,744,745],{},"exchange initial data with one authoritative system,",[221,747,748],{},"be regularly testable by key users,",[221,750,751],{},"move changes reproducibly between environments.",[186,753,754],{},"Shopware then becomes the project's integration and learning point early. A\ndeveloper's local demo store without real data, automated deployments, or\ndepartment access does not fulfil this purpose.",[207,756,758],{"id":757},"_6-model-customer-organizations-roles-and-approvals","6. Model customer organizations, roles, and approvals",[186,760,761],{},"A B2B customer is not the same as a user account. One company can have several\nbuyers, cost centers, branches, and approval levels.",[186,763,764],{},"The target model should answer:",[218,766,767,770,773,776,779,782,785],{},[221,768,769],{},"What represents the company and what is an organizational unit?",[221,771,772],{},"Which users may invite employees or assign roles?",[221,774,775],{},"Who can see which prices, assortments, and orders?",[221,777,778],{},"Above which amount is approval required?",[221,780,781],{},"Do budgets apply to people, roles, departments, or periods?",[221,783,784],{},"Which delivery addresses and payment methods are permitted?",[221,786,787],{},"How are former employees reliably deactivated?",[186,789,790,791,798],{},"Shopware's\n",[792,793,797],"a",{"href":794,"rel":795},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fcommercial-features\u002Fb2b-components",[796],"nofollow","B2B Components","\ninclude employee management, roles, approval processes, organizational units,\nand budgets. According to Shopware, they are available with the Evolve plan and\nabove. New projects should compare them with custom development and Store\nextensions.",[186,800,801,802,807],{},"Another point matters for new implementations: Shopware states ",[792,803,806],{"href":804,"rel":805},"https:\u002F\u002Fdocs.shopware.com\u002Fen\u002Fshopware-6-en\u002Fextensions\u002Fb2b-suite-administration",[796],"in its\ndocumentation","\nthat the older B2B Suite will no longer be supported from Shopware 6.8. A new store in 2026\nshould not begin on a B2B architecture that is being phased out.",[207,809,811],{"id":810},"_7-untangle-pricing-and-assortment-logic","7. Untangle pricing and assortment logic",[186,813,814],{},"Pricing is often the most complex part of a B2B project. The question is not\nonly which price appears, but when, for whom, and from which source.",[186,816,817],{},"Document:",[218,819,820,823,826,829,832,835,838,841],{},[221,821,822],{},"base, customer, group, and promotional prices,",[221,824,825],{},"quantity tiers and packaging units,",[221,827,828],{},"discount hierarchy and priorities,",[221,830,831],{},"contract periods and currencies,",[221,833,834],{},"net display and tax rules,",[221,836,837],{},"price calculation for quotes and repeat orders,",[221,839,840],{},"behavior when the ERP is unavailable,",[221,842,843],{},"permitted and blocked assortments for each customer.",[186,845,846],{},"A live ERP lookup sounds simple but can impair search, product listings, and\nperformance. Synchronization is faster but requires clear update and error\nrules. Test the choice with a prototype using real conditions.",[207,848,850],{"id":849},"_8-define-the-mvp-as-a-complete-value-path","8. Define the MVP as a complete value path",[186,852,853,854,857],{},"An MVP is not a collection of half-finished features. It is the smallest\n",[199,855,856],{},"complete"," workflow that creates measurable value for a clearly defined\ncustomer group.",[186,859,860],{},"A useful first B2B MVP might work as follows:",[862,863,864,867,870,873,876,879,882],"ol",{},[221,865,866],{},"A pilot customer signs in.",[221,868,869],{},"They see their approved assortment and prices.",[221,871,872],{},"They find products via search, product number, or quick order.",[221,874,875],{},"They order with established delivery and payment terms.",[221,877,878],{},"The order is reliably transferred to the ERP.",[221,880,881],{},"Status and order history are visible in the account.",[221,883,884],{},"Inside sales and support can trace the transaction.",[186,886,887],{},"A complex configurator, international tenants, marketing automation, and every\nconceivable approval rule can be valuable. They do not necessarily belong in\nthe first value path.",[207,889,891],{"id":890},"_9-prioritize-integrations-by-business-risk","9. Prioritize integrations by business risk",[186,893,894],{},"Integrations should not be sequenced by technical convenience alone. The key\nquestion is which failure would have the greatest operational impact.",[186,896,897],{},"The following flows usually have high priority:",[862,899,900,903,906,909,912],{},[221,901,902],{},"customer and authorization,",[221,904,905],{},"product and sales unit,",[221,907,908],{},"price and availability,",[221,910,911],{},"order transfer to the ERP,",[221,913,914],{},"return of status and documents.",[186,916,917],{},"Monitoring, retries, error storage, and a manual fallback process are part of\nthe definition of done for every integration. A successful API response in a\ndeveloper test is not yet a robust production process.",[186,919,920],{},"Shopware follows an API-first approach and can integrate ERP, CRM, PIM, and\nother systems. Technical openness does not replace decisions about data\nownership, synchronization direction, and failure behavior.",[207,922,924],{"id":923},"_10-design-ux-for-repetition-and-efficiency","10. Design UX for repetition and efficiency",[186,926,927],{},"B2B buyers often want to finish quickly rather than be inspired. The interface\nshould support how they work:",[218,929,930,933,936,939,942,945,948,951],{},[221,931,932],{},"search by product number and technical attributes,",[221,934,935],{},"quick ordering and CSV upload,",[221,937,938],{},"shopping lists and favorites,",[221,940,941],{},"repeat ordering from history,",[221,943,944],{},"clear availability and delivery information,",[221,946,947],{},"saved addresses and purchase references,",[221,949,950],{},"transparent approval and quote status,",[221,952,953],{},"mobile approvals for decision-makers.",[186,955,956],{},"This does not exclude strong content and branding. In a B2B store, design must\nfirst create orientation, confidence, and speed.",[207,958,960],{"id":959},"_11-plan-security-legal-and-operations-early","11. Plan security, legal, and operations early",[186,962,963],{},"Before the pilot, assign responsibility for data protection, taxes, contracts,\naccessibility, information security, and operations. Pay particular attention\nto:",[218,965,966,969,972,975,978,981,984,987],{},[221,967,968],{},"registration and validation of new business customers,",[221,970,971],{},"role and permission changes,",[221,973,974],{},"protection of customer-specific prices and documents,",[221,976,977],{},"audit trails for critical actions,",[221,979,980],{},"test and personal data in non-production systems,",[221,982,983],{},"backups, recovery, and update processes,",[221,985,986],{},"monitoring of store, queues, search, and integrations,",[221,988,989],{},"support and escalation outside office hours.",[186,991,992],{},"Reviewing these topics only shortly before launch puts both the timeline and\narchitecture at risk.",[207,994,996],{"id":995},"_12-begin-with-pilot-customers-and-scale-deliberately","12. Begin with pilot customers and scale deliberately",[186,998,999],{},"The first rollout should involve a small, deliberately selected customer\ngroup. Suitable partners order regularly, have representative requirements,\nand provide constructive feedback.",[186,1001,1002],{},"The pilot needs:",[218,1004,1005,1008,1011,1014,1017,1020],{},[221,1006,1007],{},"a clear period and accountable contact,",[221,1009,1010],{},"personal onboarding rather than only a mass email,",[221,1012,1013],{},"defined feedback channels,",[221,1015,1016],{},"measurement of usage, abandonment, and support requests,",[221,1018,1019],{},"daily monitoring of integrations and orders,",[221,1021,1022],{},"a safe fallback for critical purchases.",[186,1024,1025],{},"Only after the complete process is stable should additional customer groups,\ncountries, or capabilities be enabled.",[207,1027,1029],{"id":1028},"a-306090-day-roadmap-for-the-project-start","A 30\u002F60\u002F90-day roadmap for the project start",[186,1031,1032],{},"The first 90 days split into three phases: days 1 to 30 for understanding and\nfocus, days 31 to 60 for the platform and a vertical slice, and days 61 to 90\nfor hardening the MVP. After 90 days, the complete store does not need to be\nlive — but one real business process should work on the target platform and\nbe ready for a reliable assessment.",[298,1034,1036],{"id":1035},"days-1-to-30-understand-and-focus","Days 1 to 30: Understand and focus",[218,1038,1039,1042,1045,1048,1051,1054],{},[221,1040,1041],{},"define vision, product owner, and metrics,",[221,1043,1044],{},"conduct customer interviews and process observation,",[221,1046,1047],{},"record systems, data sources, and owners,",[221,1049,1050],{},"select representative customers and products,",[221,1052,1053],{},"prepare platform, plan, and operating decisions,",[221,1055,1056],{},"describe the prioritized end-to-end process.",[298,1058,1060],{"id":1059},"days-31-to-60-platform-and-vertical-slice","Days 31 to 60: Platform and vertical slice",[218,1062,1063,1066,1069,1072,1075,1078],{},[221,1064,1065],{},"establish Shopware development and test environments,",[221,1067,1068],{},"implement deployment, access, and baseline configuration,",[221,1070,1071],{},"import the data sample,",[221,1073,1074],{},"model the first customer with pricing and assortment rules,",[221,1076,1077],{},"integrate the core process end to end with the ERP,",[221,1079,1080],{},"let departments regularly test the working implementation.",[298,1082,1084],{"id":1083},"days-61-to-90-secure-the-mvp","Days 61 to 90: Secure the MVP",[218,1086,1087,1090,1093,1096,1099,1102],{},[221,1088,1089],{},"add roles, failure cases, and operating procedures,",[221,1091,1092],{},"optimize search, quick order, and customer account,",[221,1094,1095],{},"monitor data quality and integrations,",[221,1097,1098],{},"review security, privacy, and legal requirements,",[221,1100,1101],{},"train key users and prepare support,",[221,1103,1104],{},"onboard pilot customers and measure rollout criteria.",[186,1106,1107],{},"The actual timeline depends on system landscape and complexity — the order\nmatters more than the calendar.",[207,1109,1111],{"id":1110},"which-shopware-setup-fits-a-new-b2b-store","Which Shopware setup fits a new B2B store?",[186,1113,1114,1115,1119],{},"Shopware Community Edition and Rise can support simpler closed dealer areas or\nindividually developed B2B processes. Shopware's standard B2B Components are,\naccording to the ",[792,1116,1118],{"href":794,"rel":1117},[796],"current\ndocumentation",",\nincluded with Evolve and Beyond.",[186,1121,1122],{},"The decision should not be based on license price alone. Compare:",[218,1124,1125,1128,1131,1134,1137,1140],{},[221,1126,1127],{},"required standard functionality,",[221,1129,1130],{},"plugin and custom development costs,",[221,1132,1133],{},"manufacturer and agency support,",[221,1135,1136],{},"availability and response-time requirements,",[221,1138,1139],{},"expected GMV,",[221,1141,1142],{},"long-term update and maintenance effort.",[186,1144,1145,1146,1149],{},"Our guide to\n",[792,1147,1148],{"href":105},"Shopware 6 plans and pricing","\ncompares Community Edition, Rise, Evolve, and Beyond in detail.",[207,1151,1153],{"id":1152},"common-mistakes-this-checklist-prevents","Common mistakes this checklist prevents",[186,1155,1156],{},"Five mistakes recur in B2B projects: the offline process merely rebuilt\ndigitally, every edge case crammed into release one, an ERP that dictates the\nentire customer experience, a platform set up too late, and a go-live\nmistaken for project success. The checklist addresses each of them.",[298,1158,1160],{"id":1159},"simply-digitizing-the-existing-offline-process","Simply digitizing the existing offline process",[186,1162,1163],{},"A poor email or spreadsheet workflow does not become effective merely because\nit gets a web interface. Ask whether each step is necessary or exists only for\nhistorical reasons.",[298,1165,1167],{"id":1166},"putting-every-exception-into-release-one","Putting every exception into release one",[186,1169,1170],{},"Rare exceptions add complexity and delay learning. They need a documented\nfallback, but not always immediate automation.",[298,1172,1174],{"id":1173},"letting-the-erp-determine-the-entire-customer-experience","Letting the ERP determine the entire customer experience",[186,1176,1177],{},"The ERP is often authoritative for commercial data but not for navigation,\nsearch, or clear user feedback. Responsibilities should be separated\ndeliberately.",[298,1179,1181],{"id":1180},"establishing-the-platform-too-late","Establishing the platform too late",[186,1183,1184],{},"Data, process, and technical risks then arrive at the same time. An early\nvertical slice distributes learning throughout the project.",[298,1186,1188],{"id":1187},"confusing-go-live-with-project-success","Confusing go-live with project success",[186,1190,1191],{},"An accessible store does not automatically create adoption. Onboarding,\ninternal sales incentives, data quality, and continuous optimization determine\nwhether customers keep ordering digitally.",[207,1193,1195],{"id":1194},"conclusion-become-concrete-early-and-launch-in-a-controlled-way","Conclusion: Become concrete early and launch in a controlled way",[186,1197,1198],{},"Starting a B2B store does not begin with the home page. It begins with a clear\nbusiness goal, real customer processes, and the question of which data and\nsystems support a complete ordering workflow.",[186,1200,1201],{},"Shopware should nevertheless not wait until the end of the concept phase. A\nprofessionally operated project platform available early makes assumptions\nvisible, tests data and integrations, and brings every department to one shared\nimplementation. It does not reduce the need for planning; it improves the\nquality of that planning.",[186,1203,1204],{},"The most sensible route is a small, end-to-end value path: a few pilot\ncustomers, representative products, real prices, a robust ERP integration, and\na clear operating process. Once this path works, the store can gradually grow\nto include more customers, roles, countries, and B2B functionality.",[298,1206,1208],{"id":1207},"official-sources","Official sources",[218,1210,1211,1217,1224,1231],{},[221,1212,1213],{},[792,1214,1216],{"href":794,"rel":1215},[796],"Shopware B2B Components documentation",[221,1218,1219],{},[792,1220,1223],{"href":1221,"rel":1222},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fsolutions\u002Fb2b\u002F",[796],"Shopware B2B solutions",[221,1225,1226],{},[792,1227,1230],{"href":1228,"rel":1229},"https:\u002F\u002Fwww.shopware.com\u002Fen\u002Fsolutions\u002Fwholesale-and-distribution\u002F",[796],"Shopware wholesale and distribution commerce",[221,1232,1233],{},[792,1234,1236],{"href":804,"rel":1235},[796],"Shopware B2B Suite administration and migration note",{"title":1238,"searchDepth":1239,"depth":1239,"links":1240},"",2,[1241,1242,1243,1251,1257,1258,1259,1260,1261,1262,1263,1264,1265,1266,1267,1268,1269,1270,1275,1276,1283],{"id":209,"depth":1239,"text":210},{"id":256,"depth":1239,"text":257},{"id":292,"depth":1239,"text":293,"children":1244},[1245,1247,1248,1249,1250],{"id":300,"depth":1246,"text":301},3,{"id":307,"depth":1246,"text":308},{"id":314,"depth":1246,"text":315},{"id":321,"depth":1246,"text":322},{"id":328,"depth":1246,"text":329},{"id":342,"depth":1239,"text":343,"children":1252},[1253,1254,1255,1256],{"id":375,"depth":1246,"text":376},{"id":414,"depth":1246,"text":415},{"id":447,"depth":1246,"text":448},{"id":457,"depth":1246,"text":458},{"id":493,"depth":1239,"text":494},{"id":500,"depth":1239,"text":501},{"id":539,"depth":1239,"text":540},{"id":578,"depth":1239,"text":579},{"id":688,"depth":1239,"text":689},{"id":724,"depth":1239,"text":725},{"id":757,"depth":1239,"text":758},{"id":810,"depth":1239,"text":811},{"id":849,"depth":1239,"text":850},{"id":890,"depth":1239,"text":891},{"id":923,"depth":1239,"text":924},{"id":959,"depth":1239,"text":960},{"id":995,"depth":1239,"text":996},{"id":1028,"depth":1239,"text":1029,"children":1271},[1272,1273,1274],{"id":1035,"depth":1246,"text":1036},{"id":1059,"depth":1246,"text":1060},{"id":1083,"depth":1246,"text":1084},{"id":1110,"depth":1239,"text":1111},{"id":1152,"depth":1239,"text":1153,"children":1277},[1278,1279,1280,1281,1282],{"id":1159,"depth":1246,"text":1160},{"id":1166,"depth":1246,"text":1167},{"id":1173,"depth":1246,"text":1174},{"id":1180,"depth":1246,"text":1181},{"id":1187,"depth":1246,"text":1188},{"id":1194,"depth":1239,"text":1195,"children":1284},[1285],{"id":1207,"depth":1246,"text":1208},[1287,1288,1289,1290],{"name":1216,"url":794},{"name":1223,"url":1221},{"name":1230,"url":1228},{"name":1236,"url":804},"A new B2B store does not begin with design. This checklist covers processes, data, Shopware, integrations, sales enablement, self-service, and rollout.",false,"md",{"src":1295,"alt":1296},"\u002Fimages\u002Finsights\u002Fb2b-shop-starten-checkliste.png","Benedikt Rillox presenting the roadmap for starting a new B2B store from processes and data to an MVP",{},true,null,"2026-08-17",16,{"title":1303,"description":1304},"Starting a B2B store: Shopware checklist","Where should a new B2B commerce project begin? A practical checklist covering goals, processes, data, Shopware, ERP integration, MVP, and rollout.",{"loc":84},"en\u002Finsights\u002Fstart-b2b-store-shopware-checklist",[1308,1309,1310],"B2B","Shopware","Strategy","insights-b2b-shop-starten-checkliste","Wj0VOAaZY-X877eeKC2TKklrKFJaZoyANCV73d4mqxQ",{"id":1314,"title":1315,"alternateName":1299,"bio":1316,"body":1317,"description":1487,"events":1488,"extension":1293,"heroIllustration":1490,"image":1492,"meta":1495,"name":1494,"navigation":1298,"ogImage":1299,"path":174,"projects":1299,"robots":1299,"role":1496,"sameAs":1497,"schemaOrg":1299,"seo":1501,"sitemap":1502,"slug":181,"socials":1503,"stem":1504,"talks":1299,"translationKey":1505,"__hash__":1506},"team_en\u002Fen\u002Fteam\u002Fbenedikt-rillox.md","Benedikt Rillox — Founder & Strategist","Benedikt is managing partner of nuonic Digital, e-commerce consultant, and developer. Since 2009 he has been designing, building, and guiding digital platforms — from code through product ownership to strategic leadership.",{"type":183,"value":1318,"toc":1478},[1319,1323,1329,1332,1335,1338,1342,1345,1348,1351,1354,1357,1361,1364,1367,1370,1393,1396,1400,1403,1406,1409,1426,1430,1433,1436,1442,1445,1449,1452,1455,1458,1462,1465,1468],[207,1320,1322],{"id":1321},"about-benedikt-rillox","About Benedikt Rillox",[1324,1325,1326],"blockquote",{},[186,1327,1328],{},"To me, technology is not a cost item — it's a competitive advantage.",[186,1330,1331],{},"I'm Benedikt Rillox, managing partner of nuonic Digital, e-commerce consultant, and developer.",[186,1333,1334],{},"Since 2009 I have been designing, building, and guiding digital platforms. My path led from hands-on software development through product ownership and technical team leadership into entrepreneurial responsibility.",[186,1336,1337],{},"That's why I know e-commerce from very different perspectives: from the code, from product development, from budget responsibility, and from strategic leadership. Today I combine these experiences to build commerce systems that don't just work technically, but measurably move businesses forward.",[207,1339,1341],{"id":1340},"my-path-in-e-commerce","My path in e-commerce",[186,1343,1344],{},"I started out as a developer for web and e-commerce projects using technologies like Shopware, TYPO3, PHP, and Symfony. During that time I delivered solutions for smaller companies as well as for well-known brands and corporations — including Unilever, Paul Hewitt, and Framily.",[186,1346,1347],{},"At A-Z Gartenhaus my role evolved from Shopware developer to product owner. There I helped build and lead a ten-person development team and was responsible for the strategic evolution of the commerce platform and its connected third-party systems.",[186,1349,1350],{},"For the Legero United group I took on budget responsibility as product owner and coordinated the technical development of the Superfit, legero, and Think! shops.",[186,1352,1353],{},"As tech lead for ByteClub I planned and built the commerce platforms of the group with brands like COMSPOT, Shifter, GfBD, and IM.F.B. Further projects included ongoing support and the Shopware 6 rebuild for Xucker, as well as the design and development of a Shopware payment plugin for topi that digitizes B2B leasing and buy-on-invoice.",[186,1355,1356],{},"These stations taught me that successful commerce projects never consist of technology alone. They combine architecture, processes, people, and clear business goals.",[207,1358,1360],{"id":1359},"from-development-to-strategy","From development to strategy",[186,1362,1363],{},"I am a developer, a strategist, and a problem solver.",[186,1365,1366],{},"I can dive deep into technical details without losing sight of the actual goal: What impact should a solution have for the company, its people, and its customers?",[186,1368,1369],{},"Today my focus is on designing, building, and continuously evolving demanding Shopware systems. Among other things, that includes:",[218,1371,1372,1375,1378,1381,1384,1387,1390],{},[221,1373,1374],{},"technical and strategic e-commerce consulting,",[221,1376,1377],{},"software and Shopware development,",[221,1379,1380],{},"architecture and system integration,",[221,1382,1383],{},"product ownership and project management,",[221,1385,1386],{},"performance and stable operations,",[221,1388,1389],{},"automation and process optimization,",[221,1391,1392],{},"technical team leadership and collaboration with agencies.",[186,1394,1395],{},"Across more than 25 client projects I have seen what makes digital initiatives fail — and what makes them succeed. Good technology needs a clear direction, realistic requirements, and the courage to make decisions.",[207,1397,1399],{"id":1398},"i-dont-build-shops-just-so-theyre-online","I don't build shops just so they're online",[186,1401,1402],{},"A shop can work technically and still be too slow, too complicated, or economically ineffective. That's why at nuonic we don't just look at individual features. We look at the whole system: architecture, processes, integrations, performance, customer journey, and the ability to grow in the future.",[186,1404,1405],{},"I don't believe in best practices when they merely mean copying what everyone else is already doing. I believe in solutions that fit a company's business model, its team, and its actual goals.",[186,1407,1408],{},"That also means asking uncomfortable questions:",[218,1410,1411,1414,1417,1420,1423],{},[221,1412,1413],{},"Does this feature really need to exist?",[221,1415,1416],{},"Does it solve a relevant problem?",[221,1418,1419],{},"Will the system remain manageable in the long run?",[221,1421,1422],{},"Does the investment support a concrete business goal?",[221,1424,1425],{},"Can the platform grow without collapsing under its own complexity?",[207,1427,1429],{"id":1428},"responsibility-begins-after-go-live","Responsibility begins after go-live",[186,1431,1432],{},"To me, go-live is not a success. It's the beginning of responsibility.",[186,1434,1435],{},"Only in day-to-day operations does a platform prove whether it truly holds up: whether it stays stable, whether the team can work with it efficiently, and whether it can evolve without unnecessary friction.",[186,1437,1438,1439],{},"That's why my work doesn't end with the handover. That's where the real value creation begins: ",[199,1440,1441],{},"Optimize. Automate. Scale.",[186,1443,1444],{},"I don't think in short-term projects, but in commerce systems that carry their weight for the long run. Technology shouldn't just cover today's needs — it should open up new possibilities.",[207,1446,1448],{"id":1447},"clarity-is-part-of-working-together","Clarity is part of working together",[186,1450,1451],{},"Good results don't come from saying yes to every idea. That's why I also say no — to bad requirements, to short-term thinking, and to projects without a discernible direction.",[186,1453,1454],{},"I prefer working with decision-makers who take ownership. With teams that are ready to genuinely change things instead of merely managing existing problems. And with companies that see technology as an investment — not as a necessary cost item.",[186,1456,1457],{},"That's not always comfortable. But it creates clarity, protects budgets, and leads to better results.",[207,1459,1461],{"id":1460},"what-i-stand-for","What I stand for",[186,1463,1464],{},"I don't want to simply be busy. I want to create impact.",[186,1466,1467],{},"With nuonic we build commerce systems for companies that want to grow — faster, more stable, and more profitable.",[186,1469,1470,1471,1474,1475,1477],{},"Others talk about digitalization. We deliver it.",[1472,1473],"br",{},"\nOthers plan. We build.",[1472,1476],{},"\nOthers wait. We go.",{"title":1238,"searchDepth":1239,"depth":1239,"links":1479},[1480,1481,1482,1483,1484,1485,1486],{"id":1321,"depth":1239,"text":1322},{"id":1340,"depth":1239,"text":1341},{"id":1359,"depth":1239,"text":1360},{"id":1398,"depth":1239,"text":1399},{"id":1428,"depth":1239,"text":1429},{"id":1447,"depth":1239,"text":1448},{"id":1460,"depth":1239,"text":1461},"Projects, references, talks and events by Benedikt Rillox — founder and strategist at nuonic Digital, e-commerce consultant and developer since 2009.",[1489],"omr-festival-2026",{"src":1491,"alt":1238},"\u002Fimages\u002Fteam\u002Fdefender.png",{"src":1493,"alt":1494},"\u002Fimages\u002Fteam\u002Fbenedikt-rillox.jpg","Benedikt Rillox",{},"Founder & Strategist",[1498,1499,1500],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fbenedikt-rillox-4122b183\u002F","https:\u002F\u002Fgithub.com\u002Fbenediktrillox","https:\u002F\u002Fwww.xing.com\u002Fprofile\u002FBenedikt_Rillox",{"title":1315,"description":1487},{"loc":174},{"linkedin":1498,"github":1499},"en\u002Fteam\u002Fbenedikt-rillox","team-benedikt-rillox","6UE6ets3lwYRTe7YAfWy1jLeLFh6ZKquI0A2e8QqSDc",1787149680726]