Skip to content
Interface language: English
Imperium / Signal

A forecast for your supplier: distinguish a purchasing plan from an agreed order

Agree what a purchasing plan means to your supplier. Separate the forecast from the order and describe versions, periods and the response expected to an update.

Article language: English

A seated woman beside a glass sphere with dark reflections.
In this article

Description: Agree what a purchasing plan means to your supplier. Separate the forecast from the order and describe versions, periods and the response expected to an update.

A supplier receives a new spreadsheet. The subject line says “plan update”, the attachment gives quantities for several weeks, and the reply says “received”. Purchasing records that it has sent a forecast. The supplier may already be reserving production capacity. Nobody has asked what the other party understood it had received or what action was expected after opening the file.

Consider a hypothetical purchase of packaging inserts. A company sends its regular supplier its anticipated requirements for future periods. Version P-17 covers 1,200 units in the first week and 1,800 in the next. There is a separate agreed order, Z-64, for 800 units. The figures are illustrative. The important question is whether the order is already included in the plan and what the next version changes.

This is a discussion about what data mean in an existing purchasing process. We cannot determine the legal effect of a message or whether a particular document creates an obligation. That assessment depends on the relevant arrangements and contract. A team can, however, stop using one file for several different instructions that no one can reconstruct afterwards.

First agree what the supplier should do with the number

A forecast can help plan availability of people, materials or equipment. The recipient should know which decision the information is intended to support and what reply is needed. “For information” may not be enough if the buyer asks a week later why the partner has not prepared stock. Sending a new spreadsheet does not automatically create an additional purpose.

The GS1 EANCOM message classification describes ordering separately from reporting and planning messages, including forecasts for deliveries, sales and inventory. The material, updated on 2 September 2024, emphasises that partners must agree the appropriate messages. Exchanging structured data does not give every message the same purpose.

In this example the buyer asks the supplier to assess whether the anticipated increase in demand is within its capacity. The buyer expects the supplier to identify periods that need discussion, not to ship inserts on the basis of the spreadsheet alone. That scope should fit the parties' arrangements and be clear to someone covering for the regular contact at the supplier.

If the company also wants to agree that material will be prepared, it should not hide that request under the same label. It is another decision, with its own scope and approving person. The word “forecast” on the first tab will not explain what the buyer later promised in conversation. Keep the document connected to subsequent agreements instead of assigning them an assumed meaning.

A request for quotation to a supplier (in Polish) seeks a response about a defined scope. A requirements plan sent later serves a different purpose. It may use a similar product name and the same quantities, but should not automatically inherit the entire interpretation of an old RFQ, especially if the quote concerned an annual total and the partner now receives a weekly breakdown.

A message acronym does not establish the status of its contents

EDI means electronic data interchange between systems. In practice, the team needs to know both the message type and how it is used in this particular relationship. A file can contain several pieces of information with different statuses. Calling everything a “plan confirmation” erases a distinction the recipient needs in their work.

On its EDI site, Volvo Group describes a specific default Just-In-Sequence delivery flow, meaning delivery in an agreed sequence. In that description DELFOR carries forecasts, while DELJIT carries separate confirmed delivery call-offs. This is the JIS flow described by Volvo Group. It concerns the stated arrangement, not every message called DELFOR in every market.

The broader Volvo DELFOR guideline dated 5 February 2025 describes, among other things, firm and forecast dates and quantities and a material commitment. It also distinguishes a delivery forecast from a schedule combining figures with different statuses. The document states that use depends on the unit and scenario and on the order or contract conditions. The partner's expected reaction therefore cannot be inferred from the six letters of a file name alone.

The company buying inserts does not need to implement EDI to use this distinction. It can use an ordinary spreadsheet and label each range unambiguously. If some periods have a different status, that status needs to survive transfer to the next tool. Cell background colour is easily lost when numbers are copied into a message.

A company glossary (in Polish) can explain how purchasing uses “plan”, “requirement” and “order”. Also check the recipient's language. If the partner says “confirmed”, ask whether they mean receipt of the file, an assessment of capacity or an agreed action. It is hard to resolve a discrepancy while both sides use the same word with different meanings.

The 800 units should not appear twice

In the arrangement chosen here, 1,200 units in the first week means the total anticipated requirement, including order Z-64 for 800. That leaves 400 units from the plan for further agreement. If an employee adds the ordered 800 to the full 1,200, the result is 2,000. The arithmetic is correct. The mistake is combining two ranges that partly describe the same requirement.

