Commercial Display Buying Guide

Choosing a Display Partner: What to Ask, and How to Read the Answer

The product is rarely the problem. Ask for evidence tied to a specific model, judge how the answer is given, and test cooperation with a sample.
Request a project recommendationExplore display solutions
Illustrative image: A schematic of a display unit standing on a pallet with protective packaging partly open
5,900+ Projects delivered globally
OEM / ODM Hardware, software and branding options
LG · BOE · Samsung Panel options by configuration
On this page

    An assumed scenario, constructed to show the decision. It describes no named customer and reports no measured result.

    A supplier sends a catalogue with forty models, a competitive price and a promise of full support. The integrator places a first order, and then discovers that the model in the catalogue has been replaced, the replacement has a different mounting interface, and the supplier will not confirm in writing which certifications apply to it.

    The product was not the difficulty in that project. The supplier's ability to answer questions about a specific model, repeatedly, over several projects, is the thing being bought. This guide is how to evaluate that before the first order rather than during it.


    Start with your requirements, not their catalogue

    A supplier cannot confirm anything against "digital signage for retail." Write the brief first.

    • The locations, by type, and how many of each.
    • The formats you expect to use, and whether they are fixed.
    • The operating conditions: hours, orientation, indoor or window, and anything distinctive.
    • The software or player the screens must work with.
    • How installation will happen, and who does it.
    • How service will happen, and who responds when a screen fails.
    • The documents you will need, by market.

    Then mark each line mandatory or preferred. A supplier's answer is only meaningful against a brief, and the mandatory lines are what you will hold them to.


    Ask for evidence tied to the model, not to the company

    This is the test that separates suppliers more reliably than price. Ask for four things for the specific model you are considering, and see what comes back.

    What to ask for A good answer A weak answer
    Current specification A dated document for that model A catalogue with a range of models
    Configuration record What is included, and what is optional "Standard configuration"
    Document list for your market Which documents exist, and how to obtain them "We are certified"
    Change history A dated record of what has changed on this model and when, whether or not anything changed An assertion that nothing has changed, with no date and nothing on file behind it

    The fourth question is the one most often skipped, and it is the one that separates a supplier who tracks their own product from one who does not. Model details do change over time: a panel can be substituted, a bracket revised, a board updated. A supplier who can tell you what changed and when is keeping a product history. "No changes" can also be a documented answer, and it is worth the same follow-up as any other: ask for the date it applies from and what the last change was, and judge the record rather than the confidence.


    Judge the quality of an answer, not its confidence

    Three things distinguish a supplier who can support a project from one who can only sell it.

    They say "I do not know" when they do not know. Then they find out, and come back with something specific. A supplier who answers everything instantly is guessing, and you will find out where during installation.

    They separate what is verified from what is expected. "This is tested for that orientation" and "this should be fine in that orientation" are different statements, and both are useful if they are labeled. A supplier who collapses the two is telling you they do not distinguish them either.

    They volunteer the limits. The most useful sentence in a supplier conversation is "this model will not do X." It tells you they have read the documentation, and it saves you a project.

    Ask one question you already know the answer to, and see whether the answer matches. That is a cheap and legitimate test.


    A schematic record sheet for a sample evaluation, showing a unit outline with its port group, mounting holes and accessory set marked
    Figure 1. Schematic. The record a sample evaluation should produce, so a production batch can be compared against something. This is a drawing, not a photograph of a delivered unit.

    Use the sample to test cooperation as well as hardware

    A sample evaluates two things: the unit, and how the supplier behaves when something needs attention.

    Keep the sample acceptance method for the hardware side. The cooperation side shows up in how the sample was arranged:

    • how long it took, and whether the promised date held;
    • who answered questions during the evaluation, and how quickly;
    • what happened when something did not work as expected;
    • whether the configuration record arrived with the unit or had to be requested twice;
    • whether the promised documentation materialised.

    None of that is a warranty. All of it is a preview.


    Compare the commercial boundaries explicitly

    Price is one line in a comparison that has several. Ask each supplier to state, in writing:

    • what the price includes, and what it excludes;
    • the validity period of the quotation;
    • the minimum order, and whether it differs by model;
    • the lead time, and what it is measured from;
    • the payment terms;
    • how a configuration change after order is handled;
    • what happens if a specified component becomes unavailable.

    That last line is worth asking directly. Components change, and the difference between a supplier who tells you in advance and one who substitutes quietly is the difference between two very different projects. Before a first order, the project cost structure is where the exclusions in a quotation become visible.

    We publish no price, MOQ or lead-time figure, because all three depend on the configuration and the market, and a single published number would mislead more readers than it helped.


    Build a selection record you can reuse

    Write the evaluation down, because the next project will ask the same questions.

    One page per supplier: the brief they answered against; the evidence they provided, by item; what they could not confirm; the commercial boundaries; the sample result; and your assessment. Then a short paragraph on the decision and why.

    The value is not in this project. It is in the second one, where you already know which suppliers answer questions with documents and which answer with adjectives.


    What this guide does not cover

    It publishes no price, MOQ, lead time, warranty or certification statement, and makes no claim about Gemdragon's own performance against these criteria. Market-access documents depend on the destination and the product, and should be confirmed as documents rather than assurances. The cost structure shows which of those numbers a quotation has to itemise before you can compare two suppliers.


    Start with the brief

    Send us the locations, formats, operating conditions, software and service expectations, and the documents your market requires. We will answer against that brief for a specific model, tell you what we can and cannot confirm, and put the configuration in writing before you order.

    Send the brief you are sending suppliers →


    Sources

    • No external source is cited. This guide describes an evaluation method, and it makes no factual claim about any supplier.

    Compiled September 29, 2026. The method is the author's; the external sources are listed above, and the opening scenario is constructed rather than reported.

    Turn your project brief into the right display specification.

    Tell Gemdragon where the display will be installed, who will view it and how it needs to operate. Our team can help narrow the configuration.

    Request a project recommendationExplore display solutions
    View all articles →