JAN Japan Release & Delay Checks — Beta
Pricing
Pay per usage
Reconcile JAN-coded order rows against official Good Smile Japan release schedules and delay notices. Returns dated evidence, repeat-delay history, manual change suggestions and unresolved review tasks. Beta; does not guarantee current schedules or overseas arrivals.
YYYY-MM-DD, inclusive publication date. When set, walk public older-notice links in both languages until before this date. This is separate from since, which filters returned events. Omit for a latest-index-only diagnostic run. Choose a date relevant to the watched orders; no fixed commercial lookback is assumed.
Operational budget, not a validated product coverage limit. If reached before the requested boundary, the result explicitly reports incomplete history and issues no safe cursor. Increase only after measuring cost.
Objects with unique clientItemId and JAN as a 13-digit string. Optional knownSchedule: {value: YYYY-MM or YYYY-MM-DD, kind: japan_release_month / japan_dispatch / japan_wholesaler_arrival / japan_release_day}. Optional distributor: goodsmile (default).
YYYY-MM-DD. Filters returned events only, does not prove archive coverage or detect all in-place edits. Pair with seenEventIds.
Suppress processed canonical event IDs or verified equal-fact aliases from monthly summaries. Aliases do not certify corrections or batch identity. This prototype does not issue a safe next cursor.
[]Public Good Smile /ja/news/NUMBER or /en/news/NUMBER URLs. Both language versions are checked. Supports verified month change, month advance, shipping-date change and named cancellation formats. Missing JAN stays unresolved in OUTPUT; explicit URLs do not prove complete history.
[]Optional YYYY-MM-DD, inclusive original announcement-section date. Enables the documented public Japanese support section as supplementary month-change history. May be earlier than historySince to add older month-change facts in bulk. It does not extend the verified linked range or certify older shipping changes/cancellations. Article edit timestamps are not event dates.
Operational page budget for the one public JA support section, 100 articles per page. Exhaustion, malformed article or unsafe pagination keeps this scope incomplete. Not a validated commercial limit.
Operational freshness allowance. 0 revalidates every checked source; expired entries use conditional HTTP when validators exist, otherwise a full GET. Required-source failures never fall back to stale bodies. Does not certify in-place edits, order batches or complete history.
Your own lowercase alphanumeric/hyphen name (1–63 chars), dedicated to this watch workflow. Reuse across sequential runs to retain identity bindings, source snapshots, pending change diagnostics and source cache. This is not a processed-order database. Concurrent runs using the same store are unsupported; the pre-write conflict check is not atomic. Omit to disable persistent state.
Explicitly acknowledge previously received sourceChanges IDs. Pending diagnostics remain visible until acknowledged, independently of since and seenEventIds. Acknowledgment is not proof that a schedule is valid or that a removed fact is a cancellation.
[]Requires stateStoreName. After inspecting sourceReviewFindings, submit [{changeId, reviewToken, decision: source_change_reviewed}]. Token must match facts checked this run. Closing a source-fact review does not acknowledge events, identify a cancellation, resolve batch/date conflicts or prove complete history. Changed/missing source facts reopen the review.
[]