Articles

Introduction

Every line item of the fulfillmenttools order and the operative entities, like pick jobs or pack jobs, contains an article. This article contains all the basic information about the product of this line item, like a title, the identifier tenantArticleId or an imageUrl. The line item itself holds all meta information, like the ordered amount for an order or the picked amount for a pick job.

Detailed information about the article data can be found e.g. in the order REST API documentation.

Articles are no separate entity on our platform. They are part of a line item, and this line item is part of e.g. an order, pick job, or handover job.

How is the article used?

The article identifies the line item comprehensively within the fulfillmenttools platform. It will be used for routing decisions or reservations. Using the tenantArticleId, it is possible to determine, for example, which order line item a pick job line item originated from.

Facts

• Listings with the same tenantArticleId might hold different information about the (same) product.

• Please note the difference between articles and listings.

Example

In this example, fulfillmenttools receives an order, and we make a decision in which facility the order is routed. For this, the tenantArticleId within article is important.

1. An order with a line item arrives at fulfillmenttools. The line item is an apple and contains the article with the tenantArticleId 4711.

2. Facility A has apples but with the tenantArticleId 0815, this is the wrong facility for this order.

3. Facility B contains the right apples with the tenantArticleId 4711, the order will be routed into Facility B.

4. For Facility B a pick job was created. All the information from the article in the order line item will be taken and enriched by the information from the listing.