DocMaster/Customer Events

Customer events

• Support for purchase, achievement, and referral events

• Customer identification based on contact id, contact code, CIM, gift card number, OTP

Purchase Events

• Captures the purchase basket in full, total amounts and SKUs. If SKUs do not exist in CRM.COM, then they are created.

• Captures the organisation that submitted the event by matching to the organisation id or transaction acquire points

• Support for multi-currency, if purchase in another currency, then purchase event converted to business currency.

• Purchase event classification. If submitted and does not exist, then classification is created.

• Net, total and tax amount handling. Support to input or be calculated

• Two spend models. Payout-driven and POS driven.

• Optional spend request. Ability to specify that the spend is successful only if enough funds to cover the purchase

Transaction processor purchase events

• Transaction processors submitting events and routed to all businesses with the same transaction access points (terminals)

• Transaction matching mode where the purchase is matched to one submitted by the POS

• Transaction claim mode, where a customer claims the already submitted purchase via a self-service API

Purchase estimates

• Estimates what if a purchase was submitted and provides the response

Achievement event

• An event designating a customer achievement

Referral event

• An event designating a referral by a contact for another contact. Max 2 per day allowed

Event utilities

• Ability to void and list events

• Ad hoc returns, where products are returned and reversed