Booking reasons

Posting history reports or reports using the REST API output posting reasons with an internal ID.

The IDs include:

  • 1: shipped item
  • 2: Reservation cancelled
  • 3: Reserved
  • 4: Goods receipt
  • 5: Returns
  • 6: Stock transfer
  • 7: Packed
  • 8: Inventory input
  • 9: Inventory output
  • 10: Inventory stock transfer


wemalo connect rest api

The documentation for the interface wemalo connect REST API can be found here: connect-api.wemalo.com



Container management via REST

Creation/editing of containers: http://connect-api.wemalo.com/#api-Product-addUnit
Loading the available container units: http://connect-api.wemalo.com/#api-Product-getUnits

In addition: when creating a GR order, the ID of the container unit can be entered in the position: http://connect-api.wemalo.com/#api-GoodsReceipt-addGoodsReceipt
There is now the parameter “productUnitId”.

Example:

For one product a container unit “advantage pack 5 pieces” is created. This container unit contains 5 pieces of said product.
When the goods receipt is transmitted, this container unit can be specified with a number of pieces, e.g. 2 pieces.
In this case wemalo expects 10 pieces of the product (2 times the container with 5 pieces = > 2*5=10).



REST API workflow

Is using wemalos rest api, at least the following calls might be used for interacting with wemalo.

First of all, an account needs to be set up for you. You’ll get a rest api token that is being used for authorization. Please see header information: Authorization

Product master data

Orders