The Order Service has Entities and Operations concerned with orders created in Norce [Storm].
The Order Service has Entities and Operations concerned with orders created in Norce [Storm].
A post of the Order Request for the ERP or OMS,
Read more about the how to implement a receiver here
Usually weborder number (basket id in Norce Commerce). For orders from external source this is their number. Max length: 50
Buyers reference, usually added in the checkout for B2B orders. Max length: 50
List of order discounts that are not represented on order lines. Not commonly used.
True if web solution thinks that this order should be manually validated before processed
Usually empty. If exists this is a suggestion from web solution which order number the order should have in ERP. Max length: 50
Collection of fees on the order. Not commonly used, the fees are mostly implemented as order items with TypeGroup "Fee".
Collection of order rows. Other than the articles this collection can also contain fees such as freight.
An order can have several payments. Usually this is only one, but sometime there are an additional payment method like giftcard or a voucher.
Code of sales contact if a sales rep should be marked as seller. Max length: 50
Code of sales department if a sales dep should be marked as seller. Max length: 50
curl -i -X POST \ https://connect.lab.storm.io/4.0/api/webhooks \ -H 'Content-Type: */*' \ -d '[object Object]'