...
- All order rows that are added by campaigns using the campaign processor (endpoint CustomerOrderCampaignProcessor) must be included in POST request. These order rows must should if possible be marked with the used promotionName to prevent limited campaigns to be used multiple times.
- Expanded bill of material children order rows (having property billOfMaterialsParentRowPosition set in response from campaign processor) must not be included in POST request.
The endpoint CustomerOrderATP will ignore campaigns and product auto order. CustomerOrderATP is supposed to handle delivery information, ie balance and dates.
...
Both CustomerOrders POST and CustomerOrderATP can have the possibility to process campaigns if promotion property is set on customerOrderHeader:
"Promotion": {"usePromotions": "true","PromotionCode": "MegaSale2020"}
...
Notes for bill of materials response:
Rows having property billOfMaterialsParentRowPosition set in response from campaign processor must not be included in CustomerOrders POST request when placing the order.
Product auto order
Auto order request:
...
View file | ||||
---|---|---|---|---|
|
Notes for auto order
Rows having property isResultOfPromotion set in response from campaign processor must be included in CustomerOrders POST request when placing the order.
Campaign 50% off with promotion code
Campaign 50% off request:
View file | ||||
---|---|---|---|---|
|
Campaign 50% off response:
View file | ||||
---|---|---|---|---|
|
Notes for Campaign request and response
Request:
Response:
Rows having property isResultOfPromotion set in response from campaign processor must be included in CustomerOrders POST request when placing the order.