\r\n \r\niZettle offers an easy way for restaurants to process card payments using mini credit card chip and pin and contactless Readers. With iZettle integration, bills totaled by TouchBistro are automatically processed using the iZettle iPad chip and pin or contactless card readers. This provides the greatest payment convenience and security for patrons, while eliminating staff time for manual bill re-entry and lost revenues due to bill calculation errors. \r\n \r\nTouchBistro features a full suite of cloud reporting tools to further streamline restaurant operations, from seating and scheduling to inventory, payroll, and sales analysis. Total revenue and cost aggregate is calculated by TouchBistro as an end-of-day summary that can be broken out into the categories that work best for the restaurant – such as food, liquor, soft drinks, and dessert – for sales analysis, inventory restocking, and business accounting. "}]}};
const country = "US";
const language = "en-US,en;q=0.5";
const SITE_LANGUAGE = "en";
const siteName = "Hospitality Technology";
const userRoles = ["anonymous"];
const userUid = 0;
const indexName = "HT";
window.dataLayer = window.dataLayer || [];
const data = {};
data.entityTaxonomy = {};
const contentTypes = [
"article",
"blog",
"bulletin",
"embed_page",
"landing_page",
"event",
"image",
"page",
"product",
"whitepaper",
"video",
"tags",
];
if (
routeInfo &&
"bundle" in routeInfo &&
contentTypes.includes(routeInfo["bundle"])
) {
data.entityBundle = routeInfo.bundle;
data.entityTitle = `${routeInfo.title} | ${siteName}`;
data.entityId = routeInfo.id;
data.entityName = routeInfo.author?.uname;
data.entityCreated = routeInfo.created;
data.sponsored = routeInfo.sponsored;
data.sponsor = routeInfo.sponsoringCompany;
data.entityType = "node";
data.entityLangcode = SITE_LANGUAGE;
data.siteName = siteName;
data.drupalLanguage = language;
data.drupalCountry = country;
data.userRoles = userRoles;
data.userUid = userUid;
data.entityTaxonomyKeys = {};
data.entityTaxonomyHierarchies = {};
data.parentNaicsCode = {};
data.isPro = false;
data.algoliaIndexName = indexName;
// Add toxonomy data
const taxonomies = {
businessTopic: "business_topic",
contentType: "content_type",
company: "company",
marketSegment: "market_segment",
};
const getHierarchy = (term, terms = []) => {
terms.push({ id: term.id, name: term.name });
if (term.parentTerm != null) {
getHierarchy(term.parentTerm, terms);
}
return terms;
};
const getTerms = (term, useApiId = false) => {
return { id: useApiId ? term.apiId : term.id, name: term.name };
};
const getKeys = (term) => {
return { id: term.id, name: term.apiId };
};
Object.entries(taxonomies).forEach(([key, item]) => {
terms = routeInfo[key];
if (terms && terms.length > 0) {
data["entityTaxonomy"][item] = terms.map((term) =>
getTerms(term, key === "company")
);
if (key !== "company") {
data["entityTaxonomyKeys"][item] = terms.map(getKeys);
termGroups = [];
terms.forEach((term, termInd) => {
termGroups[termInd] = getHierarchy(term);
});
data["entityTaxonomyHierarchies"][item] = termGroups;
}
}
});
data["entityTaxonomy"]["tags"] = routeInfo["topics"] || [];
// Primary Topic is either the business topic or the top tag.
if (routeInfo["businessTopic"]?.length > 0) {
data["entityPrimaryTopic"] = routeInfo["businessTopic"][0]["name"];
} else {
if (routeInfo["topics"]?.length > 0) {
data["entityPrimaryTopic"] = routeInfo["topics"][0]["name"];
}
}
// Primary and secondary entityNaicsCodes come from the MarketSegment
if (routeInfo.marketSegment?.length > 0) {
data.entityNaicsCode = {};
data["entityNaicsCode"]["id"] = routeInfo["marketSegment"][0]["id"];
data["entityNaicsCode"]["name"] =
routeInfo["marketSegment"][0]["naicsCode"];
if (routeInfo["marketSegment"][0]["parentTerm"] != null) {
data["parentNaicsCode"]["id"] =
routeInfo["marketSegment"][0]["parentTerm"]["id"];
data["parentNaicsCode"]["name"] =
routeInfo["marketSegment"][0]["parentTerm"]["naicsCode"];
}
} else {
data.entityNaicsCode = [];
}
if (routeInfo.taggedPro) {
data.isPro = routeInfo.taggedPro;
}
window.dataLayer.push(data);
} else if (routeInfo && "vid" in routeInfo) {
data.entityBundle = "tags";
data.entityTitle = routeInfo.name;
data.entityId = routeInfo.id;
data.entityName = routeInfo.author?.uname;
data.entityCreated = routeInfo.created;
data.entityType = "taxonomy_term";
data.entityLangcode = SITE_LANGUAGE;
data.siteName = siteName;
data.sponsored = routeInfo.sponsored;
data.sponsor = routeInfo.sponsoringCompany;
data.drupalLanguage = language;
data.drupalCountry = country;
data.userRoles = userRoles;
data.userUid = userUid;
data.algoliaIndexName = indexName;
data["entityTaxonomy"]["tags"] = {
id: routeInfo["id"],
name: routeInfo["name"],
};
window.dataLayer.push(data);
}
})();
TouchBistro Expands Mobile Payment Support & Releases Bilingual iPad POS App
TouchBistro Expands Mobile Payment Support & Releases Bilingual iPad POS App TouchBistro is now seamlessly integrated with
iZettle , a mobile payments provider in Europe and Latin America. The TouchBistro solution is designed to work as the heart and operating system of a restaurant. It streamlines operational efficiencies, and helps to improve the bottom line and overall customer experience. Servers use the TouchBistro app to take customer orders tableside, or while patrons are in line, and instantly transmits them to the kitchen or bar for preparation. Bills are automatically calculated and split according to the patrons' requests.
iZettle offers an easy way for restaurants to process card payments using mini credit card chip and pin and contactless Readers. With iZettle integration, bills totaled by TouchBistro are automatically processed using the iZettle iPad chip and pin or contactless card readers. This provides the greatest payment convenience and security for patrons, while eliminating staff time for manual bill re-entry and lost revenues due to bill calculation errors.
TouchBistro features a full suite of cloud reporting tools to further streamline restaurant operations, from seating and scheduling to inventory, payroll, and sales analysis. Total revenue and cost aggregate is calculated by TouchBistro as an end-of-day summary that can be broken out into the categories that work best for the restaurant – such as food, liquor, soft drinks, and dessert – for sales analysis, inventory restocking, and business accounting.
X
This ad will auto-close in 10 seconds