imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

A successful request does not prove the product feed is usable.

A product endpoint can respond successfully while returning stale, incomplete or commercially incorrect records. Test how the integration treats that evidence before allowing it to replace public catalog information. Use controlled products and an explicit rule for failures and withdrawals.

Four failures a successful response can hide
  1. Stale

    A new fetch carries old facts.

  2. Partial

    A portion of the export is missing.

  3. Empty

    No records without a verified range decision.

  4. Wrong identity

    A record could update the wrong product.

Validate the input before replacing published information.

The API returns HTTP200 and an empty list. Delete the catalog?

Not without an agreed meaning and evidence of a complete export. Apply the approved stop or withdrawal policy.

Separate fetch time from information freshness

Record the export timestamp, what each time field means and when the website fetched it. A new fetch can deliver old business data. Cache validation does not itself establish when a product owner reviewed a specification.

Fictional example: today's download contains values from an older export. The operator needs to recognize that difference and decide whether continued display is acceptable. Choose a freshness threshold for the information involved, rather than inventing one universal age limit for every catalog.

Exercise empty and interrupted imports

In an isolated test, omit a pagination page, reject a request or return an empty list. Agree in advance whether processing stops, the last approved version remains or particular information is hidden.

An empty export might represent a deliberate range change, a broken filter or lost access. Do not equate it with an instruction to delete the catalog. A genuine withdrawal needs to be distinguishable from incomplete fetching.

Test inputRiskThe expected rule must identify
Old but well-formed recordsOld facts acquire a new fetch dateFreshness assessment and owner
Interrupted paginationPart of the range disappearsEvidence that fetching completed
Unexpected empty exportValid products are removed togetherRequired stop or approval
Invalid or reused IDThe wrong product changesIdentity validation and exception handling
Intentional withdrawalA removed item stays publicExplicit source signal and correct public outcome

Check meaning after checking types

Try an article ID with leading zeroes, a changed pack unit and an unknown category. A number passing schema validation does not prove the correct unit or product. Business reference records are necessary to test meaning.

Rename an item without changing its stable identifier. Confirm the right record changes and document relationships remain intact. If editors own a local description, show that the integration preserves it under the agreed mapping.

Follow the same version to the public page

After a controlled import, follow reference items through publication. Compare source values, import version and visible fields. Include an unrelated product to detect a mapping change that affects too much.

The test record should capture input, observed result, owner and retest. Exercise the alert or exception list that reveals a stopped feed. This does not guarantee future source accuracy; it makes the operating limits and responsibilities visible.

Sources and further reading

Questions, answered

Must an empty export always stop processing?

That depends on the agreed source model. The integration must distinguish an empty response from an authorized withdrawal before changing the catalog.

Is a schema enough to check product quality?

No. It can validate structure and some formats. Correct product identity, units and business meaning need additional evidence.

IMBAHUB

Let’s plan your website

Prepare four controlled failure inputs and agree on their outcomes before running the sync.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.