Serial Trail Serial Trail | Help Center

Publish the public recall page

Publish a storefront check that tells a buyer whether a serial is affected without exposing the recall ledger.

Last updated: July 15, 2026

Contents
Show all sections (11) ▼

An active case can add an Is my unit affected? check to the signed storefront proxy. Buyers enter a case reference and serial; the result is deliberately narrower than the merchant ledger.

What you'll accomplish

  • Publish clear buyer instructions for one active recall.
  • Provide an affected, not-affected, or neutral result without exposing orders or customer data.
  • Give affected buyers an approved remedy link and contact route.

Requirements

  • The recall must be active.
  • Storefront Public Lookup must be available through the commerce integration.
  • Instructions, remedy text, remedy URL, and support contact must be approved.
  • The page is informational workflow support, not a regulatory filing or legal notice by itself.

Publish the page

  1. Open the active recall case.
  2. In Public recall check, enable Publish “Is my unit affected?” on the storefront.
  3. Enter concise public instructions. State what the buyer should stop doing and what action to take only when those directions are approved.
  4. Add a specific remedy button label and an HTTPS remedy URL when a remedy page exists.
  5. Select Save public page.
  6. Open the storefront serial-check URL with the case reference and test three synthetic states: affected, not affected, and unknown.

Recall notices can link to /apps/serial-check/recall?case=RC-… on the default Shopify app-proxy path. Shopify can customize an app-proxy prefix or subpath, so use the URL generated by Serial Trail rather than typing it from memory.

What buyers can see

The page can confirm that a submitted serial is affected and show the case headline, instructions, remedy, and merchant contact line. It does not expose affected-unit lists, order references, customer information, internal notes, selector definitions, or delivery history.

Unknown input receives a neutral response. The public endpoint does not reveal whether a nearby serial exists in the registry.

What success looks like

  • The active case reports that its public page is enabled.
  • The generated storefront URL opens in the active theme.
  • A known affected synthetic serial receives the affected guidance.
  • A known unaffected serial and an unknown value do not leak registry details.
  • Disabling the page makes the case unavailable without deleting its internal evidence.

Troubleshooting

The page is unavailable

Symptom: The storefront returns a neutral unavailable state.

Likely cause: The case is not active, public publishing is disabled, Public Lookup is unavailable, or the app-proxy permission needs reconnection.

Fix: Verify the case status and saved toggle, then reconnect the store if Settings shows a platform-permission warning.

Confirm: The generated URL renders the case instructions in the active theme.

A known serial does not match

Symptom: A serial from the internal ledger receives a neutral result.

Likely cause: The wrong case reference was used, the serial was entered differently, or the unit is no longer in the current affected set.

Fix: Copy the serial and case reference from the case detail, then check current membership.

Confirm: The public result agrees with the current case ledger.

Symptom: The page settings do not save.

Likely cause: The remedy URL is incomplete or not a valid web URL.

Fix: Use the final HTTPS destination and a concrete button label.

Confirm: The saved button opens the approved destination in a new browser session.

Keep the public page consistent with the regulator-approved or counsel-approved message. Serial Trail does not determine whether a product is unsafe, satisfy reporting deadlines, or replace the notices and channels required for a particular recall.