Fulfillment

On this page

Fulfilment Product Activation

Method : SubmitFulfilmentActivation

Sample XML payload provided the following operations :

<cdis:SubmitFulfilmentActivation> <cdis:request> <cdis:ProductList> <cdis2:ProductActivationData> <cdis2:Action>{{Action}}</cdis2:Action> <cdis2:Height>{{Height}}</cdis2:Height> <cdis2:Length>{{Length}}</cdis2:Length> <cdis2:ProductEan>{{ProductEan}}</cdis2:ProductEan> <cdis2:SellerProductReference>{{SellerProductReference}}</cdis2:SellerProductReference> <cdis2:Weight>{{Weight}}</cdis2:Weight> <cdis2:Width>{{Width}}</cdis2:Width> </cdis2:ProductActivationData> </cdis:ProductList> </cdis:request> </cdis:SubmitFulfilmentActivation>

Route : POST /fulfillment-products

This route does not have any path parameters or body.

All filtering is passed as query string parameters.

Currently available filters are as follows :

  • Order State
  • Order Reference
  • Sorting
  • Pagination
  • SalesChannel filter
  • Date filters
TopicSOAP TagREST Parameter
Creation DateStates > OrderStateEnum [ multi ]NONE
Modification DateModification DateModification Date
Discussion status
EndModificationDate
DiscussionStateFilter
DiscussionType
OrderNumberList
ProductEanList
ProductSellerReferenceList

Example

The following payload :


 <GetDiscussionList>
    <discussionFilter>
        <BeginModificationDate>2023-11-15</BeginModificationDate>
        <EndModificationDate>2023-11-17</EndModificationDate>
        <StatusList>
            <DiscussionStateFilter>Open</DiscussionStateFilter>
        </StatusList>
        <DiscussionType>Discussion</DiscussionType>
    </discussionFilter>
</GetDiscussionList>

Can now be replaced with the following call :

GET /discussions

?isOpen=true

&subTypologyCode=Discussion

&updatedAtMin=2023-11-15

&updatedAtMax=2023-11-17

Create Fulfilment Supply Order

Method : SubmitFulfilmentSupplyOrder

Sample XML payload provided the following operations :

<cdis:SubmitFulfilmentSupplyOrder> <cdis:request> <cdis:ProductList> <cdis:FulfilmentProductDescription> <cdis:ExternalSupplyOrderId>{{ExternalSupplyOrderId}}</cdis:ExternalSupplyOrderId> <cdis:ProductEan>{{ProductEan}}</cdis:ProductEan> <cdis:Quantity>{{Quantity}}</cdis:Quantity> <cdis:SellerProductReference>{{SellerProductReference}}</cdis:SellerProductReference> <cdis:Warehouse>{{Warehouse}}</cdis:Warehouse> <cdis:WarehouseReceptionMinDate>{{WarehouseReceptionMinDate}}</cdis:WarehouseReceptionMinDate> </cdis:FulfilmentProductDescription> </cdis:ProductList> </cdis:request> </cdis:SubmitFulfilmentSupplyOrder>

Route : POST /inbound-shipments

This route does not have any path parameters or body.

All filtering is passed as query string parameters.

Currently available filters are as follows :

  • Order State
  • Order Reference
  • Sorting
  • Pagination
  • SalesChannel filter
  • Date filters

Method : SubmitFulfilmentOnDemandSupplyOrder

Sample XML payload provided the following operations :

<cdis:SubmitFulfilmentOnDemandSupplyOrder> <cdis:request> <cdis:OrderLineList> <cdis:FulfilmentOrderLineRequest> <cdis:OrderReference>{{OrderReference}}</cdis:OrderReference> <cdis:ProductEan>{{ProductEan}}</cdis:ProductEan> </cdis:FulfilmentOrderLineRequest> </cdis:OrderLineList> </cdis:request> </cdis:SubmitFulfilmentOnDemandSupplyOrder>
TopicSOAP TagREST Parameter
Creation DateStates > OrderStateEnum [ multi ]NONE
Modification DateModification DateModification Date
Discussion status
EndModificationDate
DiscussionStateFilter
DiscussionType
OrderNumberList
ProductEanList
ProductSellerReferenceList

Example

The following payload :


 <GetDiscussionList>
    <discussionFilter>
        <BeginModificationDate>2023-11-15</BeginModificationDate>
        <EndModificationDate>2023-11-17</EndModificationDate>
        <StatusList>
            <DiscussionStateFilter>Open</DiscussionStateFilter>
        </StatusList>
        <DiscussionType>Discussion</DiscussionType>
    </discussionFilter>
</GetDiscussionList>

Can now be replaced with the following call :

GET /discussions

?isOpen=true

&subTypologyCode=Discussion

&updatedAtMin=2023-11-15

&updatedAtMax=2023-11-17

Check product activation status

Method : GetOrderList

Sample XML payload provided the following operations :


<GetOrderList>
    <orderFilter>
      <BeginCreationDate>{{BeginCreationDate}}</BeginCreationDate>
        <BeginModificationDate>{{BeginModificationDate}}</BeginModificationDate>
        <EndCreationDate>{{EndCreationDate}}</EndCreationDate>
        <EndModificationDate>{{EndModificationDate}}</EndModificationDate>
        <FetchOrderLines>true</FetchOrderLines>
        <States>
            <OrderStateEnum>CancelledByCustomer</OrderStateEnum>
            <OrderStateEnum>WaitingForSellerAcceptation</OrderStateEnum>
            <OrderStateEnum>AcceptedBySeller</OrderStateEnum>
            <OrderStateEnum>WaitingForShipmentAcceptation</OrderStateEnum>
            <OrderStateEnum>Shipped</OrderStateEnum>
            <OrderStateEnum>RefusedBySeller</OrderStateEnum>
            <OrderStateEnum>ShipmentRefusedBySeller</OrderStateEnum>
        </States>
    </orderFilter>
</GetOrderList>

Route : GET /get-orders

This route does not have any path parameters or body.

All filtering is passed as query string parameters.

Currently available filters are as follows :

  • Order State
  • Order Reference
  • Sorting
  • Pagination
  • SalesChannel filter
  • Date filters
Scroll to Top