Selling Services and Maintenance Contracts in B2B Shops

Service has a quiet strength in mid-market businesses: it reacts more slowly to economic swings than new business, it ties customers in across the whole life of an asset, and it delivers more profit per euro of revenue. In mechanical and plant engineering, service accounts for around 20 percent (VDMA) of revenue, and depending on the sector and the maturity of the offering it sits noticeably above or below that in an individual company. The profit side is even clearer: while new machine business typically reaches an EBIT margin of around 10 percent (McKinsey 2017), aftersales sits at around 25 percent (McKinsey 2017). Even so, digitalisation in many companies stops precisely at the line between goods and services: the product can be ordered online, the service attached to it cannot.

The reasons are rarely technical. Services are seen as needing explanation, as too individual for a catalogue, as something sales has to negotiate. In practice, a large share of service business is largely standardised: commissioning a device class, the recurring inspection of portable electrical equipment (DGUV Rule 3), calibrating a measuring instrument, briefing two people over one morning. Such services have a defined scope, a calculable duration and a price. They could be catalogued - they simply are not. The price for that is a processing chain of calls, quotes, queries and follow-ups that ties up the sales desk and delays the close. Between the customer's question and a bookable answer there are days rather than clicks.

On the buying side, expectations have long since shifted. 67 percent (Gartner) of B2B buyers prefer a purchase without direct sales contact, while 69 percent (Gartner) deliberately involve sales to validate AI-generated insights. Both fit together: the standard case should be self-service, the exception stays a conversation. The digital channel carries real weight - among companies that offer e-commerce, around 34 percent (McKinsey B2B Pulse) of revenue now runs through the online channel. Analogue channels persist nonetheless: 18 percent (Bitkom) of companies in Germany still faxed frequently in 2025. In the gap between expectation and process, service business loses orders, often unnoticed, because a service order that was not placed at all appears in no statistic.

The biggest lever is not the service item itself but where it appears. Commissioning sells where the machine is decided on - not three weeks later in a separate enquiry. In practice that means the relevant services hang on the main product as selectable lines, and the customer puts machine and commissioning into the cart in a single step. Three link types have proven useful. A mandatory service is ordered along with the product as a matter of course because warranty depends on it. A recommended service is preselected but can be deselected. An optional service is offered without blocking the purchase. Which variant fits depends on the product; the structure resembles the logic of a product configurator with guided selling, except that here no variant is created but a second line item.

The link has to be clean on pricing as well. A twelve percent goods discount on a product group must not spill over onto the hourly rate, and a promotional price on the machine must not cheapen the commissioning. Service items therefore belong in their own price groups with their own conditions, maintained independently of goods discounts. How price lists, customer groups and tiers are structured in general is described in the article on price lists and tier pricing in Shopware. A second rule concerns sequence: if the main line is removed, the linked service has to follow or at least trigger a notice. Otherwise a commissioning without a machine stays in the cart and creates a service order with no subject.

A service needs more information than a delivery. Without the site, device data and a time window, scheduling cannot plan, and the order ends up back in the query loop. The temptation is to put all those fields into the checkout. That is precisely the wrong place: the average checkout already contains 11.3 form fields (Baymard Institute), while 8 fields (Baymard Institute) are enough for most shops, and 17 percent (Baymard Institute) of abandonments are caused by a checkout that is too long or too complicated. For large shops, a better designed checkout lifts the completion rate by around 35 percent (Baymard Institute) on average. The conclusion: service details belong on the service line, right where the service is selected, not as an extra block behind the payment method.

Two techniques keep the form short. First: what the system knows, it does not ask. Serial number, site and contact are in the customer account after the first order and can be offered as a selection - how a unique device identity is built is shown in the article on batches, serial numbers and traceability in B2B shops. Second: whatever is not needed to place the order moves behind it. A time window is enough to trigger the job; fine-tuning happens in the order confirmation or in the portal. Which fields are genuinely necessary at checkout and how much friction they create is examined in the article on B2B checkout optimisation.

A maintenance contract is not a product but an object with its own life cycle. It needs a start date, a term, a billing rhythm, a defined scope, a renewal rule and a notice period. The scope should be described concretely enough that nobody has to argue later: two maintenance visits a year, travel included, spare parts billed separately, an agreed response time on working days, standby optional. Billing follows either the contract interval - monthly, quarterly, annually - or the individual visit. Both have merits: the interval smooths revenue and makes it predictable, while per-visit billing stays closer to actual effort. Many providers combine the two by separating a base fee for availability and documentation from the billing of additional visits.

Renewal is the point where contract portfolios grow or quietly bleed out. If a contract expires without a rule, it often ends unnoticed, and the asset becomes a one-off job with a price discussion at the next breakdown. Automatic renewal for twelve months, combined with a three-month notice period to the end of the term and a reminder six weeks in advance, keeps the portfolio stable and stays fair for the customer, because the deadline is visible in the portal. A price adjustment clause belongs in the contract as well, worded transparently and announced with lead time. Finally, the contract needs a link to the asset: if the machine is sold or decommissioned, the contract has to be able to follow, otherwise a document remains without a subject.

Services are not legally the same as goods, and the difference reaches into the product description. Where a result is owed - the repaired asset, the calibrated instrument - German law usually assumes a contract for work (Section 631 German Civil Code). Where an activity is owed, such as standby or training, a service contract is more likely (Section 611 German Civil Code). Deadlines follow from that classification: claims for defects in work on an object generally lapse after two years (Section 634a German Civil Code), and after five years for work on a building. For the shop this mainly means care in the description: what exactly is included, what is explicitly not, what cooperation is expected and what result is promised.

The second point is documentation. A visit produces records - inspection report, calibration certificate, maintenance report, signature on site - and those records often carry their own retention period at the customer. Filing them automatically in the portal saves both sides search time and makes the work performed provable. The third point concerns invoicing: for services the date or period of performance has to be stated, not the delivery date of a parcel. As soon as invoices are exchanged in structured form, that field has to be filled correctly - what the changeover means in practice is described in the article on e-invoicing obligations and ERP integration.