Click’n’Collect - Web Order Guide.
The initial flow of Click’n’Collect is a follows:
- Web Order creation
- The POS polls for pending Web Orders
- The POS picks the Web Order
- The POS delivers the Web Order
- A sale is made
API links for routes that can be used for completing the task.
In the event of a return there are two outcomes:
- The customer receives money from the shop’s register/terminal.
- The customer does not receive money from the shop’s register/terminal.
Whether or not the customer receives money depends on the Group’s return policy.
Flow for weborders returns:
Web shop turnover shop id for Click’n’Collect.
If turnover shop id is set, the sale must be made to this turnover shop id. If not set the individual shop have the turnover.
For a DdD web-shop, a turnover shop id can be set. This can be used for collecting all turnover on one ShopId for a web-shop. A separate item-group must also be set to identify this.
If set:
- Upon delivering a Web Order, this will trigger an item transfer from deliver shop id, to turnover shop id.
- If an item is returned, an item transfer will be triggered to the return shop id, from the turnover shop id.
- All Web Order sales must be to the turnover shop id.
Web Order creation
Creation is done through the Public API. There is currently two routes for this. The difference between the two is the “VariantId”/”Ean” properties.
The standard for this system is the “VariantId”, which is unique per Group. The “Ean” alternative is not ensured unique.
The POS polls for pending Web Orders
The POS will blink in the top bar when there is a Web Order assigned to the shop in which the POS is located.
The POS picks the Web Order
The Web Order is being picked by shop staff. A pick list can be printed on the POS.
The POS delivers the Web Order
The Web Order is being packaged/delivered by shop staff. The receiver address label will be printed and put on the package, ready to be sent to the customer.
A sale is made
All payment for the Web Order is handled by integrator through DdD API.
The Group can fetch status on Web Orders. When a Web Order is delivered a sale must be made through DdD API. This sale must be marked with the “OrderNo” from the header in order to bind the Web Order and the payment.
API links
Route to implement for the web-shop to create a Click’n’Collect Web Order is here for the VariantId option.
Route to implement for the web-shop to create a Click’n’Collect Web Order is here for the Barcode option. Note: The ean/barcode option is a non-unique option.
If the Loyalty option is used - the link to the API Member section of Loyalty is here.
If you want to follow the status of all the Web Orders - the link to use is here.
If you are in doubt to what status code to use see here - entering all or All or 0 will provide you with all.
If you only want the one Web Order, with a specific OrderNo, the link to use is here.
For all Web Order routes - you can find them here.