Three fields, three different jobs
A Joyagoo spreadsheet find can carry several strings that look like links or identifiers, but they answer different questions. A product ID helps determine whether two records point to the same underlying listing. A source link preserves the marketplace page and seller context. A destination URL records the page that the buyer actually reached through the current discovery route. Keeping them in separate columns prevents one field from being stretched into evidence it cannot provide.
None of the three proves that the product is available, correctly described, well made or suitable for a buyer. A valid-looking ID can belong to a removed listing. A source link can redirect. A destination page can display a cached preview or a different option structure from the spreadsheet row. The useful method is therefore not to choose one universal identifier. It is to select the field that solves the immediate problem, then confirm the commercial facts on the live page before payment.
Use the product ID to match records
A product ID is most useful when URLs contain tracking parameters, language paths or different wrappers. Extract the marketplace item token exactly as displayed rather than copying a number that merely appears in a campaign parameter. Compare the token from the spreadsheet, the final source page and the current destination. Agreement strengthens the identity match; disagreement is a stop signal that needs explanation.
The ID is not a permanent certificate. Sellers can remove products, replace pages or create a new listing for a similar item. Even when the token is unchanged, the available colors, sizes, quantity tiers and description can change. Record the marketplace or source type beside the ID because equal-looking number formats from different systems are not interchangeable. Use the ID for equality testing and reporting, not as a shortcut for quality, authenticity, inventory or seller reliability.
Use the source link to preserve seller context
The source link points to the original marketplace environment behind a find. It can preserve the seller or shop context, option selector, title, images, quantity rules and China-side delivery fields that matter before ordering. Save the cleanest reachable version and note the date. If the page requires a current session or cannot be opened directly, record that limitation rather than inventing missing details from the spreadsheet preview.
A source link is especially useful when a buyer needs to explain where a model number, color name or size chart came from. It lets the order note refer back to the exact page instead of a cropped image. But it remains third-party seller content. The link does not mean Joyagoo endorses the seller, and it does not guarantee that the destination parser will reproduce every field. Compare what the source says with what the active ordering page accepts.
Use the destination URL to reproduce the current route
The destination URL is the final page reached after the product route has resolved. It answers a practical question: where does this spreadsheet row send a buyer today? Save the post-redirect address rather than only the original click target. Then compare title meaning, main image, product type, source identity and option structure. A successful 200 response is not enough when the content has changed.
Destination URLs are best for reproducing a problem. If a row opens a different product, loses the intended option or lands on a generic page, the final address gives an editor or buyer a concrete starting point. Preserve the input link and final URL together so the redirect can be examined. Do not silently replace the destination with a similar listing while retaining the old product ID, thumbnail or checked date.
Strip noise without deleting evidence
Long URLs often contain referral codes, campaign parameters, language settings or session values. Create a clean comparison copy only after saving the original route. Remove parameters one at a time and confirm that the cleaned address still opens the same product and option context. Never remove a parameter that carries the actual item identity. If cleaning changes the page, keep the original and label the route as dependent on that value.
Use privacy judgment as well. Do not store account tokens, personal addresses or private session data in an editorial spreadsheet or public report. A safe record normally needs the marketplace name, product ID, source link, destination URL, exact option text and checked date. When a private account view is necessary for ordering, keep that evidence in the buyer's own record rather than copying it into a public product index.
Resolve redirects with an identity ledger
Record four values for every redirect check: input URL, final URL, response date and identity result. Classify the identity as matched, partial, mismatch or unavailable. Matched means the product family and stable token agree. Partial means the family looks related but the exact option or seller context cannot be reconciled. Mismatch means the final page is another item or generic landing page. Unavailable means the page cannot currently be evaluated.
This ledger keeps network status separate from product status. A dead link is obvious, but a live redirect to the wrong item is more dangerous because it can look successful to an automated checker. Human review should compare the destination's title, image, product type, seller context and option structure. If the evidence remains partial, do not promote the row as current. Place it in a review queue with the unresolved field named.
Choose the identifier by the question
Use the product ID when asking whether two rows represent the same listing. Use the source link when checking seller wording, images, size data or quantity rules. Use the destination URL when reproducing what a visitor reaches or diagnosing a redirect. Use the exact option text when the question concerns color, size, version or quantity. Use the order number only after an order exists; it identifies a transaction, not the public product page.
A useful worksheet makes that mapping explicit. Add columns named question, controlling field and supporting evidence. For example, 'same listing?' is controlled by source type plus product ID. 'Where does the row open?' is controlled by the final destination. 'Which blue option?' is controlled by live option text and the order summary. This stops a convenient field from becoming a false answer to a different question.
Build a compact identifier packet
Before shortlisting, save the spreadsheet row, source marketplace, product ID, clean source link, input destination, final destination, title snapshot, chosen option text and checked date. Add one line describing any redirect. If a manually entered or DIY order is required, keep the buyer-supplied fields in a separate note and follow the current official instructions rather than assuming the link parser supports the source.
Before payment, reopen the final page and compare the packet with the current order summary. Confirm product identity first, then color, size, version, quantity and any seller note. If the source page and destination disagree, pause and ask which page controls the order. Do not let a matching image override a conflicting ID or option label. The packet exists to expose contradictions before money or return windows become involved.
Report a stale or mismatched row precisely
A useful stale-link report states the spreadsheet page, row or category, input URL, final URL, source type, product ID expected, identity observed and date checked. Describe the mismatch without guessing why it happened. 'Expected jacket ID 123, final page shows shoes ID 456' is actionable. 'Bad link' is not. If only one option disappeared, name that option rather than declaring the whole listing dead.
Do not include login details, private order data or unsupported accusations about the seller. The report should help an editor reproduce the result and decide whether to update, suspend or remove the row. If a replacement listing is proposed, verify it as a new record with its own ID, source, options and date. A replacement is not a continuation simply because the thumbnail looks similar.
End with a decision, not a pile of links
The final outcome should be one of four actions: proceed, ask, suspend or remove. Proceed when the source identity, destination and required option agree. Ask when one named field remains unresolved but the route is otherwise consistent. Suspend when the page cannot be evaluated or redirects unpredictably. Remove when the destination clearly represents another product or no longer supports the row's purpose.
This decision system is deliberately narrower than a product recommendation. It does not rank quality, predict seller dispatch or promise warehouse results. It makes a Joyagoo spreadsheet record reproducible and order-ready by using each identifier for the job it can actually perform. Save the evidence with a date, repeat the check before payment, and treat every later change as a new verification event rather than proof that the earlier record was wrong.
