Tradecloud API v2 manual
  • Introduction
    • Welcome
      • Checklist
      • Support
    • API
      • Rules
      • Requests
      • JSON versus XML
      • Environments
      • Standards
      • Compatibility
      • Tools
        • Swagger UI
        • Postman
        • .NET SDK
      • Webhook versus polling
        • Polling usage
        • Polling echo
      • Delivery schedule
    • Security
      • Security overview
      • Authentication
      • Authorization
      • Encryption
      • Document storage
  • Guide
    • 1. Getting an Account
    • 2. Sending your first order
      • Option A: Sending a Delivery Schedule per order line
      • Option B: Sending a Single Delivery per order line
  • Processes
    • Forecasts
      • Issue a new forecast
      • Issue a new Slimstock forecast
    • Orders
      • Buyer order process
        • Issue a new order
          • Delivery schedule
          • Indicators
          • No delivery expected
          • Propose when accepted
          • Attach a document to an order
          • Choose attach document API
        • Update an existing order
        • Receive an order response
          • Download a document attached to an order response
          • Single delivery order response
        • Receive goods
        • Complete an order
        • Reopen an order
        • Cancel an order
      • Supplier order process
        • Receive an order
          • Download a document attached to an order
          • Single delivery order
        • Send order response
          • Attach a document to an order response
        • Reopen an order
        • Cancel an order
    • Shipments
      • Supplier shipment process
        • Send despatch advice
      • Buyer shipment process
        • Receive a shipment event
          • Download a document attached to a shipment
Powered by GitBook
On this page
  • Forecast process
  • Endpoint
  • Header
  • Lines
  • Item
  • issueDateTime
  1. Processes
  2. Forecasts

Issue a new forecast

How to issue a forecast as a buyer

PreviousForecastsNextIssue a new Slimstock forecast

Last updated 1 year ago

Forecast process

As buyer you can send a new forecast to Tradecloud.

A forecast cannot be updated. Issued forecasts will always be appended to the existing set of forecasts.

Endpoint

Use the endpoint to send a forecast to Tradecloud.

When sending a forecast the provided supplier account number will be verified.

Header

  • companyId: the optional Tradecloud company identifier. You only have to provide a companyId when your integration user account has authorization for multiple companies.

  • supplierAccountNumber: the supplier account number as known in your ERP system.

The supplierAccountNumber must be set in the Tradecloud connection in the portal, after the connection request has been accepted.

  • forecastNumber: the mandatory forecast identifier, like code or number as known in your forecast or ERP system. The number must be the same for all items for all suppliers in the same generated forecast.

The forecastNumber must not contain whitespace characters.

Lines

lines: a forecast contains one or multiple lines. A forecast line consists of an item and forecast schedule. It is structured as a JSON element in the lines JSON array.

Item

lines.item: the forecasted item (or article, goods).

  • buyerItemNumber: the mandatory item code or number as known in your ERP system.

  • buyerItemRevision: the revision (or version) of this item number.

  • buyerItemName: the mandatory item short name.

  • supplierItemNumber: the item code or number as known at the supplier. Required in case of wholesale suppliers.

  • purchaseUnitOfMeasureIso: the purchase unit according to ISO 80000-1, a typical example is PCE.

buyerItemNumber should be unique within your company and never change. Never renumber or re-use buyerItemNumbers.

lines.schedule: the forecast schedule lines for this item, each consisting of a forecast period and forecasted demand during this period. It is structured as a JSON element in the schedule JSON array.

  • endDate: the last day of this forecast period.

  • quantity: the forecasted demand of this item, in this period, for this supplier. Quantity has a decimal 1234.56 format with any number of digits.

issueDateTime

startDate: the first day of this forecast period. Date has ISO 8601 date yyyy-MM-dd format. See also .

issueDateTime: Date and time the forecast was originally issued in your forecast or ERP system. DateTime has ISO 8601 local date/time format yyyy-MM-ddThh:mm:ss. See also .

Send forecast
Standards
Standards