Demand-Driven Replenishment
This page is outdated. Please go to our new documentation under https://docs.fulfillmenttools.com/documentation.
Summary
This page describes use cases where replenishments for items are made in specific time intervals based on demand or where products can be produced on demand. In that case, systems should often allow customer orders to be accepted without being limited by current stock levels until the point in time when the purchase order is placed or production schedules are defined.
Use Case Examples
Short replenishment cycles
A company offers lots of seasonal products which, naturally, are subject to high fluctuations in demand. In addition, these products can be replenished in a short time and the user knows already when orders will arrive. Thus, purchasing agents monitor already accepted customer orders and place purchase orders based on demand to avoid over-stock. As a result, there is no stock limit on the number of customer orders that can be accepted until the purchase order is placed.
Internal production facility
A company produces some goods internally. To prevent overproduction, the production schedule is made based on current demand levels. As a result, there is no stock limit on the number of customer orders that can be accepted until the production schedule is defined.
Implementation in fulfillmenttools
The described use case is mapped by creating purchase orders with a very high amount of products and allowing shop systems to access the thereby created expected stock.
1. Create listings for products that should be available in large quantities
In most set-ups, listings should already be created for all products that are managed via fulfillmenttools' systems. Still, make sure that a listing exists for each relevant product. If goods are perishable and/or should only be available for a certain time frame, stockProperties and/or stockAvailableUntil must be configured. See here for more details.
ID of facility you want to get its listing
PUT / HTTP/1.1
Host: %%HOST%%
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 529
{
"listings": [
{
"attributes": [
{
"category": "descriptive",
"key": "%%subtitle%%",
"priority": 100,
"value": "585er Gold"
}
],
"imageUrl": "text",
"price": 1200,
"tenantArticleId": "4711",
"title": "Adidas Superstar",
"weight": 1,
"scanningRule": {
"values": []
},
"scannableCodes": [
"text"
],
"outOfStockBehaviour": "BACKORDER",
"availabilityTimeframe": {
"start": "2020-02-03T08:45:50.525Z"
},
"tags": [],
"measurementUnitKey": "liter",
"stockProperties": {
"ANY_ADDITIONAL_PROPERTY": {
"inputType": "DATE",
"required": true,
"defaultValue": "text"
}
},
"legal": {
"hsCode": "text"
}
}
]
}No content
2. Create a purchaseOrder
Create a purchaseOrder including all items that have not been ordered yet but should be already available for sale and not be limited by current stock levels.
Choose a high number for the
quantity.valueofrequestedItemsDefine the date when the delivery is expected to arrive in
requestedDate.valueand setrequestedDate.typeto "TIMEPOINT"Include as many items as possible in one purchaseOrder rather than creating one purchaseOrder for each item for that a very high stock should be assumed. However, please consider the limit of 200 tenantArticleIds per purchaseOrder.
This field is deprecated. Set the status to 'CANCELED' Set the purchaseOrder to 'cancelled'. No further deliveries will be expected. Already received goods are unaffected.
Attributes that can be added to this entity. These attributes cannot be used within fulfillment processes, but enable you to attach custom data from your systems to fulfillmenttools entities.
Time and date at which the order was placed. Note: This does not refer to the creation date of this entity in the system.
Time and date at which the order is expected to arrive. Use 'ASAP' for deliveries with unknown date, but be aware that some features will not include these orders.
POST /api/purchaseorders HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 334
{
"customAttributes": {},
"facilityRef": "text",
"orderDate": "2025-07-11T17:33:59.338Z",
"requestedDate": {
"type": "ASAP",
"value": "2025-07-11T17:33:59.338Z"
},
"requestedItems": [
{
"customAttributes": {},
"quantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"tenantArticleId": "text"
}
],
"status": "OPEN",
"supplier": {
"name": "text"
}
}{
"created": "2025-07-11T17:33:59.338Z",
"customAttributes": {},
"facilityRef": "text",
"id": "text",
"inboundProcessRef": "text",
"lastModified": "2025-07-11T17:33:59.338Z",
"orderDate": "2025-07-11T17:33:59.338Z",
"requestedDate": {
"type": "ASAP",
"value": "2025-07-11T17:33:59.338Z"
},
"requestedItems": [
{
"customAttributes": {},
"quantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"tenantArticleId": "text"
}
],
"status": "OPEN",
"supplier": {
"name": "text"
},
"transfer": {
"id": "text"
},
"version": 1
}3. Enable shop systems to communicate expected stock in sales availability
Use one of the below endpoints to query stock availability in your shop's detail pages and in the checkout journey. By that, it is ensured that expected stock is considered in the shop availability. Go here to get more information on the checkout options endpoints.
Before using the delivery/earliest and delivery/timeperiod endpoints, the transit time in the carrier country service mapping for the requested carrier(s) must be configured.
The list of items depicts the items you would like to get information about their earliest possbile delivery. The provided list of tenant article ids are considered individual (as if not in a basket together, but seperately ordered). Additionally you can add information about the address these items should be delivered to to further refine the response.
The date from which to search for the earliest potential delivery date. Defaults to "now" (timestamp of the request)
2024-06-01T00:00:00.000ZThe tenant articleIds for which the check is performed. The provided items are considered individually.
DE-ZGT-4711Set this flag to true to get additional information about the availability of the requested articles
POST /api/promises/checkoutoptions/delivery/earliest HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 315
{
"earliestDeliveryDate": "2024-06-01T00:00:00.000Z",
"tenantArticleIds": [
"DE-ZGT-4711"
],
"consumerAddress": {
"city": "Langenfeld",
"country": "DE",
"province": "NRW",
"houseNumber": "42a",
"postalCode": "40764",
"street": "Hauptstr.",
"addressType": "POSTAL_ADDRESS"
},
"includeCalculationHints": true,
"filter": {
"customAttributes": {}
}
}{
"checkoutOptions": [],
"calculationHints": [
"text"
]
}The basket attribute depicts the items you would like to get details about their possbile delivery. All the provided tenantArticleIds within the basket are considered together (as if they are in the same basket/order). Additionally you can add information about the address these items should be delivered to to further refine the quality of the response.
The start of the evaluated time period. Defaults to "now" (timestamp of the request)
nowExample: 2024-06-03T00:00:00.000ZThe end of the evaluated time period. Default is the start date + 30 days. Please note that the maximum time period can not exceed 45 days.
2024-07-13T00:00:00.000ZSet this flag to true to get additional information about the availability of the requested articles
POST /api/promises/checkoutoptions/delivery/timeperiod HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 514
{
"startDate": "2024-06-03T00:00:00.000Z",
"endDate": "2024-07-13T00:00:00.000Z",
"basket": [],
"consumerAddress": {
"city": "Langenfeld",
"country": "DE",
"province": "NRW",
"houseNumber": "42a",
"postalCode": "40764",
"street": "Hauptstr.",
"addressType": "POSTAL_ADDRESS"
},
"deliveryPreferences": {
"preferredCarriers": [
"text"
],
"preferredCarriersWithProduct": [],
"preselectedFacilities": [
null
],
"serviceLevel": "DELIVERY",
"carrierProductCategory": "STANDARD",
"desiredDeliveryTime": "2020-02-03T09:45:51.525Z"
},
"includeCalculationHints": true
}{
"checkoutOptions": [],
"calculationHints": [
"text"
]
}The desired delivery date. (timestamp of the request)
2024-06-03T00:00:00.000ZThe tenant articleIds for which the check is performed. The provided items are considered individually.
DE-ZGT-4711POST /api/promises/checkoutoptions/delivery/timepoint HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 101
{
"desiredDeliveryDate": "2024-06-03T00:00:00.000Z",
"tenantArticleIds": [
"DE-ZGT-4711"
],
"facilities": []
}{
"items": []
}4. Create a new purchaseOrder
Before patching the existing purchaseOrder (created in step 2) with the actually ordered quantity, a new purchaseOrder with large quantities needs to be created. This ensures that the systems can already accept customer orders that should be fulfilled within next production or replenishment cycle. See step 2 for this.
5. Patch purchaseOrder with actual quantity
Once the purchase order was placed or the production schedule was defined, patch requested items in purchase order with quantities that were actually ordered or planned to be produced. Adjust stock properties such as expiry date if necessary.
This field is deprecated. Set the status to 'CANCELED' Set the purchaseOrder to 'cancelled'. No further deliveries will be expected. Already received goods are unaffected.
Attributes that can be added to this entity. These attributes cannot be used within fulfillment processes, but enable you to attach custom data from your systems to fulfillmenttools entities.
PATCH /api/purchaseorders/{purchaseOrderId} HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 325
{
"customAttributes": {},
"orderDate": "2025-07-11T17:33:59.338Z",
"requestedDate": {
"type": "ASAP",
"value": "2025-07-11T17:33:59.338Z"
},
"requestedItems": [
{
"customAttributes": {},
"quantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"tenantArticleId": "text"
}
],
"status": "OPEN",
"supplier": {
"name": "text"
},
"version": 1
}{
"created": "2025-07-11T17:33:59.338Z",
"customAttributes": {},
"facilityRef": "text",
"id": "text",
"inboundProcessRef": "text",
"lastModified": "2025-07-11T17:33:59.338Z",
"orderDate": "2025-07-11T17:33:59.338Z",
"requestedDate": {
"type": "ASAP",
"value": "2025-07-11T17:33:59.338Z"
},
"requestedItems": [
{
"customAttributes": {},
"quantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"tenantArticleId": "text"
}
],
"status": "OPEN",
"supplier": {
"name": "text"
},
"transfer": {
"id": "text"
},
"version": 1
}6. Create stock after delivery has arrived or products are produced
If the delivery of the ordered products has arrived or the production was finished, a receipt needs to be added to the inbound process of the purchase order to create stock. Use the GET /api/purchaseorders/{purchaseOrderId} endpoint to query the inboundProcessRef if not sure about the inboundProcess that the purchase order belongs to.
enables mapping a receipt to one of the ASNs in this inbound process
Attributes that can be added to this entity. These attributes cannot be used within fulfillment processes, but enable you to attach custom data from your systems to fulfillmenttools entities.
date-time of the arrival of the items in the facility
status of this receipt, only receipts with status 'FINISHED' are booked. IN_PROGRESS can be used to save partial receipts.
POST /api/inboundprocesses/{inboundProcessId}/receipts HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 416
{
"asnRef": "text",
"comments": [
{
"content": "text",
"userRef": "text"
}
],
"customAttributes": {},
"receivedDate": "2025-07-11T17:33:59.338Z",
"receivedItems": [
{
"acceptedQuantity": {
"unit": "text",
"value": 1
},
"comments": [
{
"content": "text",
"userRef": "text"
}
],
"customAttributes": {},
"rejectedQuantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"storageLocationRef": "text",
"tenantArticleId": "text"
}
],
"status": "OPEN"
}{
"asnRef": "text",
"comments": [
{
"content": "text",
"documentSetRef": "text",
"id": "text",
"userRef": "text"
}
],
"customAttributes": {},
"id": "text",
"receivedDate": "2025-07-11T17:33:59.338Z",
"receivedItems": [
{
"acceptedQuantity": {
"unit": "text",
"value": 1
},
"comments": [
{
"content": "text",
"documentSetRef": "text",
"id": "text",
"userRef": "text"
}
],
"customAttributes": {},
"id": "text",
"rejectedQuantity": {
"unit": "text",
"value": 1
},
"stockProperties": {
"expiry": "text"
},
"storageLocationRef": "text",
"tenantArticleId": "text"
}
],
"status": "OPEN"
}Last updated
Was this helpful?