Another arrangement is possible: the forecast could contain only requirements not yet ordered. In that case the numbers really do have a different interpretation. The company must choose and agree what its own spreadsheet means. Calling it a net or gross forecast is not enough if the people using the data do not know how it was calculated.

Aeneia conceptual photography

For each period, specify the event to which the date refers. When the plant needs to use the inserts, when it plans to collect them from the supplier and when shipment is expected are different moments. If the sheet gives only a week number, the partner may plan different actions from those expected by the recipient. The people responsible for purchasing and delivery need to agree this.

Oracle's documentation for 830/DELFOR transactions lists, among other things, quantities already received and requested shipment and delivery dates. It separately identifies forecast and firm delivery. A technical format can carry the necessary distinctions, but the team must know which fields it uses in its own process.

For a manual export, check whether the file still preserves that information. Exporting data without losing its meaning (in Polish) deals with losses between an application view and a finished attachment. Total quantities can match even though the status, unit or period has disappeared. Checking the number of rows alone will not reveal that difference.

A new version may replace, supplement or change part of the previous one

The company sends P-18: the first week remains at 1,200 units, while the second falls from 1,800 to 1,400. Should the recipient replace all of P-17 or read only a correction to the second period? If two sets of figures arrive without explanation, the supplier may keep both. The archive gains files and the plan gains inserts nobody wanted.

The Volvo guideline also sets conditions for replacing a schedule based on a combination of its key data. Changing a specified element can create a separate schedule rather than an update. The rule appears in the general section of the same implementation document. It illustrates why data identity matters; it is not an instruction to copy Volvo's rules into any spreadsheet.

In our process P-18 should identify the product, recipient, location and period affected and say how it relates to P-17. It also needs a preparation date and the point from which the plan is used. The previous version remains in the history. This makes it possible to reconstruct what the supplier knew before the update without pretending that the lower number was known from the start.

Check an empty cell too. In P-18 it might mean no new data for a period, exclusion of the period from this version or no anticipated requirement. Its meaning must not be chosen only during import. If the company wants to communicate zero, it needs a way to distinguish zero from an unfilled field. The partner needs the same interpretation, including when the plan arrives late and some listed weeks have already begun.

Consider arrival order as well. An older P-17 might reach another person again after P-18 has been sent, for example as an attachment in forwarded correspondence. The message date will be newer, but the plan is older. The recipient should recognise a version from its own identifier and the basis of the update. Sorting the inbox by the latest email does not reliably order plans.

Separate the response to a new forecast from a change to an order. If Z-64 remains for 800 units, the team should not treat a forecast update by itself as an approved correction to that order. If the parties want to change it, they need the appropriate agreement for their relationship. Internal automation should not invent that decision from a lower value in a spreadsheet.

AI may help find differences between versions, but the comparison also needs a clear scope. “Second week: minus 400” does not yet say whether it concerns anticipated demand, an order or received goods. Preserve the information type before generating a summary. Otherwise the tool may quickly and convincingly describe incorrectly combined data.

These transitions between sources, tools and human decisions are a starting point for Aeneia Audit. Bring two plan versions, the separate order and the way a summary is created. This allows the information flow and the usefulness of AI support to be assessed before another tool inherits unclear statuses.

The supplier's reply must be usable

Ask for a response suited to the forecast's purpose. If you ask about capacity to handle planned growth, a general “received” does not settle the question. The supplier may identify a period that needs discussion or information without which capacity cannot be assessed.

In response to P-18, the partner might confirm reading 1,400 units in the second week while asking when the next update will arrive. The buyer should make sure the partner read P-18 and agree when the next information will be sent. A reply of “thank you” alone leaves the planning question open. Assign it to someone who can actually update the plan rather than directing every request to the author of the attachment.

Identifying a shared source of supplier dependency (in Polish) helps assess a later availability response. Two companies may interpret the same increase differently while relying on the same source of material. Sending a plan to two recipients does not itself create two independent ways to fulfil it.

Do not transfer an unresolved response into a helper spreadsheet as certain availability. An interim workaround that becomes permanent (in Polish) can develop its own status history after several updates. Instead of adding certainty to a copy, record the missing response and the person who will clarify it with the partner.

Finally, take P-17, P-18 and Z-64. Ask someone outside the current correspondence to identify the anticipated requirement for the second week, the quantity covered by the order and the expected supplier response. If they can answer all three without speaking to the file's author, the process is becoming understandable. Otherwise, the new attachment will still be just another version of a guess.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear