Plan an ESL project in the right sequence, from discovery to live operation.
A well-designed ESL project defines the goal, data source, shelf conditions and acceptance criteria before the product list. This guide applies the same discipline to a small start or a multi-store rollout.
Prepared by Aya Teknoloji Technical TeamPublishedUpdated
01Separate a new system from an existing-system expansion02Survey, pilot, acceptance and rollout in sequence03The data pack required for an order or proposal
IN THIS GUIDE7detailed chapters
01 · GOAL
Define the scope→
02 · SURVEY
Validate data and shelving→
03 · PILOT
Test the flow on site→
04 · ROLLOUT
Measure, train and scale
THE RIGHT END-TO-END SEQUENCE
KNOWLEDGE CENTRE
Choose your reading path
Start with the ESL Guide to understand the technology, or the Project Planning Guide to plan a deployment.
Labour savings, price consistency, promotion speed, warehouse visibility and customer experience lead to different product and integration choices.
01.01
Business goal
Express success as a measurable outcome such as price-change time, error rate, task duration or shelf-data currency.
01.02
Deployment area
List stores, branches, shelves, chilled areas and warehouse scope together with approximate label counts and product groups.
01.03
New or expansion?
For an existing ZKONG system, account, access-point capacity and label compatibility are reviewed. New deployments include infrastructure design.
02
TECHNICAL SURVEY
Assess the data source and physical shelf in the same survey.
Correct data reaching the display and the label working in the right place, with the right accessory and coverage, are parts of one project.
02.01
Data map
Identify which system owns product code, price, promotion, stock and other fields, together with update authority and frequency.
02.02
Network and coverage
Review the store plan, internet/network conditions and access-point placement. New access-point quantities follow site and capacity needs.
02.03
Shelf and accessory
Match the correct rail, clip, stand and viewing angle to shelf profiles, glass, baskets, hooks, desktop or floor applications.
03
PRODUCT MATRIX
Create use cases instead of placing one model everywhere.
Standardisation simplifies cost and operation, but areas with different environmental or content needs may require separate models.
03.01
Size matrix
Determine how many display sizes are needed for compact pricing, detailed product information and promotion visibility.
03.02
Technical matrix
Choose colour, resolution, LED, NFC, IP rating and operating temperature only to the level genuinely required by each area.
03.03
Mounting matrix
Match each label model to an accessory by shelf type and plan spare accessories and an installation allowance separately.
04
PILOT AND ACCEPTANCE
Choose a small pilot with strong representation.
A pilot should test not only the device, but also data, templates, mounting, user permissions and the daily operational flow.
04.01
Representative area
Select a pilot shelf that reflects real product density, typical mounting and, where possible, a special environmental condition.
04.02
Acceptance criteria
Define correct product matching, update success, readability, mounting stability and task duration before the pilot starts.
04.03
User rehearsal
Store and central users practise price updates, pairing, exception review and support escalation on the pilot.
IMPORTANT
A pilot is not intended to imitate the whole rollout; it validates the most critical assumptions on a real site before scaling.
05
INSTALLATION
Manage go-live through coordinated product, data and site preparation.
The installation schedule is prepared with product mapping and quality checks while minimising disruption to store operation.
05.01
Pre-flight check
Labels, accessories, templates, users and data fields are verified before installation day.
05.02
Pairing and mounting
The label is paired to the correct product record, fitted to the planned accessory and checked against the physical product.
05.03
Go-live control
Coverage, updates, user access and exceptions are verified, with a clear route for reporting and resolving issues.
06
OPERATE AND SCALE
Measure the system after installation, preserve standards and scale.
ESL is a living operational system. Management standards must be maintained as products, shelves and stores are added.
06.01
Monitoring
Update jobs, device status, user activity and issue records are reviewed regularly.
06.02
Template governance
Define who can change price, promotion and information templates through an approval and publishing flow.
06.03
Capacity planning
When labels or stores are added, Cloud scope, access-point capacity, accessory standards and support needs are reviewed again.
07
PROJECT BRIEF
Submit these details together for a faster assessment.
The more concrete an order or project request is at the start, the faster product suitability and scope can be confirmed.
07.01
Business and scope
Company, contact, number of stores/areas, target date and existing ZKONG system information.
07.02
Products and quantities
Estimated total quantity, preferred display sizes, deployment areas and any preferred models.
07.03
Technical examples
Data source, sample product record, shelf-profile dimensions, site photographs and expected integration method.
IMPORTANT
Standard products that do not require survey, integration, training or special mounting can be purchased directly; not every request becomes a proposal process.
NEXT STEP
Turn what you have learned into a practical plan for your store.
Explore products directly or combine labels, accessories, infrastructure and services only to the extent your operation requires.
