GTIN Data Hub
Products

Don’t let your customer be the one who tells you the barcode is wrong.

A single wrong number brings the whole file back. GTIN Data Hub scans 10,000 numbers in one file, writes line by line why each one is invalid, and even tells you the digit it should have been. Try it without signing up — no card, no commitment.

How is a GTIN validated?purely mathematical
Spaces and hyphens are removed, then the length and GS1 Mod-10 check digit are validated. This does not prove that a product exists or belongs to a brand.

One digit. The whole file back.

It is the quietest field in your barcode list. You are usually not the one who notices it is wrong — the marketplace, the supplier or the customer is. All three cost you.

“Your file was rejected.”

They will not tell you which row. Because of one digit you comb through 10,000 rows by hand — and land in the same place the next day.

A product off the shelf sells nothing

A rejected item is not live. Your loss is not a few hours of fixing; until that item goes live it is a sale that never happened.

The wrong product ships

If the number in the supplier file belongs to another product, no system warns you. You find the mistake in the warehouse, in transit or at the returns desk — the three most expensive places.

Everyone says “invalid”. We tell you what is right.

The answer is not just valid: false : you also get the expected check digit, the format of the number and its GTIN-14 equivalent. That is the difference — one reports the problem, the other lets you fix it.

GTIN lookup

Validate the format and check digit of a single number instantly.

  • GTIN-8, GTIN-12 (UPC-A), GTIN-13 (EAN), and GTIN-14
  • The expected check digit when the input is wrong
  • GTIN-14 normalization and space/hyphen cleanup
  • Product data only from your catalogue or a licensed source

Batch validation

Paste a list or upload a CSV; up to 10,000 numbers per job, with the result downloadable as CSV.

  • The GTIN column in the CSV is found automatically, the header row is skipped
  • The result is persistent: it survives a service restart
  • Progress is live; the result is written in one go as the job finishes
  • Every row carries validity, format, expected check digit and the reason for failure

Your own catalogue

Upload your product name, brand, category and image link; they appear next to the number in every lookup.

  • CSV columns: gtin, urun_adi, marka, kategori, gorsel_url
  • If the same number is uploaded a second time it is overwritten
  • Image links are accepted over https only
  • Uploading a catalogue does not count against your quota

API and keys

Create keys in the panel, set their scope and lifetime yourself, and connect them straight to your systems.

  • Separate keys for production and test
  • No expiry, or 30/90/365 days
  • Only the SHA-256 digest of the key is stored; the raw value is shown once
  • Creating a key requires admin rights
How does batch validation work?CSV in, CSV out
The list is read, numbers are normalized, and each row’s format and check digit are validated; results download as CSV with error reasons.

The panel also has

Beyond lookups, for teams running the work together.

Team and invitations

Invite as many people as your plan allows. The invited person sets their own password; you never see it.

Query history

See the numbers you looked up earlier. Visible only to your organisation, kept for 90 days, deleted whenever you want.

Audit log

Sign-ins, key creation, catalogue uploads and admin actions are all recorded. Who, when, from which address.

We do not supply the product name and image. These fields come only come from the catalogue you upload. For a number that is not in your catalogue the screen says so plainly; no card is invented. For details see Data coverage.

4 GTIN formats

GTIN-8, GTIN-12, GTIN-13, and GTIN-14.

10,000 numbers

In one persistent batch job.

2 output formats

JSON and CSV for individual results.

Up to your first query

Four steps, five minutes.

  1. 1
    We open your account

    Leave an access request; we will set up your organisation and first user.

  2. 2
    You set your own password

    You receive a one-time link. Only you know the password.

  3. 3
    You create your key

    The API Keys screen in the panel. You choose the scope and the lifetime.

  4. 4
    You connect

    A single REST call: GET /api/v1/gtins/{gtin}.

The check digit shows the number is internally consistent; it does not prove the product exists.

A made-up but mathematically correct number also looks valid. The real evidence is the number having been observed in independent sources.

Limits

All of them depend on your plan; these are the defaults.

WhatDefaultNote
Batch job size10,000 numbers Per request. Larger lists are split.
Requests / minute120 Per key.
Items / minute20.000 Per organisation; batch jobs count here.
Items per monthdepends on the plan You can see what is left on the Usage screen in the panel.
Batch job result60 minutes It can be downloaded as CSV within that time.
A request is not an item. A batch job of 100 numbers is 1 request but 100 items. Billing is per item.