This document defines the Zonal standard loyalty interface supported by the POS Integration Engine. It forms part of the suite of Zonal Standard APIs.
\nThird parties should implement this API to allow the Zonal POS system to integrate with their loyalty system.
\nThe POSint engine is a installed at site level this means that there could be the case that mutiple versions of the POSint could be installed in an estate.
\nThis documentation relates to version 1.58 of the Zonal POS integration Engine.
\nDetails of version 1.58 have been added as pre-release versions.
\nThe onboarding process, at a high level, generally follows the below steps. This process applies irrespective of whether you have a new integration or are looking to enhance an existing integration.
\nPlanning
During this phase, the introduction to the integration is made either by you completing an enquiry form on the website or a client expressing interest via the Account Manager. Initial discussions are with the Partnerships team.
Development
During this next phase, API credentials and documentation will be released. Access to a Zonal sandbox environment will be provided. You will also be given contact information of the team who you can consult with during development.
Accreditation
Once you have finished your development and believe you have a production ready application, contact the Integrations team: integrations@zonal.co.uk
The demo will then be booked in. During the demo, your integration will be assessed to ensure you are using the Zonal API’s responsibly, and that it is clear the use cases that your integration does/does not support.
Client Onboarding
Documentation of the integration is produced and production credentials can then be issued.
Re-accreditation
From time to time, you may wish to include new features in the API to your solution. When adding a new feature, you need use the Integration Sandbox for your deployment testing and not production. Once you have completed your development you may need to be re-accredited
After a Statement of work has been signed, the integration team will setup access to the Zonal Integration Sandbox.
\nWe are not able to supply integrators with their own hardware or test environment. There are many components & specific networking requirements in setting up an estate and it is a sizeable project just to deploy an Aztec Estate. The dataset in the environment would be undocumented and we would be unable to offer any support on issues. In the past integrators have had their own environments but they have all been abandoned by the integrator in favour of the Zonal Sandbox.
\nWe are happy to support your development with the use of Zonal Integrator Sandbox estate, please contact us at integrations@zonal.co.uk and we can either
\nIt is not possible to gain early or ready only access to a clients production environment before accreditation has been completed.
\nThis documenation is written from the context of the POS calling out to a third party platform. When the phrase \"Request\" is used this is the data sent from the POS out.
\n\"Response\" is used when the third party replies to a request.
\nThe POS system supports the below types operations:
\nAssign Loyalty Account
To allow a customer to assign their loyalty account to the POS account. This will be done by scanning a barcode/QR code, swiping a loyalty card or typing in some form of customer id. Rewards can be returned as part of the assignment process if required.
Only one Loyalty account can be assigned to one POS Account. It is possable to split a POS account in to two or more accounts, then a loyalty account can be assigned to each.
\nLite Registration
To allow the POS operator to issue a loyalty id to a customer and record an e-mail address or mobile phone number against it, to allow a follow-up to obtain more customer details. Rewards can be returned as part of the registration process if required.
Request Earning Code Print Data
To generate an earning code, and corresponding text, to print on the customer’s receipt. The customer will be able to enter this code on an app or website supplied by the loyalty provider. This will allow them to get any points/rewards they should be due from their purchase, applied to their loyalty account. The code can be a bar code, QR code or just a text string depending on the site’s capabilities.
Upload Loyalty Ticket Details
Allows the POS to upload all the details of the current pos account (and corresponding loyalty id) to the loyalty server for processing in order to credit the loyalty account with any earned rewards.
Balance Check
Allows the POS to display to the end user, any rewards that have been added to the specified loyalty account.
Redeem Reward
Used to redeem prizes on the POS either by selecting them from a list of all available rewards, or, if supported, by using the loyalty account to pay for some or all of the current pos account.
Update Redemption
Used to increase the balance amount used in an initial redemption. The POS system will only use this call to add a tip amount to a loyalty payment.
Reverse Redemption
Used to reverse a previous redemption (including all of its updates).
Loyalty rewards, apart from loyalty payments, can optionally be given a points cost. If there is no cost then they can be redeemed at any time. If there is a cost, then the loyalty account must have enough points accrued to cover the cost and the points balance will be reduced in order to redeem the reward.
\n£2.50 Off
\n{\n \"pointsCost\": null\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a964\",\n \"name\": \"£2.50 off\",\n \"rewardType\": \"FixedDiscount\",\n \"percentage\": null,\n \"amount\": null,\n \"productId\": null,\n \"discountId\": \"13\",\n \"promotionId\": null,\n \"quantity\": 1\n}\n\n£5 off
\n{\n \"pointsCost\": null\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a965\",\n \"name\": \"£5 off\",\n \"rewardType\": \"FixedDiscount\",\n \"percentage\": null,\n \"amount\": null,\n \"productId\": null,\n \"discountId\": \"16\",\n \"promotionId\": null,\n \"quantity\": 1\n}\n\n20% off Food
\n{\n \"pointsCost\": null\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a967\",\n \"name\": \" 20% off Food\",\n \"rewardType\": \"FixedDiscount\",\n \"percentage\": null,\n \"amount\": null,\n \"productId\": null,\n \"discountId\": \"23\",\n \"promotionId\": null,\n \"quantity\": 1\n}\n\n5% off Bill
\n{\n \"pointsCost\": null\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a966\",\n \"name\": \"5% off Bill\",\n \"rewardType\": \"FixedDiscount\",\n \"percentage\": null,\n \"amount\": null,\n \"productId\": null,\n \"discountId\": \"25\",\n \"promotionId\": null,\n \"quantity\": 1\n}\n\n25% off Drinks
\n{\n \"pointsCost\": null\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a969\",\n \"name\": \"25% off Drinks\",\n \"rewardType\": \"FixedDiscount\",\n \"percentage\": null,\n \"amount\": null,\n \"productId\": null,\n \"discountId\": \"40\",\n \"promotionId\": null,\n \"quantity\": 1\n}\n\nPeroni For Free
\n{\n\"pointsCost\": null,\n\"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a961\",\n\"name\": \"Free Peroni\",\n\"rewardType\": \"Product\",\n\"percentage\": 100,\n\"amount\": null,\n\"productId\": \"10000000131\",\n\"discountId\": null,\n\"promotionId\": null,\n\"quantity\": 1\n}\n\nBudweiser For £1
\n{\n \"pointsCost\": null,\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a962\",\n \"name\": \"£1 Budweiser\",\n \"rewardType\": \"Product\",\n \"percentage\": null,\n \"amount\": 1,\n \"productId\": \"10000000131\",\n \"discountId\": null,\n \"promotionId\": null,\n \"quantity\": 1\n}\n\n50% off Risotto
\n{\n \"pointsCost\": null,\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a987\",\n \"name\": \"50% off Risotto\",\n \"rewardType\": \"ProductPercentageDiscount\",\n \"percentage\": 50,\n \"amount\": null,\n \"productId\": \"10000000236\",\n \"discountId\": null,\n \"promotionId\": null,\n \"quantity\": null\n}\n\n£5 off the Bill
\n{\n \"pointsCost\": null,\n \"rewardId\": \"74a57795-1abe-44f6-9d9a-345359f0a912\",\n \"name\": \"£5.00 off\",\n \"rewardType\": \"AccountAmountDiscount\",\n \"percentage\": null,\n \"amount\": 5,\n \"productId\": null,\n \"discountId\": null,\n \"promotionId\": null,\n \"quantity\": null\n}\n\nThese are very similar from the point of view of the loyalty system.
A CurrencyBalanceDiscount reward, if available, will be returned in the rewards list from balance check and presented as a reward button during a loyalty reward redemption. The user will then choose how much of their available balance to redeem and this will be debited from their loyalty account and applied to the POS account as a discount.
Paying by loyalty will be started via a payment button on the POS and follow the standard payment flow, including adding tips if supported. Again, the user will then choose how much of their available balance to pay with and this will be debited from their loyalty account and applied to the POS account as a payment.
Both will result in exactly the same /redeem call to the API with a currency balance debit entry.
In v1.58 of the POSint engine you are able to return rewards on the \"AssignLoyalty\" call, these will be automatically applied to the POS account. This enabled features like members pricing or a fixed discount to be applied automtically without further interaction for the POS user.
\nFixed Value Auto Assigned reward
\n{\n \"rewardId\": \"6d5dc8a4-fe86-4bdb-a7b3-cb9dcedc08d4\",\n \"groupingRedemptionId\": null,\n \"rewardType\": \"AccountAmountDiscount\",\n \"name\": \"£2.00 off\",\n \"percentage\": null,\n \"amount\": 2.0,\n \"quantity\": null,\n \"productId\": \"*\",\n \"promotionId\": null,\n \"paymentId\": null,\n \"discountId\": \"null\",\n \"pointsCost\": null,\n \"validOnTicket\": null,\n \"ticketItemId\": null\n }\n\nMembers Pricing (deduct 33p from product)
\n{\n \"rewardId\": null,\n \"groupingRedemptionId\": \"6bacefef-25e7-4fc8-8935-8c7a6229e00b\",\n \"rewardType\": \"ProductAmountDiscount\",\n \"name\": \"Members Price\",\n \"percentage\": null,\n \"amount\": 0.33,\n \"quantity\": null,\n \"productId\": null,\n \"promotionId\": null,\n \"paymentId\": null,\n \"discountId\": \"47\",\n \"pointsCost\": null,\n \"validOnTicket\": null,\n \"ticketItemId\": \"615726511578652\"\n }\n\nThe Aztec configuration is defined at site level in the Base data module.
\nPrint data allows you to send information to the printer so that a print out of balances or possable future rewards can be printed.
\nThe data is sent as a single string with control codes embedded in it. The control codes are in a universal format that the POS system will translate in to the format required by the specific printer the POS is configured to send the print out to.
All control codes start with the ‘#’ character followed by descriptor defining the control code and ending with another ‘#’. If you actually want to print a ‘#’ character on the receipt then you should send ‘#ESCAPEESCAPECODE#’.
Example:
\n\"printData\": \"#BOLD# Balance #NEWLINE##NEWLINE# Currency: #POUNDSYMBOL#2.67#NEWLINE#Points:5893#NEWLINE# #NEWLINE# #BOLD# Earned Rewards #NORMAL# #NEWLINE# 50% off CheeseBurger #NEWLINE# Guinness #NEWLINE# John Smiths #NEWLINE# Tetleys #NEWLINE# Directors #NEWLINE# #RUNOUT#\"
Balance Statement
\nCurrency:£2.67
Points:5893
Earned Rewards
50% off CheeseBurger
Guinness
John Smiths
Tetleys
Directors
POS user - The Point of Sale user
\nPOS - The Point of Sale
\nPOS Int - Software that runs on the back off PC, that connects out to the third party
\n3rd Party loyalty provider - The loyalty provider
\nAccount Assignment
\nUpload Ticket
\nBalance Check
\nRedeem from Loyaty
\nLoyalty Payment
\nReward Reversal
\nLoyalty Payment Reversal
\nThe Zonal interface will always send data in Camel Case format. URL parameters are all sent lower case.
\nThe interface will accept response both PascalCase or camelCase response fields.
\n‘null’ fields can be sent or omitted as preferred
\nAll loyalty ideitifers have the following restriction
\nMust have a defined prefix ie 1, the prefix mut be between 1-2 digits long.
\nMust be between 2 and 40 character long (including prefix)
\nThe prefix & identifyer can include 0-9 A-Z (only captials), . (full stop), _(underscore) - (hyphen), @ (at symbol). No other character are supported.
\nNote: A single discount may be split across multiple ticket items. Each ticket item will reflect how much a single product item is discounted by.
\nThe standard loyalty and vouchering plugin supports two methods of authentication, either basic authentication or authentication tokens. If the Auth Token Url configuration fields are populated then token authentication will be used, if not then basic authentication will be used.
\nThis standard basic authentication i.e. Every request sent will contain an ‘Authorization’ header. The field data of the header is constructed by combining the username and password with a ‘:’ separator, converting to ASCII and then base 64 encoding it. Finally the word ‘Basic ’ is prepended.
i.e.
\"Basic \" + Convert.ToBase64String(Encoding.ASCII.GetBytes(Username + \":\" + Password))
For token authentication an auth request is sent to the token server defined by the AuthTokenUrl setting.
\nIf needed the Auth Base URL can be defined differently to the Base URL for the other calls.
\nThe server will should an auth token which will be sent in all subsequent calls in the ‘Bearer’ header.
\nFor example
\n--header 'Authorization: Bearer AbCdEfghIJklm1234567890
If a 401 response is received from any subsequent call, then the token will be refreshed and the call retried.
\n","urlObject":{"path":["token"],"host":["https://third-party-loyalty-auth.com"],"query":[],"variable":[]}},"response":[{"id":"f58a142f-a37f-4176-82ab-ae1ce6706040","name":"AuthToken - Success","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"clientId\": \"site1\",\r\n \"clientSecret\": \"asecretforthesite1\"\r\n}\r\n","options":{"raw":{"language":"json"}}},"url":"https://third-party-loyalty-auth.com/AuthToken/v1/token"},"_postman_previewlanguage":null,"header":null,"cookie":[],"responseTime":null,"body":"{\r\n \"token\": \" AbCdEfghIJklm1234567890\"\r\n}\r\n"}],"_postman_id":"f95759c8-1d1a-4f89-831f-eac62ac0345a"},{"name":"Assign Loyalty Account","id":"bd053e90-0e0e-4f1e-ac9e-b020e706ad85","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\r\n \"id\": \"fcbaa7f1-b6f8-4aad-ab8a-3afbab7b2252\",\r\n \"loyaltyId\": \"1000\",\r\n \"posUserId\": \"12345600012\",\r\n \"ticket\": {\r\n \"ticketId\": \"17592186044539\",\r\n \"createdOn\": \"2011-12-05T15:16:27\",\r\n \"table\": \"14A\",\r\n \"accountNumber\": \"2345\",\r\n \"employeeId\": null,\r\n \"coverCount\": null,\r\n \"customerName\": null,\r\n \"isClosed\": false,\r\n \"closed\": null,\r\n \"updated\": null,\r\n \"updatedClosed\": null,\r\n \"ticketItems\": [\r\n {\r\n \"ticketItemId\": \"17592186046435\",\r\n \"itemId\": \"10000008\",\r\n \"portionId\": \"34\",\r\n \"destinationId\": \"4\",\r\n \"isLoyaltyReward\": false,\r\n \"itemType\": \"Product\",\r\n \"name\": \"BBQ Ribs\",\r\n \"quantity\": 1,\r\n \"amount\": 10.99,\r\n \"position\": \"1\",\r\n \"subCategory\": \"145\",\r\n \"category\": \"356\",\r\n \"division\": \"619\",\r\n \"taxesDue\": [\r\n {\r\n \"taxId\": \"1782\",\r\n \"name\": \"10% Service Charge\",\r\n \"isServiceCharge\": true,\r\n \"amount\": 1.6\r\n }\r\n ]\r\n },\r\n {\r\n \"ticketItemId\": \"17592186046436\",\r\n \"itemId\": \"5422\",\r\n \"isLoyaltyReward\": false,\r\n \"itemType\": \"Discount\",\r\n \"name\": \"10% off\",\r\n \"amount\": 0.99,\r\n \"position\": \"1.1\"\r\n },\r\n {\r\n \"ticketItemId\": \"17592186046437\",\r\n \"itemId\": \"1342\",\r\n \"itemType\": \"Promotion\",\r\n \"name\": \"£1 off Mains\",\r\n \"amount\": 1,\r\n \"position\": \"1.2\"\r\n },\r\n {\r\n \"ticketItemId\": \"17592186046438\",\r\n \"itemId\": \"10000000238\",\r\n \"portionId\": \"21\",\r\n \"destinationId\": \"4\",\r\n \"isLoyaltyReward\": false,\r\n \"itemType\": \"Product\",\r\n \"name\": \"Shiraz\",\r\n \"quantity\": 0.5,\r\n \"amount\": 6.98,\r\n \"position\": \"2\",\r\n \"subCategory\": \"234\",\r\n \"category\": \"987\",\r\n \"division\": \"459\"\r\n }\r\n ],\r\n \"payments\": [\r\n {\r\n \"paymentId\": \"17592186046512\",\r\n \"paymentMethodId\": \"2234\",\r\n \"name\": \"Card\",\r\n \"receiptNumber\": \"01/3578\",\r\n \"amount\": 1.10,\r\n \"position\": \"3\",\r\n \"eftProvider\": \"Mastercard\",\r\n \"eftPan\": \"5623\",\r\n \"cardToken\":\"paymentproviderguid\",\r\n \"taxesPaid\": [\r\n {\r\n \"taxId\": \"1782\",\r\n \"name\": \"10% Service Charge\",\r\n \"isServiceCharge\": true,\r\n \"amount\": 0.10\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n \"siteReference\": \"1234\",\r\n \"siteId\": \"34\",\r\n \"siteSalesAreaId\": \"12\"\r\n}","options":{"raw":{"language":"json"}}},"url":"https://third-party-loyalty.com/assign","description":"This functionality allows the POS operator to record a loyalty id (e.g. contained on a card or issued via a QR code etc.) against a specific POS account/check. The loyalty system will be informed of the current account state when this occurs and can choose to apply rewards to the account if required.
Enabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not required/implemented then the button should not be added to the POS theme.
This functionality allows the POS operator to unassign a loyalty id from a specific POS account/check. The loyalty system will be informed of the current account state when this occurs.
Enabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not required/implemented, then a checkbox EnableLoyaltyUnassign in Head Office -> Estate Structure -> CLM should be unchecked.
This is designed to allow the POS operator to issue a loyalty id (e.g. contained on a card or issued via a QR code
etc.) to a customer and record an e-mail address and/or mobile phone number against it, to allow a follow-up to
obtain more customer detail. The loyalty back-end should perform any issue/activation processing required for the
supplied loyalty id.
Enabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not
required/implemented then the button should not be added to the POS theme.
This call allows the POS system to request an earning code to be printed on the final payment receipt for the
account i.e. once the account is paid in full. This is intended for customers that have not used a loyaltyId for the current transaction. The customer can take this code and through some part of the third-party system (e.g. mobile app or web-site) can subsequently record the transaction against their loyalty account.
Enabling: This operation is automatically triggered by the POS whenever a receipt is printed for a payment that results in the account being full paid up. If this functionality is not required / implemented then the corresponding configuration in the sites CLM settings should be set to false.
\nNote: This functionality is only supported on Aztec version 3.26 and above.
\nThis call allows the POS system to upload all the details of the current POS account to the loyalty system in what is known as a ticket. This will include all products sold and all payments made. The loyalty system can analyse this ticket and apply any rewards earned to the corresponding loyalty account. This ticket upload can be performed at any time during the POS accounts life and can be done repeatedly. However, most commonly, it will only be done once when the account is closed.
\nticket uploads are carried out on a sceduled defined at site level, the default is set to every 5mins, but this can be changed and is defined in the unit of seconds. ie 300 Seconds = 5 mins.
\nticket retries
\nEnabling: This operation is automatically triggered by the POS whenever a bill or receipt is printed or a POS account is closed. If this functionality is not required/implemented then the corresponding configuration in the sites CLM settings should be set to false.
\nThe balance call can be triggered in one of two ways. Either by pressing the corresponding button on the POS, or as part of a redemption operation.
\nNote: URL pramaters are all sent lower case.
\nThis call is made when a rewards is redeemed manually on the POS, it is not triggered for a auto apply rewards via the assign or Autoupdate calls.
\nIf this functionality is not required/implemented then the button should not be added to the POS theme.
\nThis operation supports sending a basket up to the loyalty system for it to automatically apply any rewards due. This can be used for functionality such as member’s pricing.
\nIf a reward nees to be updated in value, then you need to remove the old reward and readd it. The removals will happen first and then the additions.
\nEnabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not required/implemented then the button should not be added to the POS theme.
\nThis is only used to add a tip to a previous loyalty payment. This call will only be made if there is a loyalty payment
method configured in the Zonal system which allows tips to be added to an existing payment.
This is only used to reverse previous redemptions or updates to redemptions. The POS cannot manually credit anything else to a loyalty account – all normal crediting is done via processing of the uploaded tickets.
Note – as rewards are reversed by merely passing the redemption id, the loyalty system is responsible for storing all other details necessary to credit the reward back onto the loyalty account e.g., type, value etc.
Enabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not required/implemented then the button should not be added to the POS theme.
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£4)
\nFinal Account Screenshot
\nPOS Flow
\nAdd 4 x Corona to account
\nAssign card PR123456789
\nPay via cash (£16)
\nFinal Account Screenshot
\nThis operation can be triggered in one of two ways. Either by pressing the corresponding button on the POS, or as part of a redemption operation.
\nNote: URL pramaters are all sent lower case.
\nPOS Flow
\nAdd Meat Board to account
\nAdd Cod & Chips to account
\nAssign card PR123456789
\nAdd reward (Two courses for £15)
\nPay via cash (16.13)
\nFinal Account Screenshot
\nThis operation can be triggered in one of two ways. Either by pressing the corresponding button on the POS, or as part of a redemption operation.
\nNote: URL pramaters are all sent lower case.
\nThis is only used to reverse previous redemptions or updates to redemptions. The POS cannot manually credit anything else to a loyalty account – all normal crediting is done via processing of the uploaded tickets.
Note – as rewards are reversed by merely passing the redemption id, the loyalty system is responsible for storing all other details necessary to credit the reward back onto the loyalty account e.g., type, value etc.
Enabling: This operation is triggered by pressing the corresponding button on the POS. If this functionality is not required/implemented then the button should not be added to the POS theme.
\nPOS Flow
\nAdd Meat Board to account
\nAdd Cod & Chips to account
\nAssign card PR123456789
\nAdd reward (Two courses for £15)
\nPay via cash (16.13)
\nFinal Account Screenshot
\nThis operation can be triggered in one of two ways. Either by pressing the corresponding button on the POS, or as part of a redemption operation.
\nNote: URL pramaters are all sent lower case.
\nPOS Flow
\nAdd Meat Board to account
\nAdd Cod & Chips to account
\nRedeem & Enter card PR123456789
\nAdd reward (Two courses for £15)
\nPay via cash (16.13)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£4)
\nFinal Account Screenshot
\nProduct added to the basket, with a warning that it is for over 18 customers only.
\nMenu: Drinks (Integration Scenarios 1) – ID 3141
Product: Birra Moretti– 10000000135
POS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£4)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Two Corona to account
\nAssign card PR123456789
\nPay via cash (£1)
\nPay via cash (£7)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nAdd service charge
\nPay via cash (£4)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via with iOrder (£5)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Love Birds & Mojito Cocktail to account
\nTwo cocktails for £12 promotion is triggered
\nAssign card PR123456789
\nPay via cash (£12)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Love Birds & Mojito Cocktail to account
\nTwo cocktails for £12 promotion is triggered
\nAdd £2.50 discount
\nAssign card 1234
\nAccount before assign Screenshot
\nPOS Flow
\nAdd Corona to account
\nAdd 10% discount
\nAssign card PR123456789
\nPay via cash (£3.60)
\nFinal Account Screenshot
\nKey Takeaways
\nPOS Flow
\nAdd Corona to account
\nAdd £.250 fixed discount
\nAssign card PR123456789
\nPay via cash (£1.50)
\nFinal Account Screenshot
\nKey Takeaways
\nPOS Flow
\nAdd Birra Moretti x 2 to account
\nAdd 10% off discount via Voucher code VOUEXC9E
\nAssign card PR123456789
\nPay via cash (£8.71)
\nFinal Account Screenshot
\nKey Takeaways
\nPOS Flow
\nAdd Stella Artois x 2 to account
\nAdd £5 off payment via Voucher code VOUHVGHZ
\nAssign card 1234
\nPress Update Account
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAdd 50% off Staff Discount
\nAssign card PR123456789
\nPay via cash (£2.00)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£4)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Absolut Blue to account
\nAssign card PR123456789
\nPay via cash (£3.50)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£4)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Corona to account
\nAssign card PR123456789
\nPay via cash (£5.60)
\nFinal Account Screenshot
\nPOS Flow
\nAdd Bombay Sapphire to account
\nSelect Tonic
\nAssign card PR123456789
\nPay via cash (£5.55)
\nFinal Account Screenshot
\n**
Key Takeaways**
The main product has postion 1
\nAny choices are in a minor postion ie 1.1 or 1.2
\nThere is never a 1.1.1
\nPOS Flow
\nCooked Breakfast
\nBacon
\nExtra Bacon
\nBaked Beans
\nPotato Cake
\nToask
\nAssign card PR123456789
\nPay via iOrder (£6.95)
\nFinal Account Screenshot
\nPOS Flow
\nBirra Moretti
\nAssign card PR123456789
\nAdd £2.00 tip
\nPay via iOrder (£6.84)
\nFinal Account Screenshot
\nPOS Flow
\nFirst Post Ticket
\nAdd products to account
\nAdd £2.50 fixed discount
\nAssign card 1001 (Assign call)
\nAdd beer
\nPress update (Update call)
\nRemove beer (auto posts update call)
\nAccount paid (upload ticket)
\nAccount at Assign call
\n-
\nAccount at Update
\n-
\nAccount at upload ticket
\n.
\nKey Takeaways
\nPOS Flow
\nFirst Post Ticket
\nAdd Stella & IPA to account
\nAssign card 1000
\nMembers pricing (10% off and £1.00 discount) added to account
\nAdd Corona to account, send update
\nNew members pricing applied
\nRemove Corona, send update
\nmembers pricing removed
\nFinal POS account
\nKey Takeaways
\n