Once an electronic shelf label shortlist exists, the procurement problem changes. The next decision is not which brochure has the longest feature list. It is whether every shortlisted supplier is pricing, documenting, and accepting responsibility for the same project boundary.
That distinction matters because two ESL proposals can show similar headline totals while covering different hardware quantities, store-network assumptions, software terms, integration work, installation responsibilities, training, support, spares, or acceptance evidence. A low quote can simply contain more exclusions. A high quote can include work another supplier expects the retailer or integrator to provide.
This guide is for retail procurement, IT, operations, and project teams that have already narrowed the field and now need a comparison-ready request for quotation. If you are still defining what kind of ESL system fits the business, start with the electronic shelf label solution selection guide. The job here begins after that stage: freeze one procurement baseline, require a consistent vendor response, expose assumptions and exclusions, and move unresolved claims into an explicit evidence or pilot plan.

An ESL quote is only comparable when the project boundary is the same
"5,000 labels plus software" is not a complete comparison unit. The buyer needs to know what those labels represent, which mounting hardware is included, how store communications are covered, which software term is priced, what source systems will be integrated, who performs implementation, and what happens after go-live.
A useful RFQ therefore separates the project into two layers:
- Buyer baseline: the conditions every supplier must price against.
- Supplier response: the exact product, service, assumption, evidence, exception, and commercial term proposed against that baseline.
If the baseline changes from vendor to vendor, the comparison has already failed. Procurement should not spend the final review meeting reverse-engineering why one proposal includes mounting and another does not, or why one software price covers a year while another covers a different term. Those differences should be visible before commercial scoring begins.
Freeze the procurement baseline before vendors price it
The RFQ should give every supplier the same working description of the project. It does not need to pretend that every detail is known. Unknowns can be marked as TBD, but they should be visible rather than replaced by silent supplier assumptions.
| Baseline area | Buyer should define | If still unknown |
|---|---|---|
| Deployment scope | Stores, rollout phases, target departments, representative store types | Request separate assumptions by store type or phase |
| Label quantity basis | How quantities were counted and which shelf positions or use cases they represent | Require supplier quantity assumptions and reconciliation method |
| Display use cases | Price, promotion, unit price, product data, stock cues, barcode or QR requirements if applicable | Mark optional use cases separately from mandatory ones |
| Operating environments | Normal aisle, refrigerated or frozen areas, unusual fixtures, lighting or mounting constraints | Require site survey or sample validation before commitment |
| Source systems | Pricing, POS, ERP, product master, promotion or other authoritative systems that may exchange data | Require interface discovery as a priced or separately identified activity |
| Buyer resources | Internal IT, store labor, integrator involvement, network ownership, project management responsibilities | Ask vendors to state every dependency on buyer-provided work |
| Commercial horizon | What period should be used for recurring software, maintenance and support comparison | Request both initial and recurring terms separately |
This baseline prevents a common procurement failure: comparing different solutions to different versions of the problem. It also gives the buyer a stable reference when scope changes later. If a supplier proposes an alternate design, the alternate should be shown as a variance from the baseline rather than silently replacing it.
Require every vendor to answer the same response matrix
A strong ESL RFQ is not only a list of questions. It is a response structure. Every shortlisted supplier should populate the same categories so that "included," "optional," "excluded," and "requires clarification" mean the same thing during review.
| Category | Buyer provides | Supplier must state | Evidence or attachment |
|---|---|---|---|
| Electronic shelf labels | Required use cases, environments and quantity basis | Exact proposed model or configuration by use case, quantity, included accessories and substitutions | Model-level specification and proposed bill of materials |
| Mounting | Representative fixture types and special areas | Included rails, clips, adapters, custom parts and installation responsibility | Mounting schedule, drawings or representative sample |
| Store communications | Store types, layout information and network constraints available to the buyer | Gateway or access-point design, required infrastructure, site-survey assumptions and ownership boundary | Proposed architecture and site-validation method |
| Software | Required user groups and business workflows | Modules, license basis, subscription term, hosting assumptions, user or site limits and renewal structure | Commercial schedule and current product documentation |
| Integration | Known source systems, data owners and required business events | Interface method, responsibilities, custom work, version constraints, error handling and acknowledgement behavior | Interface documentation and implementation scope |
| Implementation | Buyer project roles and rollout constraints | Project management, configuration, data preparation, site work, installation, migration and cutover responsibilities | Work breakdown, assumptions and deliverables |
| Training | User groups that require enablement | Audience, format, materials, sessions, language, trainer responsibility and any exclusions | Training scope and deliverables |
| Support and lifecycle | Required operating hours and escalation expectations | Support hours, escalation path, software maintenance, replacement process, spares, warranty scope and lifecycle assumptions | Support/SLA terms and lifecycle documentation |
| Compliance evidence | Target markets and project-specific compliance requirements | Which documents apply to each exact product/configuration and which remain pending | Applicable certificates, reports or declarations |
| Pilot and acceptance | Critical workflows and representative conditions to prove | What will be demonstrated, what evidence will be captured, responsibilities and prerequisites | Pilot plan or proposed acceptance method |
The matrix is deliberately more specific than "Does your system support ERP integration?" A yes/no answer does not show whether the connector is standard, custom, version-limited, separately priced, dependent on middleware, or outside the supplier's scope. The RFQ should force the commercial and technical boundary into the same answer.

