Skip to main content

Recommended data flow

This section will try to describe the recommended data flow between the WMS and TRAEDE. Starting by receiving new goods, then delivering orders and lastly looking at inventory adjustments. In all the following examples the export delivery mechanism is “JSON Webhooks”, but this can be replaced with another delivery mechanism as described in the previous section.

1. Importing product master data​

  1. The WMS periodically imports product master data by polling the endpoint. This can also be delivered by webhook.

2. Receiving goods at the WMS​

  1. The user will create a purchase order with expected quantities and expected delivery date in TRAEDE.
  2. The user will click a button in TRAEDE named “push production order to 3PL”. This will trigger a delivery of the production order to the WMS.
  3. TRAEDE will queue a delivery of the production order to the webhook endpoint specified in the integration settings
  4. The integrator will convert the received data into the WMS’ format and save the purchase order in the system
  5. Once the purchase order is received at in the WMS the integrator will send data of how many goods were received to TRAEDE
  6. This will put the same goods in stock in TRAEDE and mark the production order as “Received”

3. Shipping orders​

  1. The user will create a shipment in TRAEDE. A shipment is a picking list instruction / order for the WMS.
  2. TRAEDE will queue a delivery of the shipment to the webhook endpoint specified in the integration settings
  3. The integrator will convert the received data into the WMS’ format and save the shipment in the system
  4. Once the shipment has been picked and T&T has been generated the integrator will send data of how many colli, T&T and how many pieces were shipped back into TRAEDE
  5. This will mark the Shipment as “Completed” in TRAEDE and send T&T and invoice to the customer

4. Making inventory adjustments​

  1. If the warehouse makes any manual inventory adjustments (meaning not sending orders or receiving POs) then these should be sent to the manual adjustment endpoint

5. Nightly inventory sync​

  1. It is recommended that the WMS sends a full inventory balance to the inventory sync endpoint once every night. This will make sure that the 2 inventory systems are re-synced from small intra day synchronization errors

6. Return RMAs​

Return RMAs is when there is created a pre-advice in TRAEDE to indicate that goods are expected to be returned to the warehouse. Once returned the RMA will be received - similarly to how a PO is received. Once received TRAEDE will issue a credit note to the customer

  1. The user will create a Return RMA in TRAEDE. A Return RMA will contain expected quantities that will be returned to the warehouse.
  2. The user will click a button in TRAEDE named "Push return to 3PL". This will trigger a delivery of the Return RMA to the WMS via webhook if setup. Alternatively, you can fetch returns via the API.
  3. The integrator will convert the received data into the WMS' format and save the Return RMA in the system.
  4. Once the Return RMA is received in the WMS, the integrator will send data of how many goods were returned to TRAEDE.
  5. This will mark the Return RMA as "Received" in TRAEDE and put the same goods back in stock and issue a credit note to the customer.

7. Ad hoc returns​

Ad hoc returns are primarily used for B2C orders, but can be used to create credit notes in TRAEDE for returns that have no RMA associated with it. For Ad hoc returns you simply state the original order number and the goods returned and then TRAEDE will issue a credit note

  1. The customer (usually a B2C customer) will return the goods to the warehouse
  2. The WMS sends a message to TRAEDE with the original order number and the goods received
  3. TRAEDE issues a credit note to the customer