03

Finding when AIfurniture images aregood enough to ship

Company
Kuka Home
Year
2025 – 2026
Type
AIGC · Cross-border E-commerce
Role
Product Intern · AI Content

The cross-border e-commerce team needed large volumes of furniture scene images for Amazon and Wayfair. I used AIGC tools to explore a practical product question — when generated furniture images are trustworthy enough to enter listing workflows, and when they must be edited or regenerated.

A furniture image is not useful because it looks real. It is useful when it protects product truth.

For Amazon and Wayfair listings, a generated furniture scene has to do two jobs at once: help the customer imagine a room and preserve the exact product they are buying. If the chair color, leg structure, scale, or usage context drifts, the image becomes a commercial risk instead of a selling asset.

This project was never just about prompt quality. The real product question was whether a generated scene still represented the same SKU truthfully enough to enter a listing workflow, or whether it should be edited or rejected.

Hero Comparison
Original SKUWhite-background chair
Shippable SceneQualified lifestyle output
Rejected OutputColor / shape / scale drift
The challenge was not generating a realistic room. It was deciding whether the room still protected product truth.

03

I turned AI furniture image generation from one-off prompting into a controlled production workflow for cross-border listings.

Real-looking images can still be wrong.

The first instinct was to optimize for visual appeal: better rooms, better light, better composition. That was not enough. Some outputs looked commercially polished but quietly changed the product color, geometry, scale, or usage expectation.

That was when the task stopped being image generation and became image qualification: which outputs were safe to ship, which were worth editing, and which had to be rejected.

Color Drift
Material tone no longer matched the SKU.
Structure Drift
The model altered the product itself.
Scale Distortion
The room misled the customer's sense of proportion.
Scene Mismatch
The scene looked good but implied the wrong use case.

The task was not more images, but more reliable purchase contexts.

A white-background image answers “what is the item?” A lifestyle image answers “where does it fit in my life?” The point of this workflow was to expand purchase context without damaging product identity.

One SKU → Multiple Contexts
Original SKUWhite-background source
Dining
Vanity
Home Office
Reading Corner
The same SKU can appear in multiple scenes, but its identity has to stay stable in every one of them.

It was not a prompt problem. It was a control problem.

At first, the workflow looked like prompt optimization: rewrite the scene, improve the lighting, regenerate until the output looks better. But better-looking outputs were not always safer outputs.

BeforePrompt → Generate → Pick the best-looking image

Better-looking was not always safer.

AfterReference SKU → Define constraints → Generate batch → Quality gate → Ship / Edit / Regenerate

I separated creative variation from product constraints.

To make the workflow repeatable, I split every generation task into two layers. Creative variation could change. Product constraints could not.

Two-layer Framework
Creative Variation
Room typeLightingPropsCamera angleMoodComposition
Reference SKU
Product Constraints
Material toneSilhouetteLeg structureSeat proportionBackrest shapeScale
Only after separating creative choices from non-negotiable product facts did the workflow become controllable.

Templates made generation repeatable and reviewable.

Instead of treating every prompt as a one-off creative act, I organized recurring furniture scenarios into reusable templates. That made outputs comparable under the same intent instead of being judged as unrelated images.

Scene Template Matrix
DiningFamily meal / kitchen island
VanityCompact living
ReadingComfort / leisure
Home OfficeMulti-use furniture
CafeCommercial atmosphere
PatioOutdoor inspiration
Templates reduced random prompting and made scene outputs easier to compare, review, and reuse.

The real output was a quality gate.

The most important part of the workflow was not generation. It was the review logic after generation: whether an output could ship, needed manual editing, or should be rejected and regenerated.

Decision Logic, Not Visual Preference
Generated OutputSKU IdentityColor FidelityGeometry & ScaleScene RelevanceEditing Cost
ShipStable enough
EditFixable enough
RegenerateBroken enough
The quality gate made output review explicit enough to be reused across different image tasks.

Every batch needed a routing decision.

Once the quality gate was clear, the task became a controlled batch workflow: define constraints, generate candidates, evaluate risks, then route each output into the correct next step.

Output Routing Workflow
SKU Input
Scene Brief
Candidate Batch
Quality Gate
Routing Decision
Ship → Listing CandidateEdit → Manual RetouchRegenerate → New Batch
This is the difference between using AI as a tool and designing AI as a production workflow.

The project turned image generation into product judgment.

120+

AI furniture scene cases reviewed

50+

image tasks completed

3-5

iteration rounds per task

10+

templates and SOPs delivered

This became an early step from AI content execution toward AI product thinking. The hard part was not what the model could generate, but defining when the output was trustworthy enough to ship.

That same thinking later carried into broader AI product work: generation only becomes product capability when trust boundaries, review logic, and workflow decisions are explicit.

Next Project

Hermes · Personal AI Knowledge System