Why Shouldn’t I Combine Claid’s Product Category Hint With a Selective Object-to-Keep Request?

Translate the merchandising requirement into a retained object

A tabletop photograph may contain a sale item, shipping packaging and props. The commercial requirement could be to keep the whole visible bundle or only one bottle. The word product does not resolve that distinction by itself. Ask the reviewer to name the intended retained object in ordinary language.

Keep that editorial choice separate from the technical request. A rejected combination of options does not demonstrate poor product photography or a weak generation prompt. It first indicates that the integration’s configuration needs to match the documented contract.

Choose one background-removal branch

The category branch supplies an object-category hint. The selective branch asks which object should remain, using a short, precise object description. The documentation makes these mutually exclusive. This does not mean that combining them creates a better foreground estimate.

Have the maintainer inspect the actual submitted options, including a category injected by a reusable default. Adding selective in a later screen is insufficient if the earlier category remains in the request. Do not describe a specific HTTP response or automatic fallback unless it has actually been observed.

Illustrative exercise: bottle, gift box and decoration

Illustrative exercise: a fictional photograph shows a bottle beside a gift box and a decorative leaf. Campaign A sells a bottle-only variant. Campaign B sells a gift set that includes approved packaging. No Claid request was executed for these examples.

For Campaign A, the team can evaluate a selective bottle instruction without retaining an incompatible category option. For Campaign B, it must first clarify what belongs to the sale set; copying the bottle-only instruction would discard required content. Do not invent support for an arbitrary multi-object description from this example.

The lesson is to resolve both the object scope and the mutually exclusive request branch. A technically accepted request could still select the wrong merchandise.

Keep configuration acceptance separate from cutout approval

Before scaling the workflow, inspect one actual result for missing sale components, retained props and altered edges. Record the branch and object description beside the source identity so another reviewer can reconstruct the intention.

If a result is wrong, decide whether the brief named the wrong object, the integration sent conflicting settings, or the output failed despite a correct request. Change the relevant layer instead of stacking more options. This is a source-based integration review plan, not a new background-removal feature inside Itemlume.

Illustrative exercise: retained-object and request-branch decision

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)