Framework agreements and call-off orders in B2B shops

The contract is negotiated, the terms are agreed, both sides have signed – and then purchasing calls sales because nobody can say how much of the agreed quota is still open. A framework agreement does not live on its signature; it lives on the call-offs that follow over the months after it. That part is missing from many catalogues: prices and tier discounts are stored, the contract itself is not. This article describes the four quantities a call-off contract needs, what a call-off looks like technically, which channels carry it, what may change during the term, and how all of it can be modelled in a B2B shop. German public procurement law serves as the reference here – not because it applies to private contracts, but because it has already spelled out the questions a private framework agreement has to answer as well.

What a framework agreement models inside a shop

Framework agreements are agreements between one or more contracting authorities or sector contracting entities and one or more undertakings, serving to establish the terms for the public contracts to be awarded during a given period, in particular with regard to price.

Section 103(5) sentence 1 GWB (German Act against Restraints of Competition)

The shortest definition comes from procurement law: a framework agreement establishes the terms for contracts to be awarded during a given period, in particular with regard to price (Section 103(5) sentence 1 GWB). Two things sit in that sentence and have to be handled separately in a shop: the terms and the period. The agreement itself does not trigger a delivery; it describes the conditions under which later individual orders come about. Private-sector practice is built no differently, it is simply not defined in statute – freedom of contract leaves wide scope for arrangements, within statutory limits such as the rules on standard business terms, as long as the performance remains determinable. And that determinability is exactly the work a shop can take over.

Whether the effort pays off can be read from the weight of the business. For Germany, a study commissioned by the bevh puts B2B e-commerce turnover in 2024 at 4.3 times the B2C figure; revenue from EDI is explicitly excluded from that calculation (bevh/Oxford Economics). On the employment side, some 725,000 jobs, or 73 percent, sit with B2B companies (bevh/Oxford Economics). The part of trade that runs on contracts rather than on shopping baskets is therefore not a side business. It is merely less visible, because it rarely passes through a homepage.

Four quantities every call-off contract needs

Quota: estimated quantity and maximum quantity

The first quantity is the volume, and it is rarely a single number. Procurement law requires the intended order volume to be determined and published as precisely as possible – it expressly does not have to be fixed conclusively (Section 21(1) sentence 2 VgV). That distinction is useful under private law as well: an estimated quantity states what both sides are planning with. It is a basis for calculation, not automatically an obligation to purchase. Whether such an obligation exists is decided by the contract alone – and if the contract stays silent, someone else decides it later.

EU procurement law adds a second number. The Court of Justice of the European Union has held that the contract notice must state both the estimated quantity or value and a maximum quantity or value of the goods to be supplied, and that the framework agreement ceases to have effect once that quantity or value is reached (CJEU, Case C-23/20). The operative part expressly attaches to the contract notice and therefore binds public procurement only. As a blueprint for a private call-off contract it is useful all the same: two fields instead of one, the estimate for planning, the maximum for the limit.

In the data model this means two fields per contract line and one rule for the moment the maximum quantity is reached. The rule can be: further call-offs blocked, further call-offs at list price, further call-offs raised as an enquiry to sales. All three are defensible, but they have to be settled before the first call-off and visible in the interface. A quota that is quietly exceeded produces invoices nobody expected and, in case of doubt, a credit note. The block is usually a modest development step; the credit note costs trust.

Term: how long a framework agreement carries

Within the scope of the German Procurement Regulation, a framework agreement may in principle run for no more than four years; a special case justified by the subject matter of the agreement can carry a longer term (Section 21(6) VgV). For sector contracting entities the limit is in principle eight years, again with the option of duly justified special cases (Section 19(3) SektVO). In the defence and security field it is in principle seven years, and there the special case additionally has to be justified in the contract notice (Section 14(6) VSVgV). None of the three figures is a rigid barrier, and none of them applies to a private supply contract.

In practice, what happens at the end of the term matters more than the maximum duration. Does the contract expire, roll over silently, or lie dormant until a new round has been negotiated? The shop needs a date and a rule for that, not a note in the sales system. Anyone running contracts across several years should also settle how to get hold of their contract data if they change systems – the obligations arising from the Data Act on provider switching also concern operators who keep contract and call-off data in a hosted system.

