Build checks that explain themselves.
Integration guidance for evidence, source freshness, identity matching and honest result boundaries.
Handling VIES MS_MAX_CONCURRENT_REQ in Django
Catch temporary VIES SOAP faults in Django, return a useful form error instead of a 500, and keep service outages separate from invalid VAT numbers.
02 · Developer guideCPSC Recall API Guide for Developers
How to use CPSC recall data in an application, what the official feed contains, and why production matching needs identifiers, timestamps and explicit no-match boundaries.
03 · Catalog matchingHow to Match a Product Catalog to CPSC Recalls
A practical hierarchy for matching UPC, brand, model and product text to CPSC recall notices without turning loose similarity into false certainty.
04 · Source coverageCPSC Recalls vs. Product Safety Warnings
Why CPSC recalls and Product Safety Warnings are separate source types, and why a product-screening workflow should monitor both.
05 · VAT developer guideVIES VAT Number Validation API Guide
How developers can validate EU VAT numbers through VIES, distinguish invalid results from service unavailability, and retain a time-stamped verification record.
06 · VAT evidenceHow to Store VIES VAT Validation Evidence
What to retain from a VIES VAT number check, why a current result needs a timestamp, and how to build an audit-friendly verification record without overclaiming.
07 · Import complianceCPSC eFiling Is Mandatory: What Changed on July 8, 2026
What the July 8, 2026 CPSC eFiling rule actually requires of importers, which seven certificate fields go to CBP, and why a cleared entry still needs separate recall screening.