...
| Info |
|---|
| title | Italian Certification | Specific requirements |
|---|
|
 Italian clients using a Certified S-360 license will need to keep all the following fields and conditions in the ticket templates (both thermal and digital) as provided with the licence
 Image Removed
Please note that overheads Overheads or any other commission fee must not be included in certified tickets: such amounts should be invoiced by they organization outside of the ticketing platform. Single tickets (specific fields for single entries and general fiscal fields) Image Added
| Name | Custom value | Type | Visibility | Condition |
|---|
| 01_EventTitle_M | EVENTO: ${ita_title} | Text | |
| | 02_EventDateTime_M | DATA EVENTO: ${ita_performanceDate} ${ita_performanceTime} | Text | |
| | 03_Space_M | LOCALE: ${ita_spaceName} | Text | |
| | 04A_PriceN_M | PREZZO: ${ita_grossAmount} ${Amount_currency} - PREVENDITA: ${ita_presaleAmount} ${Amount_currency} - TOTALE: ${ita_totalAmount} ${Amount_currency} | Text | | | | 04B_PriceBF_M | PREZZO: 0,00 ${Amount_currency} - PREVENDITA: 0,00 ${Amount_currency} - TOTALE: 0,00 ${Amount_currency} | Text | | | | 05A_FigurativeF_M | IMP.FIG.: ${ita_figurativeAmount} ${Amount_currency} - PREV.FIG.: ${ita_presaleAmount} ${Amount_currency} - TOT.FIG.: ${ita_totalAmount} ${Amount_currency} | Text | | | | 05B_FigurativeB_M | BIGLIETTO ABBONAMENTO - CODICE: ${ita_sstkCode} - PROGRESSIVO: ${ita_sstkProgressiveNb} - RATEO: ${ita_totalAmount} ${Amount_currency} | Text | | | | 06_EventType_M | TIPO EVENTO: ${ita_eventType} - ${ita_eventTypeDescription} | Text | |
| | 07A_SectorNoSeat_M | ORDINE: ${ita_seatCategoryCode} - ${ita_seatCategoryName} | Text | | | | 07B_SectorSeat_M | ORDINE: ${ita_seatCategoryCode} - FILA ${Seat_row} - POSTO: ${Seat_nb} | Text | | | | 08_Tariff_M | TIPO TITOLO: ${ita_tariffCode} - ${ita_tariffName} ${ita_vatPrepayment} | Text | |
| | 09_Organizer_M | ORGANIZZATORE: ${ita_organizer} - C.F./P.I. ${ita_organizerFiscalCode} | Text | |
| | 10_Owner_M | TITOLARE: ${ita_ownername} - C.F./P.I. ${ita_ownerFiscalCode} | Text | |
| | 11_FiscalData1_M | SISTEMA: ${ita_ticketingSystem} - CARTA: ${ita_smartCardId} - PROGRESSIVO: ${ita_progressiveNumber} | Text | |
| | 12_FiscalData2_M | SF: ${ita_fiscalSeal} - EMISSIONE: ${ita_issuingDate} ${ita_issuingTime} - PV: ${ita_posCode} | Text | |
| | 13_ID_M | FILE: ${Operation_fileId} - CODICE: ${Ticket_taxNumber} - BARCODE: ${Ticket_barcodeText} | Text | |
| | Barcode | | Barcode | |
|
Season tickets (specific fields for Cards "Abbonamenti padre". General fiscal fields as above) | Name | Custom value | Type | Visibility | Condition |
|---|
| 01_SeasonTicket1_M | ABBONAMENTO: ${Product_externalName} - CODICE: ${ita_sstkCode} - PROGRESSIVO: ${ita_sstkProgressiveNb} | Text | |
| | 02A_SeasonTicket2_M | EVENTI: ${ita_nbEventsIncluded} - TURNO: ${ita_sstkType} - VALIDITÀ: ${ita_validityDate} | Text | | | | 02B_SeasonTicket2_M | TITOLO OPEN - EVENTI: ${ita_nbEventsIncluded} - TURNO: ${ita_sstkType} - VALIDITÀ: ${ita_validityDate} | Text | | |
|
...
Within the model, the previously created template is associated with a ticket type, a material family and a ticket support. More info in Organization | Tools | Ticket models
After having validated them, it is possible to associate these models to the products. For example, in the catalog module of the organization context, the model can be associated with an event.
