Skip to main content

Glossary

What is an asynchronous ingestion?

Asynchronous ingestion accepts product data first and processes it afterwards, so an accepted request is not yet a finished product.

In plain words: When a system ingests product data asynchronously, it answers 'received' straight away and does the work in the background. The sender then checks a status, or is told, when each product is finished, partly done or has failed. Acceptance and completion are 2 separate moments.

Published by Youzu · Editorial policy

Published

Why it matters

Treating an accepted request as a finished product is a common integration mistake. Storefronts then show records that are still being processed, and failures go unnoticed because no one looked at the status.

How it works

  1. Accept

    The receiver validates the request, stores the data and replies that it has been accepted.

  2. Process

    Background steps run on each product, and each product carries a status while they do.

  3. Read back

    The sender reads the status and the result, retrying or correcting products that failed.

Product states after acceptance
StateWhat it meansWhat the sender does
AcceptedThe data is stored and queuedWait and keep the identifier
ProcessingSteps are still runningDo not publish yet
FinishedAll steps are completeRead the result and use it
Partial or failedA step stopped or was rejectedCorrect the data and send it again

Examples

  • A jacket file, accepted

    A file with the 9 olive-jacket variants is accepted at once.

  • A matching step still running

    2 sofa listings are stored but not yet compared.

  • A re-sent offer

    A seller re-sends the armchair with a corrected width.

Common mistakes

  • Accepted means finished. A storefront publishes records the moment the request is accepted, before the steps behind it have run.

  • No plan for failure. Only the successful path is built, so a rejected product has no owner and no retry.

Catalog intelligence
The use of AI to turn raw product and listing data into structured, reviewed product records.
Product data enrichment
Adding missing information or improving existing information on a product record so products can be found, filtered and compared.
Product feed
A product feed is a structured file of product and offer data that a sales or shopping channel reads on a schedule.

In Youzu

Youzu helps marketplaces, classifieds and retailers turn raw seller and supplier product data into structured, reviewable catalog records.

Catalog Intelligence

Sources

  1. RFC 9110: HTTP Semantics, 15.3.3 202 Accepted, IETF. rfc-editor.org/rfc/rfc9110. Accessed .

  2. RFC 7240: Prefer Header for HTTP, respond-async, IETF. rfc-editor.org/rfc/rfc7240. Accessed .

FAQ

Questions buyers ask

No. Ingestion is asynchronous: an accepted request does not mean enrichment, indexing or deduplication has finished, and each product shows its processing status. Publish a product only once its status shows the steps you rely on have finished. Until then, keep it away from shoppers.

Read its processing status. Processed products, variants, offers, moderation state and processing status can be read back through the API with filters. Ready means the status shows that the steps you depend on have finished, and until it does the product is not ready to publish.

Changed products can be re-sent at any time; the same SKU identifies a later version of an offer. Send the corrected version, then read the status again before you rely on the new version, so that you never publish a half-processed record.

Last reviewed

Next step

Automate Commerce. Make shopping personal.

Bring your catalog, listing flow or shopping idea. Let's find the right place to start.

Book a demo

Tell us about your catalog and we will get back to you.