Optimising delivery schedule releasessteering release processes efficiently

Distinction from the classic purchase order

Unlike a single purchase order, the release only reflects the planning framework; what is legally binding is typically the framework agreement. It is important to have a clear regulation of which release details are binding and by when changes are possible. Unclear interfaces lead in practice to disputes that escalate via the complaints management process or cancellation negotiations. Buyers should therefore anchor the release logic explicitly in the contract, similar to the contract term or Incoterms DPU and other delivery clauses.

• Framework agreement defines prices, terms and delivery logic
• Release defines specific quantity, date and mode of transport
• Firm/flex windows govern changeability

Release types in practice

Weekly or monthly releases are common, teleservice or just-in-sequence models for high volumes, and consignment-like releases with stockholding at the supplier. The choice of release type depends on the value, variant diversity and logistical relevance of the parts. Supplier segmentation provides the foundation here, as A-parts require different release granularity than C-parts. For standard parts with high volume, daily release data sets have proven successful, while contract manufacturing positions tend to be planned monthly with long firm lead times.

Define release logic and firm/flex bands

First, firm lead times, firming windows and quantity tolerances are defined per article or part family. In practice, firm windows of around two to four weeks are common, in which quantities can no longer be changed, followed by more flexible bands with tolerances of frequently plus/minus 10 to 30 per cent. It is important to align with the supplier's capacity planning: flexibility that the supplier must hold available costs money and should be compensated in the price or via separate flexibility clauses.

• Define firm lead times per part class
• Agree tolerance bands with the supplier
• Assess flexibility economically

Quantity and transport consolidation

Releases should be coupled with logistical optimisation levers: consolidated loads, defined transport cycles, full utilisation of lorries or containers and alignment with Incoterms DPU and comparable delivery clauses. A network analysis of transport routes frequently reveals considerable consolidation potential when several plants or suppliers in one region are supplied. In practice, a fixed, weekly transport grid to which the releases are aligned has proven successful, rather than uncoordinated individual releases.

Automation and data quality

Releases should be generated system-supported from the demand of the ERP or PPS system. A clean procurement ETL process ensures that requirements data, open release quantities and dates are exchanged consistently between systems and supplier portals. Manual intervention is reserved for exceptions. Data quality is decisive: faulty master data, duplicate releases or unclear item assignments are the most common causes of release turbulence.

Release adherence and change rate

Release adherence measures how often actually released quantities and dates correspond to the released plan. A high change rate after firming strains the supplier relationship and frequently leads to price concessions or surcharges. In practice, release adherence of over 95 per cent is considered desirable. Both metrics should be evaluated per supplier and discussed regularly as part of supplier evaluation.

On-time delivery and inventory coverage

On-time delivery shows whether the supplier serves the release reliably; typical target values are above 98 per cent for serial parts. Inventory coverage in the supplier and receiving warehouse indicates whether release quantities are over- or under-dimensioned. If both metrics rise simultaneously, the firm/flex bands are probably set incorrectly. The on-time payment rate also belongs in the overall picture, as reliable payment increases the supplier's willingness to be flexible.

Process costs and parts per release

Transaction metrics such as the number of releases per month, average quantities per release or the effort per release transaction show whether the granularity is right. Overly fine-grained releases create handling effort without added value. Here, approaches from idea evaluation can also help: systematically evaluating and implementing improvement suggestions from the team.

Economic risks: cancellations, minimum quantities, price increases

Short-notice release changes and cancellations can trigger additional costs at the supplier, for example for material already procured or holding stock. Framework agreements should therefore contain provisions on cancellation deadlines, minimum off-takes and compensation payments. In the event of continued breach of contract – for example repeated release breaches – suppliers retain termination for cause as a last resort. Conversely, buyers must cover default risk and non-delivery risk with a risk mitigation plan.

Process risks: duplicate releases and data breaks

In SAP and portal environments, parallel releases easily arise via different channels, for example when a purchase order is placed in addition to the framework release. Double deliveries, shortfalls and inventory discrepancies are the consequences. Effective controls are reconciliation of open release quantities with goods receipts, a clear channel protocol (only one binding communication route) and regular reconciliations with the supplier, ideally with traceability of materials down to batch level.

Legal and documentary aspects

Releases are documents with evidentiary function, for example in the event of delivery delays or in complaints management. Customs and commercial documents such as the commercial invoice or the bill of lading must also be consistent with the release data for international releases. For certain products, the long-term supplier's declaration is part of the delivery documentation. Since individual questions of burden of proof and binding effect must be assessed differently depending on the contract, the wording should be reviewed legally.

EDI, portals and supply chain visibility

Instead of paper-based or email releases, more and more companies are using EDI formats (such as EDIFACT DELINS or ANSI X12 830) or supplier portals. Supply chain visibility – i.e. real-time transparency on demand, stock and transport status – allows more dynamic releases with simultaneously lower buffer requirements. Small and medium-sized suppliers are frequently integrated via portals, as setting up EDI interfaces would be disproportionately expensive for them.

Sustainability and regulatory requirements in releases

Sustainability requirements also affect the release process: consolidated transports reduce emissions, and packaging requirements such as obligations under packaging legislation must be taken into account for reusable and single-use systems. Supply chain due diligence obligations increase the pressure for gap-free documentation along the supply relationship. Releases thus also become an instrument of evidence for transport-saving and compliance-compliant processes.

Resilience instead of pure cost reduction

Experience of recent years shows that pure just-in-time optimisation is fragile. More and more procurement organisations combine lean releases with buffer strategies, dual sourcing structures and backward-planned award schedules for new parts. Lessons learned from crisis situations are regularly incorporated into the firm/flex rule sets. Tool procurement with tool deposits and the associated build-up of second sources also changes the release logic in the long term.