Frequently asked questions
Frequently Asked Questions About B2B E-Commerce
From the initial project idea to ongoing operations: here you will find answers to the most important questions about B2B shop development, technology selection, interfaces and working with XICTRON.
General Questions
- What distinguishes a B2B shop from a B2C online store? A B2B shop does not map the spontaneous one-off purchase but recurring procurement processes between companies. It starts with pricing: instead of a single consumer price, every logged-in customer sees their individually negotiated conditions, volume tiers and framework agreement prices. On top of that come multi-tier order approvals, budget and cost-center logic, quote requests instead of instant checkout, and repeatable orders via order lists and CSV upload. Technically, the biggest difference is integration. A B2B shop is rarely an island; it is tightly coupled with the inventory management or ERP system that supplies stock, prices and order status in real time. Catalogs are usually far larger and require powerful search and filtering. How these requirements are implemented in practice is described on our B2B portals and Shopware development pages. In a free initial consultation we assess your specific case.
- Which industries does XICTRON build B2B shops for? We serve companies in wholesale and distribution, manufacturing and supply industry, medical and laboratory technology, building materials trade, food and beverage as well as technical trade and office and operational supplies. Each of these sectors has its own rules: variant-rich technical articles, batch and best-before requirements for food, quantity and pallet logic in building materials, or documentation duties in medical technology. We know these specifics from 50+ B2B projects (project experience). Rather than forcing a generic solution with bolted-on workarounds, we model the actual procurement processes of your industry. An overview of all sectors we serve can be found under Industries. Whether your specific requirement fits, we are happy to clarify in an initial consultation.
- Why does XICTRON use Shopware Community Edition? Shopware Community Edition is an open-source commerce platform developed in Germany. The open source code lets us adapt the business logic deeply instead of being confined to a predefined feature set. Precisely in B2B, where pricing logic, approvals and interfaces rarely fit a standard grid, this freedom is decisive. For you, this means concretely: no revenue- or user-based license fees, full access to your own code, and no dependency on the roadmap decisions of a single vendor. An active ecosystem also delivers regular security updates and a broad selection of vetted extensions. How we extend the platform for B2B scenarios is shown on our Shopware development page. Which edition makes sense for you, we discuss in our e-commerce consulting.
- Can an existing shop be migrated to Shopware? Yes, switching from a legacy platform to Shopware Community Edition is one of our regular project types. It always starts with an assessment: which data structures exist, which custom functions must be preserved, and which URLs need to be carried over and protected with redirects for SEO reasons? From this we derive a clear migration plan for product data, customer master data, prices and order histories. The actual data transfer is automated via mapping scripts and validated multiple times on a test environment before the final move. This way, mispostings and data loss can be caught early. During the transition phase, both systems can run in parallel so operations are not interrupted. Details on the approach can be found under Shopware development. For an initial assessment of your data, get in touch.
- How does XICTRON ensure data security in the B2B shop? A B2B shop processes sensitive business data: individual conditions, order volumes and customer relationships. We therefore consider security from the outset, not as an add-on shortly before go-live. Concretely, this means encrypted data transfer via TLS, granular role-based access rights, prompt security updates and automated vulnerability scans. Added to this is a multi-tier backup concept with regularly tested restoration, because a backup is only as good as its proven recoverability. Our solutions are operated in a GDPR-compliant manner on servers in German data centers, so the data is subject to European data protection law. How we secure operations, updates and monitoring on an ongoing basis is described on our Maintenance page. An individual security assessment is available via the contact form.
- Does XICTRON offer training for shop administrators? Yes. A platform only delivers value once your team operates it confidently. After go-live, your administrators and content managers therefore receive hands-on training on the Shopware backend: product management, category and assortment maintenance, order and customer management, plus the operation of all features developed specifically for you, such as approvals or price lists. So that knowledge does not hinge on individuals, we create project-specific documentation that serves as a reference guide and also helps when onboarding new staff. Refresher sessions are available on request, for example after larger extensions. Training and knowledge transfer are part of our service scope. We tailor content and depth individually; feel free to contact us about it.
Technical Questions
- Which ERP systems can be connected to the B2B shop? We have integration experience with SAP Business One, SAP S/4HANA, Microsoft Dynamics 365, DATEV and numerous industry-specific inventory management systems. What matters is less the name of the system than the question of which interfaces it provides: standardized REST or SOAP APIs, IDoc, OData or a file exchange via CSV and EDI. Depending on complexity and data volume, we either connect directly or place a middleware layer in between that transforms data and absorbs outages. Typical synchronization areas are product master data, warehouse inventory, customer-specific conditions, orders and invoices, optionally in real time or at defined intervals. Our approach to integrations is described on the Integrations page. A feasibility assessment for your ERP is available in the initial consultation.
- How does a Shopware B2B shop perform with large catalogs? Large B2B catalogs with hundreds of thousands of products and variants are not an edge case but the norm. With the right architecture, Shopware Community Edition scales reliably for them. Among other things, we rely on a dedicated search engine for fast full-text search and faceting, in-memory caching for sessions and objects, plus optimized database queries and a multi-tier caching concept. For particularly high data volumes, read replicas and well-considered indexing strategies are added so that ERP imports do not slow down live operation. As a benchmark, we aim for page load times under two seconds, even on catalog-intensive listing pages. Which levers work in detail is described on our Performance page. An analysis of your existing shop is possible via the contact form.
- Does the B2B shop support customer-specific pricing and volume discounts? Yes, individual pricing is the heart of any B2B solution. In the business customer space there is rarely a single list price, but conditions negotiated per customer or customer group. We model customer-specific price lists, quantity-based tiered pricing, time-limited promotions and framework agreement prices, each visible only to the authorized, logged-in customer. Prices can either be synchronized directly from the ERP, so conditions maintained there remain authoritative, or managed within the shop. More complex scenarios such as currency-dependent pricing, project-specific special prices and validity periods are also feasible. How we interlink pricing logic and ERP conditions is explained under Integrations and B2B portals. We discuss your individual pricing model in the initial consultation.
- Can the shop operate in multiple languages and currencies? Yes. Shopware Community Edition natively supports multiple sales channels with different languages, currencies and tax configurations. For each target market we set up a dedicated channel, for example with country-specific tax rates, locally common payment methods and adapted shipping conditions. This way a customer in Austria or the Netherlands sees correct prices, VAT and delivery options. Translation management is integrated directly into the backend. Your team maintains product texts and content centrally in all target languages without operating a second system. Where needed, B2B-specific conditions can also be tiered per country. The technical implementation of international channels falls under Shopware development. Which markets make sense for your rollout, we clarify in our e-commerce consulting.
- Which payment methods are available for B2B customers? B2B customers expect different payment methods than consumers. The focus is on purchase on invoice with configurable payment terms, complemented by SEPA direct debit, prepayment and credit card. Which options a customer is offered can be controlled per customer group or individual, for example invoice purchase only above a certain trust status. For protection, credit checks via interfaces to business credit agencies can be integrated. For existing customers with framework agreements, automatic invoicing is common, and partial deliveries with proportional invoicing are also supported. Connecting payment and credit-check services falls under Integrations. Which setup suits your receivables management, we discuss on request.
- How are order approvals and budget limits implemented technically? Multi-tier approvals mirror your customer's purchasing organization in the shop. An orderer creates a cart that is automatically routed to the department head or procurement manager for approval, depending on the order value. Only after approval is the order placed. This way the customer retains ordering convenience at the decentralized level and control at the central level. Budget limits can be defined per department, cost center or individual; when exceeded, an automatic escalation kicks in. All approval actions are logged and are therefore traceable for internal audits and compliance documentation. Such procurement processes are a core topic of our B2B portals. What your approval hierarchy should look like, we capture in the initial consultation.
Security and Data Protection
- Where is the B2B shop data hosted? All platforms we maintain run on servers in German data centers. These feature redundant power supply, climate control and network connectivity, so the failure of a single component does not halt operations. The German location is no formality: it ensures your data is subject to the GDPR and the German Federal Data Protection Act (BDSG) and is not processed in third countries. For business-critical shops, we implement geo-redundant backup strategies on request, with mirroring to a second German data center. This way, even the failure of an entire site leaves a current copy available. Hosting and operations are part of our maintenance services. Which infrastructure suits your requirements, we clarify in conversation.
- What GDPR measures are implemented by default? We build data protection into the shop from the ground up, not after the fact. By default this includes encrypted data transfer via TLS, cookie consent management with granular choice, data subject access and deletion functions for personal data, and the preparation of processing records and data processing agreements. The guiding principle is data minimization under the GDPR: only data actually required for the respective business purpose is collected and stored. For analytics and reach measurement, we rely on privacy-friendly, consent-based methods rather than opaque third-party services. The ongoing upkeep of legal requirements we accompany as part of Maintenance. For an assessment of your specific case, get in touch.
- How is the shop protected against attacks? Protection does not come from a single measure but from several interlocking layers. These include a Web Application Firewall (WAF) against common attack patterns, rate limiting to fend off brute-force attempts, and IP-based access restrictions for the admin backend. We install security updates promptly, since known vulnerabilities are the most common entry point. In addition, automated vulnerability scans run continuously, and before go-live as well as at regular intervals we conduct manual security audits that uncover typical weak spots in the individual business logic. Continuous protection during operation is part of our maintenance packages. A security check of your existing shop can be arranged on request.
- Is there a backup concept for emergencies? Yes, every platform we maintain has a multi-tier backup concept. Daily full backups of the database and file system, complemented by more frequent incremental backups and transaction logs, enable restoration to virtually any point in time. This is crucial when, for example, a faulty import is only noticed hours later. What matters is proven recoverability: we test restorations regularly rather than relying on unverified backups. Documented emergency runbooks describe who performs which steps in an incident, so the response does not have to be improvised. Backup management and emergency preparedness are an integral part of our Maintenance. We tailor a suitable concept for your platform individually.
- Can access rights in the shop be assigned in a differentiated manner? Yes, role-based access control is a core component of any B2B solution. In a business customer account, many people often act with different rights. We map this through differentiated roles that mirror the organizational structure: administrators, buyers, orderers with a budget limit, and read-only users who, for example, only view prices. Every action is logged and thus remains traceable for revision and audit purposes. Where desired, user management can be connected to existing directory services such as Active Directory or LDAP, so that staff do not have to be maintained twice. We design such role models as part of our B2B portals. Which permission structure your customers need, we clarify in the initial consultation.
- How are sensitive data like prices and conditions protected? Individual conditions are a competitive factor in B2B and must not fall into the wrong hands. That is why customer-specific prices, discounts and contract details are visible exclusively to the respective logged-in, authorized customer. Unauthenticated visitors or customers without the corresponding authorization see no individual prices, not even through manipulated requests. On the technical level, data transfer between shop and ERP is encrypted, and the interface endpoints are secured through token-based authentication and IP restrictions. This way, condition data remains protected even in transit. The secure connection of price sources is covered under Integrations. An assessment of your current data flows is available on request.
Costs and Investment
- What does a typical B2B e-commerce project cost? A blanket figure would be misleading, because the investment depends heavily on scope. As a rough orientation: a B2B shop with standard functionality and a manageable ERP connection starts in the mid five-figure range. Projects with several system integrations, complex approval workflows, individualized catalogs and internationalization move into the six-figure range. In our experience, the biggest cost drivers are less the shop itself than the interfaces, the data quality in the legacy system and the depth of the individual business logic. We assess precisely these factors early on so there are no surprises later. A realistic budget indication based on comparable projects is provided in the free initial consultation. The included deliverables are listed under Services.
- Are there hidden costs such as license fees? The platform itself incurs no license costs: Shopware Community Edition is open source, independent of the number of your customers, orders or products. This eliminates a cost item that, with revenue-based license models, often climbs uncomfortably as you grow. Your investment is transparently composed of development, hosting, maintenance and optional further development. Costs for paid extensions or external services, such as payment providers or credit agencies, we disclose openly rather than hiding them in a lump sum. We itemize all items in detail before the project begins; the Services page gives an overview. Open questions about the calculation we answer in the initial consultation.
- What ongoing costs arise after go-live? After go-live, essentially three ongoing items arise: hosting, maintenance and optional further development. Hosting on German servers covers infrastructure, SSL certificates and backup storage and is geared to the load and data volume of your shop. Maintenance starts with a base package including monthly security updates and monitoring and can be extended up to enterprise SLAs with binding response times. Since Shopware Community Edition incurs no license fees, a frequently underestimated cost item, one that grows with revenue in other models, is eliminated. The available tiers are described on our Maintenance page. A calculation tailored to your operation we prepare on request.
- Does XICTRON work with fixed prices or on a time-and-materials basis? Both are possible, and the choice depends on how clear your requirements are. For sharply defined projects with a stable requirements catalog, we offer fixed prices that give you planning certainty. For undertakings with still open or exploratory questions, billing on a time-and-materials basis with hourly contingents is usually fairer, because it spares you laborious, often outdated detailed specifications up front. In practice, a combination frequently proves itself: a fixed price for the clearly defined initial go-live and subsequent further development on a time-and-materials basis, prioritized by business value. Which model suits your undertaking we clarify early and transparently. A recommendation is provided in the free initial consultation; the deliverable building blocks can be found under Services.
- How is the return on investment of a B2B shop calculated? The economic benefit of a B2B shop rarely stems from a single effect but from the interplay of several levers. Central is the reduction of manual order processing: orders that previously came in by phone or fax and had to be retyped now flow directly and structured into the system. In practice, the handling effort per order drops considerably as a result (typically 60 to 80 percent (project experience)). Added to this are a rising online ordering rate (often from under 10 to over 50 percent within twelve months (project experience)), a lower error rate in order entry and a relieved inside sales team that can focus on advice instead of typing. In many cases, the investment pays for itself within 12 to 18 months (project experience). An ROI estimate tailored to your figures we develop in our e-commerce consulting or directly in the initial consultation.
- Can the project be divided into sub-projects to distribute the investment? Yes, we even recommend a phased approach in many cases. Instead of implementing everything at once, phase one starts with the core shop, a basic ERP connection and the most important product categories. This makes a productively usable system available early, on which real, hands-on experience can be gathered. Phase two expands with additional interfaces, self-service functions and further sales channels; phase three with internationalization, advanced analytics and automation. This cut reduces project risk, delivers early wins and distributes the investment over a longer period. The right phase cut for your undertaking we design in our e-commerce consulting. Get in touch for an initial roadmap via the contact form.
Projects and Costs
- What does a typical B2B shop project at XICTRON look like? A typical project goes through five phases. In the analysis phase (about two to three weeks) we capture requirements, analyze existing systems and record the goals in a specification document. The concept phase (two to four weeks) clarifies information architecture, interface design and technical architecture before the first line of code is written. During implementation (eight to sixteen weeks) we develop the shop iteratively with regular interim presentations, so you can continuously steer progress and direction. The testing phase (two to three weeks) covers functional tests, load tests and user acceptance tests. After go-live, a four-week hypercare phase follows with increased availability. The concrete building blocks per phase can be found under Services. A workflow plan tailored to your undertaking we create in the initial consultation.
- How long does it take to develop a B2B shop? Duration depends on scope. A B2B shop with standard functionality, one ERP connection and up to around 50,000 products is usually operational within four to six months. Projects with several interfaces, custom order workflows and international orientation typically require six to nine months. So you do not have to wait until the end, we deliver a functional prototype after just a few weeks. Against it the concept can be validated and readjusted early, before effort flows in the wrong direction. Often it is less the development than the data quality in the legacy system that delays the schedule, which is why we address this point early. The realistic time frame for your undertaking we assess in the initial consultation; the approach is described on the Shopware development page.
- What happens if requirements change during the project? Changes are the rule in the B2B environment, not the exception. Over the course of a project, new insights almost always emerge from operational business, and a good process must be able to handle them instead of rigidly clinging to the first plan. We therefore work with a structured change request process: every change is documented, evaluated for effort and impact on schedule and budget, and agreed with you before it is implemented. For fixed-price projects we calculate change requests separately and transparently; for time-and-materials projects they feed into ongoing prioritization. How we create transparency over such decisions is described on our Services page. Open points we discuss at any time on request.
- What internal resources do I need to provide? The biggest contribution is a fixed subject matter contact on your side who knows the business processes and can make decisions. Without this ability to decide, projects stall, which is why this point matters more than pure person-days. During the analysis phase, representatives of the relevant departments should additionally be available on an ad-hoc basis, for example from sales, procurement and IT, to clarify processes and ERP details. The ongoing effort for your team during the active project phase is typically two to four hours per week. We deliberately keep this effort low so your day-to-day business does not suffer. How we organize the collaboration is part of our service scope. The concrete resource requirement for your project we estimate in the initial consultation.
- How are progress and quality ensured during the project? Transparency is not a buzzword for us but a way of working. You receive regular status updates with progress reports and an honest risk assessment, so delays become visible early and not only shortly before go-live. After each iteration we provide a working version on a staging environment that you can test yourself. A shared project board shows the current state, open points and priorities at any time. We safeguard quality through automated and manual tests; before go-live we document the results and obtain your formal sign-off. This process discipline is part of our Services. What a shared project rhythm can look like, we are happy to discuss on request.
- What support do I receive after go-live? Go-live is the beginning of productive operation, not the end of the collaboration. Directly afterwards, a four-week hypercare phase starts with increased availability and accelerated response times. In this particularly sensitive ramp-up period we quickly catch the typical practical questions from real operation. Subsequently, tiered maintenance packages are available that include regular security updates, monitoring, backup management and a defined hourly contingent for bug fixes and minor adjustments. Larger enhancements we handle as standalone projects or on a time-and-materials basis. Which support model suits your platform we coordinate individually.
Ongoing Support and Maintenance
- What maintenance packages does XICTRON offer? Our maintenance is tiered, because a small specialist retailer has different requirements than a business-critical procurement platform. The base package covers the essentials: monthly security updates, daily backups and basic monitoring, so your shop stays secure and up to date. Extended packages add performance monitoring, proactive optimization suggestions and a defined hourly contingent for adjustments and bug fixes. For particularly critical platforms we offer enterprise SLAs with binding response times and extended availability, including outside business hours. The tiers in detail are described on our Maintenance page. Which package suits your risk profile we clarify on request.
- How quickly does XICTRON respond to technical issues? Response time depends on the agreed service package, so you only pay for the service level you actually need. With the base package we respond within 24 hours on business days, which is usually sufficient for platforms without hard real-time dependencies. Enterprise SLAs offer response times of four hours or less, including weekends. Critical security incidents we treat with the highest priority regardless of the package, because here every hour counts. All response times and escalation paths we record contractually, so in an incident it is clear who does what by when. The SLA tiers are part of our maintenance offerings. Which response times your operation requires we discuss in conversation.
- Can the shop be extended with new features after go-live? Yes, and that is exactly how it is intended. A B2B shop is not a finished product but grows with your business. Because we build on an open, open-source foundation, new features can be added at any time without hitting the limits of a rigid system. New requirements we implement as standalone commissions or within an ongoing hourly contingent. Prioritization we do jointly with you, weighed by business value and effort. Typical post-go-live extensions are additional ERP or logistics interfaces, expanded self-service functions, further sales channels and targeted performance optimizations. Possible expansion stages we assign to Integrations and B2B portals. Your wish list we capture on request.
- How are Shopware updates applied? We never apply updates blindly to the live environment. First we evaluate them in a test environment and check compatibility with your individual modifications and extensions, because that is precisely where most problems arise when interfaces or templates have been adapted. We test all critical business processes, from login through price display to order completion, and document any adjustment requirements. Only after successful validation does the update move via the staging environment into production. This way we avoid an otherwise harmless update disrupting ongoing operations. This update management is part of our maintenance services. How we set the update strategy for your platform we discuss on request.
- What happens if we want to switch providers? A provider switch should be possible for you at any time, without technical or contractual ties standing in the way. Because we rely exclusively on open-source technologies, the entire source code belongs to you. There are no proprietary components that only we could operate or license. In the event of a switch, we provide complete handover documentation covering architecture, configurations, interfaces and individual modifications, and we actively support the process. This way your investment remains independent of a single agency. This deliberate avoidance of vendor lock-in is part of our understanding of fair collaboration. How we design documentation and knowledge transfer is part of our Services. Questions about it we are happy to answer via the contact form.
- How is shop performance monitored long-term? Performance is not a state you establish once but a quantity that can creep downward as the catalog grows and load increases. That is why we continuously monitor the most important metrics: page load times, server utilization, database performance, interface response times and error rates. When values deviate from defined thresholds, notifications are triggered automatically, so we can react before customers notice any degradation. In regular reviews we look at the development over time and derive proactive optimizations from it, for example adjusted caching or indexing strategies. This monitoring is part of our Maintenance; the underlying levers are described on the Performance page. A status assessment of your shop is available on request.