Normalize commercial pricing before you compare totals
Headline price is a weak comparison metric when vendors package the project differently. Before procurement compares totals, rebuild each proposal into a common commercial structure.
| Commercial bucket | Examples to normalize | Question to resolve |
|---|---|---|
| Hardware | Labels, gateways/access points, mounting, spares, accessories | Are quantities and configurations based on the same project scope? |
| Software | Platform license, subscription, modules, hosting, management functions | What period, site count, user basis or device basis is priced? |
| Integration | Interface development, configuration, middleware, data mapping, testing | What is standard, custom, buyer-provided or separately priced? |
| Implementation | Project management, surveys, configuration, installation, cutover | Which labor and travel assumptions are included? |
| Pilot | Samples, pilot hardware, temporary infrastructure, engineering support | Are pilot charges separate, credited, reusable or excluded? |
| Training | Store, IT, administrator or support training | Who is trained, how, and how many sessions are included? |
| Recurring service | Support, maintenance, software renewal, monitoring | What recurs, at what interval, and under which service scope? |
| Third-party dependencies | Network work, hosting, middleware, installer, integration partner | Is the cost included in the proposal or merely assumed to exist? |
The purpose is not to invent a universal ESL market price. It is to make the quoted project economically comparable. For the factors that can change ESL cost before quotation, use the separate ESL cost-driver guide. In the RFQ, require each supplier to expose the quantity basis, commercial term, optional items, exclusions, and recurring charges behind its own proposal.
Turn integration claims into testable interface obligations
"API available," "POS compatible," or "ERP integration supported" are discovery statements, not procurement-ready commitments. The RFQ should turn each required data flow into a defined obligation.
For every integration path, ask the supplier to state:
- the source and destination systems involved;
- the proposed interface method;
- the business events and data objects exchanged;
- the direction of each flow;
- authentication or access dependencies that the buyer must provide;
- version or environment constraints;
- who builds, configures and maintains each side;
- how acceptance, rejection, retry, duplicate requests and partial failures are represented;
- what logs or status evidence remain available for troubleshooting;
- which work is included, optional, custom or excluded.
This approach is safer than treating a named connector or protocol as proof that the complete business workflow is ready. The exact integration obligation belongs in the proposal and implementation scope for the selected configuration. If the project requires a deeper update-control design, the site's ESL API idempotency and duplicate-update guide covers that narrower technical task.
Make assumptions and exclusions visible before scoring
Many proposal gaps are not stated as "excluded." They appear as assumptions. A vendor may assume the retailer provides network work, cleans the data, installs the rails, supplies power where infrastructure is required, performs product-to-label mapping, provides middleware, or handles overnight store access. Those assumptions can materially change price and rollout risk.
Maintain a separate assumptions and exclusions register during proposal review:
| Assumption or exclusion | Owner | Commercial impact | How it will be validated | Status |
|---|---|---|---|---|
| Example: mounting labor is buyer-provided | Buyer / Supplier / Integrator | Included, excluded, optional or unknown | Clarification, sample install or revised quote | Open / Resolved |
| Example: software price covers only the initial term | Supplier | Recurring cost needs normalization | Commercial schedule | Open / Resolved |
| Example: integration requires an existing middleware component | Buyer / Integrator | Potential third-party cost and dependency | Architecture review | Open / Resolved |
| Example: certification evidence is available only for a product family | Supplier | Configuration approval may remain pending | Exact SKU/configuration document review | Open / Resolved |
Do not score an unresolved assumption as if it were an included capability. First classify it. Then either close it through clarification, price it as a variance, or move it into a defined verification stage.
Score evidence separately from feature claims
One of the most useful changes a procurement team can make is to stop treating four different statements as equivalent:
- Claim: the supplier says the capability exists.
- Commitment: the proposal explicitly says the capability is included for this project.
- Evidence: the supplier provides documentation, architecture, certificates, interface material, test records, or another reviewable basis.
- Pilot proof: the critical workflow is demonstrated under agreed project conditions.
A feature can be real and still be out of scope commercially. A feature can be included and still need validation in the buyer's environment. A certificate can exist and still apply to a different model or configuration. Keeping these states separate prevents a brochure checkbox from receiving the same procurement score as a documented and testable commitment.
| Requirement | Claimed? | Committed in proposal? | Evidence supplied? | Must prove in pilot? |
|---|---|---|---|---|
| Required product/configuration | Yes / No | Yes / Conditional / No | Model-level documentation | If sample or environmental proof is needed |
| Integration workflow | Yes / No | Included / Custom / Excluded | Interface and scope documentation | Usually for business-critical flows |
| Security requirement | Yes / No | Committed / Conditional | Architecture, policy or test evidence as applicable | Only where project acceptance requires it |
| Support response process | Yes / No | Contract/SLA term | Escalation path and service terms | Optional drill or operating review |
Cybersecurity is a good example of why evidence must be separated from a generic feature statement. The detailed ESL cybersecurity procurement guide covers security requirements and evidence in depth; the RFQ page only needs to ensure that required security evidence is named, assigned, and not hidden behind "secure platform" language.

