Render evidence
Room-wide composition, coverage, contrast, scale, lighting response, and how several materials work together.
Kitchen finish review
How to Compare Kitchen Finish Samples with Presentation Renders
A presentation render helps a client understand the room as a whole. A physical sample helps them assess the selected product. Experienced showrooms need both, but each carries different evidence. This guide gives teams a repeatable way to compare them without turning a persuasive screen image into an unintended finish guarantee.
The short answer: the visual explains the scheme; the sample approves the finish
Do not ask whether a small sample and a large screen image are identical. First confirm they refer to the same product. Then compare the design intent: colour family, relative contrast, texture direction, sheen, pattern scale, and the relationship with surrounding finishes. Keep exact selection tied to current physical evidence.
Sample evidence
Physical colour, texture, sheen, touch, edge detail, and product identity under the conditions in which it is viewed.
Project evidence
Current quote, schedule, supplier information, decor and product codes, approved substitutions, and recorded client decisions.
Build one comparison pack before the client meeting
The most common comparison mistake starts before anyone looks at colour: the team places an unlabelled sample beside a visual and assumes they belong together. Build a compact reference pack for the exact design revision being shown.
Current design and finish schedule
Use the latest approved design image, quote, and finish schedule. Retire superseded views and mark unresolved substitutions so an old visual cannot silently become the current proposal.
Named physical samples
Label every sample with supplier, range, product or decor code, finish or texture code, and relevant date or collection. Similar-looking boards are not interchangeable evidence.
One coherent presentation set
Gather the hero view and supporting angles that show the same revision. Include close views only when they genuinely help explain pattern, edge, hardware, or junction detail.
A decision record
Prepare a short place to record what the client is selecting, what remains illustrative, what needs supplier confirmation, and who owns each follow-up.
Use a six-pass sample-to-render comparison
Run the passes in order. This prevents an attractive overall impression from hiding an identity or specification problem.
Confirm identity before appearance
Match the render annotation or schedule to the sample label. Check cabinet fronts, panels, worktops, splashbacks, flooring, handles, and visible metal finishes individually. If the product code is uncertain, stop and verify it rather than trying to resolve the question by eye.
Stabilise the viewing conditions
Move away from strongly coloured walls, mixed pools of warm and cool light, and extreme screen brightness. View the sample flat and upright because sheen and texture can respond differently with angle. You are reducing avoidable confusion, not creating laboratory conditions.
Compare relationships, not isolated pixels
Ask whether the cabinet still reads warmer or cooler than the worktop, whether the splashback provides the intended contrast, and whether dark finishes retain enough separation. These relative relationships are more useful for presentation review than sampling one screen pixel and declaring a colour match.
Separate colour, texture, and sheen
A render can be close in hue but wrong in surface character. Review colour family, lightness, undertone, grain or texture, gloss or matt response, and edge treatment as separate observations. A polished, super-matt, embossed, and brushed finish should not collapse into the same generic surface.
Check scale, direction, and repetition
For timber, stone, concrete, and patterned surfaces, compare feature size and direction with supplier imagery and project information. Check vertical and horizontal grain, bookmatching or deliberate continuation where specified, repeated motifs, slab or board scale, and changes across doors, panels, islands, and splashbacks.
Compare every approved view as a set
A finish should not move from warm oak to grey oak, matt to glossy, or fine grain to oversized grain between angles. Cross-view differences can confuse the client even when each image looks plausible alone. Record the exact view that needs correction.
Use client language that is accurate and still helpful
A defensive disclaimer can weaken a good presentation. A better explanation gives each tool a clear job: "This visual shows how the finishes work together across the room. The physical samples and current product information are the reference for the exact finishes you are selecting."
If the render appears warmer, darker, shinier, or less textured than the sample, say so plainly. Explain whether the difference is presentation-only, caused by the illustrated lighting, or needs a revised image. Do not adjust the sample story to defend the render.
Classify the outcome instead of arguing about "accuracy"
Accept for presentation
Identity is confirmed, relationships are credible, surface character is useful, and any normal display or lighting variation has been explained.
Revise the visual
The image changes the colour family, contrast, texture, sheen, scale, direction, coverage, or cross-view consistency enough to mislead the presentation.
Verify the project
The sample, schedule, quote, or supplier information conflicts, is missing, or may be superseded. Resolve the project record before approving the image.
Write the finding so another designer could act on it: identify the view, surface, expected reference, visible difference, and required next action. "Island front should use supplier X, decor Y, texture Z; current view appears high-gloss and redder than the labelled sample; rerender all three approved angles" is more useful than "colour off."
Technical sources and claim boundaries
This method is for presentation review, not colour measurement, product approval, procurement, installation, or compliance. Its boundaries are supported by these primary sources:
- EGGER's current decor guidance says colour-matching a decor selection is only possible with the original sample and recommends comparison with an actual sample rather than treating reference colour systems as exact matches.
- EGGER's Texture Meets Colour brochure states that shown decors are reproductions and that printing variables can produce differences from the actual product.
- NIST's colour and appearance overview explains that illumination and viewing conditions affect material appearance and treats colour, gloss, haze, and reflectance as distinct appearance concerns.
- CIE guidance on comparing softcopy and hardcopy images explains why mixed illumination and incomplete visual adaptation complicate comparisons between a display and a physical reproduction.
These sources do not validate a project-specific sample, display, render, product choice, or ARQ workflow. Use current samples, supplier data, contracts, drawings, and competent professional checks for the actual project.
Where ARQ fits after your existing kitchen design software
ARQ does not replace the software used to design, price, or specify the kitchen. Your team supplies an image from the existing design workflow. ARQ handles queued render production, automatically compares the result with the original design, and flags possible changes before a person approves the image.
That comparison can help expose a visibly changed finish, missing material boundary, or inconsistent view. It does not identify the physical sample, read the quote, approve colour, or replace a designer's product and client checks.
Test the workflow with a real kitchen finish set
Bring two or three current design images, the design tool your team uses, and one finish comparison worth testing. A focused founder-led pilot can show how automatically checked, human-approved visuals fit after your existing design process.
Start a founder-led pilotFrequently asked questions
Can a kitchen render be used to approve an exact cabinet or worktop colour?
No. Displays, room light, viewing conditions, image treatment, texture, and sheen all affect appearance. Use current physical samples and product information for product approval; use the render to explain the coordinated scheme and spatial effect.
Should the physical sample and render look identical?
Not necessarily. A small reflective sample viewed under showroom light and a large rendered surface viewed on a display are different viewing situations. Confirm product identity first, then compare colour family, contrast, texture direction, sheen behaviour, and relationships rather than demanding pixel-level equality.
What should be recorded after a kitchen finish review?
Record the product and decor codes, sample version or date where available, lighting and display context, which visual was reviewed, any presentation-only variation, unresolved checks, and who owns the next action.
How should a showroom explain colour differences to a client?
Explain that the visual communicates the overall room, contrast, and material relationships, while the physical sample and current supplier information remain the reference for the selected finish. Avoid promising an exact screen-to-product colour match.
What does ARQ check automatically?
ARQ automatically compares the rendered result with the original design and flags possible visual changes. A person still verifies product identities, samples, colour and texture expectations, quoted specification, and final client approval.