Posti WMS
Posti Warehouse Integration
Posti WMS integration is part of Posti’s Supply Chain Solution interfaces. Posti Supply Chain Solution supports several supply chain business models
- - warehouse fulfillment
- - drop shipping
- - click & collect
Warehouse fulfillment means principals 3PL warehouse service including all warehouse work for inbound, outbound and warehouse processing with additional services. Drop shipping means order delivery directly from supplier’s warehouse to end customer. See more “Tutorial: Getting started with drop shipping for webshops or suppliers”. Click & collect means order delivery and receival from principal’s store. See more Posti.fi. This description is for warehouse integration.
See usage.
Warehouse Integration Processes
Master Data
Product data is the master data of warehouse process. InItemMaster is used in the warehouse to identify uniquely each principal’s product in a warehouse and to input logistic information to warehouse such as measures which are used to optimize logistic processes inside a warehouse. Product identification is the key that will be used both when goods are coming in to a warehouse and when they are picked from a warehouse as defined in a sales order row data.
Purchase Order
Purchase order processing has two interfaces. InPurchaseOrder initiates warehouse inbound process. All goods coming in must be verified against a purchase order. If purchase order doesn’t exist warehouse will do purchase order manually depending on the service agreement with a principal. Processed purchase orders are confirmed with OutReceiptConfirmation message.
Advanced Shipping Notice (ASN)
Advanced shipping notice can be used instead of purchase order. The difference is that ASN is assumed to have exact information of incoming goods. Goods received with ASN will be processed assuming that there is no need to validate order lines against the purchase order. The goods will be simply received and moved to put away process.
Sales Order
Sales order processing has two alternative input interfaces and three output interfaces. InSalesOrder is a sales order used only in warehouse orders. Order API is an interface that can be used both for warehouse and drop shipping orders (see Tutorial: Drop shipping for webshops or suppliers). Sales order processing in a warehouse is confirmed with
- - OutDeliveryConfirmation is sent after a single shipment has been sent based on the order – an order may generate one to many shipments
- - OutSalesOrderConfirmation is sent after the order has been completely fulfilled by the warehouse
- - Order API can be used to get order status from a warehouse based on data sent by the OutSalesOrderConfirmation
Return Order
Return order processing has two interfaces. InReturnOrder is recommended if principal can send return order to warehouse before return arrives there. Return order would make return processing more efficient because otherwise return order must be created manually to warehouse system based on the information in returned batch.Information about returned goods are send to principal using OutReturnConfirmation.
Stock Keeping
With InUpdateBatch message principal can update stored batches' statuses and product classes (e.g. release batch for picking after maturation or reserve some batch for specific customer by changing its product class).
The other stock keeping messages are used to send information about inventory changes to a principal. Stock keeping messages are
- - OutStockAdjustmentInventory is used to send information of stock changes noted in inventory counting
- - OutStockBalanceInventory is used to get current stock inventory
- - OutStockMovementInventory is used to notify inventory movement from a stock area to another (e.g. from active to guaranteed stock)
| Interface group | Interface purpose | Developer guide | Field list | XML-schema | XML-sample |
|---|---|---|---|---|---|
| Master data | Item data to warehouse | Doc | Excel | Xsd | Xml |
| Item data from warehouse | Doc | Excel | Xsd | Xml | |
| Master data V2 | Item data to warehouse V2 | Doc | Excel | Xsd | Xml |
| Item data from warehouse V2 | Doc | Excel | Xsd | Xml | |
| Purchase order processing | Purchase order | Doc | Excel | Xsd | Xml |
| Advanced Shipping Notice (ASN) | Doc | Excel | Xsd | Xml | |
| Receipt confirmation | Doc | Excel | Xsd | Xml | |
| Sales order processing | Sales order | Doc | Excel | Xsd | Xml |
| Delivery confirmation | Doc | Excel | Xsd | Xml | |
| Sales order confirmation | Doc | Excel | Xsd | Xml | |
| Online integration for B2C-like orders | GLUE Order API | GLUE Order API | |||
| Return order processing | Return order | Doc | Excel | Xsd | Xml |
| Return confirmation | Doc | Excel | Xsd | Xml | |
| Inventory | Batch update | Doc | Excel | Xsd | Xml |
| Stock adjustment inventory | Doc | Excel | Xsd | Xml | |
| Stock balance inventory | Doc | Excel | Xsd | Xml | |
| Stock movement inventory | Doc | Excel | Xsd | Xml | |
| WorkOrder | Work Order | Doc | Excel | Xsd | Xml |
| Work Order Confirmation | Excel | Xsd | Xml |
Usage
Authentication
Authentication is required before making calls to API endpoints. See Authentication API.
API Endpoints
| Environment | Protocol | Host | Base Path |
|---|---|---|---|
| UAT | HTTPS | connect.ja.posti.fi | /kasipallo/warehouse |
| Prod | HTTPS | connect.posti.fi | /warehouse |
Paths
BOM character is not allowed in the XML messages.
| Path | Method | Request Content | Response Codes | Response Content |
|---|---|---|---|---|
| /items/v1 | POST | InItemMasterSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /items/v1 | GET | 200 204 401 500 |
OutItemMasterSchema No content. Authorization error. Error while processing request. |
|
| /items/v2 | POST | InItemMasterSchema_v2 | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /out-items/v2 | GET | 200 204 401 500 |
OutItemMasterSchema No content. Authorization error. Error while processing request. |
|
| /purchaseOrder/v1 | POST | InPurchaseOrderSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /advanceShippingNotice/v1 | POST | InAdvanceShippingNoticeSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /receiptConfirmation/v1 | GET | 200 204 401 500 |
OutReceiptConfirmationSchema No content. Authorization error. Error while processing request. |
|
| /salesOrders/v1 | POST | InSalesOrderSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /salesOrderConfirmation/v1 | GET | 200 204 401 500 |
OutSalesOrderConfirmationSchema No content. Authorization error. Error while processing request. |
|
| /returnOrder/v1 | POST | InReturnOrderSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /returnOrderConfirmation/v1 | GET | 200 204 401 500 |
OutReturnConfirmationSchema No content. Authorization error. Error while processing request. |
|
| /updateBatch/v1 | POST | InUpdateBatchSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /stockAdjustmentInventory/v1 | GET | 200 204 401 500 |
OutStockAdjustmentInventorySchema No content. Authorization error. Error while processing request. |
|
| /stockBalanceInventory/v1 | GET | 200 204 401 500 |
OutStockBalanceInventorySchema No content. Authorization error. Error while processing request. |
|
| /stockMovementInventory/v1 | GET | 200 204 401 500 |
OutStockMovementInventorySchema No content. Authorization error. Error while processing request. |
|
| /deliveryConfirmations/v1 | GET | OutDeliveryConfirmation | 200 400 401 500 |
OutDeliveryConfirmation No content. Authorization error. Error while processing request. |
| /workOrders/v1 | POST | InWorkOrderSchema | 200 400 401 500 |
PostixmlServiceResponse with resultMessage: Request received successfully! Bad request. Authorization error. Error while processing request. |
| /workOrderConfirmation/v1 | GET | 200 204 401 500 |
OutWorkOrderConfirmationSchema No content. Authorization error. Error while processing request. |