972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Planning and inventory

SLSFCT Sales forecast

The UN/EDIFACT message used to send forecast data for products or services by location, period, quantity and value.

Sent by
Retailer, distributor or manufacturer
Received by
Supplier or trading partner
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT SLSFCT message?

SLSFCT is the UN/EDIFACT sales forecast message. The directory defines it as a message for transmitting forecast data for products or services, such as location, period, product identification, pricing, amounts, quantities, market sector information and sales parties, so the recipient can process it automatically for production, planning, marketing and other purposes.

Forecasts complement actual sales reports (SLSRPT). In collaborative planning, retailers and suppliers exchange forecasts so production and replenishment are planned against expected demand rather than past orders alone. Forecasts are refreshed on an agreed cycle, such as weekly.

How the EDIFACT SLSFCT message worksDiagram of the UN/EDIFACT SLSFCT Sales forecast message. Retailer, distributor or manufacturer sends it to supplier or trading partner. It usually starts the exchange. It is usually followed by ORDERS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG5 loop with LOC (Place/location identification). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SLSFCT message worksSales forecast: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSLSFCTSENDERRetailer, distributor ormanufacturerRECEIVERSupplier or tradingpartnerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDERSPurchase order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage SLSFCTUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 5NADName and addressMandatory group SG5 · repeats many timesLOCPlace/location identification+ 4 conditional groups, starting with:CTARFFCUXLINBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for SLSFCT. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT SLSFCT message worksDiagram of the UN/EDIFACT SLSFCT Sales forecast message. Retailer, distributor or manufacturer sends it to supplier or trading partner. It usually starts the exchange. It is usually followed by ORDERS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with NAD (Name and address) and the required SG5 loop with LOC (Place/location identification). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SLSFCTmessage worksSales forecast: who sends it, where it fits andwhat the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSLSFCTSENDERRetailer,distributor ormanufacturerRECEIVERSupplier ortrading partnerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDERSPurchase order2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message SLSFCT (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 5NADName and addressMandatory group SG5 · repeatsmany timesLOCPlace/location identification+ 4 conditional groups, starting with:CTARFFCUXLINBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for SLSFCT.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends SLSFCT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around SLSFCT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Sharing demand forecasts with suppliers
  • Supporting collaborative planning and replenishment
  • Forecasting promotional demand

Where it fits in the message flow

This message SLSFCT Sales forecast
Usually followed by ORDERS Purchase order

Structure

Mandatory segments in SLSFCT (directory D.21A)

In UN/EDIFACT directory D.21A, the SLSFCT message has 25 segment positions arranged in 7 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG1 (NAD)
  • SG5 (LOC)
  • UNT

Practical example

SLSFCT in practice

A drugstore chain shares a 13-week forecast with a health products supplier each week, by item and distribution center, including expected promotional uplifts. The supplier's planning system loads the SLSFCT, plans production against it and flags weeks where forecast demand exceeds capacity.

Implementation

Implementation considerations for SLSFCT

  • Agree forecast horizon, granularity and update frequency.
  • Distinguish baseline and promotional forecasts.
  • Compare forecasts with sales reports to measure accuracy.
  • Treat forecasts as planning data, not as orders.

How ECOM helps

Automate SLSFCT with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related planning and inventory messages

All 6 planning and inventory messages

Need help with SLSFCT?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us