Remaining quantity: the figure both sides see

The remaining quantity is not a separate agreement but a calculation: quota minus the sum of previous call-offs. It is nevertheless the figure everything revolves around day to day. As long as it lives only in the ERP, you get exactly the phone call to sales this article opened with. The question is therefore less whether the number exists and more when it changes and who is allowed to see it. Five decisions determine whether the figure in the customer account is reliable or merely approximate.

• The trigger. Does submitting the call-off already reduce the remaining quantity, or does the order confirmation do it? Either is defensible; leaving it open is expensive, because the two sides then keep different figures.
• The approval stage. Where a call-off passes through an order approval workflow, the quantity belongs in a reserved pool until the decision – visible, but not yet consumed.
• The cancellation case. A withdrawn call-off has to return the quantity, and in the same unit in which it took it. With packaging units and conversion factors that is less obvious than it sounds.
• Partial deliveries. Is the remaining quantity updated on ordering or on delivery? With long lead times the two figures drift far apart, and both are needed.
• Visibility. Who in the customer account may see the figure – every requester, only the head of purchasing, only with a specific role? A contract balance is commercial information, not a product attribute.

That visibility is a security topic at the same time. An account showing remaining quantities, contract prices and delivery addresses is worth more to an attacker than an ordinary consumer account: it holds what a competitor would like to know. Measures against account takeover through credential stuffing therefore belong in the same project rather than in a later phase.

Price commitment: where it comes from

The fourth quantity is price, and this is where the wrong provision is often invoked. A person who offers to another to conclude a contract is bound by that offer unless the binding effect has been excluded (Section 145 BGB) – that concerns a single offer, not price stability across a contract term. The binding effect ends where the offer is rejected or not accepted in good time (Section 146 BGB). Price commitment over months does not follow from the law on offers but from the framework agreement itself: what is agreed there as the price for the term applies until an agreed adjustment rule takes effect.

Where one party is to determine something itself – the call-off quantity per lot, say, or the timing – it is in case of doubt to be assumed that the determination is to be made at reasonable discretion (Section 315(1) BGB). For the shop this means a right of determination may exist in the form, but it needs limits that are written into the contract: minimum call-off quantity, lot size, lead time. An input field without limits merely postpones the argument, into the moment when a delivery is already on its way.

Technically the contract price rarely lives in the shop but in the leading system. How customer-specific prices from the ERP reach the shop co-determines whether a call-off pulls the right amount: cached price lists age, live queries cost time and fail along with the system. In practice a middle path carries furthest – a price list in the shop with a validity period per line, a live comparison only at checkout, and a log that makes discrepancies visible instead of overwriting them.

The call-off as a transaction in the shop

Technically a call-off is an order with a contract reference. What distinguishes it from a free order is not the basket but three fields: contract number, reference to the contract line, and a sequential call-off number. If one of them is missing, nobody can later say which order reduced which quota – and invoice verification on both sides depends on exactly that mapping. The three fields are usually quick to set up – considerably quicker than a later clarification without them takes.

In terms of usability, making the contract the entry point instead of the product search has proven itself. Purchasing opens the contract, sees the agreed lines with price and remaining quantity, enters quantities and submits. That is the same idea as quick order for regular business customers, only with a quantity limit and a contract behind it. Full-text search stays available alongside – for everything that is not in the contract and therefore runs at list price.

{
  "contract": "RV-2026-0041",
  "call_off": 7,
  "order_date": "2026-10-02",
  "lines": [
    {
      "contract_line": 3,
      "item": "4711-16A",
      "quantity": 240,
      "unit": "PCE",
      "net_price": "4.90",
      "price_as_of": "2026-01-01",
      "quota": 12000,
      "called_off_so_far": 7360,
      "remaining_after": 4400
    }
  ],
  "requested_delivery": "2026-10-20",
  "approval": { "status": "required", "role": "head_of_purchasing" }
}

Two fields in this example deserve attention. The price-as-of date makes it traceable which version of the price list the amount came from; without it, every later check is reconstruction. And the remaining quantity after the call-off travels with the message, not just the figure before it: the recipient can reconcile against it without knowing your own balance. If their calculation differs, it shows up at the call-off and not at the annual reconciliation.

Which channel carries the call-off

A framework agreement in the shop does not rule out the machine-to-machine route – quite the opposite. Official statistics show how electronic sales are distributed across the EU: in 2024, EU enterprises generated around 19.49 percent of their total turnover from e-sales, of which 8.39 percentage points came from websites or apps and 11.07 percentage points from EDI-type messages (Eurostat). The larger share of this e-sales turnover therefore runs through the machine channel, while the number of enterprises paints a different picture.

In 2024, 17.99 percent of EU enterprises sold exclusively via websites or apps, 2.9 percent exclusively via EDI-type messages and another 2.7 percent via both routes (Eurostat). Many enterprises with a web interface, few with EDI, and turnover concentrated among the few: that is not an inconsistency but the usual split between many small and a few large supply relationships. A framework agreement often sits precisely on the seam between the two.

Broken down by size class the picture sharpens. Among small enterprises making e-sales, 91.19 percent had web sales and 17.52 percent sales via EDI-type messages (Eurostat). For medium-sized enterprises the channels move closer together: 78.95 percent web against 38.26 percent EDI (Eurostat). Large enterprises reported the highest share of turnover from e-sales at 24.24 percent, and 14.25 percentage points of that came from EDI-type sales (Eurostat). These figures describe large enterprises as sellers; the statistics do not show how they place call-offs with their own suppliers. Anyone supplying a large organisation under a framework agreement should therefore clarify in advance whether call-offs will arrive via the web interface or as EDI messages.

The sector matters too. In manufacturing, almost half of the EU enterprises making e-sales received orders via EDI-type messages in 2024 – 46.04 percent, followed by transport and storage at 29.02 percent (Eurostat). For a supplier to industrial customers this means the web interface is the entrance for people and the message interface the entrance for systems, and both point at the same contract.

For the web channel itself, the customer type is worth a look. Of the web sales made by EU enterprises in 2024, 4.34 percent of total turnover came from sales to other enterprises and public authorities against 4.04 percent from sales to private consumers (Eurostat). The vast majority of it ran through own websites and apps – 7.08 percent of total turnover against 1.30 percent via online marketplaces (Eurostat). And the trend points slowly upwards: between 2014 and 2024 the share of EU enterprises with e-sales rose from 18.93 to 23.59 percent (Eurostat). Measured by turnover, your own shop is therefore the usual route in the web channel, not the marketplace.

What may change during the term

A framework agreement is not a frozen state, but it is not an open negotiating window either. Procurement law puts the limit for individual call-offs briefly: no substantial amendments may be made to the terms of the framework agreement in the process (Section 21(2) sentence 3 VgV). Transferred to a private contract this means that whatever gets negotiated at call-off time was not a term beforehand – and whoever negotiates at every call-off does not have a framework agreement but a price list with sentimental value.

For changes to the contract itself, procurement law knows graduated thresholds. Without a new procurement procedure a modification is permitted, among other cases, where the overall character of the contract does not change and the value of the modification stays both below the thresholds under Section 106 GWB and below 10 percent for supply and service contracts, or 15 percent for works contracts, of the original contract value (Section 132(3) GWB). That is a de minimis threshold, not a ceiling on every change: in the cases of Section 132(2) sentence 1 nos. 2 and 3 GWB the price may be increased by up to 50 percent of the value of the original contract (Section 132(2) sentence 2 GWB).

When things go wrong: notice of defects, termination, leftovers

The first kind of trouble is a defect. In a commercial transaction for both parties, the buyer has to examine the goods without undue delay after delivery, so far as this is practicable in the ordinary course of business, and to give notice of a defect without undue delay (Section 377(1) HGB). What matters for a framework agreement: the duty attaches to the individual delivery, not to the contract. Every call-off triggers it afresh. Anyone who checked the first call-off but not the twelfth stands without a notice of defects on the twelfth.

The second kind of trouble is the break-off. Where a framework agreement is structured as a continuing obligation – which depends on how it is drafted and cannot simply be assumed – either party may terminate it for good cause without observing a notice period (Section 314(1) sentence 1 BGB). That termination has two limits: where the good cause consists in the breach of a duty under the contract, it is permitted only after a period set for remedial action has expired without result or after an unsuccessful warning notice (Section 314(2) sentence 1 BGB); and the entitled party may terminate only within a reasonable period after obtaining knowledge of the cause for termination (Section 314(3) BGB). Anyone who documents a breach for months and then terminates has the second limit working against them.

• Open call-offs. Do call-offs already placed but not yet delivered survive, or do they end with the contract? Without a rule you get an argument about goods that are already in production.
• Remaining quantity not taken up. Does it lapse, is it invoiced, does it move into a follow-up contract? All three answers are possible, none of them goes without saying.
• Price after the end. At which price is anything delivered that still flows from the contract after the term has ended – the contract price or the list price?
• Records and evidence. Call-off history, price-as-of dates and approvals need archiving, for as long as commercial and tax retention periods require.
• Access in the shop. A finished contract may stay visible in the customer account, but it must no longer be actionable – otherwise the interface produces orders without a basis.

Outlook: call-offs and invoicing during the transition

Every call-off ends in an invoice, and there a transitional period is running. For a supply carried out after 31 December 2026 and before 1 January 2028, a paper invoice – or, subject to the recipient's consent, an invoice in an electronic format that does not meet the statutory requirement – remains permissible only where the issuing trader's total turnover in the preceding calendar year did not exceed 800,000 euros (Section 27(38) no. 2 UStG).

Alongside it sits a second exception that works without any turnover limit: invoices issued by electronic data interchange (EDI) may, with the recipient's consent, be created in a deviating electronic format – for the last time for a supply carried out before 1 January 2028 (Section 27(38) no. 3 UStG). The 800,000 euros are therefore not a limit for every electronic format; they belong to the first exception. Anyone invoicing call-offs via EDI falls under the second rule and does not have to check the turnover limit.

Effort, sequence and acceptance

How much an ordering transaction costs is hard to measure and easy to assert. One of the few published surveys on the subject comes from HTWK Leipzig: in an online survey of 110 procurement managers at German companies conducted from December 2016 to January 2017, a manual ordering transaction cost 115 euros and a digitalised one 67 euros (HTWK Leipzig). The survey is years old and covers indirect procurement; it is no basis for a promise about your own project. As an indication that the process rather than the item price is the expensive part of an order, it remains useful.

1. Take stock. Which contracts exist, where do they live, who maintains them? In practice you find three filing places: the ERP, a sales folder and a spreadsheet. A shop check turns that into a reliable list with terms and quantities.
2. Data model. Contract, line, estimated quantity, maximum quantity, price-as-of date, term – first as fields with rules, then as an interface.
3. Call-off screen. Contract entry instead of product search, a quantity limit in the form, the remaining quantity visible before submitting, a confirmation carrying contract and call-off number.
4. Integration. Price and stock from the leading system, the call-off written back into that same system, a reconciliation run with a log instead of silent corrections.
5. Channels. Put the message inbox and the web interface on the same remaining quantity, then run one test call-off through each route and compare the balances.
6. Acceptance. A call-off beyond the maximum quantity, a cancellation, a partial delivery and a contract ending – four cases to play through once before go-live.

Which system leads is not a matter of taste. Where prices and quotas live in the ERP, the ERP stays the source and the shop is the interface; for an integration with SAP Business One, for instance, that means writing the call-off back as an order and reading the quota balance from there rather than keeping a second tally in the shop. Anyone having contract and call-off data processed in someone else's data centre also needs the contractual basis for it – the duties around data processing agreements and vendor audits apply to a B2B customer account as well. Everything after that is scoping, and scoping starts with the question of which contracts belong in the B2B shop in the first place.