Skip to main content

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. Read more under Recommended data flow

The return object

ParameterRequiredDefaultDescription
rmaYesThe RMA of the return
statusYesThe status of the return. Possible values: open, approved, received, credited
customer_numberYesThe customer number of the return
customerYesThe name of the customer of the return
customer_metaYes{}An object with {"key": "value"} with custom meta data of the return. See custom fields for more information
customer_vat_numberYesThe VAT number of the customer
currencyYesThe currency of the return
notesnullOptionally some notes to the return delivery
return_metaobject{}An object with {"key": "value"} with custom meta data of the return. See custom fields for more information
created_atYes
updated_atYes
linesYesArray of object lines

Lines

ParameterRequiredDefaultDescription
product_nameYesThe name of the product. This is the name of the product without attributes (Color, Size, etc.)
item_numberYesThe item number of the product. NOTE: This is the number on the product-level, not variant-level. For variant-level refer to sku
attributesYesAn object with {"key": "value"} with the attributes of the variant. This will be Colors, Sizes, etc.
full_nameYesThe name of the product plus its attributes. Use this for delivery notes and packing lists
skuYesThe unique identifier of this specific variant. Use this for identification in your WMS
eannullThe EAN code of this variant
country_of_originnullCountry of origin of the product. This is given as a 2-letter ISO code (DK, DE, etc.)
compositionnullThe composition of the product (materials)
hs_tariff_codenullThe HS Tariff Code of the product
returnedYes0The number of pieces that was received at the warehouse
expected_quantityYesThe number of pieces that is expected to be received on the return delivery

Get returns

Endpoint: GET /3pl/returns

Available properties for filtering: customer_id, created_at, updated_at

caution

It is recommended to use the Export version of this API to get returns out of TRAEDE. The export version will allow you to easily keep track of returns you have already exported and only serve you with new returns.

Data of response

ParameterRequiredDefaultDescription
returns.*YesAn array of Return RMA
totalYesThe total number of returns

Export returns

Endpoint: GET /3pl/returns/export

This is a version of the GET returns API that is designed to be used for exporting returns to a WMS system. It is recommended to read our Introduction to the Export system to get a better understanding of how the export system works. Note this endpoint is different than the Export Returns API. In this endpoint the data is formatted in the same manner as the 3PL API GET returns endpoint. In the normal returns API the data is normalized. It is recommended to use this endpoint instead of the normal GET returns endpoint, since it's easier to use.

You can add a date+time to the query string using the parameter not_exported_since in return to re-export returns that have already been exported

Available properties for filtering: created_at, updated_at (NOTE: These filters have to be added using our Filters Syntax, however system_id and not_export_since should be added as a normal query string parameter)

The endpoint will fetch all returns that have not been exported yet

Available query parameters

ParameterData typeRequiredDefaultDescription
system_idstringYesA string identifying the system the returns should be exported to. This is used so returns can be exported to multiple systems.
not_exported_sincedatetime (UTC)Current timeAdd this to re-export returns that have already been exported. Note the timezone should be UTC
include_draftsinteger0Export draft RMAs. 0 = only export non-draft RMAs. 1 = also include draft RMAs in export
include_receivedinteger0Export already received RMAs. 0 = only export non-received RMAs. 1 = also include received RMAs in export
filter_groupsArray<Filters>Optional filters to add. See which filters are available above

Data of response

ParameterRequiredDefaultDescription
returns.*YesAn array of object 3PL API return)

Receiving a return

Marking a return as received

Endpoint: POST /3pl/returns/receive

ParameterRequiredDefaultDescription
returnYesObject of return

Return

ParameterRequiredDefaultDescription
rmaYesThe identifier of the return delivery
linesYesArray of object lines

Delivery note lines

ParameterRequiredDefaultDescription
skuYes, if no ean is givenThe SKU of the line
eanYes, if no sku is givenThe EAN of the line
received_quantityYesThe number of pieces that were received

Example

POST /3pl/returns/receive

{
"return": {
"rma": "1000-1",
"lines": [
{
"sku": "1000-Black-S",
"received_quantity": 10
},
{
"sku": "1000-Black-M",
"received_quantity": 10
}
]
}
}

Mark return as exported

caution

NOTE It is highly recommended to read our Export Returns guide on how the Export API works

Endpoint: POST /3pl/returns/mark-as-exported

ParameterData typeRequiredDefaultDescription
returnsArray<Returns that have been exported>YesReturns that have been exported. You can at a max mark 10 returns at a time

Returns that have been exported

ParameterData typeRequiredDefaultDescription
return_idintYesThe ID of the return that has been exported
system_idstringYesA string identifying the system the returns should be exported to. This is used so returns can be exported to multiple systems.
notestringAny notes regarding the sync you want to add. These will be displayed in the timeline of the return