Block Service
Block Service
The hotel decides on which level the services are to be sent, supercat, middlecat, articlecat, article or as mapping over serviceID.
| name | description |
|---|---|
| supercat | ID of the super goods group/category |
| supercat_desc | description of supercat |
| middlecat | ID of the goods group/category |
| middlecat_desc | description of middleca |
| articlecat | ID of the article group/category |
| articlecat_desc | description of articlecat |
| articleno | ID of the article |
| articleno_desc | description of article |
| priceperunit | price per unit of the service |
| pricetotal | total of the service |
| amount | number of units |
| billno | Number of the bill/ticket in the POS |
| cashno | Outlet/number of the POS |
| cashier | Number of the cashier in the POS |
| source | BlockSource |
| vatpercentage | Processing date of the payment in the PDQ/external payment system |
| serviceID | SIHOT.PMS service code ( if the existing SIHOT.PMS services are to be used in the interface). optional, max. 15 char |
| fiscalBookingSignature | Trace number for the payment (needed for cancellations, for example) |
| vattype | description of the payment type |
SUPERCAT, MIDDLECAT, ARTICLECAT AND ARTICLENO
If the according service is not available in SIHOT.PMS, it has to be inserted. Therefore it has to be defined if the service is to be booked according to the supercat, middlecat, articlecat, or articleno.
Whether to use supercat / middlecat, articlecat or articleno depends on the needs of the hotel.
In the SIHOT registry [5144], you can define which category is used. Middlecat groups several articles into one “middle” category and supercat groups several middlecats into “super categories”
EXAMPLE:
Cash number 1:
| articlecat | articlecat_desc | middlecat | middlecat_desc | supercat | supercat_desc |
|---|---|---|---|---|---|
| 1 | Onion soup | 1 | Entrees | 1 | Food |
| 2 | Tomato soup | 1 | Entrees | 1 | Food |
| 7 | Prawn cocktail | 1 | Entrees | 1 | Food |
| 25 | Steak | 2 | Main dishes | 1 | Food |
| 56 | Icecream | 3 | Desserts | 1 | Food |
| 101 | Pilsener | 4 | Alcoholic beverages | 2 | Beverages |
| 117 | Cabernet Sauvignon | 4 | Alcoholic beverages | 2 | Beverages |
| 134 | Coke | 5 | Non-alcoholic beverages | 2 | Beverages |
| 160 | Coffee | 6 | Hot beverages | 2 | Beverages |
Most hotels use middlecat since they do not want to post every single article on the customer’s account but some also use supercat since it can be enough to know how much of the amount was beverages and how much was food.
If you have more points of sale than just a restaurant, maybe a second restaurant with different dishes or a souvenir shop with completely different articles, they can send the same article numbers as the others but since they have a different cash number, SIHOT will create different articles from it.
Cash number 2:
| articlecat | articlecat_desc | middlecat | middlecat_desc | supercat | supercat_desc |
|---|---|---|---|---|---|
| 1 | T-Shirt | 1 | Clothing | 1 | Fan articles |
| 2 | Trouser | 1 | Clothing | 1 | Fan articles |
| 7 | Jacket | 1 | Clothing | 1 | Fan articles |
| 25 | Cap | 1 | Clothing | 1 | Fan articles |
| 56 | Sticker | 2 | Non-Clothing | 1 | Fan articles |
| 101 | Pencil | 2 | Non-Clothing | 1 | Fan articles |
| 117 | Tickets to Cats | 4 | Tickets | 2 | Tickets |
| 134 | Tickets to U2 | 4 | Tickets | 2 | Tickets |
| 160 | Tickets to Opera | 4 | Tickets | 2 | Tickets |
You do not need to create these articles in SIHOT.PMS, our interface will generate them automatically when the first unknown article is received. You should just stick to the type of that is used. E.g. if you’d set the registry to use supercat and then later change to middlecat, the old service that was generated combining cash number 1 with supercat 1 would then be the same as now cash number 1 combined with middlecat 1 which might cause problems then.
AMOUNT, PRICEPERUNIT AND PRICETOTAL
priceperunit is always positive. Whether a posting results in a positive or in a negative amount depends on the amount that is sent. If the result of “amount * priceperunit” equals “abs(pricetotal)”, the interface will post the values “amount” and “priceperunit” as they were sent. If the result differs, the interface will post “amount=1” and “pricetotal”.
Note: To cancel a previous posting, the POS should only send the negative amount, not a negative amount and a negative pricetotal. Example:
A posting of
amount: 2 priceperunit: 1,80 pricetotal: 3,60
will result in the same posting as a posting of
amount: -2 priceperunit: 1,80 pricetotal: -3,60
This posting can be cancelled like this:
amount: -2 priceperunit: 1,80 pricetotal: 3,60
Examples for the posting and cancellation of a voucher:
amount: -1 priceperunit: 12,00 pricetotal: 12,00
will post a voucher of 12 EUR (or whichever currency is being used).
amount: 1 priceperunit: 12,00 pricetotal: 12,00
will cancel this voucher.
VATPERCENTAGE
By default the POS sends to the PMS a percentage for the VAT. SIHOT checks if there is an equal percentage defined in the PMS and creates the new services linked to this percentage.
The same algorithm is used in case of posting a charge from the POS in the PMS.
See also vattype.
VATTYPE
Instead of a percentage the internal identification in SIHOT can be sent from the POS to the PMS. This could be used in this scenario:
| ID | Percentage | Description |
|---|---|---|
| 1 | 0% | Without tax |
| 2 | 0% | Not taxable |
In this case the vatpercentage would not operate correctly, because the service would always be linked to the first entry. If there is a vattype in a message this field has a higher priority than vatpercentage.
But in this scenario we need the first and the second entry to have a correct invoice with two different vat descriptions.
SERVICEID
The SERVICEID accesses SIHOT.PMS service code. If the SERVICEID is filled in the request, articlecat, middlecat, supercat will be ignored.