Push each unresolved requirement into the right proof stage
Not every question belongs in a store pilot. Some should be answered by documents before the pilot starts; others require a physical sample; still others depend on the deployed environment or contract terms. Moving every uncertainty into "we will test it later" creates an expensive pilot full of preventable ambiguity.
| Proof stage | Best used for | Typical output |
|---|---|---|
| Document review | Exact model/configuration, interface scope, warranty, certification evidence, software terms | Approved document set or open clarification |
| Sample review | Mounting fit, physical readability, representative label form factor, accessories | Sample approval record and exceptions |
| Store pilot | Store communications, real data flow, update/reconciliation behavior, representative operating conditions | Measured acceptance evidence and defect log |
| Contract / SLA review | Support hours, escalation, renewal, lifecycle obligations, responsibility boundaries | Signed commercial and service commitments |
Battery life is a useful example of this discipline. Do not force one generic number into the RFQ as though every label, environment and update pattern were identical. Ask the supplier for the model-specific claim, the assumptions behind it, and how the proposed operating profile affects that claim. The same principle applies to coverage, refresh behavior, environmental limits, and service commitments.
Use a variance log to compare proposals fairly
After clarification, procurement should be able to see every material difference without rereading three complete proposals. A variance log converts those differences into decision items.
| Requirement | Vendor A | Vendor B | Vendor C | Variance | Commercial or delivery impact | Decision |
|---|---|---|---|---|---|---|
| Required configuration | Compliant | Alternate | Conditional | Different configuration proposed | Needs technical review | Open |
| Integration scope | Included | Custom work | Excluded | Different responsibility boundary | Changes total implementation cost | Clarify |
| Training | Defined | Unclear | Optional | Different service scope | May add rollout work | Normalize |
| Evidence requirement | Supplied | Pending | Not supplied | Different proof level | Changes pre-award risk | Request evidence |
Useful variance labels are simple: compliant, conditional, alternate, excluded, unclear, and evidence pending. The point is not to produce a complicated scoring model. It is to make the reason for every score visible.

Do not let lifecycle and support disappear behind the hardware quote
The proposal should state what happens after initial installation. Ask how replacements are handled, what spare strategy is expected, which software and support services recur, how firmware or platform changes are managed, what happens when a model reaches end of life, and which responsibilities remain with the retailer.
These questions are intentionally about ownership and evidence rather than a universal warranty period or spare percentage. Those values depend on the selected product, contract and operating model. For teams designing the operational spare process after procurement, the ESL spare inventory and replacement guide covers that narrower lifecycle task.
Award should depend on unresolved risk, not the prettiest demo
By the end of proposal review, every critical requirement should have one of three outcomes:
- Ready to advance: scope is clear, commercial treatment is normalized, and evidence is sufficient for the next stage.
- Conditional: the proposal can advance only if a named clarification, document, sample or pilot result closes the remaining risk.
- Not comparable or not acceptable: a material requirement remains excluded, unclear, unsupported, or outside the agreed project boundary.
This produces a better procurement decision than ranking vendors by presentation quality or headline price. The winning proposal should be the one whose project boundary, obligations, commercial terms, evidence, and remaining risks are clear enough to contract and validate.
If the project is moving from procurement into implementation planning, the broader electronic shelf label solution framework provides the system context. The RFQ itself should remain narrower: one baseline, one response matrix, one assumptions register, one evidence standard, and one variance log that make every shortlisted proposal genuinely comparable.