Technical Questions
The technical implementation of a B2B shop naturally raises the most questions. From choosing the right ERP integration to performance optimization with large catalogs and implementing complex order approvals: in this section, we address the technical details that make the difference between a functioning and a truly capable B2B shop.
In short and in plain language
On this page you will find questions and answers on the topic “Technical Questions”.
Each question has its own page with the answer. Below the question you see the start of the answer. Click on a question. Then you can read the whole answer.
At the bottom, a link takes you back to all 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…
- 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…
- 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…
- 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…
- 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…
- 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…