All 65 tools

Validate barcodes in bulk: check digits, GS1 prefixes, Excel corruption, restricted ranges and placeholder codes.

Complete a UPC, EAN or GTIN-14 from its first digits — with the step-by-step Mod-10 calculation shown.

Convert barcodes between UPC-A, EAN-13 and GTIN-14 case codes in bulk — validated first, check digits recalculated, CSV out.

Decode the string under a logistics barcode into its Application Identifiers — with the FNC1 separator rule that most parsers get wrong.

Check a Digital Link URI against the current standard — qualifier order, the new 14-digit GTIN rule, removed alphabetic names — and get the corrected URI back.

Verify a VIN check digit, decode its sections, and see every model year the year code could mean — the ambiguity most decoders hide.

Check an IMEI Luhn digit, complete a 14-digit one, and tell IMEI apart from IMEISV — the 16-digit form no checksum can validate.

Validate a shipping container number against ISO 6346 — including the letter values that skip multiples of 11, where hand-written code always goes wrong.

Generate print-ready EAN-13, UPC-A, EAN-8 and ITF-14 barcodes as SVG — with the check digit validated before anything is drawn.

Expand the short 8-digit barcode on small packages to its full UPC-A — with the zero-suppression rule shown, and EAN-8 told apart from UPC-E.

Convert ISBN-10 ⇄ ISBN-13 with both forms shown at once — correct mod-11 check character, and an honest answer for 979 ISBNs.

Validate GS1 logistics and location keys: 18-digit SSCC pallet codes and 13-digit GLNs, including the leading zero spreadsheets eat.

Check journal ISSNs (which have a check digit) and recording ISRCs (which have none), and convert between an ISSN and its 977 barcode.

Verify CAS Registry check digits and convert NDC drug codes to the 11-digit billing form — showing all three readings when the hyphens are missing.

See which parts of a product description HTML the marketplace will silently remove — and which unclosed tag is breaking the page around it.

Turn titles into URL slugs and Shopify handles — showing both romanisations where a name has two, and what the platform silently creates when handles collide.

Count backend keywords in bytes (not characters), see which words cost the most, and catch the waste that silently kills indexing.

Check a title against every marketplace's length limits and style rules, with the problems highlighted on the words themselves.

Check listing bullets for length, caps, HTML and off-platform contact details, and screen the copy for FDA/FTC claim language — with the reason each phrase is risky.

Find out whether an image is secretly CMYK — the one defect that looks completely normal until the marketplace rejects it.

See whether a product photo carries GPS coordinates, your name or a camera serial number — and strip them without re-encoding the image.

See the actual RGB of your image's background — the difference between 250 and 255 that your eye cannot catch but Amazon's scanner does.

Audit a whole batch of images and videos against every marketplace’s size, file size and format limits — as a matrix.

Convert dimensions and weights in bulk and see what rounding to the field precision actually costs — the factors are exact, the rounding is not.

Catch the ambiguous decimal separator that turns 19,99 into 1999 — plus ISO 4217 currency codes and their decimal places.

Work out watt hours correctly — the cell voltage, not the USB output — and see which passenger-carriage band a battery falls into.

Check an 11-digit air waybill number against its modulo-7 check digit — and learn why none of them ever ends in 7, 8 or 9.

Work out which carrier a tracking number belongs to — and verify its check digit where the algorithm is public, instead of guessing from the shape.

Compare dimensional weight across carrier divisors, and get the break-even box size at which volume stops setting the price.

Search the Hazardous Materials Table by product name or UN number, and see every entry sharing that number with its own limits.

Check whether a trade term is valid for how the goods actually travel — FOB on a container is the classic contract error.

Check a tariff code against every published heading and subheading - and see what each pair of digits means, and who decides it.

Catch Merchant Center disapprovals before you upload: required attributes, GTIN validity, identifier logic, price and enum formats.

Check a product CSV before importing — including the handle collisions that silently overwrite live products.

Find out which CSV dialect a file actually is — delimiter, quoting, line endings, BOM — detected by column consistency, not by counting commas.

Find out what a spreadsheet broke in your column — and whether each value can still be repaired or is gone for good.

Compare two feed exports aligned by SKU rather than by line — so reordered rows produce no false differences.

Check a product feed for Meta, TikTok, Walmart or Amazon — and catch the values that are correct on the platform you copied it from.

Convert a Google Shopping feed to a Meta catalog feed - translating the values that differ and leaving blank the two that have no equivalent.

Repair a damaged feed in one pass - mojibake, spreadsheet damage, invisible characters - and get a list of every cell it would not guess at.

Check Prop 65 warnings against the safe-harbour wording, allergen declarations against the nine major US allergens, and CE / UKCA / FCC claims for a verifiable reference.

Check fibre content against 16 CFR 303 — including the under-5% "other fiber" rule — and care wording against 16 CFR 423.

Validate Product structured data without publishing the page — including the barcode, the currency and the comma that turns 19,99 into nothing.

Compare a whole set of campaign URLs and find the values that differ only by case — the split that every single-URL checker misses.

Validate hreflang annotations and get back the identical block every page in the set must carry — starting with why en-UK does nothing.

See the share card your meta tags produce, and catch the two failures a browser never shows: name= instead of property=, and relative image URLs.

Render an email template with a full record and with the fields empty, and catch unclosed merge fields or two syntaxes pasted into one template.

Check a postcode column against each country’s usual format — separating a spacing problem from one that needs a real lookup.

Check and convert ISO 3166-1 country codes — and find the ones that look right but are not assigned, starting with UK.

Check IBAN check digits and per-country layout, and SWIFT/BIC structure — including test BICs, which look completely normal until a payment fails.

Check EU VAT numbers and EORI numbers against their published formats — including the GR-for-EL and GB-for-XI prefix traps.

Convert EU, UK and US shoe sizes from the unit definitions with the working shown — and see why apparel size charts are not trustworthy.

Repair text mangled by an encoding mix-up — by working out the actual encoding chain, not by matching a substitution table.

Find full-width punctuation and lookalike letters from another script — the characters that survive proofreading because they look right.

Show every reading of an ambiguous date, decode spreadsheet serial numbers, and check Merchant Center date ranges and time zones.

Find the zero-width spaces, BOM and look-alike characters hiding in your text — and see what each one is doing to your data.

Find which values in a column are the same thing — exact duplicates, spelling differences, and synonym sets like L and Large.

Check a UBL invoice against the published Peppol BIS Billing 3.0 rules - reported under their official identifiers so every finding can be looked up.

Compare the preferential origin declaration on your invoice against the wording EU law prescribes - word for word, in every prescribed language.

Pick the right one of the four prescribed supplier's declarations, and check a long-term validity period against the limit the annex actually states.

Tell UBL from CII, read the CustomizationID, and find out which profile an e-invoice declares - Peppol, XRechnung or the EN 16931 core - before you validate it.

Check a German XRechnung invoice against KoSIT's official BR-DE rules, in UBL or CII, reported under their official identifiers.

Find the missing and duplicated numbers in an invoice column - with independent series split apart, so two healthy sequences are not reported as gaps.

Check the structure and check digit of a Legal Entity Identifier - and see plainly what a passing check digit does not prove.

Check an ISO 11649 RF creditor reference - the structured payment reference on European invoices - including the mod-97 check digit IBAN uses.