Inbound Process
Last updated
Was this helpful?
Last updated
Was this helpful?
An inbound process maps all processes around incoming goods in a store or warehouse. This can include delivery of goods but also interfacility transfers or similar processes. Whenever a purchaseOrder or a receipt is created, a corresponding inboundProcess is automatically created as well.
An overview of all inbound process can be found in the or in the . Incoming goods can be accepted via the of our inventory app. The event of checking and accepting incoming goods is represented via .
The inbound process has sub-entities, which can be created and modified as part of the inbound process, or alternatively via their own endpoints.
A purchase order is issued when new stock is ordered for a store or warehouse. It includes the following information:
Mandatory values:
facilityRef
: facility for which the order is destined
purchaseOrder
:
orderDate
: time and date on which order was placed
requestedDate
: time and date on which order is expected to arrive
requestedItems
:
tenantArticleId:
unique identifier for item
quantity:
quantities and units of ordered items (maximum of 200 items can be processed)
Optional values:
tenantInboundProcessId:
unique identifier for inbound used in the customer systems
onHold
: Setting an inbound process on hold means that it should be paused for now. Can be set manually via Backoffice or via API. By setting the flag to true
, the inboundProcess status is set to onHold
.
scannableCodes
: scannableCodes such as barcodes that are relevant in the inboundProcess, e.g. , barcode of the delivery note
purchaseOrder
:
requestedItems:
cancelled
: If no further deliveries are expected, a purchaseOrder can be cancelled by an admin via Backoffice or via API. This is also possible, if several items have already been accepted. By setting the flag to true
, the inboundProcess status is set to closed
.
supplier
: information on supplier of delivery (name)
customAttributes
After a goods receipt was performed and goods have been accepted, a receipt is issued that adds the stock to the facility. It includes the following information:
Mandatory values:
receivedDate
: date when the order was accepted in the facility
receivedItems
: for each item that was announced via purchaseOrder the following information can be provided:
tenantArticleId:
unique identifier for item
acceptedQuantity
: quantity that was accepted in the goods receipt
rejectedQuantity
: Quantity that was rejected in the goods receipt (due to being, e.g., broken).
comments
: information relevant for that specific lineItem such as comments, photos, or other attachments
comments
: information relevant for that specific delivery such as comments, photos, or other attachments
Rejected items are not a subset of accepted items and are not booked to the facility as stock.
Optional values:
asnRef:
can be used to store the reference to an internal advanced shipping note
receivedItems
: for each item that was announced via purchaseOrder the following information can be provided:
storageLocationRef
: the storage location on which the item was placed
comments
: information relevant for that specific delivery
status
: If a goods receipt has been started via inventory app, the status of the receipt changes to IN_PROGRESS
and then to FINISHED
after the process was completed in the app.
customAttributes
: Attributes that can be added to the receipt. These attributes cannot be used within fulfillmenttools' processes, but can be used to carry custom information on receipt.
The inboundProcess itself as well as its sub-entities can have different status. Our clients show the status that are most relevant to the user in the inbound view and in the inventory app.
OPEN
Delivery has not arrived yet
inboundProcess
PARTIAL_DELIVERY
Items in the delivery were missing
inboundProcess
CLOSED
All items that were announced via purchase order have arrived (either as accepted or rejected quantity) or purchase order was cancelled.
inboundProcess
ON_HOLD
Inbound process should be paused for now. Can be set manually via Backoffice or via API.
inboundProcess
CANCELLED
No further deliveries are expected. No real status, can be either true or false. Can be set manually via Backoffice or via API.
purchaseOrder
OPEN
No functional meaning
purchaseOrder
IN_PROGRESS
Goods receipt for (one part of the) delivery has been started (via inventory app)
receipt
FINISHED
Goods receipt for (one part of the) delivery has been finished (via inventory app)
receipt
If there is a measurementUnitKey defined for a listing that is part of the inboundProcess, each new line item in inboundProcess.purchaseOrder.requestedItems and inboundProcess.receipts.receivedItems is validated against it: All quantities MUST match the unit of the Listing.
If there are stockProperties defined for a listing that is part of the inboundProcess, each new line item in inboundProcess.purchaseOrder.requestedItems and inboundProcess.receipts.receivedItems is validated against it. The validation for requested and received items behaves slightly different as we do not expect systems to know the exact properties of all items before they have arrived.
All stockProperties that are part of the requestedItems must also be defined in the stockProperties of the listing.
Not all stockProperties that are part of the listing must also be present in the requestedItems.
This means, it is allowed to create a purchaseOrder without stockProperties in the requestedItems even though the included listing has stockProperties defined.
All stockProperties that are part of the receivedItems must also be defined in the stockProperties of the listing.
Not all stockProperties that are part of the listing must also be present in the requestedItems. Only stockProperties where required
is true need to be present in both listing and receivedItems. This is because creating a stock without providing a value for a required
property is forbidden and will fail.
customAttributes
: can be used to carry custom information that might be of interest to connectors or services outside of fulfillmenttools. For more information see .
stockProperties
: information on of requested items such as expiry date
: information specific to that lineItem such as expiry date or batch number
For more information on measurementUnits, click .
For more information on stockProperties on listing, click .
25
Matches partial values; The queries terms and therefore the result set of the query can change in the future:
Only matches complete values; The queries terms and therefore the result set of the query can change in the future:
25
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.
Facility in which the inbound process takes place
Indicates if the inbound process is on hold and will not be processed further
scannableCodes such as barcodes that are relevant in the inboundProcess, e.g. , barcode of the delivery note
Identifier of the process provided by the tenant system. It is recommended to be unique
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.
Line items which are expected to be delivered.
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.
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.
Line items which are expected to be delivered.
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.
Line items which are expected to be delivered.
enables mapping a receipt to one of the ASNs in this inbound process
comments regarding the receipt itself
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
list of item that arrived in the facility
status of this receipt, only receipts with status 'FINISHED' are booked. IN_PROGRESS can be used to save partial receipts.
enables mapping a receipt to one of the ASNs in this inbound process
comments regarding the receipt itself
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
list of item that arrived in the facility
status of this receipt, only receipts with status 'FINISHED' are booked. IN_PROGRESS can be used to save partial receipts.