Sending orders to Spaaza
All orders or transactions (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.
Orders should be 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.
If an order cannot be sent to Spaaza, for example due to a connectivity issue in the store or the unlikely event of Spaaza’s API being unavailable we recommend using queue or some other solution to allow the orders to be sent to Spaaza once the connection becomes available again. We also recommend communicating any connectivity issue to staff.
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 retailers 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 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 retailers business.
Non-member orders are sent to Spaaza using the add-basket API endpoint.
Return orders (members and non-members)
All returned items also need to be sent to Spaaza, for both members and non-members, as a return order.
Orders with returned items are sent to Spaaza using the “inline” returns feature in the add-basket API endpoint. If items are only being returned and no new items are being bought the returned items should be sent as a new order to Spaaza.