\n \n\"A lot of the initial features that were appealing to us related to the solution's ability to offer integration with other systems, including pricing and inventory, and the possibility of printing in-store,\" says Janetha Jones, business systems analyst for the signage application at Belk. \n \nPrior to implementing the solution, Belk used hand written requests for signage, and sent to an external company that created a PDF, which was then manually printed and these were sent to stores based on a spreadsheet. This method took a great deal of time and effort. Belk then tried a different process, using a Lotus Notes based application, with the templates designed in Quark, but it turned out be a very slow system, with which it was difficult to customize or integrate. \n \nBenefits of the Retail Enterprise Suite solution include the more descriptive information on signage, including product detail and benefits, which act as a \"silent salesman.\" Other benefits have included simplifying the spooling process. Previously this was done manually, with a user having to click and spool on each and every store before being able to print the signage. Now spooling is done by the system automatically in the background. \n \nJones continued, \"One of our biggest wins has been library signs, where at the start of a season we are now able to send the stores a set of signs for each applicable product with appropriate prices depending on the type of promotion being run at any time. This has reduced the number of signs we print by 30 to 40%. We will get a further reduction when we implement inventory integration and only send signs to stores that have the merchandise.\"\n"}]}};
const country = "US";
const language = "en-US,en;q=0.5";
const SITE_LANGUAGE = "en";
const siteName = "RIS News";
const userRoles = ["anonymous"];
const userUid = 0;
const indexName = "risnews";
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);
}
})();
Belk Dramatically Cuts Printing by Adding In-Store Signage Solution
Belk Dramatically Cuts Printing by Adding In-Store Signage Solution
12/23/2009
Belk manages its in-store signage with Retail Enterprise Suite Episys and has already seen a reduction of approximately 30-40% in signage printing. Belk replaced a largely manual and time-consuming series of processes in favor of an integrated, automated solution from Episys.
"A lot of the initial features that were appealing to us related to the solution's ability to offer integration with other systems, including pricing and inventory, and the possibility of printing in-store," says Janetha Jones, business systems analyst for the signage application at Belk.
Prior to implementing the solution, Belk used hand written requests for signage, and sent to an external company that created a PDF, which was then manually printed and these were sent to stores based on a spreadsheet. This method took a great deal of time and effort. Belk then tried a different process, using a Lotus Notes based application, with the templates designed in Quark, but it turned out be a very slow system, with which it was difficult to customize or integrate.
Benefits of the Retail Enterprise Suite solution include the more descriptive information on signage, including product detail and benefits, which act as a "silent salesman." Other benefits have included simplifying the spooling process. Previously this was done manually, with a user having to click and spool on each and every store before being able to print the signage. Now spooling is done by the system automatically in the background.
Jones continued, "One of our biggest wins has been library signs, where at the start of a season we are now able to send the stores a set of signs for each applicable product with appropriate prices depending on the type of promotion being run at any time. This has reduced the number of signs we print by 30 to 40%. We will get a further reduction when we implement inventory integration and only send signs to stores that have the merchandise."