Sending completed orders to Spaaza

All orders or transactions (also referred to in Spaaza as “baskets”) need to be sent to Spaaza. This includes member orders (customers who are part of the loyalty program) and non-member or anonymous orders.

Spaaza requires that orders are sent in real time (or in near-real time )so customers get immediate rewards and benefits and also to prevent the fraudulent use of vouchers. In the case of the webshop orders are usually sent once the payment has been processed.

A typical webshop voucher redemption and order flow

The diagram below illustrates the typical flow between Spaaza and webshop system needed to redeem vouchers and send completed orders as well as returns to Spaaza.

Member orders

Member orders are used by Spaaza to calculate points and rewards that a customer should have, show a customer their purchase history and digital receipts (in an app, on the webshop etc). They are also used by Spaaza to create insights for brands to help understand their customers better.

Member orders are sent to Spaaza using the add-basket API endpoint. The member number is included to identify the customer.

Non-member orders

Non-member orders are used by Spaaza to understand how the loyalty program member and specific customer groups compare to non-members. This is important to understand the impact of the program and also to improve the program and the brands business.

Non-member orders are sent to Spaaza using the add-basket API endpoint.

Return orders

All returned items also need to be sent to Spaaza, for both members and non-members. Orders with returned items are sent to Spaaza using the add-basket API endpoint.

If the webshop is “unaware” of return orders then the system responsible (for example the order management system) should send the returns to Spaaza.