Framework Contracts and Call-off Orders in a B2B Store

In B2B, procurement has been shifting into self-service for years: buyers want to order around the clock, view the status of their contracts and act without inquiries. Almost a quarter (ECC KÖLN, B2B-Marktmonitor 2025) of B2B revenue is already generated online, and the trend is rising. Framework contracts are especially valuable here because they represent a long-term business relationship and secure recurring revenue. Mapping these contracts in the store binds the customer more closely to the supplier, because whoever can conveniently see their quota, their price and their call-off history in the portal has little reason to switch providers. Anyone who extends their B2B store services with real call-off logic turns a catalog into a contract portal.

The reality in many companies looks different. Call-offs arrive as informal emails, by phone or even by fax: 63 percent (Bitkom) of trading companies with online sales still offer ordering by fax. The sales desk then maintains the remaining quota in a spreadsheet, reconfirms the negotiated price in every email and types the order into the inventory system by hand. That is slow, error-prone and opaque, because neither customer nor supplier can see at the push of a button how much of the quota is still open. Every one of these manual steps is a candidate for digitization and a recurring reason for inquiries that digital call-off logic makes unnecessary.

A digital call-off order follows a clear flow that can be mapped entirely in the store. What matters is that every step is checked automatically against the contract data, so that neither an overdraw of the quota nor a wrong price is possible. The customer moves through a guided process that enforces the rules of the framework contract in the background. This is what a typical call-off looks like in a Shopware store:

The benefit is obvious: what used to mean several emails, a phone call and manual entry into the ERP becomes a task of a few minutes that the customer triggers themselves. The sales desk is relieved of routine confirmations and can focus on advice and exceptions. How the individual line items are presented cleanly with technical data and tiered prices is shown in our article on the B2B product detail page with data sheets and downloads.

Not every employee may call off arbitrarily large quantities. In B2B, a call-off often carries a noticeable budget, and internal rules require approval above a certain amount. Digital call-off logic maps these rules directly: call-offs below a threshold go through immediately, larger quantities first go to a responsible person for approval. That preserves the speed of self-service without losing control over the budget. These approval processes are a core part of our B2B store services and can be configured differently per customer, role and cost center.

For the approvals to fit the customer's organization, a well-thought-out role and permission concept is needed. A requester triggers call-offs, an approver authorizes them, a viewer only sees the status. Cost centers and budgets can be stored per department, so the call-off is automatically assigned to the right pot. Through the integration with ERP and inventory management, these approvals flow back into the supplier's systems, so approved call-offs reach order processing without a media break. The result is a process that respects the customer's internal governance while staying fast.

In Shopware, framework contracts can be mapped on the basis of the existing B2B functions and targeted extensions. Customers and customer groups form the basis for the personalized price commitment, while quota, term and remaining quantity are kept as contract-related data fields. A call-off is created as an order that is validated against these fields: quantity less than or equal to the remaining quota, price equal to the contract price, date within the term. Because we build exclusively on the open-source Shopware base, the solution stays extensible and independent, without tying you to closed add-on packages.

The call-off logic only unfolds its full value in interplay with the inventory system. Quotas and prices usually come from the ERP, and every call-off has to flow back there as an order. Through the appropriate interface between store and ERP, contracts, remaining quotas and call-offs are kept in sync, so both sides always see the same status. Clear error handling is important: if a contract expires or the quota is exhausted, the store has to report this cleanly instead of allowing an invalid call-off. This robustness decides whether customers trust the digital process in the long run.

The path to a digital framework contract runs through manageable steps rather than a large project. It starts with selecting one or a few representative contracts whose quota, price and call-offs are mapped in the store. In parallel, it becomes clear which approval rules and ERP fields are needed. Because buyers increasingly trigger call-offs on the move, mobile operability belongs in from the start; what matters in B2B procurement via smartphone is covered in a dedicated article. After a pilot phase with real customers, the logic is gradually extended across the entire contract portfolio.

Which expansion stage makes sense for your company depends on the number of contracts, the complexity of the approvals and the existing system landscape. A look at typical scenarios from wholesale, industry and technical trade can be found in our references, and how we calculate scope and effort is shown in the services and pricing overview. What matters is not to view the framework contract as an isolated feature but as a continuous process from contract to call-off to order processing in the ERP.